Hermosa incident count from CPD open data

A mechanical Hermosa count, on purpose

Mechanical counts are the ones other people can repeat. Take the indexed CPD file, keep rows assigned to Hermosa, and you should land on 2,160. There is no seriousness score and no extra weight for certain codes. LocalCrimeVault does not drop reports that look minor. If the open file has the row and the geography matches, it is in the total.

Mechanical is also limited. Publication rules, geocoding, and later edits all shape 2,160. Cite it as an indexed CPD report count for Hermosa inside 410,083 Chicago records. Then send anyone who needs a single event’s wording to the incident table. The table is not a different dataset; it is the 2,160 taken apart.

2,160 inside 410,083 citywide reports

Hermosa’s 2,160 rows are about 0.53 percent of 410,083 published incidents, or about one in 190 citywide reports. Half of one percent of the municipal extract still leaves more than two thousand local records. Report both numbers. A chart that shows only the percentage hides 2,160. A chart that shows only 2,160 hides Chicago.

This packet has no population, so 0.53 percent of reports is not a rate per resident. It has no date span, so the share is not “this year’s share.” The Chicago crime hub is the parent for the 410,083. Use it when you need the rest of the file. Do not mix Hermosa’s 2,160 with a different agency’s table and call the result a comparison.

The Hermosa table as a source, not a story engine

Identifiers, timestamps, location strings, and offense text are CPD’s published fields. Quote them as recorded. Do not treat a location string as proof of who did what. Do not treat an offense string as a finding of guilt. If two rows look similar, say so; do not merge them from this guide.

Filters are a viewing tool. They do not authorize a second Hermosa total unless the extract is rebuilt. If you need a calendar window, take it from the date fields on the rows. This page will not invent a year for the 2,160. Join other spreadsheets on source identifiers rather than on reconstructed street names.

Reports remain reports when you publish them

Quoting 2,160 in an article does not convert the number into convictions. CPD’s portal product is a police-records release. Prosecutors and courts keep other products. Many reports never become charges. This packet has no court counts, so this page has none. The accurate noun is still reports.

Respectful writing names Hermosa, names the Chicago Police Department, and stops before inventing defendants. Neighborhood-level copy can be specific without being lurid: it can say 2,160 published incident reports in a city file of 410,083. That sentence is complete.

Hermosa’s named URL and numbered overlay

Titles and the H1 use Hermosa. The overlay follows the numbered community-area path that CPD bulk columns use. The named Hermosa page is the same 2,160 reports. Researchers should bookmark the numbered route for joins. General readers should use the named route. The city hub above them holds 410,083 reports. Three links, one extract.

What not to infer from Hermosa’s 2,160

Do not infer a dominant offense, a year, or a per-person rank. Those inferences need fields this packet does not supply. What you can infer is narrower: CPD’s published extract, as indexed here, assigns 2,160 incident reports to Hermosa out of 410,083 citywide, about 0.53 percent of the file, and those reports remain public police records rather than convictions.

Dull methods survive contact with other researchers. Hermosa’s 2,160 is a community-area filter on an indexed CPD extract, not a scored ranking and not a highlights reel. Another person with the same file should land on the same total. Cite it with 410,083 so the municipal denominator travels too. Then point to the incident table for row-level CPD fields and to the city hub for the parent file. If a project needs a rate, a year, or a conviction count, it needs a different packet. This one does not have those fields. Hermosa’s 2,160 is the community-area filter on this extract; the city hub is how 410,083 stays in view. Named and numbered URLs are the same 2,160. The Chicago crime hub holds the parent file.

Questions

How many police reports are listed for Hermosa, Chicago?

The index lists 2,160 CPD incident reports for Hermosa. They are part of 410,083 Chicago records from the city open-data portal. The total counts published reports assigned to this community area, not convictions and not a per-capita rate. Read the incident table for CPD’s published fields on each row rather than inferring an offense mix from the headline.

What share of Chicago reports come from Hermosa?

Hermosa’s 2,160 reports are about 0.53 percent of 410,083 citywide CPD incidents, or about one in 190 published rows. That percentage describes how this extract is split. It is not a crime rate, because this packet does not include population.

Are Hermosa’s crime numbers convictions?

No. The 2,160 figure is a count of public CPD incident reports. A report can be unfounded, reclassified, or closed without a charge. Quote Hermosa’s total as police reports drawn from Chicago open data, not as guilty findings. Quote the neighborhood total as public police reports from city open data, not as arrests, charges, or convictions.

Where can I see Hermosa’s underlying rows?

Open the Hermosa incident table on the community-area overlay, or use the named Hermosa path. For citywide context, use the Chicago crime hub, which holds the parent 410,083-report index. Named and numbered neighborhood URLs in this index point at the same community-area extract, not at two different counts.