Crime reports in Fuller Park, Chicago

Fuller Park’s 1,160 follows CPD’s area assignment

A row enters the 1,160 when the indexed extract assigns it to Fuller 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 Fuller Park. The reverse is also true. LocalCrimeVault does not move rows to match listing-site maps.

The method is a filter, so the citation stays a filter: 1,160 CPD incident reports for Fuller Park inside 410,083 Chicago records. Anyone who wants the text on a single event should open the incident table. Expanding 1,160 into a story about what usually happens here would require an offense mix this packet does not have.

Share of Chicago’s 410,083 published reports

1,160 is about 0.28 percent of 410,083 citywide incidents, or about one in 354 published rows. Under three-tenths of one percent of the municipal file is still more than a thousand local records. Keep both numbers in view. A percentage without 1,160 hides the neighborhood total. A neighborhood total without 410,083 hides Chicago.

This packet has no population, so 0.28 percent of reports is not a rate per resident. A smaller raw count than some other community areas is not, by itself, a safety grade. Size, reporting, and land use can all move a total. 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 Fuller 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.

Filters change what you see. They do not rewrite the indexed 1,160 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 Fuller Park’s count. The named Fuller Park page and the numbered overlay are the same slice.

The conviction gap for Fuller Park

Police reports and convictions answer different questions. Fuller Park’s 1,160 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.

Respectful use names Fuller Park, names CPD, and names open data. It does not treat the 1,160 as a list of guilty people. 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.

Fuller Park by name and by numbered path

Titles and the H1 use Fuller Park. The overlay follows the numbered community-area geography in CPD bulk files. The named Fuller Park URL is the same 1,160 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.

What this Fuller Park page will not invent

It will not invent a dominant offense, a year-over-year change, or a per-capita rank. Those need fields that are not in the facts. It will state that 1,160 CPD incident reports are indexed for Fuller Park inside 410,083 Chicago records, about 0.28 percent of the extract, as public police reports. The incident table is the next document for dates and CPD descriptions.

Fuller Park’s 1,160 sits below many other community-area totals in the same extract and still above one thousand published CPD reports. Both facts matter. A smaller raw count is not a safety grade, because this packet has no population. It is also not a claim that the table is empty. Cite 1,160 inside 410,083 Chicago records, about 0.28 percent of the file, as public police reports. Then open the incident table for the row text. The city hub remains the parent for comparisons that stay on this extract. Fuller Park’s 1,160 is a four-digit CPD table inside 410,083 city records, not a blank and not a rate.

Questions

How many crime reports are indexed in Fuller Park?

Fuller Park has 1,160 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 Fuller Park?

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

Are Fuller Park’s 1,160 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 1,160 as CPD open data for Fuller Park. Quote the neighborhood total as public police reports from city open data, not as arrests, charges, or convictions.

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

Use the Fuller Park incident table on the numbered overlay or the named Fuller Park page for the same 1,160 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.