Armour Square police reports in Chicago

1,972 is a four-digit slice, not a rounded talking point

Armour Square’s indexed total is 1,972 CPD incident rows, not a rounded 2,000 chosen for a headline. The number is a filter on the extract: keep rows assigned to this community area. LocalCrimeVault does not grade seriousness and does not drop reports that look routine. If the open file has the row and the geography matches, it is in the 1,972.

Because the method is a filter, the citation can stay short. Say that this index holds 1,972 CPD incident reports for Armour Square inside 410,083 Chicago records, and that the figure counts reports rather than convictions. Anyone who needs the wording on a single event should open the incident table rather than inflating the headline into a narrative.

Armour Square as a fraction of 410,083

1,972 is about 0.48 percent of 410,083 citywide reports, or about one in 208 published rows. Under half of one percent of a large municipal file is still nearly two thousand local records. Keep the fraction attached to 1,972 so Armour Square neither vanishes into Chicago nor looks like a separate jurisdiction.

0.48 percent of reports is not a per-capita rate. Population is not in this packet. The share is not a violent-crime share, because there is no offense split in the facts. The Chicago crime hub holds the 410,083-report parent. Cross-area charts should stay on that extract rather than mixing in another publisher’s table.

Using the Armour Square table as the row-level source

The overlay lists CPD’s published identifiers, timestamps, location strings, and offense text. Quote those fields as departmental labels. A location may be a block or coarser. A timestamp follows the extract. An offense string is not a jury finding. If two rows look related, say they look related; do not merge them from this guide.

Filters change the window on the 1,972. They do not mint a second official total 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 Armour Square’s count. The named Armour Square URL and the numbered overlay show the same slice.

Open police data is not a conviction file

Chicago’s portal publishes CPD incidents. Clerks and prosecutors publish other files. Armour Square’s 1,972 belongs to the first product. Many reports never become charges. This packet has no arrest total and no conviction total, so this page does not guess them. Calling 1,972 proven crimes would overstate the source.

Respectful copy names Armour Square as a community area in an open police file. It does not treat the 1,972 as a roster of defendants. Locations in the table are published strings, not accusations authored by LocalCrimeVault. Readers who need dockets need dockets.

Armour Square by name and by numbered overlay

This title and H1 use Armour Square. The overlay follows the numbered community-area geography in CPD bulk files. The named Armour Square page is the same 1,972 reports. Use the numbered link for spreadsheet joins and the named link for neighborhood search. The city hub remains the 410,083-report parent. Do not add the three pages together.

Claims the Armour Square packet will not support

It will not support a typical-offense claim, a yearly trend, or a rate per person. Those need an offense split, dates, or population. It will support 1,972 CPD incident reports, a citywide denominator of 410,083, a share of about 0.48 percent, and the statement that these are public police reports rather than convictions. That is the checkable set.

The claim this page can defend is narrow on purpose. LocalCrimeVault indexes 1,972 CPD incident reports for Armour Square in a city file of 410,083. Those reports are the department’s published records, not later court findings. Anyone repeating the number should repeat the source: Chicago Police Department incidents via the city open-data portal. Adding a typical-offense clause, a year label, or a per-person rank would step outside the packet. The incident table is the place to go when those extra fields actually appear on rows. The 1,972 and the 410,083 are one extract. Quoting only one of them is how the scale goes missing. Use both numbers in captions. The Chicago crime hub holds the parent file.

Questions

How many CPD reports are indexed for Armour Square?

Armour Square has 1,972 Chicago Police Department incident reports in this index, inside 410,083 citywide records from the open-data portal. The figure counts published reports assigned to the 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 Armour Square?

1,972 is about 0.48 percent of 410,083 citywide CPD reports, or about one in 208 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 Armour Square’s 1,972 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,972 as CPD open data for Armour Square. Quote the neighborhood total as public police reports from city open data, not as arrests, charges, or convictions.

Where do I open Armour Square’s rows and the city file?

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