Beverly incident reports from CPD open data

How to cite Beverly’s 1,601 without extra clauses

A complete citation is: LocalCrimeVault indexes 1,601 CPD incident reports for Beverly inside a Chicago file of 410,083 records drawn from the city open-data portal, and the figure counts reports rather than convictions. Extra clauses about typical crimes, last year, or per-person risk are not complete unless those fields are in the packet. They are not.

The temptation to add color is strong when a neighborhood name is familiar. Color that is not in the facts is still invention. This page stays with the filter that produced 1,601: published CPD rows assigned to Beverly in the indexed extract. The incident table is where additional fields actually exist.

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

1,601 divided by 410,083 is about 0.39 percent, or about one in 256 citywide reports. Under four-tenths of one percent of a large municipal extract is still more than a thousand local rows. Report the percentage with 1,601 attached so Beverly does not flatten into a rounding error or inflate into a standalone crime file.

Share of reports is not a safety score. This packet has no population, so a rate is out of scope. 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 Beverly’s 1,601 with a different publisher’s table is not a like-for-like comparison.

The Beverly 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 1,601. 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 Beverly’s count.

Socrata stops at the police report

Chicago’s portal publishes CPD incidents. It does not publish Beverly’s convictions. 1,601 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.

Respectful writing names Beverly as a geography in an open police file. It does not treat the 1,601 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.

Beverly’s named page and numbered community-area path

Titles and the H1 use Beverly. The overlay URL follows the numbered geography in CPD bulk files. The named Beverly path is the same 1,601-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.

What not to build on top of 1,601

Do not build a most-common-crime graphic, a year-over-year sparkline, or a per-capita rank from this page alone. Those products need fields this packet does not have. Do build a sourced sentence: 1,601 CPD incident reports for Beverly in a city file of 410,083, about 0.39 percent of the indexed extract, as public police reports. The table and hub are the next clicks for everything the rows actually contain.

A sourced sentence for Beverly does not need adjectives. LocalCrimeVault indexes 1,601 Chicago Police Department incident reports for the community area, drawn from the city’s open-data portal, inside a file of 410,083. The figure counts reports, not convictions. That sentence can travel into a footnote, a map caption, or a reporter’s notebook without picking up claims the packet cannot support. The named Beverly page, the numbered overlay, and the Chicago crime hub are the three links that keep the sentence attached to rows. Beverly’s 1,601 remains a CPD report total even after it is copied into a caption or a notebook.

Questions

How many police reports are indexed for Beverly, Chicago?

Beverly has 1,601 CPD incident reports in this index. The citywide file holds 410,083 records from the open-data portal. 1,601 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.

What percentage of Chicago reports come from Beverly?

1,601 is about 0.39 percent of 410,083 citywide CPD reports, or about one in 256. That share describes this extract only. Population is not in the packet, so a per-person rate is not computed here. The Chicago crime hub remains the parent index of 410,083 reports if you need citywide context next to this slice.

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

Where do I browse Beverly’s rows?

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