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)

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.

Historical availability of bicycles and docks to return bicycles at the Divvy stations (http://divvybikes.com/). For the current list of stations, see https://data.cityofchicago.org/d/bbyy-e7gq For real-time status of stations in machine-readable format, see https://feeds.divvybikes.com/stations/stations.json.

Due to a change in the data source, discussed at http://dev.cityofchicago.org/open%20data/data%20portal/2019/07/10/divvy-datasets-frozen.html, records between 7/7/2019 and 12/9/2019 are missing.

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

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

NOTE, 10/17/2019: As of 9/30/2019, the sensors are undergoing a hardware upgrade. No new data are being collected or loaded to this dataset until they come back into service later this year. This is discussed in http://dev.cityofchicago.org/open%20data/data%20portal/2019/10/17/beach-weather-stations-down.html. -- 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.

Vacant and abandoned building violations issued on properties owned by financial institutions since January 1, 2011. Each violation is tied to a Docket Number. A Docket may have more than one violation associated with it. Fees are assessed based on all violations associated with a particular Docket. This dataset displays the most recent action (disposition description) for each violation, the fees and fines associated with the docket and the amount paid or outstanding for the docket. If the docket is a City Non-Suit or the owner is found to be Not Liable, then no payment is required. Note that multiple addresses may be associated with a violation; in these cases, multiple records will be included in this dataset for a single violation. / Data Owners: Administrative Hearings / Finance / Time Period: January 1, 2011 to present / Update Frequency: Data is updated daily

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.

Pro forma invoices with required receipt numbers for submission to Department of Housing and Economic Development.

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.

List of ordinance violations filed with the Department of Administrative Hearings. This data set reflects violations brought before the Chicago Department of Administrative Hearings. It does not reflect violations brought before the Circuit Court of Cook County. Each row of data represents a unique violation. Multiple violations may be associated with a single case. The most recent status of the case is shown in the dataset and is updated daily. Hearing date corresponds to the date of the most recent hearing. Each case often consists of multiple hearings and may encounter continuances due to various circumstances before a final disposition is rendered. The case disposition, date of the disposition, and any applicable fines and administrative costs are listed when the case is fully completed. The latest hearing status or disposition reflects the condition of the property at that time and may not reflect the current condition of the property. When multiple respondents are cited, each respondent is separated by a pipe ("|") character. Respondents sometimes are added to cases for technical legal reasons so are not necessarily the parties believed to have committed the violations. This dataset currently lists violations issued by the Department of Buildings. Additional ordinance violations will be added over time. Therefore, it is advisable to use the department-specific filtered view listed under the More Views button for purposes that require only one department's violations.

This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that occurred in the City of Chicago from 2001 to present, minus the most recent seven days. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at PSITAdministration@ChicagoPolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data are updated daily. To access a list of Chicago Police Department - Illinois Uniform Crime Reporting (IUCR) codes, go to http://data.cityofchicago.org/Public-Safety/Chicago-Police-Department-Illinois-Uniform-Crime-R/c7ck-438e

A list of the stations currently in service where one can pick up and return bicycles from the Divvy bicycle sharing system (http://divvybikes.com/). For real-time status of stations in machine-readable format, see https://gbfs.divvybikes.com/gbfs/gbfs.json.

A list of the stations currently in service where one can pick up and return bicycles from the Divvy bicycle sharing system (http://divvybikes.com/). For real-time status of stations in machine-readable format, see https://gbfs.divvybikes.com/gbfs/gbfs.json.

A list of the stations where one can pick up and return bicycles from the Divvy bicycle sharing system (http://divvybikes.com/). For real-time status of stations in machine-readable format, see https://gbfs.divvybikes.com/gbfs/gbfs.json.

A list of the stations where one can pick up and return bicycles from the Divvy bicycle sharing system (http://divvybikes.com/). This dataset contains all stations. For a list of only those stations currently in service, see https://data.cityofchicago.org/d/67g3-8ig8. For real-time status of stations in machine-readable format, see https://gbfs.divvybikes.com/gbfs/gbfs.json.

This API is based on the Alternative Fuel Locations (https://data.cityofchicago.org/d/f7f2-ggz5) dataset.

List of locations in Chicago where alternative vehicle fuels are available. For more detailed descriptions of fields, see http://developer.nrel.gov/docs/transportation/alt-fuel-stations-v1.

List of locations in NE Illinois, NW Indiana, and SE Wisconsin where alternative vehicle fuels are available. For a Chicago-only filtered view, see https://data.cityofchicago.org/d/fi3z-jc3f. For more detailed descriptions of fields, see http://developer.nrel.gov/docs/transportation/alt-fuel-stations-v1 or https://data.cityofchicago.org/developers/docs/alternative-fuel-locations.

Map of locations in NE Illinois, NW Indiana, and SE Wisconsin where alternative vehicle fuels are available. For more detailed descriptions of fields, see http://developer.nrel.gov/docs/transportation/alt-fuel-stations-v1.

List of locations in Chicago where alternative vehicle fuels are available. For more detailed descriptions of fields, see http://developer.nrel.gov/docs/transportation/alt-fuel-stations-v1 or https://data.cityofchicago.org/developers/docs/alternative-fuel-locations.