City data freshness
Last ingest time measures a download; newest incident date measures source data recency. Review each separately, along with source cadence and availability. NYC publishes quarterly.
Last updated: 2026-11-04
Last ingest is the download time, not the incident date. A successful recent ingest can still contain old source data. Snapshot built 2026-11-03; check /v1/cities for current coverage.
New York City's configured source updates quarterly. Daily ingestion attempts do not make NYC source data daily. Incident times are city-local; ingest times include their time zone.
| City | Status | Last ingest time | Newest incident date | Source cadence | Source and scope |
|---|---|---|---|---|---|
| San Francisco, CA | Live | Unavailable | 2026-11-01 | daily | San Francisco portal ODC PDDL (public domain) Source rows keyed by row_id (incident_id fallback); not guaranteed unique events. Uses source latitude/longitude; precision is unspecified. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| New York City, NY | Stale source records | Unavailable | 2026-06-30 | quarterly | New York City portal NYC Admin Code 23-502(d): no restrictions on use; source identified Complaint-number records; source updates quarterly. Uses source latitude/longitude; precision is unspecified. Missing complaint time becomes midnight. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Seattle, WA | Live | Unavailable | 2026-11-01 | daily | Seattle portal Public Domain Offense-ID records, not deduplicated events. Uses source latitude/longitude; precision is unspecified. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Dallas, TX | Live | Unavailable | 2026-11-02 | daily | Dallas portal ODC-BY (attribution required) Service-number records (incident-number fallback). Uses geocoded_column coordinates; precision is unspecified. Missing time becomes midnight. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Cincinnati, OH | Live | Unavailable | 2026-10-26 | daily | Cincinnati portal Public Domain Report-number records classified from starscategory. Uses lat_x/lon_x coordinates; precision is unspecified. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Kansas City, MO | Live | Unavailable | 2026-10-26 | daily | Kansas City portal Public Domain Source has one row per person involved; adapter retains offense and place only, keyed by report plus IBRS code, so rows are not unique events. Uses source location coordinates; precision is unspecified. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Boston, MA | Live | Unavailable | 2026-10-28 | daily | Boston portal ODC PDDL (public domain) Records keyed by incident number plus offense code, not unique incidents. Uses source Lat/Long; precision is unspecified. Date labels say UTC but adapter retains local wall time. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Washington, DC | Live | Unavailable | 2026-11-01 | daily | Washington portal CC BY 4.0 (attribution required) Records keyed by CCN plus offense. Uses source LATITUDE/LONGITUDE; precision is unspecified. Yearly layers are discovered with last-known layers as fallback; start date falls back to report date. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Minneapolis, MN | Live | Unavailable | 2026-11-01 | daily | Minneapolis portal City of Minneapolis has waived all copyright and related or neighboring rights to Open Data (CC0 1.0), to the extent possible under law Records keyed by case number plus offense. Uses centerLat/centerLong; precision is unspecified. Missing begin time becomes midnight; yearly layers may fall back to last-known layers. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Milwaukee, WI | Live | Unavailable | 2026-10-31 | daily | Milwaukee portal CC BY (attribution required) One source row per case with one or more NIBRS codes mapped to one category; any sexual code makes the case a sexual offense. Uses Address_Latitude/Address_Longitude; precision is unspecified. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Denver, CO | Unavailable — ingesting / awaiting source data | Unavailable | Unavailable | daily | Denver portal CC BY 3.0 (attribution required) One source row per offense; source addresses are hundred-block. Uses GEO_LAT/GEO_LON; coordinate precision is unspecified. Adapter retains local wall clock despite UTC labels. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
| Baltimore, MD | Unavailable — ingesting / awaiting source data | Unavailable | Unavailable | weekly | Baltimore portal Open licence by city ordinance, commercial use allowed (Baltimore City Code 9-8) One source row per offense and victim; adapter keys by CCNumber plus CrimeCode, so these are not unique events. Victim fields and street address are not requested. Uses source Latitude/Longitude; precision is unspecified. Rows with missing, zero or invalid coordinates or missing dates are dropped; source offenses map to shared categories. Completeness is unknown. |
Unavailable data does not mean zero crime. Stale means the newest record is older than the source cadence plus 14 days; source publication and reporting delays vary.
What should I know about this data?
Where does the incident data come from?
Incident data comes from city open-data portals under the licence shown for each city. It is police-reported data, not convictions, and sources can revise it.
Where can I check coverage and freshness?
The city coverage pages and GET /v1/cities identify covered cities, source licences and newest record dates.
Do scores predict personal risk?
No. Scores describe incident density within a city, are not comparable across cities and do not predict personal risk.
Where can I find related information?
Crime API reference · Incident density methodology · MCP setup for AI agents