South Deering police reports from CPD data

What “indexed for South Deering” means

Indexed means the row survived three tests: CPD published it, the city portal carried it, and the extract assigned it to South Deering’s community area. Fail any test and the row is not in the 3,083. 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 3,083 with the universe attached: CPD incident reports for South Deering in this index, inside 410,083 Chicago records. Then stop, unless the incident table supplies the next field you need.

South Deering’s 3,083 inside 410,083

3,083 is about 0.75 percent of 410,083 citywide reports, or about one in 133 published rows. Three-quarters of one percent of a large municipal file is still a four-digit local count. Percentage language without 3,083 makes South Deering 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 South Deering 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.75 percent of reports is not a per-person rate.

Reading South Deering rows as CPD labeled them

The incident table is the 3,083 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 3,083; 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

South Deering’s 3,083 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 South Deering 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.

South Deering by name and by area code

This title and H1 use South Deering. The overlay URL uses the numbered community-area geography that bulk CPD files carry. The named South Deering path is the same 3,083-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 South Deering 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 South Deering (3,083), how large the city file is (410,083), and what kind of number 3,083 is (a public police-report count, not a conviction count). The table and hub exist for everything else that actually appears in the rows.

Quote the universe first: indexed CPD incident reports assigned to South Deering. Then quote the count: 3,083, inside 410,083 Chicago records. Universe-then-count is the order that keeps 3,083 from being mistaken for “everything that happened” or “everything that was proven.” The incident table is the 3,083 with fields attached. The city hub is the 410,083. Named and numbered South Deering URLs are the same slice. Adding those pages together would double-count the extract. South Deering’s 3,083 is a universe of indexed CPD reports, then a count, not a finished set of proven crimes. The city hub is the 410,083 parent. The Chicago crime hub holds the parent file.

Questions

How many police reports are indexed in South Deering?

South Deering has 3,083 CPD incident reports in this index. The citywide file holds 410,083 records from Chicago’s open-data portal. 3,083 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 South Deering?

3,083 is about 0.75 percent of 410,083 citywide CPD reports, or about one in 133. 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 South Deering’s 3,083 proven crimes?

No. They are public Chicago Police Department incident reports. Later review and court process sit outside the open-data count. Cite 3,083 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 South Deering by neighborhood name?

Use the named South Deering path, or the numbered community-area overlay for the same 3,083 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.