How Long Does 311 Take in Your Neighborhood?

This is the interactive companion to groundbreaking analysis of 311 wait times, the Geography of Waiting — the same underlying data, sliced along three axes you control. Pick a ward or ZIP, an agency or issue, and the table below tells you how long the city is actually taking to respond.

Notes, Sources, and Methodology

The 311 data is the same OpenDataPhilly public_cases_fc table that drives the rest of my 311 series — roughly 484,000 service requests from 2024 onward. ZIP-level median household income and neighborhood names come from the ACS 5-year estimates the rest of the 311 series uses.

Methodology details. I filter to closed tickets with a wait time between 0 and 365 days. Closed-only matters: bias-corrected survival estimates put the income-based gap at 17 days rather than the headline 2.6, so dropping open tickets understates inequity — but the underlying cache is structured that way. Medians are precomputed server-side because medians can't be reconstructed from per-group medians, so the table is shipped as a flat cube rather than computed in the browser. Wards are assigned via point-in-polygon against the CARTOpolitical_wards layer.

Limitations. Income and neighborhood are ZIP-only. ACS publishes median household income at the ZCTA level, but a ward isn't a Census geography — the population-weighted tract-to-ward aggregation that would attach income to a ward isn't in this build. Tickets with fewer than 10 occurrences under the current filter are hidden to keep the long tail from dominating the table.