Live from NYC Open Data · 311

A day on the 311 line

Pick any New York City police precinct and any day, and this pulls every non-emergency 311 service request from that neighborhood that day — noise, parking, heat, potholes, rats — from the city's own records, and rebuilds the map, the timeline and the resolution breakdown. The third of a trio, alongside the police and fire versions.

🚓 Police 911 version → 🚑 Fire & medical version →
311 is near-real-time. Source: 311 Service Requests, NYC Open Data (erm2-nwe9), clipped to the precinct boundary.
The day, block by block

Where the requests came from

Each dot is one 311 request, at the location it was reported and colored by what kind of complaint it was. Press play to sweep through the 24 hours, tap the chips to isolate a complaint type, and click any dot for the details.

Nothing matches these filters

All day—
In “Live flow” mode, dots brighten as their request comes in and fade over the following 40 minutes. Clicking an hour below filters the map to that hour.
The day as it happened

Play the request log

The same day as a readable log: press play to stream every 311 request in the order it came in, with the handling agency and how long it took to close.

00:00press play
Speed
Press play to start the day at midnight, or drag the slider to any hour…
The rhythm of the day

When the requests came in

311 requests by hour of the day. Click any bar to pin the map to that hour.

What people reported

The complaint mix

Every distinct 311 complaint type that day, grouped into families. Click a family to isolate it on the map.

Who handles it

Which agency the city routed it to

311 is one phone number for the whole city; behind it, each request is routed to the agency responsible. Acronyms are spelled out.

By agency

Median time to close, by agency

Methodology

How this works — and its limits

Source & method

  • Data: 311 Service Requests, NYC Open Data (erm2-nwe9). Queried live in your browser for the date you pick.
  • Clipped to the precinct: 311 records carry no police-precinct field, so each request is clipped to the precinct's official boundary (y76i-bdw7) by point-in-polygon — a request counts if its coordinates fall inside this precinct. This matches how the police page defines a precinct.
  • Near-real-time: 311 updates continuously (unlike the six-month-lagged police feed), so you can pick recent days here that have no police counterpart.

Definitions & caveats

  • “Time to close” = created to closed timestamp. This is resolution, not emergency response — it can be minutes (a police-handled noise call marked closed on scene) or days (a housing-code repair). Agencies close requests very differently, so compare within an agency, not across.
  • Agency codes are the city's; the plain-language name is shown next to each. A few rare codes appear as their raw abbreviation.
  • “Families” are this tool's grouping of hundreds of raw complaint types; the raw type is always shown in the request log and dot popups.
  • Requests, not incidents. One situation can generate several 311 requests, and a request reflects what a resident reported — not a verified condition.

Made with AI assistance

  • Verified: every figure is computed in your browser from the raw 311 records returned for your selection — nothing is estimated or cached.
  • Verified: agency full names were taken from the city's own agency list, not invented; map points use the city's own coordinates.
  • Not independently verified: the accuracy of the underlying 311 records, including how each request was categorized, routed and closed.
  • Judgment calls: the complaint “families” grouping is editorial. A single day is a snapshot, not a typical pattern.