Crime reports in Edison Park, Chicago

Edison Park’s 433 follows CPD’s area assignment

A row enters the 433 when the indexed extract assigns it to Edison Park’s community area. Conversational names for nearby streets do not override that assignment. An address a resident groups with an adjacent neighborhood can still sit here if CPD geocoded it into Edison Park. The reverse is also true. LocalCrimeVault does not move rows to match listing-site maps, and it does not drop rows to make a small total look like zero.

The method is a filter, so the citation stays a filter: 433 CPD incident reports for Edison Park inside 410,083 Chicago records. 433 is among the smaller community-area totals in this extract. Smaller is not empty. Anyone who wants the text on a single event should open the incident table. Expanding 433 into a story that nothing happens here would contradict the rows that exist.

Share of Chicago’s 410,083 published reports

433 is about 0.11 percent of 410,083 citywide incidents, or about one in 947 published rows. About one-tenth of one percent of the municipal file is still hundreds of local records. Keep both numbers in view. A percentage without 433 hides the neighborhood total. A neighborhood total without 410,083 hides Chicago. More than 99 percent of the indexed file sits in other community areas.

This packet has no population, so 0.11 percent of reports is not a rate per resident. It has no date window, so the share is not labeled as a single year. A smaller raw count than another area is not a safety grade. The Chicago crime hub is the parent for the 410,083. Comparisons that leave this extract for another publisher’s table are no longer comparisons of the same rows.

Reading Edison Park rows without over-interpreting them

The overlay shows CPD’s identifiers, timestamps, location strings, and offense text. Treat them as published labels. A timestamp is when the extract associated the report with a time. A location may be a block or coarser. An offense string is not a jury finding. If two rows look alike, they may be related, duplicated, or independent. With 433 rows, scanning more of the table is practical; scanning still does not create an offense-mix fact in this packet.

Filters change what you see. They do not rewrite the indexed 433 unless the extract is rebuilt. Join other files on source identifiers. Homemade address cleanup is a common way to lose rows that still belong in Edison Park’s count. The named Edison Park page and the numbered overlay are the same slice. Search is a window on the 433, not a second official total.

The conviction gap for Edison Park

Police reports and convictions answer different questions. Edison Park’s 433 answers how many CPD incidents in this extract were assigned here. It does not answer how many people were found guilty. Many reports never become charges. This packet has no court totals, so this page does not estimate them. A small report total does not become a conviction total, and it does not become proof that courts had nothing to do.

Respectful use names Edison Park, names CPD, and names open data. It does not treat the 433 as a list of guilty people, and it does not treat a small total as a blank. Locations in the table are departmental fields, not accusations authored by this site. Readers who need case outcomes need the system that records case outcomes.

Edison Park by name and by numbered path

Titles and the H1 use Edison Park. The overlay follows the numbered community-area geography in CPD bulk files. The named Edison Park URL is the same 433 reports. Researchers joining area codes should use the numbered route. Readers searching the neighborhood name should use the named route. The city hub above both holds 410,083 records. Do not add the three pages together.

What this Edison Park page will not invent

It will not invent a dominant offense, a year-over-year change, or a per-capita rank, including a claim that Edison Park is the safest community area. Those need fields that are not in the facts. It will state that 433 CPD incident reports are indexed for Edison Park inside 410,083 Chicago records, about 0.11 percent of the extract, as public police reports. The incident table is the next document for dates and CPD descriptions. The city hub is the next document for the parent file.

Questions

How many crime reports are indexed in Edison Park?

Edison Park has 433 CPD incident reports in the LocalCrimeVault index, out of 410,083 Chicago records from the city open-data portal. The total counts published police 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 share of Chicago’s file is Edison Park?

433 is about 0.11 percent of 410,083 citywide CPD reports, or about one in 947. That share describes this extract only. Without population in the packet, it is not a rate per resident. A smaller slice is not the same as an empty file.

Are Edison Park’s 433 reports proven crimes?

No. They are public Chicago Police Department incident reports. Review, charging, and trial sit in other systems. This packet has no conviction count. Cite 433 as CPD open data for Edison Park. Quote the neighborhood total as public police reports from city open data, not as arrests, charges, or convictions.

Where do I open Edison Park’s table and the city hub?

Use the Edison Park incident table on the numbered overlay or the named Edison Park page for the same 433 reports. The Chicago crime hub holds the parent 410,083-report file. Named and numbered neighborhood URLs in this index point at the same community-area extract, not at two different counts.