Stalking reports in Chicago

Course-of-conduct reports on the CPD feed

Stalking on the public extract is the primary type CPD assigned. Related conduct can also be filed as harassment-like codes under Other Offense, as Assault, or under other types depending on how the report was written. This page does not add those types together. The headline is 985 rows labeled Stalking.

A single course of conduct can produce one report or several. The 985 count is rows, not unique victims and not unique suspects. Cyberstalking versus in-person descriptions, when present, live on the table as CPD wrote them. This packet does not include those subtotals.

Illinois stalking statutes describe a course of conduct. The public extract still stores rows. One course can produce several of the 985 rows among 410,083 city incidents. The count is reports, not unique victims. This page does not invent a unique-victim figure.

Cite 985 among 410,083 Chicago incidents. Course-of-conduct reports do not equal unique victims. This page will not invent that unique count. Keep assault and residual harassment codes on their own hubs unless you disclose a custom mix.

Share of the 410,083-incident extract

Relative to 410,083 Chicago incidents, 985 stalking reports are a small share. Small share is not a statement that stalking is rare in victimization surveys; those surveys are not packet facts. The honest open-data number is 985 CPD rows in this harvest.

Maps use block-level geography and official community area names. Pins must not be treated as identifying a victim's home. Coarse location is a privacy feature of the public file.

Harassment-like residual codes under Other Offense are not automatically stalking. Keep 985 attached to IUCR primary type Stalking. LocalCrimeVault does not recode those residual rows onto this hub.

Protective-order databases are not 985. Quote CPD IUCR primary type Stalking. Block-level maps must stay coarse. Official community area names are the 77-area list. LocalCrimeVault does not reclassify charges or describe individual cases.

Reading the stalking table

Use date and community area filters on the 985 rows. Arrest flags are not convictions. Missing geography stays blank. LocalCrimeVault does not impute a community area or a name.

This narrative stays aggregate. Graphic or identifying detail is not added. The legitimate use of the table is report volume, timing, and official community area.

Orders of protection are a court product. They can exist without a stalking incident row, and a stalking row can exist without an order. Quote 985 as CPD reports. Block-level maps must not be treated as victim-home identifications. Official community area names are the 77 areas.

What 985 is not

It is not a count of plenary orders of protection, not a hotline volume, and not a court caseload. Those systems overlap imperfectly with CPD incident rows. Quote 985 as IUCR primary type Stalking in the indexed Chicago extract of 410,083 reports.

CPD and the City of Chicago publish the incidents. LocalCrimeVault does not reclassify charges.

Chicago hub placement

The stalking type hub holds the live table. The Chicago hub places these 985 rows beside assault, battery, and the rest of the IUCR mix. A cross-city stalking page follows other agencies' statute names, which may not match Illinois IUCR.

Cite 985 as Chicago Police Department incident rows with IUCR primary type Stalking among 410,083 city reports. Related conduct can also be filed as assault or under residual codes. This page does not add those types. The headline is 985 rows labeled Stalking.

A course of conduct can produce one report or several. The 985 count is rows, not unique victims and not unique suspects. Cyber versus in-person descriptions, when present, live on the table. This packet has no such subtotal.

Citing stalking as a course-of-conduct type

Orders of protection and hotline volumes are different systems. They overlap imperfectly with CPD incident rows. Quote 985 as the open-data primary type. This page does not describe individual cases.

Maps must stay coarse. Block-level ranges and official community area names (77 areas) are not victim-home identifications. Record the harvest. LocalCrimeVault does not reclassify charges. The overlay table is for aggregate date and area.

Questions

How many stalking reports are in the Chicago CPD index?

This extract lists 985 Chicago incidents with IUCR primary type Stalking, in a city file of 410,083 reports. The source is Chicago Police Department open data. The figure counts police reports, not unique victims, orders of protection, or convictions. LocalCrimeVault does not reclassify CPD charges.

Is stalking the same as assault or harassment in this data?

Not automatically. CPD files Stalking as its own primary type. Assault and residual harassment-like codes can sit under other types. This page covers only the 985 stalking rows. Do not merge types without listing what you combined. Read IUCR codes on the table for the language CPD used.

Does a stalking row mean a conviction?

No. Public incident rows are reports. They can exist without an arrest or after charges change. The 985 count is report volume among 410,083 indexed Chicago incidents. Court orders and verdicts live in other systems. This page does not describe individual cases. The 985 count is report volume among 410,083 city incidents, not unique victims.

Can the map identify a victim's home?

CPD's public extract uses block-level ranges and official community areas, not street-number addresses. Treat geography as coarse on purpose. Use the type table and Chicago hub for aggregate location as published, not to identify people. The 985-row map uses CPD block ranges, not street-number addresses of victims.