Business licenses and building permits are required to operate a business in Chicago or to ensure that a building construction project conforms to the minimum standards of the Chicago Building Code. Currently the performance target for processing most business license types is approximately 15 days.

All restaurants and food stores selling perishable items are required to apply for a Retail Food License (RFL). This metric tracks the average number of days the Department of Business Affairs and Consumer Protection (BACP) takes to issue RFLs. The target response time for processing is within 15 days.

Limited Business Licenses (LBLs) are required for all Chicago businesses not specifically exempt from licensing requirements. This includes all business that provide services, or engage in office operations or general sales. Currently the performance target for processing Limited Business Licenses is 3 days.

A Bed and Breakfast License is required to rent out rooms in a home to overnight guests, and to provide a breakfast meal. Currently the performance target for processing Bed and Breakfast Licenses is 15 days.

FOIA requests received by Water as of May 1, 2010

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Note: As discussed in http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html, some trips in November-December 2014 are known to be missing. --Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Note: As discussed in http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html, some trips in 2015 are known to be missing. --Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

Chart of Taxi Trips and Fare Totals by Month

Taxi trips reported to the City of Chicago in its role as a regulatory agency. 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, and times are rounded to the nearest 15 minutes.

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.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html for further discussion of the approach to privacy in this dataset.

See http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/01/taxi-dataset-relaunch.html for discussion of significant changes in July 2019.

FOIA requests received by Ethics as of May 1, 2010

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.

Employees may be reimbursed for expenses through two mechanisms. This view shows mileage reimbursements through the payroll system. See https://data.cityofchicago.org/d/g5h3-jkgt for reimbursements of multiple types through direct vouchers.

Employees may be reimbursed for expenses through two mechanisms. This dataset shows reimbursements through the payroll system. See https://data.cityofchicago.org/d/g5h3-jkgt for reimbursements through direct vouchers.