Average Annual Daily Traffic data for use with GIS mapping software, databases, and web applications are from Caliper Corporation and contain data on the total volume of vehicle traffic on a highway or road for a year divided by 365 days.

This web map displays traffic count data provided by the City of Tempe Transportation Department. Data are symbolized by line thickness per each street section.Each segment's popup contains a weblink to historical traffic count data that are provided by the City of Tempe for public use.

Web App. Traffic counts in St. Louis County, Missouri. Traffic count locations showing day, time, volume, etc. Link to Metadata.

Web traffic statistics for the several City-Parish websites, brla.gov, city.brla.gov, Red Stick Ready, GIS, Open Data etc. Information provided by Google Analytics.

This traffic-count data is provided by the City of Pittsburgh's Department of Mobility & Infrastructure (DOMI). Counters were deployed as part of traffic studies, including intersection studies, and studies covering where or whether to install speed humps. In some cases, data may have been collected by the Southwestern Pennsylvania Commission (SPC) or BikePGH.

Data is currently available for only the most-recent count at each location.

Traffic count data is important to the process for deciding where to install speed humps. According to DOMI, they may only be legally installed on streets where traffic counts fall below a minimum threshhold. Residents can request an evaluation of their street as part of DOMI's Neighborhood Traffic Calming Program. The City has also shared data on the impact of the Neighborhood Traffic Calming Program in reducing speeds.

Different studies may collect different data. Speed hump studies capture counts and speeds. SPC and BikePGH conduct counts of cyclists. Intersection studies included in this dataset may not include traffic counts, but reports of individual studies may be requested from the City. Despite the lack of count data, intersection studies are included to facilitate data requests.

Data captured by different types of counting devices are included in this data. StatTrak counters are in use by the City, and capture data on counts and speeds. More information about these devices may be found on the company's website. Data includes traffic counts and average speeds, and may also include separate counts of bicycles.

Tubes are deployed by both SPC and BikePGH and used to count cyclists. SPC may also deploy video counters to collect data.

NOTE: The data in this dataset has not updated since 2021 because of a broken data feed. We're working to fix it.

You can also access an API version of this dataset.

TMS

(traffic monitoring system) daily-updated traffic counts API

Important note: due to the size of this dataset, you won't be able to open it fully in Excel. Use notepad / R / any software package which can open more than a million rows.

Data reuse caveats: as per license.

Data quality

statement: please read the accompanying user manual, explaining:

how

 this data is collected identification 

 of count stations traffic 

 monitoring technology monitoring 

 hierarchy and conventions typical 

 survey specification data 

 calculation TMS 

 operation. 

Traffic

monitoring for state highways: user manual

[PDF 465 KB]

The data is at daily granularity. However, the actual update

frequency of the data depends on the contract the site falls within. For telemetry

sites it's once a week on a Wednesday. Some regional sites are fortnightly, and

some monthly or quarterly. Some are only 4 weeks a year, with timing depending

on contractors’ programme of work.

Data quality caveats: you must use this data in

conjunction with the user manual and the following caveats.

The

 road sensors used in data collection are subject to both technical errors and 

 environmental interference.Data 

 is compiled from a variety of sources. Accuracy may vary and the data 

 should only be used as a guide.As 

 not all road sections are monitored, a direct calculation of Vehicle 

 Kilometres Travelled (VKT) for a region is not possible.Data 

 is sourced from Waka Kotahi New Zealand Transport Agency TMS data.For 

 sites that use dual loops classification is by length. Vehicles with a length of less than 5.5m are 

 classed as light vehicles. Vehicles over 11m long are classed as heavy 

 vehicles. Vehicles between 5.5 and 11m are split 50:50 into light and 

 heavy.In September 2022, the National Telemetry contract was handed to a new contractor. During the handover process, due to some missing documents and aged technology, 40 of the 96 national telemetry traffic count sites went offline. Current contractor has continued to upload data from all active sites and have gradually worked to bring most offline sites back online. Please note and account for possible gaps in data from National Telemetry Sites. 

The NZTA Vehicle

Classification Relationships diagram below shows the length classification (typically dual loops) and axle classification (typically pneumatic tube counts),

and how these map to the Monetised benefits and costs manual, table A37,

page 254.

Monetised benefits and costs manual [PDF 9 MB]

For the full TMS

classification schema see Appendix A of the traffic counting manual vehicle

classification scheme (NZTA 2011), below.

Traffic monitoring for state highways: user manual [PDF 465 KB]

State highway traffic monitoring (map)

State highway traffic monitoring sites

The City of Houston captures traffic activity and throughput through the use of traffic counts, which are turned into Average Daily Traffic (ADT) counts estimates to provide...

This dataset consists of 24-hour traffic volumes which are collected by the City of Tempe high (arterial) and low (collector) volume streets. Data located in the tabular section shares with its users total volume of vehicles passing through the intersection selected along with the direction of flow.Historical data from this feature layer extends from 2016 to present day.Contact: Sue TaaffeContact E-Mail: sue_taaffe@tempe.govContact Phone: 480-350-8663Link to embedded web map:http://www.tempe.gov/city-hall/public-works/transportation/traffic-countsLink to site containing historical traffic counts by node: https://gis.tempe.gov/trafficcounts/Folders/Data Source: SQL Server/ArcGIS ServerData Source Type: GeospatialPreparation Method: N/APublish Frequency: As information changesPublish Method: AutomaticData Dictionary

Traffic volumes data across Dublin City from the SCATS traffic management system. The Sydney Coordinated Adaptive Traffic System (SCATS) is an intelligent transportation system used to manage timing of signal phases at traffic signals. SCATS uses sensors at each traffic signal to detect vehicle presence in each lane and pedestrians waiting to cross at the local site. The vehicle sensors are generally inductive loops installed within the road. 3 resources are provided: SCATS Traffic Volumes Data (Monthly) Contained in this report are traffic counts taken from the SCATS traffic detectors located at junctions. The primary function for these traffic detectors is for traffic signal control. Such devices can also count general traffic volumes at defined locations on approach to a junction. These devices are set at specific locations on approaches to the junction but may not be on all approaches to a junction. As there are multiple junctions on any one route, it could be expected that a vehicle would be counted multiple times as it progress along the route. Thus the traffic volume counts here are best used to represent trends in vehicle movement by selecting a specific junction on the route which best represents the overall traffic flows. Information provided: End Time: time that one hour count period finishes. Region: location of the detector site (e.g. North City, West City, etc). Site: this can be matched with the SCATS Sites file to show location Detector: the detectors/ sensors at each site are numbered Sum volume: total traffic volumes in preceding hour Avg volume: average traffic volumes per 5 minute interval in preceding hour All Dates Traffic Volumes Data This file contains daily totals of traffic flow at each site location. SCATS Site Location Data Contained in this report, the location data for the SCATS sites is provided. The meta data provided includes the following; Site id – This is a unique identifier for each junction on SCATS Site description( CAP) – Descriptive location of the junction containing street name(s) intersecting streets Site description (lower) - – Descriptive location of the junction containing street name(s) intersecting streets Region – The area of the city, adjoining local authority, region that the site is located LAT/LONG – Coordinates Disclaimer: the location files are regularly updated to represent the locations of SCATS sites under the control of Dublin City Council. However site accuracy is not absolute. Information for LAT/LONG and region may not be available for all sites contained. It is at the discretion of the user to link the files for analysis and to create further data. Furthermore, detector communication issues or faulty detectors could also result in an inaccurate result for a given period, so values should not be taken as absolute but can be used to indicate trends.

Traffic sensors at over 1,200 locations in Allegheny County collect vehicle counts for the Pennsylvania Department of Transportation. Data included in the Health Department's DASH project includes hourly averages and average daily counts. The data was collected from years 2012-2014 and compiled by Carnegie Mellon University’s Traffic21 Institute.

In December 2024, social video platform YouTube recorded approximately 56 billion visits on mobile and over 23 billion visits from users on desktop devices. The web visitors traffic count from mobiles and smartphones appeared consistently higher than the desktop visit count in the examined months.

This dataset contains the Department of Transport and Main Roads road location details (both spatial and through distance) as well as associated traffic data.

It allows users to locate themselves with respect to road section number and through distance using the spatial coordinates on the state-controlled road network.

Through distance – the distance in kilometres measured from the gazetted start point of the road section.

Note: "Road location and traffic data" resource has been updated as of July 2023.

This table provides location data and summary statistics of each traffic study. The SDOT Traffic Counts group runs studies across the city to collect traffic volumes. Most studies are done with pneumatic tubes, but some come from video systems as well. Use the field study_id to match it with other tables for more detailed information. Data are binned in 15 minute and 60 minute bins in other tables.

Annualized, Hourly and Classification count data for the TPB modeled region. Data are collected from state DOTs and processed by TPB staff.Layers IncludedAnnualized Traffic Volumes Historic AADT by Count Station This database contains the Annual Average Daily Traffic (AADT) estimates reported at permanent and short term counting stations in the TPB modeled region. Please note: Interstates in Virginia are typically represented by two stations (one in each direction) while Interstates in the other states are represented by one station. Therefore, the AADT estimates displayed for the stations on Virginia Intestates will be around half of the total for the directional roadway. The AADT estimates for recent years in this file are based on counts taken at the actual count station locations that are indicated by the station points. The AADT estimates for earlier years are based on volumes reported along roadway segments that the station points currently represent. Specific data sources for each state are listed below:District of ColumbiaAADT estimates since 2006 are based on counts taken at the station locations in the file for purpose of Federal HPMS reporting.AADT estimates prior to 2006 are based on Traffic Volume maps produced by DDOT (Formerly DC DPW).MarylandAADT estimates since 2000 are based on counts taken at the station locations in the file and reported by MD SHA.AADT estimates prior to 2000 are based on volumes reported by MD SHA in the Highway Location Reference documents and matched to links in the COG/TPB highway network. The volumes are shown at the count locations that currently represent those network links.VirginiaAADT estimates since 1997 are based on counts taken at the station locations in the file and reported by VDOT.AADT estimates prior to 1997 are based on volumes reported by VDOT in the Average Daily Traffic Volumes documents and matched to links in the COG/TPB highway network. The volumes are shown at the count locations that currently represent those network links.West VirginiaAADT estimates since 1999 are based on counts taken at the station locations in the file and reported by WV DOT.Traffic Counts by Network LinkThis layer was created by assigning the state DOT traffic counting station locations to their corresponding COG/TPB network links. Facility names and route numbers were added to the network. AADT Average Annual Daily Traffic (2016 - 2018), AAWDT Average Annual Weekday Daily Traffic (2016 - 2018) and Count Type (2016 - 2018) are included as well as Single Unit Truck Percent AAD (2018), Combination Unit Truck Percent AADT (2018), Bus Percent AADT (2018, only available for Maryland and Virginia), K Factor (2018), Dir Factor (2018), and Count Year (last year the link was counted). Count Type denotes the source of the count. Please note: for bi-directional roads, the AADT and AAWDT values for each location were divided in two and assigned to both network links that represent the Anode-Bnode direction and the Bnode-Anode direction. Therefore, in most cases the AADT/AAWDT values associated with an individual link in this network will be half of the AADT/AAWDT values reported at the associated individual count station point. Traffic Counts by External StationThis layer was created by placing points where major facilities cross the TPB Modeled Area boundary. In some cases, the external station represents more than one facility. The facility field indicates which road or roads the station represents. AADT and AAWDT estimates at external stations are provided for 2007 through 2022. Each external station is assigned to a state DOT traffic counting station(s). An effort was made to assign stations or combinations of stations that would come closest to measuring the traffic volume on each facility as it enters/exits the region. In some cases, these volumes are measured just inside the modeled area; in other cases, the volumes are measured just outside the modeled area. The external stations around the Baltimore Beltway are exceptions to this rule. These stations all measure the traffic just south of the Baltimore Beltway in order lessen the influence of traffic specific to Baltimore. AADT Average Annual Daily Traffic (2007 – 2022) and AAWDT Average Annual Weekday Daily Traffic (2007 – 2022) are included. Count Type denotes when the location was last counted. West Virginia does not report AAWDT, so the AADT values were increased by 5% to arrive at AAWDT estimates in West Virginia.

Esri ArcGIS Online (AGOL) Hosted Feature Layer for accessing the MDOT SHA Annual Average Daily Traffic (AADT) data product.MDOT SHA Annual Average Daily Traffic (AADT) data consists of linear & point geometric features which represent the geographic locations & segments of roadway throughout the State of Maryland that include traffic volume information. Traffic volume information is produced from traffic counts used to calculate annual average daily traffic (AADT), annual average weekday traffic (AAWDT), AADT based on vehicle class (current year only) for roadways throughout the State. Ten (10) years of historic AADT & AAWDT traffic volume metrics are also available for each geographic location or segment of roadway throughout the State, where applicable.Annual Average Daily Traffic (AADT) data is collected from over 8700 program count stations and 84 ATRs, located throughout Maryland. The quality control feature of the system allow data edit checks and validation for data from the 91 permanent, continuous automatic traffic recorders (ATRs) and short-term traffic counts. Program count data is collected in both directions (inventory & non-inventory) at regular locations on either a three (3) year or six (6) year cycle depending on the type of roadway. Growth factors are applied to counts which were not taken during the current year and the counts are factored based on the past yearly growth of an associated ATR. Counters are placed for 48 hours on a Monday or Tuesday and are picked up that Thursday or Friday, respectively. The ATR and toll count data is collected on a continuous basis. Toll station data is provided by the Maryland Transportation Authority (MDTA). A special numeric code was added to the AADT numbers, starting in 2006, to identify the years when the count was actually taken. The last digit represents the number of years prior to the actual count. Where “0” represents the current year when data was collected (in 2020), “1” represents the count taken in 2019, “2” represents the count taken in 2018, “3” represents the count taken in 2017 and so forth.Annual Average Daily Traffic (AADT) data is a strategic resource for the Federal Highway Administration (FHWA), the Maryland Department of Transportation (MDOT), the Maryland Department of Transportation State Highway Administration (MDOT SHA), as well as many other Federal, State & local government agencies. The data is essential in the planning, design and operation of the statewide road system and the development & implementation of State highway improvement & safety programs. The MDOT SHA Traffic Monitoring System (TMS) is a product of the ISTEA Act of 1991, which required a traffic data program to effectively & efficiently meet MDOT SHA’s long-term traffic data monitoring & reporting requirements.Annual Average Daily Traffic (AADT) data is updated & published on an annual basis for the prior year. This data is for the year 2023.View the most current AADT data in the MDOT SHA Annual Average Daily Traffic (AADT) LocatorFor more AADT data information, contact MDOT SHA OPPE Traffic Monitoring System (TMS) Unit:Email: TMS@mdot.maryland.govFor more general information, contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

Data Dictionary for District Traffic Web Map used in TPP Statewide Traffic Count App

This dataset contains estimates of the average number of vehicles that used roads throughout the City of Detroit in 2020. Each record indicates the Annual Average Daily Traffic (AADT) and Commercial Annual Average Daily Traffic (CAADT) for a road segment, where the road segment is located, and other characteristics. This data is derived from Michigan Department of Transportation's (MDOT) Open Data Portal. SEMCOG was the source for speed limits and number of lanes.The primary measure, Annual Average Daily Traffic (AADT), is the estimated mean daily traffic volume for all types of vehicles. Commercial Annual Average Daily Traffic (CAADT) is the estimated mean daily traffic volume for commercial vehicles, a subset of vehicles included in the AADT. The Route ID is an identifier for each road in Detroit (e.g., Woodward Ave). Routes are divided into segments by features such as cross streets, and Location ID's are used to uniquely identify those segments. Along with traffic volume, each record also states the number of lanes, the posted speed limit, and the type of road (e.g., Trunkline or Ramp) based on the Federal Highway Administration (FHWA) functional classification system.According to MDOT's Traffic Monitoring Program a commercial vehicle would be anything Class 4 and up in the FHWA vehicle classification system. This includes vehicles such as buses, semi-trucks, and personal recreational vehicles (i.e., RVs or campers). Methods used to determine traffic volume vary by site, and may rely on continuous monitoring or estimates based on short-term studies. Approaches to vehicle classification similarly vary, depending on the equipment used at a site, and may consider factors such as vehicle weight and length between axles.For more information, please visit MDOT Traffic Monitoring Program.

This is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. Traffic monitoring data is a strategic resource for SHA and Maryland's Department of Transportation. The data is essential in the planning - design and operation of the statewide road system and the development and implementation of state highway improvement and safety programs. TMS is a product of the ISTEA Act of 1991 - which required a traffic data program to effectively and efficiently meet SHA's long-term traffic data monitoring and reporting requirements. The quality control feature of the system allow data edit checks and validation for data from the 84 permanent - continuous automatic traffic recorders (ATRs) and short-term traffic counts.The Maryland Traffic Volume Maps depict the Annual Average Daily Traffic (AADT) at various locations on Maryland's roadways by county. Traffic Volume data is collected from over 8700 program count stations and 84 ATRs - located throughout Maryland. To date - four (4) ATRs have been removed from the ATR Program. Program count data is collected (both directions) at regular locations on either a three (3) year or six (6) year cycle depending on type of roadway. Growth Factors are applied to counts which were not taken during the current year and the counts are factored based on the past yearly growth of an associated ATR. Counters are placed for 48 hours on a Monday or Tuesday and are picked up that Thursday or Friday - respectively. The ATR and toll count data is collected on a continuous basis. Toll station data is provided by the Maryland Transportation Authority. A special numeric code was added to the AADT numbers - starting in 2006 - to identify the years when the count was actually taken. The last digit represents the number of years prior to the actual count. Where '0' represents the current year when data was collected (in 2014) - '1' represents the count taken in 2013 - '2' represents the count taken in 2012 - '3' represents the count taken in 2011 and so forth. Last Updated: Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Transportation/MD_AnnualAverageDailyTraffic/FeatureServer/1 ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.

In the measured time period, September 2024 saw the highest figures for online traffic to the C2C fashion marketplace depop.com. According to the data, desktop and mobile visits to depop.com reached 27.2 million visits that month.

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