Brighton Park police reports in Chicago

The Brighton Park total is a published-report tally

3,553 is the number of CPD incident records in this index that carry Brighton Park’s community-area assignment. It is not an estimate, a survey, or a newsroom count of major crimes. If CPD’s extract includes a row for the area, it is in the 3,553. If a row was never published or was assigned elsewhere, it is not. LocalCrimeVault does not score seriousness and does not drop rows that look minor.

That mechanical rule is useful and limited. It is useful because anyone can return to the same open-data source. It is limited because publication rules, geocoding, and later edits all shape the total. Cite 3,553 as an indexed CPD report count for Brighton Park, then send readers to the incident table if they need the row text. The table is not a different dataset; it is the 3,553 taken apart.

Brighton Park versus the 410,083-report city file

Citywide, the index holds 410,083 reports. Brighton Park’s 3,553 rows are about 0.87 percent of that file, or about one in 115 published incidents. A share under one percent still represents thousands of records. It also means more than 99 percent of the indexed file sits in other community areas. Both statements are just arithmetic on the same extract.

Comparisons across areas should stay on this same file. Mixing Brighton Park’s 3,553 with a different agency, a different year extract, or a UCR summary from another publisher will not match. The Chicago crime hub is the parent for this particular 410,083-row index. If a chart needs a denominator, 410,083 is the one that belongs with 3,553. This packet has no population figure, so a rate per resident is out of scope.

Using the Brighton Park table without over-reading it

Each table row is a CPD record. Location fields show how the department stored the place, which may be a block, an intersection, or a coarser description. Time fields show when the report was associated with the event in the extract, which is not always the moment a resident would remember. Offense text is CPD’s code or description, not a verdict. Identifiers in the source beat homemade address cleanup if you are joining files.

Sorting by date or by type can surface clusters. Clusters in a table are still clusters of reports. They may reflect where people call the police, where officers work, or where geocoding piles points. They are not, on their own, a map of guilt. Filters change the view. They do not rewrite the indexed 3,553 unless the extract itself is rebuilt.

CPD Socrata data and the conviction gap

Chicago’s open-data portal is the source. LocalCrimeVault does not adjudicate the rows. A report in Brighton Park can close without an arrest. An arrest can close without a conviction. None of those later outcomes are packed into the 3,553 figure. If a project needs court results, it needs court data. This packet has none, so this page invents none.

The respectful summary is short: CPD published 3,553 incident reports for this community area in the indexed extract. That sentence is complete. Adding words like convicted or criminals would go beyond the file. Neighborhood-level writing that stays with reports is still specific: it names Brighton Park, names CPD, and names the 3,553.

Two URLs for the same Brighton Park slice

The numbered overlay matches the community-area code that appears in CPD exports. The named Brighton Park URL is the same geography under the official neighborhood name used in this title. Link the numbered path in technical notes and the named path in reader-facing copy. Both sit under the Chicago crime hub. Neither path is a second count; both carry the same 3,553 indexed reports.

What Brighton Park’s packet will not support

There is no offense mix in the facts, so this guide will not say which report types dominate. There is no date span, so it will not say “this year” or invent a trend. There is no population, so it will not rank Brighton Park as more or less safe than another area on a per-person basis. What it will support is the sourced claim: 3,553 CPD incident reports in a city file of 410,083, available as public police records rather than as convictions.

Questions

How many CPD reports are indexed for Brighton Park?

Brighton Park has 3,553 incident reports in the LocalCrimeVault Chicago index. The citywide file contains 410,083 CPD records from the open-data portal. 3,553 counts published police reports assigned to this community area, not convictions or a completed case tally. Read the incident table for CPD’s published fields on each row rather than inferring an offense mix from the headline.

What percentage of Chicago incidents are in Brighton Park?

3,553 is about 0.87 percent of 410,083 citywide reports, or roughly one in 115 rows. The percentage is a share of this CPD extract, not a victimization survey and not a rate per resident. Population is not part of this packet.

Can I treat Brighton Park’s 3,553 as proven crimes?

No. CPD incident reports are the department’s published records of what was reported or recorded. Review, reclassification, and court process sit outside this count. Quote the number as open police data for Brighton Park, then use the incident table if you need the offense text on each row.

How do I open Brighton Park by neighborhood name?

Use the named Brighton Park path for the neighborhood label, or the community-area overlay for the numbered geography. Both hold the same 3,553 indexed reports. The Chicago crime hub provides the 410,083-report parent file. Named and numbered neighborhood URLs in this index point at the same community-area extract, not at two different counts.