Chicago police reports — 2025-05

The 2025-05 report-date window

The 19,790 figure is every indexed CPD incident with a report date in 2025-05, across IUCR primary types. A theft row and a homicide row each count as one. The month page is a time filter on the Chicago extract, not a new offense taxonomy. Late-spring calendars, Memorial Day weekend, and school-year events are not packet subtotals; this page will not attribute 19,790 to any of them.

Report date is the field that defines membership in 2025-05. Occurrence date, when CPD filled it, can sit outside the month even if the report was taken inside it, or the reverse. This narrative does not invent a split between those two columns because that split is not in the packet facts. Read the table headers on the overlay.

CAD calls that never became incident rows sit outside 19,790. Unreported events never enter the extract. Cite 19,790 as the current indexed count for Chicago report dates in 2025-05, not as a closed yearbook cell.

Researchers pulling Chicago for 2025-05 should treat 19,790 as a report-date membership count on the CPD Socrata extract, then say so in the caption. Late-spring school calendars and Memorial Day weekend are visible on a civil calendar; they are not columns in this packet. If you need a weekend window, filter the overlay by date and stop quoting 19,790 as that weekend. LocalCrimeVault does not reclassify IUCR primary types inside the May mix. Counts are reports, not convictions, and OEMC CAD volume is a different system.

City-wide geography on a May slice

Official community area names appear on rows when CPD published them. The 19,790 headline belongs to Chicago as a whole. Summing a few areas from the table will not equal 19,790 if some rows lack geography or if you already filtered the overlay.

Block-level locations are coarse by design. They are not street-number addresses of victims or accused persons. Treat the map as public-record geography, not a household list and not a named-venue indictment.

Festival corridors and lakefront pins, if they appear denser in the table, are report locations. They are not a packet fact about event crime. Filter by community area on the overlay if you need one official area.

On the 2025-05 overlay, official community area names are the geography this Chicago index supports when CPD published them. The 19,790 headline is not Austin, not Near North Side, and not any other single official area. Researchers who need one area should filter the table and caption the subset as a subset. Block-level coordinates, when present, are offset public-record locations. They do not identify a resident, a school, or a storefront by street number. CPD incident rows can lack an area; those rows still sit inside 19,790. LocalCrimeVault does not impute a community area to complete a pin map. Festival-corridor or lakefront density, if you observe it after sorting, is a table observation about report locations, not a packet fact about event crime. Keep 19,790 attached to Chicago as a whole for 2025-05.

How to read the 2025-05 table

Sort 19,790 rows by date, IUCR primary type, or community area. Arrest flags are not convictions. Missing coordinates stay blank. LocalCrimeVault does not impute a community area to complete a pin map.

Later harvests can add late-submitted reports or drop rows CPD has updated. The factual claim on this page is the extract LocalCrimeVault currently holds for report dates in 2025-05.

The 2025-05 table is the working surface for these 19,790 rows. Sort by date, by IUCR primary type, or by geography. An arrest field, if shown, is still an attribute of a CPD report. It is not a charging decision and not a guilty finding. Unfounded or later-reclassified rows can remain until the source extract changes. Missing coordinates stay missing. OEMC CAD calls that never became incident numbers sit outside the total. Unreported events never enter 19,790. Sealed or restricted records that CPD does not publish never enter 19,790. If a type filter reduces the table, the caption should say the slice is no longer the city-wide 2025-05 headline. LocalCrimeVault does not reclassify charges inside the 19,790 mix.

What 19,790 leaves out

The total is not a conviction count, not a unique-offender count, and not a 911-call count. OEMC calls and CPD incidents are different systems. Unfounded reports may remain until the source row changes. Court outcomes live elsewhere.

This page does not compare 2025-05 to any other month. Those other counts are not in this packet. The claim is 19,790 Chicago reports with report dates in 2025-05.

Using the overlay and the Chicago hub

The 2025-05 overlay is the live table for these 19,790 rows. The Chicago hub holds type and community-area views that are not limited to this month. Use the hub when you need a window other than 2025-05, or a single IUCR type across many months.

The 19,790 mix is unfiltered IUCR. Type hubs exist for a single primary type across time. The month page is the date filter. Do not read 19,790 as one crime category.

How to cite the 2025-05 harvest

Citation form: "19,790 Chicago Police Department incidents with a report date in 2025-05, indexed on LocalCrimeVault from city open data." Add that counts are reports, not convictions, and that report date can differ from occurrence date.

CPD and the City of Chicago publish the incident extract. LocalCrimeVault indexes monthly slices by report date. Later extracts can move. LocalCrimeVault does not reclassify charges inside the May mix.

A durable citation for this page names the agency, the date field, the month, the integer, and the indexer: 2025 CPD incidents with a report date in 2025-05, indexed on LocalCrimeVault from city open data. Add that counts are reports, not convictions, and that report date can differ from occurrence date. If you filtered the overlay to one type or one community area, say so; that subset is no longer 2025. Later harvests can move the integer as CPD adds late-submitted rows or revises old ones. Do not mix this 2025-05 total with another month's count on a chart unless that other integer is actually in hand from its own packet. This file's facts support 19,790 only.

Questions

How many Chicago CPD incidents are indexed for 2025-05?

LocalCrimeVault currently indexes 19,790 incidents with a report date in 2025-05. The source is Chicago Police Department open data on the city portal. The figure counts police reports across IUCR primary types, not convictions. LocalCrimeVault does not reclassify CPD charges.

Does 2025-05 include a Memorial Day or festival subtotal?

No. The packet facts give one month total, 19,790. Event days, if they produced reports, sit inside that count when the report date falls in 2025-05. Filter the table by date. This page does not publish a holiday or festival subtotal.

Is 19,790 a community-area total?

No. It is city-wide. Community area names on rows are official city geography when CPD published them. Some rows lack an area. Use table filters for a single area. Block-level pins are not household identifications. 19,790 is city-wide for Chicago. Official community area names appear when the source published them. Some rows lack geography. Filter the overlay for a single official community area; do not treat the headline as that area's volume. Block-level pins are not household identifications.

Does a 2025-05 incident mean a conviction?

No. Public incident rows are reports. The 19,790 count is monthly report volume from CPD, not court outcomes. LocalCrimeVault indexes incidents by report date and does not reclassify charges. Public incident rows for Chicago in 2025-05 are Chicago Police Department reports across IUCR primary types. An arrest field is not a court finding. LocalCrimeVault indexes by report date and does not treat 19,790 as a guilty-finding total. Court outcomes live in a different system.