Burnside incident reports from CPD open data

How to cite Burnside’s 438 without turning it into none

A complete citation is: LocalCrimeVault indexes 438 CPD incident reports for Burnside inside a Chicago file of 410,083 records drawn from the city open-data portal, and the figure counts reports rather than convictions. 438 is among the smaller community-area totals in this extract. Smaller is not the same as empty. Rounding 438 down to zero, or writing that nothing was reported, would misstate the file.

Extra clauses about typical crimes, last year, or per-person risk are not complete unless those fields are in the packet. They are not. This page stays with the filter that produced 438: published CPD rows assigned to Burnside in the indexed extract. The incident table is where additional fields actually exist. With a few hundred rows, the table is still the evidence, not a rumor that Burnside has no reports.

Burnside’s share of the 410,083-record file

438 divided by 410,083 is about 0.11 percent, or about one in 936 citywide reports. About one-tenth of one percent of a large municipal extract is still hundreds of local rows. Report the percentage with 438 attached so Burnside does not flatten into a rounding error or get inflated into a standalone crime file. More than 99 percent of the indexed file sits in other community areas.

Share of reports is not a safety score. This packet has no population, so a rate is out of scope, including a claim that Burnside is the safest community area. It has no offense mix, so the share is not a violent-crime share. The Chicago crime hub holds the 410,083-report parent. Cross-area work should stay on that extract. Mixing Burnside’s 438 with a different publisher’s table is not a like-for-like comparison.

The Burnside table as row-level CPD text

Open the overlay to read identifiers, timestamps, location strings, and offense descriptions as CPD stored them. Treat each as a published label. A block string is not a full address history. An offense string is not a verdict. Two similar rows may be duplicates, related events, or coincidence. This guide will not merge them remotely.

Filters and sorts change the window on the 438. They do not mint a second official total unless the extract is rebuilt. If you need a calendar window, take dates from the rows. This page will not invent a year. Join other spreadsheets on source identifiers. Homemade geocoding is a common way to drop rows that still belong in Burnside’s count. Pagination is a window, not a new headline.

Socrata stops at the police report

Chicago’s portal publishes CPD incidents. It does not publish Burnside’s convictions. 438 reports can include events that were unfounded, declined, or never charged. Arrest and court totals are absent from the packet, so they are absent from this page. The gap is a source limit, not a missing adjective. A small report total does not become a conviction total, and it does not become a claim that courts were idle.

Respectful writing names Burnside as a geography in an open police file. It does not treat the 438 as a cast of guilty people. Locations in the table are departmental fields. If a reader needs to know what happened after a specific report, that reader needs a docket. Neighborhood copy can name 438 published reports in a city file of 410,083 without turning the community area into a character.

Burnside’s named page and numbered community-area path

Titles and the H1 use Burnside. The overlay URL follows the numbered geography in CPD bulk files. The named Burnside path is the same 438-row slice. Use the numbered link when joining area codes and the named link when matching neighborhood search. The Chicago crime hub remains the 410,083-report parent. Do not add the three pages. Three links, one extract.

What not to build on top of 438

Do not build a most-common-crime graphic, a year-over-year sparkline, or a per-capita rank from this page alone. Do not build a no-crime-here headline either. Those products need fields this packet does not have, or they contradict the 438 rows that do exist. Do build a sourced sentence: 438 CPD incident reports for Burnside in a city file of 410,083, about 0.11 percent of the indexed extract, as public police reports. The table and hub are the next clicks.

Questions

How many police reports are indexed for Burnside, Chicago?

Burnside has 438 CPD incident reports in this index. The citywide file holds 410,083 records from the open-data portal. 438 counts published reports assigned to this community area, not convictions 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 Burnside’s 438 small enough to ignore?

No. 438 is hundreds of published CPD reports, about 0.11 percent of 410,083 citywide records, or about one in 936. It is a smaller slice than many community areas, not a blank file. Without population in the packet, it is also not a per-person rate.

Is Burnside’s 438 a conviction count?

No. It is a count of public Chicago Police Department incident reports. Charging and court outcomes live in other systems. This packet has no conviction figure. Cite 438 as CPD open data for Burnside. Quote the neighborhood total as public police reports from city open data, not as arrests, charges, or convictions.

Where do I browse Burnside’s rows?

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