Jefferson Park CPD reports in Chicago

A repeatable count, not a scored ranking

1,550 is what you get if you take the indexed CPD extract and keep the rows assigned to Jefferson Park. There is no seriousness score, no extra weight for certain IUCR codes, and no subtraction of reports that later went nowhere in court. Repeatability is the point. Another person with the same extract and the same community-area filter should land on the same 1,550.

Repeatable does not mean complete in every moral sense. It means complete relative to the published file. Reports that CPD never released, or released with a different area assignment, are outside the 1,550 by definition. Cite the number as an indexed open-data total. Then send anyone who needs the wording on a single event to the incident table rather than to this headline.

Jefferson Park as a fraction of 410,083

1,550 is about 0.38 percent of 410,083 citywide reports, or about one in 265 published rows. A percentage that small is still more than a thousand records. Citywide denominators shrink every community area; they do not erase the local file. Report both numbers. A chart that shows only the percentage hides 1,550. A chart that shows only 1,550 hides Chicago.

This packet has no population, so 0.38 percent of reports is not a rate per resident. It also has no date span, so the share is not this year’s share. It is the share of this extract. The Chicago crime hub is the parent page for the 410,083. Use it when you need the rest of the file, not a second Jefferson Park total.

Footnote language that stays inside the file

A defensible footnote for Jefferson Park looks like this: LocalCrimeVault indexes 1,550 CPD incident reports for the community area, drawn from Chicago’s open-data portal, inside a citywide file of 410,083. Add that counts are reports rather than convictions. That is the whole sourced claim. Extra clauses about typical offenses or trends would require facts this packet does not contain.

If a briefing needs those extra clauses, the incident table is the next document, not a paragraph of invented color. Dates, locations as stored, and CPD descriptions live on the rows. This guide will not summarize a mix it cannot source. Leaving the mix on the table is how the page stays honest.

Police reports versus later case outcomes

Jefferson Park’s 1,550 should not be rewritten as 1,550 guilty findings. A report can be unfounded, reclassified, or closed without a charge. Arrest and court files are separate systems. This packet has no totals from those systems, so this page does not estimate them. The gap is a property of the source, not a missing adjective.

Respectful copy names the department and the product: CPD incident records on the city portal. It does not treat a community area as a character in a crime story. Locations in the table are published fields. They are not proof of who did what on a block.

Named Jefferson Park and the numbered overlay

Titles and the H1 use Jefferson Park. The overlay URL follows the numbered community-area geography that CPD bulk files use. The named Jefferson Park path is the same 1,550-row slice under the neighborhood label. Researchers joining on area codes should prefer the numbered route. Readers searching the neighborhood name should prefer the named route. The city hub sits above both.

What not to infer from 1,550

Do not infer a dominant offense. Do not infer a year. Do not infer that Jefferson Park is safer or less safe than another area on a per-person basis. Those inferences need fields this packet does not supply. What you can infer is narrower and still useful: CPD’s published extract, as indexed here, assigns 1,550 incident reports to Jefferson Park out of 410,083 citywide, and those reports remain public police records rather than convictions.

Jefferson Park’s 1,550 CPD incident reports are about 0.38 percent of 410,083 citywide records. The useful citation is the pair, not the local number alone. A pair keeps the community area inside Chicago’s published file. It also blocks a slide that treats 1,550 as a finished prosecution tally. The figure counts public police reports. The incident table holds the rows. The named and numbered Jefferson Park URLs index the same slice. The city hub holds the parent extract.

Questions

How many CPD reports are indexed for Jefferson Park?

Jefferson Park has 1,550 Chicago Police Department incident reports in this index, inside a citywide file of 410,083 records from the open-data portal. The figure counts published reports assigned to the community area. It does not count 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 Jefferson Park?

1,550 is about 0.38 percent of 410,083 citywide CPD reports, or about one in 265 rows. That is a share of this extract, not a per-capita rate. Population is not in the packet, so a rate is not computed here.

Are Jefferson Park’s 1,550 reports the same as court cases?

No. They are public police incident reports. Review, charging, and trial sit in other systems. This page has no conviction total because that number is not in the packet. Quote 1,550 as CPD open data for Jefferson Park. Quote the neighborhood total as public police reports from city open data, not as arrests, charges, or convictions.

Where do I open Jefferson Park’s rows and the city file?

Use the Jefferson Park incident table on the community-area overlay, or the named Jefferson Park page for the same slice. The Chicago crime hub holds the parent 410,083-report index. All three links stay in this CPD collection. Named and numbered neighborhood URLs in this index point at the same community-area extract, not at two different counts.