The Chicago Park District issues swim advisories at beaches along Chicago's Lake Michigan lakefront based on E. coli levels. This dataset shows predicted E. coli levels based on an experimental analytical modeling approach.

This dataset contains the current estimated speed for about 1250 segments covering 300 miles of arterial roads. For a more detailed description, go to: http://bit.ly/Q9AZAD.

The Chicago Traffic Tracker estimates traffic congestion on Chicago’s arterial streets (nonfreeway
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 ten minutes: 1) by Traffic Segments and 2) by Traffic Regions or Zones. Congestion estimate by traffic segments gives the 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).
This dataset contains the current estimated speed for about 1250 segments covering 300 miles of arterial roads.
There is much volatility in traffic segment speed. However, the congestion estimates for the traffic regions remain consistent for 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 the current estimated congestion for the 29 traffic regions. For a detailed description, go to: http://bitly.com/TeqrNv.

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 presents current and former locations of vehicles that have been relocated by the City of Chicago within the last 90 days. Vehicles may be relocated, but not impounded, due to inoperability, accident, severe weather, special events, construction or other work being performed in a thoroughfare where the vehicle was previously located.

Related Applications: Find Your Vehicle (http://j.mp/iZiX0B).

This dataset displays location for vehicles that have been towed and impounded by the City of Chicago within the last 90 days. Illegally parked vehicles, abandoned vehicles and vehicles used for illegal activities may be towed by the Chicago Police Department, the Department of Streets and Sanitation, the Department of Revenue, Aviation and the office of the City Clerk. After a tow request is issued, an inventory number is assigned by the Department of Streets and Sanitation and a truck is dispatched to tow the requested vehicle to a City auto pound. Disclaimer: This dataset includes vehicles towed or relocated by the City of Chicago; it does not include vehicles towed by a private towing company.

Background Information:
Auto Pound Locations (http://j.mp/kG5sgF).
Tow Process Overview (http://j.mp/lfBOEP).
Common Towing Questions (http://j.mp/imFYlp).
Parking and Standing Violations (http://j.mp/ifW8Uj).
Related Applications: Find Your Vehicle (http://j.mp/lWn0S7).

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.

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.

The Chicago Park District maintains sensors in the water 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/d/k7hf-8y75 for a dataset with land-based weather measurements at selected beaches. The sensor locations are listed at https://data.cityofchicago.org/d/g3ip-u8rb.

Please note that sensor locations change with the Park District’s operational needs, primarily related to water quality. For more information on beach operations, please see https://www.chicagoparkdistrict.com/parks-facilities/beaches.

311 Service Requests received by the City of Chicago. This dataset includes requests created after the launch of the new 311 system on 12/18/2018 and some records from the previous system, indicated in the LEGACY_RECORD column.

For purposes of all columns indicating geographic areas or locations, please note that requests of the type 311 INFORMATION ONLY CALL often are entered with the address of the City's 311 Center.

NOTE, 11/20/2018: Please see http://dev.cityofchicago.org/open%20data/data%20portal/2018/11/19/public-chauffeurs-changes.html for recent changes to this dataset -- 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.

The Chicago Park District collects and analyzes water samples from beaches along Chicago’s Lake Michigan lakefront. The Chicago Park District partners with the University of Illinois at Chicago Department of Public Health Laboratory to analyze water samples using a new DNA testing method called Rapid Testing Method (qPCR analysis) which tests for Enterococci in order to monitor swimming safety.

The rapid testing method (qPCR analysis) is a new method that measures levels of pathogenic DNA in beach water. Unlike the culture based test that requires up to 24 hours of processing, the new rapid testing method requires a 4-5 hours for results. The Chicago Park District can use results of the rapid test to notify the public when levels exceed UPEPA recommended levels, which is 1000* CCE. When DNA bacteria levels exceed 1000 CCE, a yellow swim advisory flag is implemented. For more information please refer to the USEPA Recreational Water Quality Criteria (http://water.epa.gov/scitech/swguidance/standards/criteria/health/recreation).

Historically, the Chicago Park District used the culture based analysis method and statistical prediction models to monitor beach water quality.
The culture based method tests for Escherichia coli (E. coli) bacteria which is an indicator species for the presence of disease-causing bacteria, viruses, and protozoans that may pose health risks to the public. This method requires 18-24 hours of processing to receive results. The Chicago Park District would use results of the culture based method to notify the public when levels exceed UPEPA recommended levels, which is 235* CFU. When bacteria levels exceed 235 CFU, a yellow swim advisory flag was implemented. This standard is still used at most beaches throughout the Great Lakes region. For more information please refer to the USEPA Recreational Water Quality Criteria.

The statistical prediction model forecasted real-time Escherichia coli (E. coli) bacteria levels present in the water. The Chicago Park District (CPD) in partnership with the US Geological Survey, developed statistical prediction models by using weather data pulled from CPD buoys (https://data.cityofchicago.org/d/qmqz-2xku) and weather stations (https://data.cityofchicago.org/d/k7hf-8y75). The Chicago Park District would use results of the predictive model to notify the public when bacteria levels would exceed 235 CFU. When bacteria levels exceed 235 CFU, a yellow swim advisory flag was implemented.

* The unit of measurement for Escherichia coli is Colony Forming Units (CFU) per 100 milliliters of water. (Culture Based Method / Statistical Prediction Model)
*The unit of measuring DNA is Enterococci Calibrator Cell Equivalents (CCE) per 100 milliliters of water. (Rapid Testing Analysis)

Street sweeping schedule by Ward and Ward section number. To find your Ward section, visit https://data.cityofchicago.org/d/7j9e-rz4v. For more information about the City's Street Sweeping program, go to http://bit.ly/H2PHUP.

Corrections are possible during the course of the sweeping season.

The Chicago Park District issues swim advisories at beaches along Chicago's Lake Michigan lakefront based on E. coli levels. This map shows predicted E. coli levels -- with bubble size corresponding to predicted level -- and whether the predicted E. coli level was at least 235 Colony Forming Units (CFU) per 100 ml of water (red bubbles).

This map updates daily and its predictions depend on data from https://data.cityofchicago.org/Parks-Recreation/Beach-Lab-Data/2ivx-z93u. It will show no predictions from midnight until the new day's predictions have been generated.

311 Service Requests received by the City of Chicago. This dataset includes requests created after the launch of the new 311 system on 12/18/2018 and some records from the previous system, indicated in the LEGACY_RECORD column.

For purposes of all columns indicating geographic areas or locations, please note that requests of the type 311 INFORMATION ONLY CALL often are entered with the address of the City's 311 Center.

This information is derived from payments made to City of Chicago employees from January 1 of the previous calendar year to the present. Payments are initiated by City Departments and issued by the Department of Finance. Descriptions of each attribute follow:

- Voucher Number: This is a unique number assigned to each payment and is used for identifying that particular payment.

- Amount: This is the dollar amount of the payment made.

- Payment Date: This is the date payment was issued.

- Vendor Name: This is the name of the person or entity to which payment was made.

- Description: This is an optional field that indicates the reason payment was made.

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

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