Clearing incident count from CPD open data

A mechanical Clearing count, on purpose

Mechanical counts are the ones other people can repeat. Take the indexed CPD file, keep rows assigned to Clearing, and you should land on 1,699. 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 1,699. Cite it as an indexed CPD report count for Clearing 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 1,699 taken apart.

1,699 inside 410,083 citywide reports

Clearing’s 1,699 rows are about 0.41 percent of 410,083 published incidents, or about one in 241 citywide reports. Four-tenths of one percent of the municipal extract still leaves more than a thousand local records. Report both numbers. A chart that shows only the percentage hides 1,699. A chart that shows only 1,699 hides Chicago.

This packet has no population, so 0.41 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 Clearing’s 1,699 with a different agency’s table and call the result a comparison.

The Clearing 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 Clearing 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 1,699. Join other spreadsheets on source identifiers rather than on reconstructed street names.

Reports remain reports when you publish them

Quoting 1,699 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 Clearing, names the Chicago Police Department, and stops before inventing defendants. Neighborhood-level copy can be specific without being lurid: it can say 1,699 published incident reports in a city file of 410,083. That sentence is complete.

Clearing’s named URL and numbered overlay

Titles and the H1 use Clearing. The overlay follows the numbered community-area path that CPD bulk columns use. The named Clearing page is the same 1,699 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 Clearing’s 1,699

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 1,699 incident reports to Clearing out of 410,083 citywide, about 0.41 percent of the file, and those reports remain public police records rather than convictions.

Clearing’s 1,699 CPD incident reports are about 0.41 percent of 410,083 citywide records. Write the local number and the city number in the same citation so Clearing does not look like a separate police file. The share is a property of this extract. It is not a victimization survey, not a year-specific figure, and not a rate per resident. Population and a date window are absent from the packet, so they stay absent from this page. The incident table is where dates and CPD descriptions actually live. Clearing’s 1,699 is still a public-report tally after it leaves this page; it does not become a docket on contact with a headline. Keep the noun reports in every reuse. The Chicago crime hub holds the parent file.

Questions

How many police reports are listed for Clearing, Chicago?

The index lists 1,699 CPD incident reports for Clearing. 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 Clearing?

Clearing’s 1,699 reports are about 0.41 percent of 410,083 citywide CPD incidents, or about one in 241 published rows. That percentage describes how this extract is split. It is not a crime rate, because this packet does not include population.

Are Clearing’s crime numbers convictions?

No. The 1,699 figure is a count of public CPD incident reports. A report can be unfounded, reclassified, or closed without a charge. Quote Clearing’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 Clearing’s underlying rows?

Open the Clearing incident table on the community-area overlay, or use the named Clearing 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.