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 the delegate agencies with which the Department of Family and Support Services has contracted to provide services to residents of Chicago. For more information on the department and its services, please see http://www.cityofchicago.org/city/en/depts/fss.html.

This dataset contains the historical estimated congestion for the 29 traffic regions, from January 2013 to May 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. Current estimates of traffic congestion by region are available at http://bit.ly/103beCf.

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.

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.

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 “RD NO” field. Since this dataset is a combination of vehicles, pedestrians, and pedal cyclists not all columns are applicable to each record. Look at the Unity Type field to determine what additional data may be available for that record.

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. 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.

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 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 “RD NO” 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.

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.

Entities, individuals or both are subject to debarment. The following list provides info regarding entities or individuals, date of debarment, length of debarment and cause. Lifetime debarment pertains to individuals, permanent pertains to entities. In addition, this list also identifies individuals and entities that are ineligible to do business with the City pursuant to Section 1-23-020 of the Municipal Code, and Building Code Scofflaws ineligible to do business with the City pursuant to Section 2-92-416 of the Municipal Code.

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.

This dataset includes recommended positions and salaries for 2020 by title (without names) and salary. The dataset is excerpted from the 2020 Budget Recommendations, which is the line-item budget proposed by the Mayor to the City Council for approval. Disclaimer: the “Total Budgeted Unit” column displays either A) the number of employees AND vacancies associated with a given position, or B) the number of budgeted units (ie. hours/months) for that position. “Position Control” determines whether Total Budgeted Units column will count employees and vacancies or hours/months. If a Position Control is 1, then employees and vacancies are displayed; if a Position Control is 0, then the total number of hours/months recorded is displayed.

This dataset follows the format of the equivalent datasets from past years except that Section Code and Division Code have changed from Number to Text in order to accommodate non-numeric values.

For more information about the budget process, visit the Budget Documents page: http://j.mp/lPotWf.

The Annual Appropriation Ordinance is the final City operating budget as approved by the City Council. It reflects the City’s operating budget at the beginning of the fiscal year on January 1, 2017.

This dataset displays the positions and related salaries detailed in the budget as of January 1. It is extracted from the personnel portion of the Appropriation Ordinance. The dataset presents the position titles (without names) and salaries described in the budget, but does not provide a reflection of the current city workforce with full names and salaries.

Disclaimer: the “Total Budgeted Units” column displays either A) the number of employees AND vacancies associated with a given position, or B) the number of budgeted units (ie. hours/months) for that position. “Position Control” determines whether Total Budgeted Units column will count employees and vacancies or hours/months. If a Position Control is 1, then employees and vacancies are displayed; if a Position Control is 0, then the total number of hours/months recorded is displayed.

For information on the current city workforce, with names, positions and salaries, visit the "Current Employee Names, Salaries, and Position Titles" dataset: https://data.cityofchicago.org/d/xzkq-xp2w.

TIF Investment Committee (TIC) data includes all projects reviewed by the TIF Investment Committee, since May, 2019. This includes all requests for TIF funding, including TIF-funded public infrastructure projects from the City departments and Sister Agencies, as well as private-sector housing and economic development projects. TIF is a special funding tool used by the City of Chicago to promote public and private investment across the city. Projects must be located on parcels within an active TIF district to be eligible.