Crime reports in Bridgeport, Chicago

Bridgeport’s 2,755 is every indexed row, not a highlights list

The neighborhood total includes each CPD incident in this extract that carries Bridgeport’s community-area assignment. LocalCrimeVault does not keep only “major” reports and does not drop rows that look routine. If the open file has the row and the geography matches, it is in the 2,755. That is why the number can be checked against the same portal product.

Completeness relative to the extract is not completeness relative to every event a resident remembers. Unpublished reports, reports assigned to another area, and court cases that never appeared as CPD incidents are outside the 2,755. Cite the universe when you cite the number: indexed CPD reports for Bridgeport, inside 410,083 Chicago records.

2,755 as a slice of 410,083

Bridgeport’s 2,755 reports are about 0.67 percent of the citywide file, or about one in 149 published rows. Two-thirds of one percent of 410,083 is still a four-digit local count. Keep the fraction attached to 2,755 so Bridgeport neither disappears into the city nor stands as if it were a separate jurisdiction.

This packet has no population, so 0.67 percent of reports is not a per-capita rate. It has no offense split, so the share is not a violent-crime share. It has no date span, so it is not “this year’s share.” The Chicago crime hub is the parent page for the 410,083. Use that hub when the question is citywide, and return to Bridgeport’s table when the question is this slice.

How the Bridgeport table should be quoted

Quote CPD’s fields as CPD’s fields. Identifiers are join keys. Timestamps follow the extract. Location strings may be blocks or coarser. Offense text is a departmental description, not a finding of guilt. If you are writing for the public, the safest verb is recorded, not committed, unless a court file is in front of you—and this index is not a court file.

Pagination and search change what is on screen. They do not rewrite the indexed 2,755 unless the extract is rebuilt. Clusters of points can be concentrations of reporting or concentrations of geocoding. This guide will not pick. The named Bridgeport URL and the numbered overlay show the same rows.

Police reports stop short of convictions

A report can close without an arrest. An arrest can close without a charge. A charge can close without a conviction. Bridgeport’s 2,755 sits at the first of those stages as published by CPD. This packet has no totals for the later stages, so this page does not invent them. Calling 2,755 convictions would be a category error.

Respectful use of the file names Bridgeport, names the Chicago Police Department, and names open data. It does not treat a community area as a defendant. Locations in the table are published strings. They are not this site’s accusations. Readers who need dockets need dockets.

Bridgeport by neighborhood name and by area number

This title and H1 use Bridgeport. The overlay path follows the numbered community-area geography in CPD bulk files. The named Bridgeport page is the same 2,755-row slice. 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 pages together.

Gaps in the Bridgeport packet

No year label, no offense mix, no population, no arrest count, no conviction count. This guide therefore will not produce a trend, a typical crime, or a safety rank. It will produce the sourced claim: 2,755 CPD incident reports for Bridgeport in a city file of 410,083, about 0.67 percent of the indexed extract, as public police reports. The incident table is the next document for dates and CPD descriptions.

Completeness is easy to overclaim. Bridgeport’s 2,755 is complete relative to the indexed CPD extract: every published row assigned to this community area is in the total. It is not complete relative to every event a resident remembers, every unpublished report, or every court case that never appeared as an incident. Cite 2,755 with that boundary, and keep 410,083 next to it so the municipal file remains the denominator. The incident table is how a reader inspects the 2,755 without treating the headline as a finished story.

Questions

How many crime reports are indexed in Bridgeport?

Bridgeport has 2,755 CPD incident reports in the LocalCrimeVault index, out of 410,083 Chicago records from the city open-data portal. That total counts published police reports assigned to this 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 indexed reports is Bridgeport?

2,755 is about 0.67 percent of 410,083 citywide CPD reports, or about one in 149. The share describes this extract only. Without population in the packet, it is not a rate per resident. The Chicago crime hub remains the parent index of 410,083 reports if you need citywide context next to this slice.

Does Bridgeport’s 2,755 include only serious offenses?

No. The 2,755 figure is every indexed CPD incident assigned to Bridgeport in this extract, not a seriousness subset. This packet does not break the total out by offense type. Offense labels live on the incident table rows. Quote the neighborhood total as public police reports from city open data, not as arrests, charges, or convictions.

Where do I open Bridgeport’s table and the city hub?

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