Annual Average Daily Traffic volumes (AADT) is a product of IDOT’s Traffic Count Program. Counts from this program range in duration from data continuously recorded at permanent count stations to thousands of coverage count locations that are counted for a 24-hour period throughout the year. More information about IDOT’s Traffic Count Program can be found at the Illinois Travel Statistics site.

Annual Average Daily Traffic volumes (AADT) is a product of IDOT’s Traffic Count Program. Counts from this program range in duration from data continuously recorded at permanent count stations to thousands of coverage count locations that are counted for a 24-hour period throughout the year. More information about IDOT’s Traffic Count Program can be found at the Illinois Travel Statistics site.

For the latest traffic count information, please see the IDOT Data Portal or the Getting Around Illinois map.

This dataset contains historic turning movement counts for selected intersections and segments during morning, noon, and afternoon peak hours between 2001 and 2017.

Historic Average Daily Traffic (ADT) counts by segments in Champaign County are available for various years between 2001 to 2016.

Vehicle counts at selected intersections in the urbanized area and Rantoul are available from 2010 to 2017.

Bicycle counts at selected intersections in the urbanized area and Rantoul are available from 2012 to 2017 (excluding 2014).

Please refer to the name of the dataset for specific traffic counts.

Annual Average Daily Traffic volumes (AADT) is a product of IDOT’s Traffic Count Program. Counts from this program range in duration from data continuously recorded at permanent count stations to thousands of coverage count locations that are counted for a 24-hour period throughout the year. More information about IDOT’s Traffic Count Program can be found at the Illinois Travel Statistics site.

Annual Average Daily Traffic volumes (AADT) is a product of IDOT’s Traffic Count Program. Counts from this program range in duration from data continuously recorded at permanent count stations to thousands of coverage count locations that are counted for a 24-hour period throughout the year. More information about IDOT’s Traffic Count Program can be found at the Illinois Travel Statistics site.

Annual Average Daily Traffic volumes (AADT) is a product of IDOT’s Traffic Count Program. Counts from this program range in duration from data continuously recorded at permanent count stations to thousands of coverage count locations that are counted for a 24-hour period throughout the year. More information about IDOT’s Traffic Count Program can be found at the Illinois Travel Statistics site.

This dataset details traffic counts in the Chicago Southland from 2010 thru 1998. This dataset is a mashup of IDOT, County, and CMAP traffic counts

This coverage contains a highway Annual Average Daily Traffic (AADT) subset of the information included in the IDOT Illinois Highway Information System (IHIS) -- Illinois Roadway Information System (IRIS). Information is collected for all public highways as defined in Illinois Compiled Statutes (605 ILCS 5/2-202).

Annual Average Daily Traffic volumes (AADT) is a product of IDOT’s Traffic Count Program. Counts from this program range in duration from data continuously recorded at permanent count stations to thousands of coverage count locations that are counted for a 24-hour period throughout the year. More information about IDOT’s Traffic Count Program can be found at the Illinois Travel Statistics site.

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.

Annual Average Daily Traffic volumes (AADT) is a product of IDOT’s Traffic Count Program. Counts from this program range in duration from data continuously recorded at permanent count stations to thousands of coverage count locations that are counted for a 24-hour period throughout the year. More information about IDOT’s Traffic Count Program can be found at the Illinois Travel Statistics site.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Primary roads are generally divided, limited-access highways within the interstate highway system or under State management, and are distinguished by the presence of interchanges. These highways are accessible by ramps and may include some toll highways. The MAF/TIGER Feature Classification Code (MTFCC) is S1100 for primary roads. Secondary roads are main arteries, usually in the U.S. Highway, State Highway, and/or County Highway system. These roads have one or more lanes of traffic in each direction, may or may not bedivided, and usually have at-grade intersections with many other roads and driveways. They usually have both a local name and a route number. The MAF/TIGER Feature Classification Code (MTFCC) is S1200 for secondary roads.

The information is the same data transmitted to the Illinois Department of Transportation (IDOT) with two additions: the "Motivation for Stop", and the offense codes recorded. Traffic stops appear from 2012, when the State revised the format to the current standard, until February 2023 when the system changed.

IMPORTANT!! (please click "More" to read this...) Adding the Offense Codes means that each line of information represents a single Offense.

For example: a traffic stop for speeding results in an arrest for an outstanding warrant and for possession of narcotics. That would appear on this listing THREE times (speeding, arrest warrant, and narcotics). The Incident Number will be the same (and the driver demographics), but the Crime Codes will be different on each line.

So counting rows of this dataset will return a higher count than the actual stops. This will cause some discrepancies with State data, which only count each stop once.

Please refer to the attachment for more details.

Splitgraph serves as an HTTP API that lets you run SQL queries directly on this data to power Web applications. For example:

See the Splitgraph documentation for more information.

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 Chicago Department of Transportation (CDOT) after monthly reviews of fatal traffic crash information provided by Chicago Police Department’s Major Accident Investigation Unit (MAIU). CDOT uses a standardized process – sometimes differing from other sources and everyday use of the term -- to determine whether a death is a “traffic fatality.” 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 an annual basis. This VZC Traffic Fatality List is updated monthly. Once IDOT publishes its crash data for a year, this dataset is edited to reflect IDOT’s findings. VZC Traffic Fatalities can be linked with other traffic crash datasets using the “Person_ID” field. State of Illinois considers a “traffic fatality” as any death caused by a traffic crash involving a motor vehicle, within 30 days of the crash. Fatalities that meet this definition are included in this VZC Traffic Fatality List unless excluded by any 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," and are derived from Federal and State reporting standards. 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 the fatality was not attributable to road user movement on a public roadway. (Note: If a person driving suffers a medical emergency and consequently hits and kills another road user, the other road user is included, although the driver suffering a medical emergency is excluded.) The crash did not occur within a trafficway. The crash involved a train or other such mode of transport within the rail dedicated right-of-way. 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 VZC Traffic Fatality List. 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 centerline. The fatality is not a person (e.g., an animal). Change 12/7/2023: We have removed the RD_NO (Chicago Police Department report number) for privacy reasons.

The information is the same data transmitted to the Illinois Department of Transportation (IDOT). This dataset does not have Offense details - see the other Traffic Stops dataset for that.

Traffic stops appear since 2012, when the State revised the format to the current standard, until February 2023 when the computer system changed.

Please refer to the attachment for more details.

Splitgraph serves as an HTTP API that lets you run SQL queries directly on this data to power Web applications. For example:

See the Splitgraph documentation for more information.

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.

Change 11/21/2023: We have removed the RD_NO (Chicago Police Department report number) for privacy reasons.

Conditions are updated every 10 minutes during the winter season (October 15 to April 15) and on an as-needed basis during the non-winter months. Layer and service is maintained by the Iowa DOT GIS team on behalf of the Office of Traffic Operations. This data is provided as is through this value added REST service. All conditions have been remapped to the best of our ability to meet the condition reporting criteria as defined by the Iowa DOT. Some discrepancies may appear. This data service should only be used for reference only. For the most accurate information, please utilize the authoritative state 511 sites below.

State 511 Sites

511 Vendor

Disclaimers

North Dakota

Iteris

The data is provided as is and without liability from the North Dakota Department of Transportation (NDDOT). The NDDOT does not guarantee this data to be free from errors, or inaccuracies, and disclaims any responsibility or liability for interpretations or decisions based on this data. Additional Disclai

South Dakota

Iteris

Disclaimer

Nebraska

Castle Rock

Disclaimer

Kansas

Disclaimer

Missouri

Disclaimer

Illinois

The conditions reported on this page only represent conditions of routes maintained by the Illinois Department of Transportation. Conditions on roads maintained by cities, counties, townships or other entities may be different than what is reported here. The Illinois Department of Transportation and the State of Illinois hereby give notice to all users that these maps and the data included hereon, lack the accuracy required for site-specific uses. Since all boundaries and all data are based on information derived from multiple sources within and outside the Illinois Department of Transportation, the Department of Transportation and the State of Illinois make no representation, guarantee, or warrant, either express or implied, regarding the accuracy of these maps or the data furnished thereon, including, but not limited to, the condition of this product, this product's merchantability, or this product's fitness for any particular purpose or use.

Wisconsin

Access to and use of the Wisconsin Department of Transportation (WisDOT) 511wi website is provided subject to these terms and conditions. Please read these terms at WisDOT Legal Notices link.

Minnesota>

Castle Rock

Disclaimer

Dissolved ADT created for improved labeling. Updated from ADT_COMP_2024Annual Average Daily Traffic volumes (AADT) is a product of IDOT’s Traffic Count Program. Counts from this program range in duration from data continuously recorded at permanent count stations to thousands of coverage count locations that are counted for a 24-hour period throughout the year. More information about IDOT’s Traffic Count Program can be found at the Illinois Travel Statistics site.

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.

Change 11/21/2023: We have removed the RD_NO (Chicago Police Department report number) for privacy reasons.

Annual Average Daily Traffic volumes (AADT) is a product of IDOT’s Traffic Count Program. Counts from this program range in duration from data continuously recorded at permanent count stations to thousands of coverage count locations that are counted for a 24-hour period throughout the year. More information about IDOT’s Traffic Count Program can be found at the Illinois Travel Statistics site.