List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored or supported by the Chicago Department of Public Health.

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored or supported by the Chicago Department of Public Health.

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

List of public events sponsored by the Chicago Department of Public Health

The Chicago Park District issues swim advisories at beaches along Chicago's Lake Michigan lakefront based on predicted E. coli levels. This dataset shows the predictions and whether a swim advisory was issued due to the predicted E. coli level being at least 235 Colony Forming Units (CFU) per 100 ml of water.
The data used to make the predictions can be found in https://data.cityofchicago.org/d/qmqz-2xku and https://data.cityofchicago.org/d/k7hf-8y75. The measured E. coli levels determined later can be found in https://data.cityofchicago.org/d/2ivx-z93u.

This dataset is historical-only. A similar dataset starting in 2017 can be found at https://data.cityofchicago.org/d/xvsz-3xcj -- The Chicago Park District issues swim advisories at beaches along Chicago's Lake Michigan lakefront based on predicted E. coli levels. This dataset shows the predictions and whether a swim advisory was issued due to the predicted E. coli level being at least 235 Colony Forming Units (CFU) per 100 ml of water.

The data used to make the predictions can be found in https://data.cityofchicago.org/d/qmqz-2xku and https://data.cityofchicago.org/d/k7hf-8y75. The measured E. coli levels determined later can be found in https://data.cityofchicago.org/d/2ivx-z93u.

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.

This dataset contains individual-level homicide and non-fatal shooting victimizations, including homicide data from 1991 to the present, and non-fatal shooting data from 2010 to the present (2010 is the earliest available year for shooting data). 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-access dataset, but with "UNKNOWN" in the shooting column.

Each row represents a single victimization, i.e., a unique event when an individual became the victim of a homicide or non-fatal shooting. Each row does not represent a unique victim—if someone is victimized multiple times there will be multiple rows for each of those distinct events.

The dataset is refreshed daily, but excludes the most recent complete day to allow the Chicago Police Department (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.

A version of this dataset with additional crime types is available by request. To make a request, please email dataportal@cityofchicago.org with the subject line: Violence Reduction Victims Access Request. Access will require an account on this site, which you may create at https://data.cityofchicago.org/signup.

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 do not align with the homicide/non-fatal shooting categorization:

1. In instances where a homicide victimization does not correspond to an IUCR code 0110 or 0130, we set the IUCR code to "01XX" to indicate that the victimization was a homicide but we do not know whether it was a first-degree murder

Number of employees in each department or sister agency who owe funds to the City. For each department, the dataset provides the following as of the date noted: total number of individuals employed by the department or agency, number of individuals that owe funds to the City in the department; and the total amount of debt owed by those employees. Data Owner: Revenue. Time Period: mid-October 2011 to present. Frequency: Data is updated weekly.

INFORMATION ABOUT 7/12/2019 CHANGES TO THIS DATASET: http://bit.ly/2XV3ERS -- This dataset includes information about currently-valid building permits issued by the City of Chicago from 2006 to the present. Building permits are issued subject to payment of applicable fees. If building or zoning permit fees show as unpaid, the permit is not valid. (A permit is valid if only “other fees” are shown as unpaid.) This dataset does not include permits which have been issued and voided or revoked. This dataset also does not include permits for mechanical amusement riding devices and carnivals issued by the Department of Buildings.

Property Index Numbers (PINs) and geographic information (ward, community area and census tract) are provided for most permit types issued in 2008 or later.

For more information on building permits, see https://www.chicago.gov/city/en/depts/bldgs/provdrs/permits.html.

For an application related to building permits and inspections, see https://webapps1.chicago.gov/buildingrecords.

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.