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.

List of City of Chicago licensed Public Chauffeurs, who may operate a licensed Taxicab, Livery, or Horse-Drawn Carriage. For questions or issues regarding this dataset, please e-mail BACPPV@cityofchicago.org with chauffeur name, number, and question or issue. For more information on the Public Chauffeur program, please see http://www.cityofchicago.org/city/en/depts/bacp/supp_info/public_chauffeurinformation.html.

This is the place to look for important information about how to use this dataset, so please expand this box and read on!

This is the source data for some of the metrics available at https://www.chicago.gov/city/en/sites/covid-19/home/latest-data.html.

For all datasets related to COVID-19, see https://data.cityofchicago.org/browse?limitTo=datasets&sortBy=alpha&tags=covid-19.

Only Chicago residents are included based on the home ZIP Code, as provided by the medical provider, or the address, as provided by the Cook County Medical Examiner.

Cases with a positive molecular (PCR) or antigen test are included in this dataset. Cases are counted on the date the test specimen was collected. Deaths are those occurring among cases based on the day of death. Hospitalizations are based on the date of first hospitalization. Only one hospitalization is counted for each case. Demographic data are based on what is reported by medical providers or collected by CDPH during follow-up investigation.

Because of the nature of data reporting to CDPH, hospitalizations will be blank for recent dates They will fill in on later updates when the data are received, although, as for cases and deaths, may continue to be updated as further data are received.

All data are provisional and subject to change. Information is updated as additional details are received and it is, in fact, very common for recent dates to be incomplete and to be updated as time goes on. At any given time, this dataset reflects data currently known to CDPH.

Numbers in this dataset may differ from other public sources due to definitions of COVID-19-related cases, deaths, and hospitalizations, sources used, how cases, deaths and hospitalizations are associated to a specific date, and similar factors.

Data Source: Illinois National Electronic Disease Surveillance System, Cook County Medical Examiner’s Office

Description: Pursuant to the Sex Offender and Child Murderer Community Notification Law, 730 ILCS 152/101,et seq., the Chicago Police Department maintains a list of sex offenders residing in the City of Chicago who are required to register under the Sex Offender Registration Act, 730 ILCS 150/2, et seq. To protect the privacy of the individuals, addresses are shown at the block level only and specific locations are not identified. The data are extracted from the CLEAR (Citizen Law Enforcement Analysis and Reporting) system developed by the Department.
Although every effort is made to keep this list accurate and current, the city cannot guarantee the accuracy of this information. Offenders may have moved and failed to notify the Chicago Police Department as required by law. If any information presented in this web site is known to be outdated, please contact the Chicago Police Department at srwbmstr@chicagopolice.org, or mail to Sex Registration Unit, 3510 S Michigan Ave, Chicago, IL 60653.
Disclaimer: This registry is based upon the legislature's decision to facilitate access to publicly available information about persons convicted of specific sexual offenses. The Chicago Police Department has not considered or assessed the specific risk of re-offense with regard to any individual prior to his or her inclusion within this registry, and has made no determination that any individual included within the registry is currently dangerous. Individuals included within this registry are included solely by virtue of their conviction record and Illinois law. The main purpose of providing this data on the internet is to make the information more available and accessible, not to warn about any specific individual.

Anyone who uses information contained in the Sex Offender Database to commit a criminal act against another person is subject to criminal prosecution.
Data Owner: Chicago Police Department.
Frequency: Data is updated daily.
Related Applications: CLEARMAP (http://j.mp/lLluSa).

This is the place to look for important information about how to use this dataset, so please expand this box and read on!

This is the source data for some of the metrics available at https://www.chicago.gov/city/en/sites/covid-19/home/latest-data.html.

For all datasets related to COVID-19, see https://data.cityofchicago.org/browse?limitTo=datasets&sortBy=alpha&tags=covid-19.

Only Chicago residents are included based on the home ZIP Code as provided by the medical provider. If a ZIP was missing or was not valid, it is displayed as "Unknown".

Cases with a positive molecular (PCR) or antigen test are included in this dataset. Cases are counted based on the week the test specimen was collected. For privacy reasons, until a ZIP Code reaches five cumulative cases, both the weekly and cumulative case counts will be blank. Therefore, summing the “Cases - Weekly” column is not a reliable way to determine case totals. Deaths are those that have occurred among cases based on the week of death.

For tests, each test is counted once, based on the week the test specimen was collected. Tests performed prior to 3/1/2020 are not included. Test counts include multiple tests for the same person (a change made on 10/29/2020). PCR and antigen tests reported to Chicago Department of Public Health (CDPH) through electronic lab reporting are included. Electronic lab reporting has taken time to onboard and testing availability has shifted over time, so these counts are likely an underestimate of community infection.

The “Percent Tested Positive” columns are calculated by dividing the number of positive tests by the number of total tests . Because of the data limitations for the Tests columns, such as persons being tested multiple times as a requirement for employment, these percentages may vary in either direction from the actual disease prevalence in the ZIP Code.

All data are provisional and subject to change. Information is updated as additional details are received.

To compare ZIP Codes to Chicago Community Areas, please see http://data.cmap.illinois.gov/opendata/uploads/CKAN/NONCENSUS/ADMINISTRATIVE_POLITICAL_BOUNDARIES/CCAzip.pdf. Both ZIP Codes and Community Areas are also geographic datasets on this data portal.

Data Source: Illinois National Electronic Disease Surveillance System, Cook County Medical Examiner’s Office, Illinois Vital Records, American Community Survey (2018)

All trips, from November 2018 to December 2022, reported by Transportation Network Providers (sometimes called rideshare companies) to the City of Chicago as part of routine reporting required by ordinance.

Census Tracts are suppressed in some cases, and times are rounded to the nearest 15 minutes. Fares are rounded to the nearest $2.50 and tips are rounded to the nearest $1.00.

For a discussion of the approach to privacy in this dataset, please see http://dev.cityofchicago.org/open%20data/data%20portal/2019/04/12/tnp-taxi-privacy.html.

This dataset contains the historical estimated congestion for over 1,000 traffic segments, starting in approximately March 2018. Older records are in https://data.cityofchicago.org/d/77hq-huss. The most recent estimates for each segment are in https://data.cityofchicago.org/d/n4j6-wkkf.

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.

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.

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

Each complaint is represented by a single line. When multiple people are involved, values for each of them are separated by the | character. In all such columns, the people are presented in the same order. For example, the first value in one column corresponds to the same person as the first value in another column.

Other than identifying the Log Number associated with an investigation being conducted by the Bureau of Internal Affairs section of the Chicago Police Department, information regarding such investigations is not included in this data set.

This dataset contains the historical estimated congestion for the 29 traffic regions, starting in approximately March 2018. Older records are in https://data.cityofchicago.org/d/emtn-qqdi. The most recent estimates for each segment are in https://data.cityofchicago.org/d/t2qc-9pjd.

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.

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

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.

As described in http://bit.ly/311HistoricalPost, the function of this dataset was replaced by https://data.cityofchicago.org/d/v6vf-nfxy. This dataset is historical-only.

This dataset contains all open 311 reports of one or two lights out on metal poles on a residential or arterial street and all completed requests since January 1, 2011. Whenever CDOT receives a report of a street light outage, the electrician assigned to make the repair looks at all the lights in a group (circuit) to make sure that they are working properly. If two requests regarding the same group are made within 30 calendar days of each other, the newest CSR is automatically given the status of “Duplicate (Open).” Since the electrician will be looking at all the lights in a group to verify that they are all working the “Duplicate (Open)” address will also be observed and repaired. Once the street lights are repaired, the CSR status will read “Completed” for the original request and “Duplicate (Closed)” for any duplicate requests. Data is updated daily.

The Chicago Park District maintains weather sensors at beaches along Chicago's Lake Michigan lakefront. These sensors generally capture the indicated measurements hourly while the sensors are in operation during the summer. During other seasons and at some other times, information from the sensors may not be available. See https://data.cityofchicago.org/id/qmqz-2xku for a dataset with similar measurements on the lake water, itself. The sensor locations are listed at https://data.cityofchicago.org/d/g3ip-u8rb.

This lists 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. For more information see https://ride.divvybikes.com/system-data.

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.

This dataset contains the historical estimated congestion for 1270 traffic segments, in selected time periods from August 2011 to May 2018. Newer records are in https://data.cityofchicago.org/d/sxs8-h27x. The most recent estimates for each segment are in https://data.cityofchicago.org/d/n4j6-wkkf.

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

The Chicago Building Energy Use Benchmarking Ordinance calls on existing municipal, commercial, and residential buildings larger than 50,000 square feet to track whole-building energy use, report to the City annually, and verify data accuracy every three years. The law, which was phased in from 2014-2017, covers less than 1% of Chicago’s buildings, which account for approximately 20% of total energy used by all buildings. For more details, including ordinance text, rules and regulations, and timing, please visit www.CityofChicago.org/EnergyBenchmarking

The ordinance authorizes the City to share property-specific information with the public, beginning with the second year in which a building is required to comply.

The dataset represents self-reported and publicly-available property information by calendar year. Currently, the data includes calendar year 2014 information for 243 properties, calendar year 2015 information for over 1,500 properties, calendar year 2016 information for over 2,700 properties, and calendar year 2017 information for almost 2,800 properties.

The "Data Year" column and filtered views under "More Views" can be used to isolate specific years.

This is the place to look for important information about how to use this dataset, so please expand this box and read on!

This is the source data for some of the metrics available at https://www.chicago.gov/city/en/sites/covid-19/home/latest-data.html.

For all datasets related to COVID-19, see https://data.cityofchicago.org/browse?limitTo=datasets&sortBy=alpha&tags=covid-19.

This dataset is a companion to the COVID-19 Daily Cases and Deaths dataset (https://data.cityofchicago.org/d/naz8-j4nc). The major difference in this dataset is that the case, death, and hospitalization corresponding rates per 100,000 population are not those for the single date indicated. They are rolling averages for the seven-day period ending on that date. This rolling average is used to account for fluctuations that may occur in the data, such as fewer cases being reported on weekends, and small numbers. The intent is to give a more representative view of the ongoing COVID-19 experience, less affected by what is essentially noise in the data.

All rates are per 100,000 population in the indicated group, or Chicago, as a whole, for “Total” columns.

Only Chicago residents are included based on the home address as provided by the medical provider.

Cases with a positive molecular (PCR) or antigen test are included in this dataset. Cases are counted based on the date the test specimen was collected. Deaths among cases are aggregated by day of death. Hospitalizations are reported by date of first hospital admission. Demographic data are based on what is reported by medical providers or collected by CDPH during follow-up investigation.

Denominators are from the U.S. Census Bureau American Community Survey 1-year estimate for 2018 and can be seen in the Citywide, 2018 row of the Chicago Population Counts dataset (https://data.cityofchicago.org/d/85cm-7uqa).

All data are provisional and subject to change. Information is updated as additional details are received and it is, in fact, very common for recent dates to be incomplete and to be updated as time goes on. At any given time, this dataset reflects cases and deaths currently known to CDPH.

Numbers in this dataset may differ from other public sources due to definitions of COVID-19-related cases and deaths, sources used, how cases and deaths are associated to a specific date, and similar factors.

Data Source: Illinois National Electronic Disease Surveillance System, Cook County Medical Examiner’s Office, U.S. Census Bureau American Community Survey

NOTE, 3/30/2023: We have added columns for bivalent (updated) doses to this dataset. We have also added age group columns for 0-17 and 18-64 and stopped updating the 5+ and 12+ columns, although previously published values remain for those columns.

COVID-19 vaccinations administered to Chicago residents based on the home ZIP Code of the person vaccinated, as provided by the medical provider in the Illinois Comprehensive Automated Immunization Registry Exchange (I-CARE). The ZIP Code where a person lives is not necessarily the same ZIP Code where the vaccine was administered.

Definitions:
·People with at least one vaccine dose: Number of people who have received at least one dose of any COVID-19 vaccine, including the single-dose Johnson & Johnson COVID-19 vaccine.

·People with a completed vaccine series: Number of people who have completed a primary COVID-19 vaccine series. Requirements vary depending on age and type of primary vaccine series received.

·People with a bivalent dose: Number of people who received a bivalent (updated) dose of vaccine. Updated, bivalent doses became available in Fall 2022 and were created with the original strain of COVID-19 and newer Omicron variant strains.

·Total doses administered: Number of all COVID-19 vaccine doses administered.

Data Notes:
Daily counts are shown for the total number of doses administered, number of people with at least one vaccine dose, number of people who have a completed vaccine series, and number of people who have received a bivalent dose. Cumulative totals for each measure as of that date are also provided. Vaccinations are counted based on the day the vaccine was administered.

Coverage percentages are calculated based on cumulative number of people who have received at least one vaccine dose, cumulative number of people who have a completed vaccine series, and cumulative number of people who have received a bivalent dose in each ZIP Code.

Population counts are from the U.S. Census Bureau American Community Survey 2015-2019 5-year estimates and can be seen in the ZIP Code, 2019 rows of the Chicago Population Counts dataset (https://data.cityofchicago.org/d/85cm-7uqa).

Actual counts may exceed population estimates and lead to >100% coverage, especially in areas with small population sizes. Additionally, the medical provider may report a work address or incorrect home address for the person receiving the vaccination which may lead to over or under estimates of vaccination coverage by geography. 

All data are provisional and subject to change. Information is updated as additional details are received and it is, in fact, very common for recent dates to be incomplete and to be updated as time goes on. At any given time, this dataset reflects data currently known to CDPH.

Numbers in this dataset may differ from other public sources due to when data are reported and how City of Chicago boundaries are defined.

For all datasets related to COVID-19, see https://data.cityofchicago.org/browse?limitTo=datasets&sortBy=alpha&tags=covid-19.

Data Source: Illinois Comprehensive Automated Immunization Registry Exchange (I-CARE), U.S. Census Bureau American Community Survey

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

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.

Other than identifying the Log Number associated with an investigation being conducted by the Bureau of Internal Affairs section of the Chicago Police Department, information regarding such investigations is not included in this data set.

COVID-19 vaccinations administered to Chicago residents based on home address, as reported by medical providers in the Illinois Comprehensive Automated Immunization Registry Exchange (I-CARE). I-CARE includes doses administered in Illinois and some doses administered outside of Illinois and reported in I-CARE by Illinois providers.

Definitions:
·People with at least one vaccine dose: Number of people who have received at least one dose of any COVID-19 vaccine, including the single-dose Johnson & Johnson COVID-19 vaccine.

·People with a completed vaccine series: Number of people who have completed a primary COVID-19 vaccine series. Requirements vary depending on age and type of primary vaccine series received.

·People with an original booster dose: Number of people who have a completed vaccine series and have received at least one additional monovalent dose. This includes people who received a monovalent booster dose and immunocompromised people who received an additional primary dose of COVID-19 vaccine. Monovalent doses were created from the original strain of the virus that causes COVID-19.

·People with a bivalent dose: Number of people who received a bivalent (updated) dose of vaccine. Updated, bivalent doses became available in Fall 2022 and were created with the original strain of COVID-19 and newer Omicron variant strains.

·Total doses administered: Number of all COVID-19 vaccine doses administered.

Daily counts are shown for the total number of doses administered, number of people with at least one vaccine dose, number of people who have a completed vaccine series, number of people with a monovalent booster dose, and number of people with a bivalent dose. Cumulative totals are also provided for each measure as of that date. Vaccinations are counted based on the day the vaccine was administered.

Coverage percentages for the City of Chicago are calculated based on cumulative number of people with that vaccination status.

Daily totals of all doses, number of people with at least one vaccine dose, number of people who have completed a vaccine series, number of people with a booster dose, and number of people with a bivalent dose are shown by age group, gender, and race/ethnicity.

Denominators are from the U.S. Census Bureau American Community Survey 1-year estimate for 2019 and can be seen in the Citywide, 2019 row of the Chicago Population Counts dataset (https://data.cityofchicago.org/d/85cm-7uqa).

The Chicago Department of Health (CDPH) uses the most complete data available to estimate COVID-19 vaccination coverage among Chicagoans, but there are several limitations that impact our estimates. Data reported in I-CARE only include doses administered in Illinois and some doses administered outside of Illinois reported historically by Illinois providers. Doses administered by the federal Bureau of Prisons and Department of Defense, are also not currently reported in I-CARE. The Veterans Health Administration began reporting doses in I-CARE beginning September 2022. Due to people receiving vaccinations that are not recorded in I-CARE that can be linked to their record, such as someone receiving a vaccine dose in another state, the number of people with a completed series or a booster dose is underestimated. Inconsistencies in records of separate doses administered to the same person, such as slight variations in dates of birth, can result in duplicate first dose records for a person and overestimate of the number of people with at least one dose and underestimate the number of people with a completed series or booster dose.

All data are provisional and subject to change. Information is updated as additional details are received and it is, in fact, very common for recent dates to be incomplete and to be updated as time goes on. At any given time, this dataset reflects data currently known to CDPH.

Numbers in this dataset may differ from other public sources due to when data are reported and how vaccination

Street sweeping schedule by Ward and Ward section number. To find your Ward section, visit https://data.cityofchicago.org/d/m245-s86v. For more information about the City's Street Sweeping program, go to https://www.chicago.gov/city/en/depts/streets/provdrs/streets_san/svcs/street_sweeping2020.html.

Corrections are possible during the course of the sweeping season.

Population totals for groupings commonly used in other datasets.

Not all values are available for all years.

Note that because the "Citywide" rows roll up the values from the individual ZIP Codes and the "Age 0-4," "Age 5-11," "Age 12-17," "Age 5+," "Age 18+," and "Age 65+" columns overlap other age categories, as well as each other in some cases, care should be taken in summing values to avoid accidental double-counting. The "Age 5-11" and "Age 12-17" columns only include children who live in households.

Data Sources: U.S. Census Bureau American Community Survey (ACS) 5-year estimates (ZIP Code) and 1-year estimates (Citywide). The U.S. Census Bureau did not release standard 1-year estimates from the 2020 ACS. In 2020 only, 5-year estimates were used for the Citywide estimates.

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

A case will generate multiple rows, sharing the same LOG_NO if there are multiple complainants or subjects. Each row in this dataset is a complainant or subject in a specific case.

Other than identifying the Log Number associated with an investigation being conducted by the Bureau of Internal Affairs section of the Chicago Police Department, information regarding such investigations is not included in this data set.