NOTE, 11/21/2023: Please see the information below about the RD_NO column.

Crash data shows information about each traffic crash on city streets within the City of Chicago limits and under the jurisdiction of Chicago Police Department (CPD). Data are shown as is from the electronic crash reporting system (E-Crash) at CPD, excluding any personally identifiable information. Records are added to the data portal when a crash report is finalized or when amendments are made to an existing report in E-Crash. Data from E-Crash are available for some police districts in 2015, but citywide data are not available until September 2017. About half of all crash reports, mostly minor crashes, are self-reported at the police district by the driver(s) involved and the other half are recorded at the scene by the police officer responding to the crash. Many of the crash parameters, including street condition data, weather condition, and posted speed limits, are recorded by the reporting officer based on best available information at the time, but many of these may disagree with posted information or other assessments on road conditions. If any new or updated information on a crash is received, the reporting officer may amend the crash report at a later time. A traffic crash within the city limits for which CPD is not the responding police agency, typically crashes on interstate highways, freeway ramps, and on local roads along the City boundary, are excluded from this dataset.

All crashes are recorded as per the format specified in the Traffic Crash Report, SR1050, of the Illinois Department of Transportation. The crash data published on the Chicago data portal mostly follows the data elements in SR1050 form. The current version of the SR1050 instructions manual with detailed information on each data elements is available here.

As per Illinois statute, only crashes with a property damage value of $1,500 or more or involving bodily injury to any person(s) and that happen on a public roadway and that involve at least one moving vehicle, except bike dooring, are considered reportable crashes. However, CPD records every reported traffic crash event, regardless of the statute of limitations, and hence any formal Chicago crash dataset released by Illinois Department of Transportation may not include all the crashes listed here.

Change 11/21/2023: We have removed the RD_NO (Chicago Police Department report number) for privacy reasons.

Fire station locations

This dataset reflects the daily volume of violations created by the City of Chicago Red Light Program for each camera. The data reflects violations that occurred from July 1, 2014 until present, minus the most recent 14 days. This data may change due to occasional time lags between the capturing of a potential violation and the processing and determination of a violation. The most recent 14 days are not shown due to revised data being submitted to the City of Chicago during this period. The reported violations are those that have been collected by the camera system and reviewed by two separate City contractors. In some instances, due to the inability the registered owner of the offending vehicle, the violation may not be issued as a citation. However, this dataset contains all violations regardless of whether a citation was actually issued, which provides an accurate view into the Red Light Program. Because of occasional time lags between the capturing of a potential violation and the processing and determination of a violation, as well as the occasional revision of the determination of a violation, this data may change. More information on the Red Light Program can be found here: http://www.cityofchicago.org/city/en/depts/cdot/supp_info/red-light_cameraenforcement.html. The corresponding dataset for speed camera violations is https://data.cityofchicago.org/id/hhkd-xvj4.

NOTE, 11/21/2023: Please see the information below about the RD_NO column.

This dataset contains information about vehicles (or units as they are identified in crash reports) involved in a traffic crash. This dataset should be used in conjunction with the traffic Crash and People dataset available in the portal. “Vehicle” information includes motor vehicle and non-motor vehicle modes of transportation, such as bicycles and pedestrians. Each mode of transportation involved in a crash is a “unit” and get one entry here. Each vehicle, each pedestrian, each motorcyclist, and each bicyclist is considered an independent unit that can have a trajectory separate from the other units. However, people inside a vehicle including the driver do not have a trajectory separate from the vehicle in which they are travelling and hence only the vehicle they are travelling in get any entry here. This type of identification of “units” is needed to determine how each movement affected the crash. Data for occupants who do not make up an independent unit, typically drivers and passengers, are available in the People table. Many of the fields are coded to denote the type and location of damage on the vehicle. Vehicle information can be linked back to Crash data using the “CRASH_RECORD_ID” field. Since this dataset is a combination of vehicles, pedestrians, and pedal cyclists not all columns are applicable to each record. Look at the Unit Type field to determine what additional data may be available for that record.

The Chicago Police Department reports crashes on IL Traffic Crash Reporting form SR1050. The crash data published on the Chicago data portal mostly follows the data elements in SR1050 form. The current version of the SR1050 instructions manual with detailed information on each data elements is available here.

Change 11/21/2023: We have removed the RD_NO (Chicago Police Department report number) for privacy reasons.

NOTE, 11/21/2023: Please see the information below about the RD_NO column.

This data contains information about people involved in a crash and if any injuries were sustained. This dataset should be used in combination with the traffic Crash and Vehicle dataset. Each record corresponds to an occupant in a vehicle listed in the Crash dataset. Some people involved in a crash may not have been an occupant in a motor vehicle, but may have been a pedestrian, bicyclist, or using another non-motor vehicle mode of transportation. Injuries reported are reported by the responding police officer. Fatalities that occur after the initial reports are typically updated in these records up to 30 days after the date of the crash. Person data can be linked with the Crash and Vehicle dataset using the “CRASH_RECORD_ID” field. A vehicle can have multiple occupants and hence have a one to many relationship between Vehicle and Person dataset. However, a pedestrian is a “unit” by itself and have a one to one relationship between the Vehicle and Person table.

The Chicago Police Department reports crashes on IL Traffic Crash Reporting form SR1050. The crash data published on the Chicago data portal mostly follows the data elements in SR1050 form. The current version of the SR1050 instructions manual with detailed information on each data elements is available here.

Change 11/21/2023: We have removed the RD_NO (Chicago Police Department report number) for privacy reasons.

This dataset reflects the daily volume of violations that have occurred in Children's Safety Zones for each camera. The data reflects violations that occurred from July 1, 2014 until present, minus the most recent 14 days. This data may change due to occasional time lags between the capturing of a potential violation and the processing and determination of a violation. The most recent 14 days are not shown due to revised data being submitted to the City of Chicago. The reported violations are those that have been collected by the camera and radar system and reviewed by two separate City contractors. In some instances, due to the inability the registered owner of the offending vehicle, the violation may not be issued as a citation. However, this dataset contains all violations regardless of whether a citation was issued, which provides an accurate view into the Automated Speed Enforcement Program violations taking place in Children's Safety Zones. More information on the Safety Zone Program can be found here: http://www.cityofchicago.org/city/en/depts/cdot/supp_info/children_s_safetyzoneporgramautomaticspeedenforcement.html. The corresponding dataset for red light camera violations is https://data.cityofchicago.org/id/spqx-js37.

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.

Traffic fatalities within the City of Chicago that are included in Vision Zero Chicago (VZC) statistics. Vision Zero is Chicago’s commitment to eliminating fatalities and serious injuries from traffic crashes. The VZC Traffic Fatality List is compiled by the City’s multi-departmental Fatal Crash Response Coordination Committee (FCRCC) that reviews fatal traffic crashes provided by Chicago Police Department’s Major Accident Investigation Unit (MAIU). The dataset is updated after the FCRCC meetings in the 4th week of the month. Thus, the fatality list for a particular month will be available in the dataset after the 4th week of the following month.

This committee uses a standardized process – sometimes differing from other sources and everyday use of the term -- to determine whether a death is a “traffic fatality” for VZC purposes. Therefore, the traffic fatalities included in this list may differ from the fatal crashes reported in the full Traffic Crashes dataset (https://data.cityofchicago.org/d/85ca-t3if).

Official traffic crash data are published by the Illinois Department of Transportation (IDOT) on a yearly basis. The traffic fatality list determined on an ongoing basis through the year may differ from IDOT’s official crash data for Chicago as IDOT may define the cause and location differently from the FCRCC. Once IDOT publishes its data for a year, crashes in this dataset for that year are edited to match IDOT’s determinations, unless the FCRCC disagrees with the IDOT determination – which happens only rarely and usually due to an interpretation of one of the criteria below.

VZC Traffic Fatalities can be linked with other traffic crash datasets using the “RD_NO” or “Person_ID” fields.

The FCRCC defines a “traffic fatality” for the purpose of VZC statistics as "any death caused by a traffic crash, within 30 days of the crash” and “involves a motor vehicle.” Fatalities that meet the VZC definition of a traffic fatality are included in this dataset unless excluded by the criteria below. There may be records in this dataset that do not appear as fatalities in the other datasets.

The following criteria exclude a death from being considered a "traffic fatality" for VZC purposes:

1. The Medical Examiner determined that the primary cause of the fatality was not the traffic crash, including:

a. The fatality was reported as a suicide based on a police investigation.

b. The fatality was reported as a homicide in which the "party at fault" intentionally inflicted serious bodily harm that caused the victim's death.

c. The fatality was caused directly and exclusively by a medical condition or where the fatality was not attributable to road user movement on a public roadway. (Note: If a person driving suffers a medical emergency and consequently hit and kills another road user, the other road user is included although the driver suffering a medical emergency is excluded.)

2. The crash did not occur within the public right-of-way.

3. The crash involved a train or such mode of transport within their dedicated right-of-way.

4. The fatality was on a roadway not under Chicago Police Department jurisdiction, including:

a. The fatality was occurred on an expressway. The City of Chicago does not have oversight on the expressway system. However, a fatality on expressway ramps occurring within the City jurisdiction will be counted in Vision Zero Chicago Traffic Fatalities.

b. The fatality occurred outside City limits. Crashes on streets along the City boundary may be assigned to another jurisdiction after the investigation if it is determined that the crash started or substantially occurred on the side of the street that is outside the City limits. Jurisdiction of streets along the City boundary are split between City and neighboring jurisdictions along the street center line.

5. The fatality is not for a person (e.g., an animal).

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.

Chicago Public Schools, in partnership with parents, the Chicago Police Department (CPD) and City of Chicago, has expanded the District's successful Safe Passage Program to provide safe routes to and from school every day for your child. This map presents the Safe Passage Routes specifically designed for designated schools during the 2015-2016 school year. To view or use these shapefiles, compression software, such as 7-Zip, and special GIS software, such as Google Earth or ArcGIS, are required.

Locations of kits designed to assist City of Chicago employees and members of the public control severe bleeding in emergency situations while waiting for first responders with more advanced equipment and training to arrive. Always call 911 before locating and using a bleeding control kit.

The kits are placed in occupied buildings owned or leased by the City of Chicago, as part of the Safe Chicago project led by the Office of Emergency Management & Communications.

For more information on the Safe Chicago program, please see https://www.chicago.gov/city/en/depts/oem/supp_info/safe-chicago.html.

The safe passages program has been implemented to increase children’s safety as they come and go each day. 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 Safe Chicago Bleeding Control Kit Locations

Each record is an administrative notice of violation (ANOV), a citation issued for violating a Municipal Code of Chicago ordinance, issued by a Chicago Police Department (CPD) member. This dataset was used by CPD analysts to create an assessment report in support of a consent decree executed between the Office of the Attorney General of the State of Illinois (OAG) and the City of Chicago.

The CPD is currently engaged in a reform process, as governed by that consent decree. A consent decree is a written settlement resolving a legal dispute. The OAG/City of Chicago consent decree includes detailed requirements organized into 11 core areas (e.g., use of force, accountability and transparency), collectively designed to create organizational change within CPD. To review the consent decree and learn more about the process, see the City of Chicago’s police reform webpage:

This dataset is made available to the public pursuant to consent decree requirements described in Paragraph 79 and Paragraph 80.

Paragraph 79 of the consent decree states that:
By April 1, 2020, and every year thereafter, CPD will conduct an assessment of the relative frequency of all misdemeanor arrests and administrative notices of violation (“ANOVs”) effectuated by CPD members of persons in specific demographic categories, including race and gender.

Then, the last sentence of Paragraph 80 states that:
Upon completion of the assessment, CPD will publish the underlying data, excluding personal identifying information (e.g., name, address, contact information), via a publicly-accessible, web-based data platform.

This dataset was used by CPD analysts to create an assessment report pursuant to Paragraph 79. The report was designed to achieve compliance with Paragraph 79. Each record in the dataset shows information about an ANOV issued by a CPD member. An ANOV is a citation issued for violating a Municipal Code of Chicago ordinance. ANOV’s are adjudicated by the City of Chicago Department of Administrative Hearings (DOAH). ANOV data are owned and housed by the Department of Administrative Hearings. CPD receives a daily data extraction from the DOAH data system, whereupon ANOV data is ingested into the CPD data system.

To request the aforementioned report contact the CPD Freedom of Information Act Section at https://home.chicagopolice.org/information/freedom-of-information-act-foia..

NOV NUMBER is the record identifier for the dataset. Each record in the dataset is a unique, unduplicated citation.

Users interested in learning more about how CPD handles ANOV citations can review the current policy, using the CPD Automated Directives system (http://directives.chicagopolice.org/directives/). CPD Special Order S04-22, entitled “Municipal Administrative Hearings”, provides guidelines for CPD members when issuing an ANOV.