Calumet Heights CPD reports in Chicago

2,189 is the extract, not a newsroom shortlist

LocalCrimeVault did not pick the most dramatic Calumet Heights reports and add them up. The 2,189 is every indexed CPD incident assigned to this community area in the current extract. Rows that look routine still count. Rows that later went nowhere in court still count if they were published. That is how an open-data total stays checkable.

Checkable is not the same as complete in every human sense. Reports CPD never released, reports assigned to another area, and court cases that never appeared as incidents are outside the 2,189. Cite the universe with the number: indexed CPD reports for Calumet Heights, inside 410,083 Chicago records. Then use the incident table if you need a row’s wording.

Calumet Heights beside the 410,083-report city file

2,189 divided by 410,083 is about 0.53 percent, or about one in 187 citywide reports. Half of one percent of Chicago’s published file is still a four-digit neighborhood total. Pair the fraction with 2,189 so Calumet Heights neither disappears into the denominator nor looks detached from the city.

Do not convert 0.53 percent into a safety rank. This packet has no population and no offense mix. A rank would need at least one of those. The Chicago crime hub holds the 410,083-report parent so the denominator stays visible. Stay on that extract when you compare community areas.

How to read the Calumet Heights table

Each row is a CPD record with published identifiers, times, locations, and offense text. Quote those fields as departmental labels. A location may be a block or coarser. A timestamp follows the extract, which may not match a resident’s memory of a moment. An offense string is not a verdict.

Pagination is a window on the 2,189, not a new count. Clusters of points can be concentrations of reporting or concentrations of geocoding. This page will not pick. If you join another spreadsheet, join on source identifiers. Rebuilt extracts can move the live table even while this page still quotes 2,189 as the indexed snapshot.

Public CPD records stop before the courthouse

Chicago’s Socrata portal releases police incidents. Clerks and prosecutors keep other products. Calumet Heights’s 2,189 belongs to the first product. Many reports never become charges. This packet has no conviction count, so this page has none. Substituting convictions for reports would be a category error.

Respectful copy names Calumet Heights as a geography in an open police file. It does not treat the 2,189 as a cast of guilty people. Locations in the table are published strings, not accusations written by this site. If a project needs case outcomes, it needs the system that records case outcomes.

Calumet Heights by name and by area code

This title and H1 use Calumet Heights. The overlay path follows the numbered community-area geography in CPD bulk files. The named Calumet Heights page is the same 2,189-row slice. Use the numbered link for joins and the named link for neighborhood search. The city hub remains the 410,083-report parent. Do not sum the three URLs.

Packet gaps for Calumet Heights

No year range, no offense-type totals, no population, no arrest total, no conviction total. This guide will not fill those gaps with guesses. What it will state is sourced: 2,189 CPD incident reports for Calumet Heights inside 410,083 Chicago records, about 0.53 percent of the indexed file, as public police reports. The table and hub are the next documents.

Newsroom edits pick. Filters do not. Calumet Heights’s 2,189 is the output of a filter on the indexed CPD file, not a shortlist of reports an editor found interesting. That is why the number can be checked against the same open-data product. It is also why the number can look large to a reader who expected a highlights reel and small to a reader looking at 410,083 citywide. Both reactions are about scale. Neither reaction changes the method. The table holds the rows; the hub holds the parent file. Calumet Heights’s 2,189 is the extract, and 410,083 is the city file that gives it a denominator. That pairing is the whole sourced claim. The Chicago crime hub holds the parent 410,083-report file for citywide context.

Questions

How many CPD incidents are indexed in Calumet Heights?

Calumet Heights has 2,189 Chicago Police Department incident reports in this index. The citywide file holds 410,083 records from the open-data portal. 2,189 counts published reports assigned to this community area, not convictions. 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 reports is Calumet Heights?

2,189 is about 0.53 percent of 410,083 citywide CPD reports, or about one in 187. The percentage is a share of this extract, not a victimization survey and not a rate per resident. Population is not in the packet. The Chicago crime hub remains the parent index of 410,083 reports if you need citywide context next to this slice.

Does 2,189 mean 2,189 convictions in Calumet Heights?

No. The figure is a count of public police reports. Charging and court outcomes live elsewhere. This packet has no conviction total. Cite 2,189 as CPD open data for Calumet Heights. Quote the neighborhood total as public police reports from city open data, not as arrests, charges, or convictions.

Where do I browse Calumet Heights and the city index?

Open the Calumet Heights incident table on the numbered overlay or the named Calumet Heights page. For the parent file of 410,083 reports, use the Chicago crime hub. Calumet Heights’s 2,189 rows are about 0.53 percent of that hub file.