This dataset is historical. For recent data, we recommend using https://chicagotraffictracker.com. -- Average Daily Traffic (ADT) counts are analogous to a census count of vehicles on city streets. These counts provide a close approximation to the actual number of vehicles passing through a given location on an average weekday. Since it is not possible to count every vehicle on every city street, sample counts are taken along larger streets to get an estimate of traffic on half-mile or one-mile street segments. ADT counts are used by city planners, transportation engineers, real-estate developers, marketers and many others for myriad planning and operational purposes. Data Owner: Transportation. Time Period: 2006. Frequency: A citywide count is taken approximately every 10 years. A limited number of traffic counts will be taken and added to the list periodically. Related Applications: Traffic Information Interactive Map (http://webapps.cityofchicago.org/traffic/).

The Traffic Counts feature layer models the locations and daily volume of traffic counts within the Pikes Peak Area Council of Governments (PPACG) region. The data in this feature class is developed by PPACG from information provided by or acquired from the Colorado Department of Transportation (CDOT), county and municipal governments within the region, and private companies contracted to perform traffic count collections.The 'Source_ID' field references the ID for the counter, location, or report provided by the source of each count, which may not be unique to the dataset. The 'RouteCL_ID' field stores the unique ID for a related Route_Centerlines feature class segment, while the 'Loc_Desc' field describes the relative location of the traffic counter.The Hourly Traffic Counts layer records the average number of vehicles at each location in one-hour intervals, and has fields for storing each hour's count and a field identifying the number of days the counter collected at each location. The Daily Traffic Counts layer records daily traffic volume at each location, and has a 'Count_Type' field that identifies the type of count collected. Most of the daily counts are a measure of Annual Average Daily Traffic (AADT), which is a calculated average of traffic volume recorded at that location throughout a single year, while an Average Daily Traffic (ADT) count is an average of traffic volume recorded at that location across multiple days, and a 24-hr count is the traffic volume recorded during a single day. Both layers have a 'Count_Yr' field to record the year the count was collected.For more detailed information regarding the information contained, including available attribute fields, extents, and data sources, please examine the descriptions and metadata for each layer.

DescriptionFeatures in this dataset represent segments of public highways that are maintained by and under the jurisdiction of the Colorado Department of Transportation. These highways consist of Interstates, US Highways, and State Highways. These highway segments are classified by Traffic data from the TRAFFON table. Last Update2024Update FrequencyAnnuallyData OwnerDivision of Transportation DevelopmentData ContactTraffic Analysis UnitCollection MethodTraffic CountersProjectionNAD83 / UTM zone 13NCoverage AreaStatewideTemporal Disclaimer/LimitationsThere are no restrictions and legal prerequisites for using the data set. The State of Colorado assumes no liability relating to the completeness, correctness, or fitness for use of this data.

Traffic counts on highways and various calculations, from Colorado Department of Transportation (CDOT), for 2022.

The Traffic_Counts_Daily feature class models the locations and daily volume of traffic counts within the Pikes Peak Area Council of Governments (PPACG) region. The data in this feature class is developed by PPACG from information provided by or acquired from the Colorado Department of Transportation (CDOT), county and municipal governments within the region, and private companies contracted to perform traffic count collections.The 'Source_ID' field references the ID for the counter, location, or report provided by the source of each count, which may not be unique to the dataset. The 'RouteCL_ID' field stores the unique ID for a related Route_Centerlines feature class segment. The 'Loc_Desc' field describes the relative location of the traffic counter, while the the 'Count_Type' field identifies the type of count collected. Most records are a measure of Annual Average Daily Traffic (AADT), which is a calculated average of traffic volume recorded at that location throughout a single year, while an Average Daily Traffic (ADT) count is an average of traffic volume recorded at that location across multiple days, and a 24-hr count is the traffic volume recorded during a single day. The 'Count_Yr' field records the year the count was collected, while the 'Count_Date' field further identifies the specific date when a 24-hr count was collected. The 'TotalCount' field stores the total volume of traffic in all directions at each location, while the remaining fields report the volume in each direction of travel, if collected, and identify the source of each traffic count.

DescriptionFeatures in this dataset represent segments of public highways that are maintained by and under the jurisdiction of the Colorado Department of Transportation. These highways consist of Interstates, US Highways, and State Highways. These highway segments are classified by Traffic data from the TRAFFON table.Last Update2023Update FrequencyAnnuallyData OwnerDivision of Transportation DevelopmentData ContactTraffic Analysis UnitCollection MethodTraffic CountersProjectionNAD83 / UTM zone 13NCoverage AreaStatewideTemporalDisclaimer/LimitationsThere are no restrictions and legal prerequisites for using the data set. The State of Colorado assumes no liability relating to the completeness, correctness, or fitness for use of this data.

Traffic counts on public roads under local jurisdiction in 2023. Provided by the CDOT.

Total for each direction and each camera grouped by date

Traffic counts on highways and various calculations, from Colorado Department of Transportation (CDOT), for 2017

Traffic Counts in the vicinity of Aurora, Colorado. This data is a subset from the DRCOG Data Catalog. The data was built from a variety of sources: CDOT, local jurisdictions, and other sources.

Features in this dataset represent traffic counts on public roads under local jurisdiction that are functionally classified as arterials or collectors. Features are represented by polyline (linear) geographic shapes from the Colorado Department of Transportation (CDOT), for 2014

Traffic counts on highways and various calculations, from Colorado Department of Transportation (CDOT), for 2015

Traffic counts on highways and various calculations, from Colorado Department of Transportation (CDOT), for 2016

The Traffic_Counts_Hourly feature class models the locations and hourly volume of traffic counts within the Pikes Peak Area Council of Governments (PPACG) region. The data in this feature class is developed by PPACG from information provided by or acquired from the Colorado Department of Transportation (CDOT), county and municipal governments within the region, and private companies contracted to perform traffic count collections.The 'Source_ID' field references the ID for the counter, location, or report provided by the source of each count, which may not be unique to the dataset. The 'RouteCL_ID' field stores the unique ID for a related Route_Centerlines feature class segment, and the 'NetLink_ID' field stores the unique ID for a related roadway network link. The 'Loc_Desc' field describes the relative location of the traffic counter, while the the 'Travel_Dir' field identifies which direction of traffic was collected at that location. The 'Count_Yr' field records the year the count was collected, while the 'AvgDayTot' field identifies the total Average Daily Traffic (ADT) count of all traffic at each location. The remaining fields store the average traffic count for each one-hour period throughout the day, the number of days the counter collected at each location, and identify the source of each traffic count.

Traffic counts on public roads under local jurisdiction in 2016. Provided by the CDOT.

The Chicago Department of Transportation (CDOT) receives reports from 311’s Customer Service Requests (CSR) system of traffic light outages. This metric tracks the average number of days CDOT takes to complete traffic light repair requests. Total number of requests fulfilled per week is also available by mousing over columns Due to the public safety importance of traffic signals, the target time to respond to traffic light outages is within 1 day.

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.

Traffic counts on highways and various calculations, from Colorado Department of Transportation (CDOT), for 2019.

When moisture seeps into pavement, it expands when it freezes and contracts when it thaws. This flexing of the pavement, combined with the melted water and the stress of vehicular traffic, causes pavement to deteriorate and potholes to form. The Department of Transportation (CDOT) responds to potholes reported through 311’s Customer Service Requests (CSR) system by mapping open pothole requests each morning and routing crews in geographic clusters so as to fill as many potholes as possible per day. This metric tracks the average number of days CDOT takes to complete pothole repairs per week. Total number of requests fulfilled per week is also available by mousing over columns. The target response time for pothole repairs is within 7 days. For more information about pothole repairs, see CDOT’s pothole Frequently Asked Questions page: http://www.cityofchicago.org/content/dam/city/depts/cdot/PotholeFAQ_winter1011.pdf

Local Roads are functionally identified as local and excludes major roads or highways. Each road is segmented with a to and from description. The direction, length, type (paved/dirt), width (in feet), local route name and id, number of lanes, one/two-way bridges, average daily traffic counts, locations of count stations, if it is congested, if maintenance is under shared jurisdiction and the year it was built or last updated from the Colorado Department of Transportation (CDOT).