This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that occurred in the City of Chicago from 2001 to present, minus the most recent seven days. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at 312.745.6071 or RDAnalysis@chicagopolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data are updated daily. The dataset contains more than 65,000 records/rows of data and cannot be viewed in full in Microsoft Excel. Therefore, when downloading the file, select CSV from the Export menu. Open the file in an ASCII text editor, such as Wordpad, to view and search. To access a list of Chicago Police Department - Illinois Uniform Crime Reporting (IUCR) codes, go to http://data.cityofchicago.org/Public-Safety/Chicago-Police-Department-Illinois-Uniform-Crime-R/c7ck-438e

This dataset is a listing of all current City of Chicago employees, complete with full names, departments, positions, employment status (part-time or full-time), frequency of hourly employee –where applicable—and annual salaries or hourly rate. For hourly employees, the City is providing the hourly rate and frequency of hourly employees (40, 35, 20 and 10) to allow dataset users to estimate annual wages for hourly employees. Please note that annual wages will vary by employee, depending on number of hours worked and seasonal status. For information on the positions and related salaries detailed in the annual budgets, see https://www.cityofchicago.org/city/en/depts/obm.html

Historical availability of bicycles and docks to return bicycles at the Divvy stations (http://divvybikes.com/).  For the full data, see the bottom of this page or https://data.cityofchicago.org/d/eq45-8inv.

For the current list of stations, see https://data.cityofchicago.org/d/bbyy-e7gq For real-time status of stations in machine-readable format, see http://divvybikes.com/stations/json.

In the Percent Full column, N/A (denominator is zero) values are indicated by either blank or -1.

This information is derived from inspections of restaurants and other food establishments in Chicago from January 1, 2010 to the present. Inspections are performed by staff from the Chicago Department of Public Health’s Food Protection Program using a standardized procedure. The results of the inspection are inputted into a database, then reviewed and approved by a State of Illinois Licensed Environmental Health Practitioner (LEHP). For descriptions of the data elements included in this set, go to http://bit.ly/tS9IE8
Disclaimer:  Attempts have been made to minimize any and all duplicate inspection reports. However, the dataset may still contain such duplicates and the appropriate precautions should be exercised when viewing or analyzing these data. The result of the inspections (pass, pass with conditions or fail) as well as the violations noted are based on the findings identified and reported by the inspector at the time of the inspection, and may not reflect the findings noted at other times. For more information about Food Inspections, go to http://bit.ly/tD91Sb.

This dataset contains the historical estimated congestion for over 1,000 traffic segments, starting in approximately March 2018.

The Chicago Traffic Tracker estimates traffic congestion on Chicago’s arterial streets (non-freeway streets) in real-time by continuously monitoring and analyzing GPS traces received from Chicago Transit Authority (CTA) buses. Two types of congestion estimates are produced every 10 minutes: 1) by Traffic Segments and 2) by Traffic Regions or Zones. Congestion estimates by traffic segments gives observed speed typically for one-half mile of a street in one direction of traffic. Traffic Segment level congestion is available for about 300 miles of principal arterials.

Congestion by Traffic Region gives the average traffic condition for all arterial street segments within a region. A traffic region is comprised of two or three community areas with comparable traffic patterns. 29 regions are created to cover the entire city (except O’Hare airport area). There is much volatility in traffic segment speed. However, the congestion estimates for the traffic regions remain consistent for a relatively longer period. Most volatility in arterial speed comes from the very nature of the arterials themselves. Due to a myriad of factors, including but not limited to frequent intersections, traffic signals, transit movements, availability of alternative routes, crashes, short length of the segments, etc. Speed on individual arterial segments can fluctuate from heavily congested to no congestion and back in a few minutes.

The segment speed and traffic region congestion estimates together may give a better understanding of the actual traffic conditions.

Taxi trips reported to the City of Chicago in its role as a regulatory agency. For the full data, see the bottom of this page or https://data.cityofchicago.org/d/wrvz-psew.

To protect privacy but allow for aggregate analyses:

- The Taxi ID is consistent for any given taxi medallion number but does not show the number.

- Census Tracts are suppressed in some cases.

- Times are rounded to the nearest 15 minutes.

Trip Total, which is used on some cards below, is the total paid, although cash tips do not appear in either that column or the Tips column.

Due to the data reporting process, not all trips are reported but the City believes that most are.

See http://digital.cityofchicago.org/index.php/chicago-taxi-data-released for more information about this dataset and how it was created.

Summary of individual Divvy bike sharing trips, including the origin, destination, and timestamps for each trip. Trips are included when there is an starting and end date.

Trips using a subscriber pass will include some basic demographic data (gender and age) that is associated with the account.  To see only subscriber trips, click the "Subscriber" column on the "Number of Trips by USER TYPE" card.

For more information see https://www.divvybikes.com/data

The information displayed represents a de-identified listing of arrest data from August 1, 2012 to July 31, 2016, that is used by the Chicago Police Department’s Strategic Subject Algorithm, created by the Illinois Institute of Technology and funded through a Department of Justice Bureau of Justice Assistance grant, to create a risk assessment score known as the Strategic Subject List or “SSL.” These scores reflect an individual’s probability of being involved in a shooting incident either as a victim or an offender. Scores are calculated and placed on a scale ranging from 0 (extremely low risk) to 500 (extremely high risk).

Based on this time frame’s version of the Strategic Subject Algorithm, individuals with criminal records are ranked using eight attributes, not including race or sex. These attributes are: number of times being the victim of a shooting incident, age during the latest arrest, number of times being the victim of aggravated battery or assault, number of prior arrests for violent offenses, gang affiliation, number of prior narcotic arrests, trend in recent criminal activity and number of prior unlawful use of weapon arrests.

Please note that this data set includes fields that are not used to calculate SSL, for example, neither race nor sex are used in the Strategic Subject Algorithm. Portions of the arrest data are de-identified on the basis of privacy concerns. The attributes used in the Strategic Subject Algorithm are updated as the model is revised on an ongoing basis. The data set below will be updated periodically to reflect these revisions. 

A list of buildings excluded from short-term rental activity under the Shared Housing Ordinance.

See https://www.cityofchicago.org/city/en/depts/bacp/provdrs/bus/alerts/2016/july/Prohibited_Buildings_List_Affidavit.html for more information on the exclusion process.

Applications to the Chicago Department of Transportation for permits under its jurisdiction, which typically are permits to block or otherwise affect public streets in some way. Because all permits start as applications, this dataset also serves as a list of permits granted.

See more information about CDOT permits at http://www.cityofchicago.org/city/en/depts/cdot/provdrs/construction_information/svcs/online-permit-portal.html.

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

The (No value) bars below come from Bureau of Internal Affairs records. Other than identifying the Log Number associated with an investigation being conducted by the BIA section of the Chicago Police Department, information regarding such investigations is not included in this data set.

Cases received by the Civilian Office of Police Accountability and its predecessor agencies.

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.

The (No value) bars below come from Bureau of Internal Affairs records. Other than identifying the Log Number associated with an investigation being conducted by the BIA section of the Chicago Police Department, information regarding such investigations is not included in this data set.

Cases received by the Civilian Office of Police Accountability and its predecessor agencies.

A case will generate multiple rows, sharing the same LOG_NO if there are multiple reported victims. Each row in this dataset is a reported victim in a specific case.

The (No value) bars below come from Bureau of Internal Affairs records. Other than identifying the Log Number associated with an investigation being conducted by the BIA section of the Chicago Police Department, information regarding such investigations is not included in this data set.