dataset · Philadelphia Fire Department · ArcGIS

Philadelphia Fire Department incidents

Every PFD dispatch since 2024-01-01 — false alarms, EMS assists, hazmat conditions, and the ~14% that are actual fires. Queried directly against the city's stat360_fire_incidents ArcGIS Feature Service through our Cloudflare worker proxy.

data through 2026-01-31 · 128,491 rows

About this dataset

The Philadelphia Fire Department's quarterly-updated dispatch log, hosted by the city as an ArcGIS Feature Service. Each row is one PFD response — false alarm, EMS assist, hazmat condition, structure fire, vehicle fire — with timestamps, geocoded latitude/longitude, NFIRS-coded incident type, and property-use category. Only ~14% of dispatches are actual fires; false-alarm and good-intent calls together account for over 65%.

Source

  • Catalog page: data-phl.opendata.arcgis.com
  • Endpoint: https://services.arcgis.com/fLeGjb7u4uXqeF9q/arcgis/rest/services/stat360_fire_incidents/FeatureServer/0
  • Layer: stat360_fire_incidents · layer 0 (128,491 rows)

How we query it

All requests go through our Cloudflare Worker proxy at /api/arcgis. The proxy embeds the upstream ArcGIS URL as a single query parameter, hashes it into a KV cache key, and serves repeats from KV (TTL: 24h for layer info and count-only queries, 1h for outStatistics aggregates, 5min for raw rows). On a fresh deploy or a cache miss the proxy forwards to ArcGIS and writes the response back. ArcGIS REST is public — no API key required.

Unlike the Carto-backed datasets, ArcGIS has no SQL endpoint, so this dataset doesn't ship a Playground tab — the ArcGisAdapter advertises supportsRawQuery: false. A Views tab with a structured filter builder will land in a follow-up.

Caveats

  • NFIRS coding. Categories like "1 - Fire" follow the National Fire Incident Reporting System's two-tier coding. The leading number is the high-level category; we strip it for display in chart labels but keep the raw form in the underlying-data table.
  • Standard change in 2026. PFD switched to the new NERIS reporting standard for calendar year 2026; a parallel layer stat360_neris_fire_incidents uses different category names. This dataset stays on the pre-NERIS schema until backfilled.
  • Quarterly cadence. The layer publishes quarterly, not realtime. Recent incidents may be missing for up to ~90 days.
  • Address vs. location. Geocoded latitude/longitude is the dispatch address, not necessarily where the incident originated.

Citation

City of Philadelphia / Philadelphia Fire Department (2026). stat360_fire_incidents. Retrieved 2026-01-31 via data-phl.opendata.arcgis.com.