Chicago police reports — 2025-04

April as a report-date filter, not a story

Membership in 2025-04 is a date field, not a narrative about spring weather or school calendars. The 18,716 rows are CPD incidents whose report date falls in that month, every primary type included. This page will not invent an Easter, spring-break, or tax-deadline subtotal. Those events, if they produced reports, sit inside 18,716 only when the report date is in April.

IUCR primary types on the overlay are CPD's labels. Filter the table if you need one type. The month page does not recode charges and does not rank types, because type counts are not in this packet.

Report date can differ from occurrence date. An event that happened in March can be reported in April; an April occurrence can be reported later. This packet has one integer: 18,716 indexed reports with April report dates.

Anyone citing Chicago for 2025-04 should keep 18,716 glued to report date, not to occurrence date, and not to a spring-break story. Easter and tax-week civic calendars can produce reports; this packet does not isolate them. Filter the overlay if you need a narrower April window. Official community area names on rows are the city's list when CPD filled the field. The 18,716 headline is still city-wide. LocalCrimeVault does not impute blank areas or rewrite charges.

Where the 18,716 rows sit on the map

Chicago community area names on the table are the official city list when CPD filled that field. The headline 18,716 is not one area. Blank geography stays blank. LocalCrimeVault does not guess an area from a nearby pin.

Block-level coordinates, when present, are offset public-record locations. They do not identify a resident, a business, or a school by street number. Do not treat a cluster of April pins as a named-place indictment.

If downtown or lakefront rows look dense after you sort the overlay, that is a table observation. It is not a packet fact about Loop crime. Stay with 18,716 as the city-wide April total.

On the 2025-04 overlay, official community area names are the geography this Chicago index supports when CPD published them. The 18,716 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 18,716. 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 18,716 attached to Chicago as a whole for 2025-04.

Working the April overlay

Sort by date, type, or community area. Arrest flags, if shown, are still report attributes. They are not guilty findings. Duplicate or unfounded rows can remain until CPD updates the source extract.

Later harvests can move 18,716. Cite the figure as the indexed count LocalCrimeVault holds for 2025-04 report dates, with the reports-not-convictions clause on the same line.

The 2025-04 table is the working surface for these 18,716 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 18,716. Sealed or restricted records that CPD does not publish never enter 18,716. If a type filter reduces the table, the caption should say the slice is no longer the city-wide 2025-04 headline. LocalCrimeVault does not reclassify charges inside the 18,716 mix.

Boundaries of the April extract

Eighteen thousand seven hundred sixteen is not OEMC call volume, not a unique-person count, and not a prosecutor file. Unreported events are outside the total. Sealed or restricted records that CPD does not publish never enter the 18,716.

This page does not compare April 2025 to March or May. Those integers are not in this packet. Cross-month charts belong on pages that actually carry those facts.

Chicago hub versus the 2025-04 slice

The overlay at the 2025-04 path is the live table for these 18,716 rows. The Chicago hub is the parent city view: other months, type pages, and community-area pages. Use the hub when April is the wrong window.

Type pages split IUCR labels across time. They are not a substitute for this month filter. Keep 18,716 attached to 2025-04 when you quote the April harvest.

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-04, 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-04 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 18,716 only.

Documenting the 2025-04 harvest for Chicago

Chicago 2025-04 remains 2025 indexed CPD incidents with report dates in 2025-04 in this harvest. The overlay is the live table. The city hub is the parent view for other months and for type or geography pages that are not limited to 2025-04. Keep the reports-not-convictions clause next to 2025. LocalCrimeVault does not dramatize individual cases and does not turn 2025 into a ranking of neighborhoods, boroughs, or divisions.

Open data lags live dispatch. 2025 is the published extract LocalCrimeVault indexed for 2025-04, not a live CAD feed and not a promise that a portal query tomorrow returns the same integer. Record the month label 2025-04 next to 2025 if you republish the figure so a later snapshot is not silently mixed into the same sentence.

Questions

How many Chicago police reports are indexed for April 2025?

LocalCrimeVault currently indexes 18,716 CPD incidents with a report date in 2025-04. The feed is Chicago Police Department open data. The count covers all IUCR primary types in that month window. It is a report total, not a conviction total.

Can I get an Easter or spring-break count from this page?

No. Packet facts supply one number: 18,716. Holiday and school-calendar days are not broken out. If those days produced reports, they are inside 18,716 when the report date falls in 2025-04. Use a date filter on the overlay for a narrower window.

Does 18,716 belong to one neighborhood?

No. It is a Chicago city-wide monthly total. Official community area names appear when CPD published them. Some rows have no area. Filter the table for a single area; do not treat the headline as that area's count. 18,716 is city-wide. Filter the overlay for one official community area. Pins are not household identifications.

Are April 2025 incident rows court outcomes?

No. They are police reports. Arrest flags are not convictions. LocalCrimeVault indexes CPD incidents by report date and does not reclassify charges. Court files live in a different system. Public incident rows for Chicago in 2025-04 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 18,716 as a guilty-finding total. Court outcomes live in a different system.