Ashburn Chicago crime reports, CPD index

How Ashburn’s 3,508 reports were counted

The count is a filter on a CPD extract: keep rows whose community-area field maps to Ashburn, then total them. In this index that total is 3,508. No weighting, no exclusion of minor reports, and no addition of court cases that never appeared as CPD incidents in the open file. The method is intentionally dull. Dull methods are the ones other people can repeat.

Because the method is a filter, the honest citation is also simple. Say that LocalCrimeVault indexes 3,508 CPD incident reports for Ashburn inside a 410,083-report Chicago file. Do not upgrade that sentence into a claim about guilt, and do not downgrade it into a guess. It is a published-record total. If CPD later revises the extract, the live table can move even while this page still quotes 3,508 as the indexed snapshot.

Ashburn’s place in the citywide 410,083

3,508 divided by 410,083 is about 0.86 percent, or about one in 117 citywide reports. Ashburn is therefore a modest slice of the municipal extract and still a neighborhood with thousands of indexed rows. City-scale files make that combination common. The useful habit is to report both the neighborhood total and the city total in the same breath so neither number floats free.

Nothing in this packet ranks Ashburn against other community areas by rate. A higher raw count than a smaller area may reflect size, reporting practice, or land use. A lower raw count may reflect the same things in reverse. The incident table, not the headline percentage, is where variation inside Ashburn shows up. Without population in the facts, a per-person ranking would be invented math, so it is omitted.

Working from the Ashburn incident table

Open the overlay table to see the CPD rows behind 3,508. Read the fields as CPD published them. If you are matching to another spreadsheet, join on the identifiers in the source rather than on a cleaned address you invent. If you are writing for the public, quote offense text as CPD described the report rather than as a settled fact about what occurred. Location strings can be blocks or coarser; they are not automatically a precise porch.

The named Ashburn page and the numbered overlay are the same slice. Use whichever URL matches the audience. For a reminder of scale, keep the Chicago crime hub nearby so 3,508 stays attached to 410,083. Sorting and filtering change the window you see. They do not create a second official total unless the extract is rebuilt.

Why this page will not call 3,508 convictions

Police reports and convictions answer different questions. A report asks what was recorded. A conviction asks what a court found. Ashburn’s indexed total answers the first question only. The packet has no arrest field summary and no court summary, so those numbers are omitted rather than guessed. Skipping them is the difference between indexing open data and narrating a trial.

Chicago’s Socrata portal is still the right source for the report question. Cite CPD, cite the open-data portal, and cite the indexed 3,508. That is the full factual claim this guide can make. Readers who need case outcomes have to move to prosecutor or clerk systems. This site will not invent a bridge between those files.

Ashburn’s numbered geography for researchers

Bulk CPD files often carry a community-area number rather than a neighborhood string. Ashburn’s number is noted once in the lede so that join is possible. Reader-facing titles use Ashburn. The overlay path follows the numbered route; the named path follows the label. Both belong under the Chicago hub. Using both links in one document does not double-count the 3,508 reports.

Gaps you should not fill from this page

The packet does not include a start date or end date, so 3,508 is not labeled as a single year here. It does not include an offense-type split, so this guide will not name a dominant crime. It does not include population, so it will not compute a rate. What remains is still usable: a CPD report total for Ashburn, a citywide denominator of 410,083, and links to the table and hub where the rows live.

Questions

How many CPD incidents are indexed in Ashburn?

Ashburn has 3,508 Chicago Police Department incident reports in this index. The citywide file holds 410,083 records from the city’s open-data portal. 3,508 is a published-report total for the community area, not a conviction total and not a rate. Read the incident table for CPD’s published fields on each row rather than inferring an offense mix from the headline.

Is Ashburn’s crime count a yearly figure?

This packet does not include a start date or end date. The 3,508 figure is the number of CPD incident rows indexed for Ashburn in the current extract, sitting inside 410,083 citywide rows. If you need a calendar window, read dates on the incident table rather than assuming a year here.

Do Ashburn’s 3,508 reports equal 3,508 convictions?

No. They are public police reports. Many reports never become prosecutions. This page has no conviction count because that fact is not in the packet. Cite Ashburn’s total as CPD open data, then use court sources if you need case outcomes.

Where can I compare Ashburn with the rest of Chicago?

The Chicago crime hub holds the parent 410,083-report index. Ashburn’s 3,508 rows are about 0.86 percent of that file. The community-area overlay and the named Ashburn page both open the neighborhood slice. Named and numbered neighborhood URLs in this index point at the same community-area extract, not at two different counts.