NYPD Crash Data Now Easier to Use and Updated Daily

No need to reformat NYPD's monthly reports anymore. Now, crashes, fatalities and injuries can be easily mapped and sorted. And it's updated daily. Image: NYC Crashmapper
No need to reformat NYPD’s monthly reports anymore. Now, crashes, fatalities and injuries can be easily mapped and sorted. And it’s updated daily. Image: NYC Crashmapper

The city went live with a major upgrade to NYPD’s crash data today. Information about traffic crashes was previously released via difficult-to-use monthly updates posted on the police department’s website. Now it’s available through a standardized feed updated daily on the city’s open data portal, allowing the public to sort crashes by time of day, street, zip code, and borough, as well as by the number of injuries and fatalities.

Later today EDC will be launching the BigApps competition, and Mayor de Blasio has asked NYC’s tech community to take on the issue of street safety. With this NYPD data upgrade, developers will have more flexibility to build useful tools for the public. A community board, for example, could receive an alert within 24 hours whenever there is a traffic injury or fatality within its borders.

“Up until now, New Yorkers haven’t had the opportunity to easily assess the relative safety of their street, the route their child walks to school, or their neighborhood at large,” said Transportation Alternatives Executive Director Paul Steely White in a city press release. “The Mayor’s announcement represents an important step forward to present crash data in a timely fashion that New Yorkers can view, understand and use, so that we can all make our city safer.”

“On first pass, this looks fantastic,” said John Krauss, who developed a map of crashes using the old data set. “This is amazing, and more than I was expecting.”

By opening the source data to the public, the city has essentially leapfrogged a City Council bill that would require NYPD to map its crash data. But despite the improvements, there are some remaining questions. The updated data goes back to July 2012, but NYPD has been publishing crash information since August 2011. The updated data adds geographic coordinates, making it easier to map the information, but they are tied to the nearest intersection, not the actual location of the crash. (NYPD has said it will work with the DMV to update crash forms to allow for more precise location data.)

Many in the civic tech community are also hoping for more than just improved crash data. While NYPD already reports how many tickets it issues for moving violations, there are significant limitations to that information.

“The summons data is just on the precinct level, which is not that great,” said Akil Harris, a web developer who used what he described as “just a PDF full of numbers” to create interactive maps of summonses issued by precinct. “I would like to see the data that’s there be more granular…[to show] exactly where the stop was made.”

Data on moving violations remains stuck in the old format and can only be mapped by precinct. Map: NYC Moving Violations
The city announced better crash data today, but information on moving violations remains stuck in the old format and can only be mapped by precinct. Map: NYC Moving Violations

This type of information could be useful to see if NYPD’s traffic enforcement efforts are happening in the same places that have the most crashes, Harris said. (The department said it will step up enforcement along arterial slow zones, but there is no way for the public to track NYPD’s progress on this promise.)

Precincts often cite this type of geographically detailed information on moving violations to report their enforcement efforts at public meetings. Today’s announcement didn’t include any news about opening up this data to the public.

  • The People of New York City

    Dear Ray Kelly:

    You can take your pathetic, cynical, lazy, once-per-month crash report PDF documents and stick them up your…

    Sincerely,
    The People of New York City.

  • Make Queens Safer

    Geocoded data is great for many purposes, but zones are helpful for tracking trends over time (e.g. http://makequeenssafer.org/home/2014/05/vz-2014-03/). It also helps with analysis when GIS isn’t available. It would be great if NYPD could tag its new data feed by precinct.

  • mistermarkdavis

    The old data, which is still available had precinct data in it. the city has a shape file of all the precincts on nyc open data that could be used to assign each collision to a precinct.

  • millerstephen

    There’s a problem with that, though: Let’s say a crash occurs on a street that forms the border between two precincts. Which precinct is it assigned to? The shapefiles likely won’t help there. NYPD knows which precinct has jurisdiction, but it’s not obvious to the public.

  • J

    Indeed. A precinct can increase the # of speeding tickets it issues fivefold, but if all those tickets are given out on limited-access highways, there will be zero improvement to pedestrian safety.

  • Joe R.

    Yes, exactly. What you said really makes the case for increasing the NYC speed limit on limited access highways to the 95th percentile. That will in effect severely limit the number of tickets police can give on highways, forcing them to concentrate instead on local streets in order to meet their (supposedly nonexistent) ticket quota. Giving speeding tickets on highways with artificially low legislated speed limits does nothing for safety, even for motorist safety. The local streets are where the bulk of speed enforcement, indeed traffic enforcement in general, needs to be.

  • sbauman

    One problem with the new NYPD daily crash data format is that vehicle type has been removed from the csv file.

  • ThunderMaps

    We’ve put together a geo-targeted alert service (http://goo.gl/31anp1) similar to the Portland 911 callout service used by Neighborhood Watch groups in Portland – explained here: http://learn.thundermaps.com/neighborhood-watch-911-alerts-portland/

    The quality and reliability of this NYPD crash data is questionable
    by comparison to Portland Police data. A shame, as real-time or at least standardized update periods would increase the value of this data set immeasurably from the point of view of citizens.

    Is there someone we can contact in order to request an improvement
    to this NYPD data? It’s nearly useful.

ALSO ON STREETSBLOG

DOT Unveils Interactive Vision Zero Map, But NYPD Data Still Incomplete

|
As the Transportation Alternatives Vision Zero for Cities Symposium got underway in Downtown Brooklyn this morning, DOT released an interactive map of traffic crashes, street safety projects and more. One piece that’s still missing, though: NYPD enforcement data. “Vision Zero View” maps injury and fatal crashes based on the latest available data, updated monthly, and […]

CrashStat Upgrade Provides Interactive, Up-To-Date Street Safety Data

|
Transportation Alternatives launched an updated version of its CrashStat website today, providing a wealth of new data about street safety in New York City and where pedestrians and cyclists are most at risk. The upgrade adds four years of geo-coded data about traffic injuries and fatalities, a smoother interface, and a wealth of interactive features. […]

New Map Presents NYPD Crash Data as It Was Meant to Be Seen

|
There is a new mapping tool that presents NYPD crash data in a way that will be useful to advocates, electeds, and citizens who want to improve safety on neighborhood streets. A bit of background. For years, NYPD guarded traffic crash data like a state secret. After the City Council forced the department to make […]

NYPD: Public Too Stupid to Understand a Citywide Crash Map

|
This morning’s City Council transportation committee hearing covered a number of bills, including one that would require NYPD to release data to the Department of Information Technology and Telecommunications for a public map of crash locations and traffic fatalities, to be updated monthly. NYPD testified in opposition to the bill, claiming that it was already […]