Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Complaints received by the Civilian Office of Police Accountability and its predecessor agency.

A case will generate multiple rows, sharing the same LOG_NO if there are multiple officers. Each row in this dataset is an officer in a specific case.

Other than identifying the Log Number associated with an investigation being conducted by the Bureau of Internal Affairs section of the Chicago Police Department, information regarding such investigations is not included in this data set.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Complaints received by the Civilian Office of Police Accountability and its predecessor agency.

A case will generate multiple rows, sharing the same LOG_NO if there are multiple complainants or subjects. Each row in this dataset is a complainant or subject in a specific case.

Other than identifying the Log Number associated with an investigation being conducted by the Bureau of Internal Affairs section of the Chicago Police Department, information regarding such investigations is not included in this data set.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

This dataset contains all ShotSpotter alerts since the introduction of ShotSpotter to some Chicago Police Department (CPD) districts in 2017. ShotSpotter is a gunshot detection system designed to automatically determine the location of potential outdoor gunfire. ShotSpotter audio sensors are placed in several CPD districts throughout the city (specific districts are noted below). If at least three sensors detect a sound that the ShotSpotter software determines to be potential gunfire, a location is determined and the alert is sent to human ShotSpotter analysts for review. Either the alert is sent to CPD, or it is dismissed. Each alert can contain multiple rounds of gunfire; sometimes there are multiple alerts for what may be determined to be one incident. More detail on the technology and its accuracy can be found on the company’s website here. It should also be noted that ShotSpotter alerts may increase year-over-year while gun violence did not necessarily increase accordingly because of improvements in detection sensors.

ShotSpotter does not exist in every CPD district, and it was not rolled out in every district at the same time. ShotSpotter was first deployed in Chicago in 2017, and sensors exist in the following districts as of the May 2021 launch of this dataset: 002, 003, 004, 005, 006, 007, 008, 009, 010, 011, 015, and 025.

Records from the Crimes - 2001 to Present dataset for the indicated year.

Please see the description section of the full dataset for further information about the data.

Chicago Police district station locations. To view or use these files, compression software and special GIS software, such as ESRI ArcGIS, is required. To download, right-click the "Download" link above and choose "Save link as."

This dataset contains aggregate data on violent index victimizations at the quarter level of each year (i.e., January – March, April – June, July – September, October – December), from 2001 to the present (1991 to present for Homicides), with a focus on those related to gun violence. Index crimes are 10 crime types selected by the FBI (codes 1-4) for special focus due to their seriousness and frequency. This dataset includes only those index crimes that involve bodily harm or the threat of bodily harm and are reported to the Chicago Police Department (CPD). Each row is aggregated up to victimization type, age group, sex, race, and whether the victimization was domestic-related. Aggregating at the quarter level provides large enough blocks of incidents to protect anonymity while allowing the end user to observe inter-year and intra-year variation. Any row where there were fewer than three incidents during a given quarter has been deleted to help prevent re-identification of victims. For example, if there were three domestic criminal sexual assaults during January to March 2020, all victims associated with those incidents have been removed from this dataset. Human trafficking victimizations have been aggregated separately due to the extremely small number of victimizations.

This dataset includes a " GUNSHOT_INJURY_I " column to indicate whether the victimization involved a shooting, showing either Yes ("Y"), No ("N"), or Unknown ("UKNOWN.") For homicides, injury descriptions are available dating back to 1991, so the "shooting" column will read either "Y" or "N" to indicate whether the homicide was a fatal shooting or not. For non-fatal shootings, data is only available as of 2010. As a result, for any non-fatal shootings that occurred from 2010 to the present, the shooting column will read as “Y.” Non-fatal shooting victims will not be included in this dataset prior to 2010; they will be included in the authorized dataset, but with "UNKNOWN" in the shooting column.

The dataset is refreshed daily, but excludes the most recent complete day to allow CPD time to gather the best available information. Each time the dataset is refreshed, records can change as CPD learns more about each victimization, especially those victimizations that are most recent. The data on the Mayor's Office Violence Reduction Dashboard is updated daily with an approximately 48-hour lag. As cases are passed from the initial reporting officer to the investigating detectives, some recorded data about incidents and victimizations may change once additional information arises. Regularly updated datasets on the City's public portal may change to reflect new or corrected information.

How does this dataset classify victims?

The methodology by which this dataset classifies victims of violent crime differs by victimization type:

Homicide and non-fatal shooting victims: A victimization is considered a homicide victimization or non-fatal shooting victimization depending on its presence in CPD's homicide victims data table or its shooting victims data table. A victimization is considered a homicide only if it is present in CPD's homicide data table, while a victimization is considered a non-fatal shooting only if it is present in CPD's shooting data tables and absent from CPD's homicide data table.

To determine the IUCR code of homicide and non-fatal shooting victimizations, we defer to the incident IUCR code available in CPD's Crimes, 2001-present dataset (available on the City's open data portal). If the IUCR code in CPD's Crimes dataset is inconsistent with the homicide/non-fatal shooting categorization, we defer to CPD's Victims dataset.

For a criminal homicide, the only sensible IUCR codes are 0110 (first-degree murder) or 0130 (second-degree murder). For a non-fatal shooting, a sensible IUCR code must signify a criminal sexual assault, a robbery, or, most commonly, an aggravated battery. In rare instances, the IUCR code in CPD's Crimes and Victims dataset

Police beats in Chicago that were effective through December 18, 2012. The current police beats boundaries are always available at https://data.cityofchicago.org/d/aerh-rz74. The data can be viewed on the Chicago Data Portal with a web browser. However, to view or use the files outside of a web browser, you will need to use compression software and special GIS software, such as ESRI ArcGIS (shapefile) or Google Earth (KML or KMZ), is required.

Map of Crimes - 2001 to Present

This dataset was used by Chicago Police Department analysts to create the publicly available “Chicago Police Sentiment Dashboard” (https://home.chicagopolice.org/statistics-data/data-dashboards/sentiment-dashboard/). This online dashboard displays information related to how safe Chicago residents feel and how much trust they have in the police.

The dashboard and this dataset are updated monthly and users are able to view data citywide, as well as within the five detective areas and in each of the 22 districts. Users can sort this data based on year, month and location. Information is also available based on demographics, including age, sex, race, education and income level. The dashboard is meant to improve transparency as well as work toward compliance with the consent decree.

The first five columns indicate the type of organizational unit described by the records and which particular unit. Subsequent columns show either a safety or trust score for a demographic group. Scores are derived from responses to survey questions, with each response being a value that ranges from 0-10. Please note that Elucd trust and safety scores are NOT a percentage. A score of 65 means that average response to the questions is 6.5 out of 10. The final two columns show the time period in which the data were collected.

The dataset was created by our partner, Elucd (https://elucd.com), through delivering short surveys to Chicago residents through digital ads. See [https://home.chicagopolice.org/wp-content/uploads/2020/12/Dashboard_FAQ_11_25_20.pdf] for more information on the project.

This effort is one element of a Chicago Police Department reform process, governed by a consent decree executed between the Office of the Attorney General of the State of Illinois (OAG) and the City of Chicago. For more information on the consent decree, see https://www.chicago.gov/city/en/sites/police-reform/home/consent-decree.html.