NYC Data at Work: 2018 Open Data for All Report
  • Introduction
  • NYC Data at Work: Cases
    • Data in the Public Right of Way
    • How Data Helps Coordinate Street Closures for Community Events
    • The Geospatial Data Backbone of NYC Emergency Services
    • What Taxi Trip Data Tells Us About Mobility and Driver Welfare
    • Digital Transformation Offers Insight Into Our Vertical City
    • Multiple Datasets Come Together to Shed Light on Urban Problems
    • Open Data Opens Doors
Powered by GitBook
On this page
  1. NYC Data at Work: Cases

Multiple Datasets Come Together to Shed Light on Urban Problems

PreviousDigital Transformation Offers Insight Into Our Vertical CityNextOpen Data Opens Doors

Last updated 6 years ago

Combining public datasets can reveal trends and help decision-makers optimize City resources.

Agency

Dataset

A row is

Link

DCP

Property Land Use Tax Lot Output

A tax lot

311

311 Service Requests

A 311 complaint routed to an agency

This is the story of two different datasets. The first set comprises information about who owns what, and where property data today serves as the digital backbone to many municipal operations. In New York City, the Information Technology Division at the Department of City Planning compiles information on tax lots from several City agencies in the

The second set comprises 311 data. When a New Yorker dials 311, they want an answer to a question or a solution to a problem; the service is powered by digital infrastructure, artificial intelligence applications, and reams of data. Most 311 inquiries are informational, but one in ten calls, texts, and application-based messages to 311 trigger a request to City agencies for services ranging from restoring heat and hot water to filling a pothole. Each record is tracked digitally, coming together to form the roughly three million annual service requests in .

So what do 311 and PLUTO have in common? While each open dataset is collected in different ways and serves different purposes, together they can be analyzed to tell the story of who, what, where, when, and why of urban issues.

Data scientists at MODA have seen this firsthand. In one project, MODA built a statistical model to help the Department of Buildings and the Fire Department prioritize how to allocate 200 inspectors to investigate complaints of illegally converted dwellings. Using PLUTO and 311 data alongside, MODA found that homes with histories of tax delinquency, mortgage liens, and buildings violations reported through 311 are the most likely to contain illegal conversions. Based on this discovery, MODA developed a model to send inspectors to the riskiest places first.

In another project with the NYC Tenant Harassment Prevention Task Force, MODA helped focus enforcement resources by testing whether potential signs of tenant harassment—including 311 complaints about dust from illegal construction and dirty conditions such as mold or standing water—could predict a building’s risk of losing rent stabilized units. Properties that displayed those conditions were nominated to inspectors for a closer look. Like the open datasets that power them, the methodology and results of these analyses are made public on MODA’s and GitHub account.

Analyzing incident-level data (like 311 service requests) alongside locational data (such as PLUTO data on a property’s physical conditions, or Census data on neighborhood characteristics) starts to piece together a more holistic picture of city problems than each data source on its own.

Primary Land Use Tax Lot Output dataset, called “PLUTO."
the 311 Service Request dataset
fire incident data
open source analytics library
xuk2-nczf
erm2-nwe9