Hegewisch Chicago police reports, CPD index

What “indexed for Hegewisch” means

Indexed means the row survived three tests: CPD published it, the city portal carried it, and the extract assigned it to Hegewisch’s community area. Fail any test and the row is not in the 1,286. LocalCrimeVault does not harvest rumors, news clips, or court minutes to pad the total. The open file is the universe for this number.

That universe is smaller than everything that happened and larger than everything that ended in a guilty finding. Both mismatches are normal for police open data. Cite 1,286 with the universe attached: CPD incident reports for Hegewisch in this index, inside 410,083 Chicago records. Then stop, unless the incident table supplies the next field you need.

Hegewisch’s 1,286 inside 410,083

1,286 is about 0.31 percent of 410,083 citywide reports, or about one in 319 published rows. Three-tenths of one percent of a large municipal file is still more than a thousand local records. Percentage language without 1,286 makes Hegewisch look empty. Raw-count language without 410,083 makes it look detached from Chicago. Use both.

The Chicago crime hub is the parent for the 410,083. Cross-area charts should stay on that hub’s extract. Pulling a Hegewisch number from this index and a different neighborhood’s number from a press release is not a comparison. This packet also lacks population, so 0.31 percent of reports is not a per-person rate.

Reading Hegewisch rows as CPD labeled them

The incident table is the 1,286 with their published fields visible. Offense text is CPD’s code or description. Location text is how the department stored the place. Time fields follow the extract, not a reconstructed timeline from interviews. If you quote a row, quote it as a report. That single habit prevents most overclaiming.

Clusters on the table can be real concentrations of reporting, artifacts of geocoding, or both. This page will not pick. Filters change the view of the 1,286; they do not authorize a new headline total unless the extract is rebuilt. Identifiers in the source are the join keys if you are matching another spreadsheet.

The conviction gap is a source limit

Hegewisch’s 1,286 is not a conviction ledger. CPD’s Socrata release does not wait for a judge. Reports can be unfounded or closed without charges. Arrest and court totals are not in this packet, so they are not estimated here. Omitting them is how the page stays inside the facts.

Respectful writing names Hegewisch as a geography in an open police file. It does not treat the community area as a cast of characters. If a reader needs to know what happened to a specific case, that reader needs a docket, not a neighborhood sum.

Hegewisch by name and by area code

This title and H1 use Hegewisch. The overlay URL uses the numbered community-area geography that bulk CPD files carry. The named Hegewisch path is the same 1,286-row slice. Researchers should bookmark the numbered route for joins. General readers should use the named route. The city hub above them holds 410,083 reports. Do not sum the three pages.

Questions the Hegewisch packet cannot answer

It cannot name a dominant offense, a calendar year, or a population-adjusted rank. Those answers need fields that are not in the facts. It can answer how many CPD incident reports are indexed for Hegewisch (1,286), how large the city file is (410,083), and what kind of number 1,286 is: a public police-report count, not a conviction count. The table and hub exist for everything else that actually appears in the rows.

Hegewisch’s 1,286 will get reused in maps, briefs, and search snippets. Reuse is fine if the noun stays reports. It is not fine if the noun becomes convictions or “typical crimes.” The indexed extract assigns 1,286 CPD incident records to Hegewisch inside 410,083 Chicago rows. That is the reusable claim. Dates and offense text live on the incident table. Court outcomes live in other systems. Mixing those stages into one neighborhood headline is how open data gets overstated. Hegewisch’s 1,286 stays honest when the noun remains reports and the denominator remains 410,083. The table is the 1,286 taken apart. The Chicago crime hub holds the parent 410,083-report file for citywide context.

Questions

How many police reports are indexed in Hegewisch?

Hegewisch has 1,286 CPD incident reports in this index. The citywide file holds 410,083 records from Chicago’s open-data portal. 1,286 is a published-report total for the community area, not a conviction total. 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 are in Hegewisch?

1,286 is about 0.31 percent of 410,083 citywide CPD reports, or about one in 319. That share describes this extract only. Without population in the packet, it is not a crime rate per resident. The Chicago crime hub remains the parent index of 410,083 reports if you need citywide context next to this slice.

Can I call Hegewisch’s 1,286 proven crimes?

No. They are public Chicago Police Department incident reports. Later review and court process sit outside the open-data count. Cite 1,286 as CPD reports, then use the incident table for offense text on each row. Quote the neighborhood total as public police reports from city open data, not as arrests, charges, or convictions.

How do I open Hegewisch by neighborhood name?

Use the named Hegewisch path, or the numbered community-area overlay for the same 1,286 reports. The Chicago crime hub provides the parent 410,083-report index for citywide context. Named and numbered neighborhood URLs in this index point at the same community-area extract, not at two different counts.