The census count of vehicles on city streets is normally reported in the form of Average Daily Traffic (ADT) counts. These counts provide a good estimate for the actual number of vehicles on an average weekday at select street segments. Specific block segments are selected for a count because they are deemed as representative of a larger segment on the same roadway. ADT counts are used by transportation engineers, economists, real estate agents, planners, and others professionals for planning and operational analysis. The frequency for each count varies depending on City staff’s needs for analysis in any given area. This report covers the counts taken in our City during the past 12 years approximately.
This data set features a hyperlink to the New York State Department of Transportation’s (NYSDOT) Traffic Data (TD) Viewer web page, which includes a link to the Traffic Data interactive map. The Traffic Data Viewer is a geospatially based Geographic Information System (GIS) application for displaying data contained in the roadway inventory database. The interactive map has five viewable data categories or ‘layers’. The five layers include: Average Daily Traffic (ADT); Continuous Counts; Short Counts; Bridges; and Grade Crossings throughout New York State.
ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
License information was derived automatically
Traffic-related data collected by the Boston Transportation Department, as well as other City departments and State agencies. Various types of counts: Turning Movement Counts, Automated Traffic Recordings, Pedestrian Counts, Delay Studies, and Gap Studies.
~_Turning Movement Counts (TMC)_ present the number of motor vehicles, pedestrians, and cyclists passing through the particular intersection. Specific movements and crossings are recorded for all street approaches involved with the intersection. This data is used in traffic signal retiming programs and for signal requests. Counts are typically conducted for 2-, 4-, 11-, and 12-Hr periods.
~_Automated Traffic Recordings (ATR)_ record the volume of motor vehicles traveling along a particular road, measures of travel speeds, and approximations of the class of the vehicles (motorcycle, 2-axle, large box truck, bus, etc). This type of count is conducted only along a street link/corridor, to gather data between two intersections or points of interest. This data is used in travel studies, as well as to review concerns about street use, speeding, and capacity. Counts are typically conducted for 12- & 24-Hr periods.
~_Pedestrian Counts (PED)_ record the volume of individual persons crossing a given street, whether at an existing intersection or a mid-block crossing. This data is used to review concerns about crossing safety, as well as for access analysis for points of interest. Counts are typically conducted for 2-, 4-, 11-, and 12-Hr periods.
~_Delay Studies (DEL)_ measure the delay experienced by motor vehicles due to the effects of congestion. Counts are typically conducted for a 1-Hr period at a given intersection or point of intersecting vehicular traffic.
~_Gap Studies (GAP)_ record the number of gaps which are typically present between groups of vehicles traveling through an intersection or past a point on a street. This data is used to assess opportunities for pedestrians to cross the street and for analyses on vehicular “platooning”. Counts are typically conducted for a specific 1-Hr period at a single point of crossing.
New York City Department of Transportation (NYC DOT) uses Automated Traffic Recorders (ATR) to collect traffic sample volume counts at bridge crossings and roadways. These counts do not cover the entire year, and the number of days counted per location may vary from year to year. Also see Automated Traffic Volume Counts: https://data.cityofnewyork.us/Transportation/Automated-Traffic-Volume-Counts/7ym2-wayt
Open Government Licence - Canada 2.0https://open.canada.ca/en/open-government-licence-canada
License information was derived automatically
Linear network representing the estimated traffic flows for roads and highways managed by the Ministry of Transport and Sustainable Mobility (MTMD). These flows are obtained using a statistical estimation method applied to data from more than 4,500 collection sites spread over the main roads of Quebec. It includes DJMA (annual average daily flow), DJME (summer average daily flow), DJME (summer average daily flow (June, July, August, September) and DJMH (average daily winter flow (December, January, February, March) as well as other traffic data. It is important to note that these values are calculated for total traffic directions. Interactive map: Some files are accessible by querying a section of traffic à la carte with a click (the file links are displayed in the descriptive table that is displayed when clicking): • Historical aggregated data (PDF) • Annual reports for permanent sites (PDF and Excel) • Hourly data (hourly average per weekday per month) (Excel) • Annual reports for permanent sites (PDF and Excel) • Hourly data (hourly average per weekday per month) (Excel)**This third party metadata element was translated using an automated translation tool (Amazon Translate).**
A collection of historic traffic count data and guidelines for how to collect new data for Massachusetts Department of Transportation (MassDOT) projects.
The American motor vehicle fleet traveled about ***** billion vehicle-miles in February 2025. Compared with January 2025, traffic decreased by about **** billion vehicle-miles. Between January and December 2024, traffic volume came to around *** trillion vehicle-miles of travel.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
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.
https://dataintelo.com/privacy-and-policyhttps://dataintelo.com/privacy-and-policy
The global real-time traffic data market size is anticipated to reach USD 15.3 billion by 2032 from an estimated USD 6.5 billion in 2023, exhibiting a robust CAGR of 10.1% over the forecast period. This substantial growth is driven by the increasing need for efficient traffic management systems and the rising adoption of smart city initiatives worldwide. Governments and commercial entities are investing heavily in advanced technologies to optimize traffic flow and enhance urban mobility, thus fostering market expansion.
The surge in urbanization and the consequent rise in vehicle ownership have led to severe traffic congestion issues in many metropolitan areas. This has necessitated the implementation of real-time traffic data systems that can provide accurate and timely information to manage traffic effectively. With the integration of sophisticated technologies such as IoT, AI, and big data analytics, these systems are becoming more efficient, thereby driving market growth. Furthermore, the growing emphasis on reducing carbon emissions and enhancing road safety is also propelling the adoption of real-time traffic data solutions.
Technological advancements are playing a pivotal role in shaping the real-time traffic data market. Innovations in sensor technology, the proliferation of GPS devices, and the widespread use of mobile data are providing rich sources of real-time traffic information. The ability to integrate data from multiple sources and deliver actionable insights is significantly enhancing traffic management capabilities. Additionally, the development of cloud-based solutions is enabling scalable and cost-effective deployment of traffic data systems, further contributing to market growth.
Another critical growth factor is the increasing investment in smart city projects. Governments across the globe are prioritizing the development of smart transportation infrastructure to improve urban mobility and reduce traffic-related issues. Real-time traffic data systems are integral to these initiatives, providing essential data for optimizing traffic flow, enabling route optimization, and enhancing public transport efficiency. The involvement of private sector players in these projects is also fueling market growth by introducing innovative solutions and fostering public-private partnerships.
The exponential rise in Mobile Data Traffic is another significant factor influencing the real-time traffic data market. As more people rely on smartphones and mobile applications for navigation and traffic updates, the demand for real-time data has surged. Mobile data provides a wealth of information about traffic patterns and congestion levels, enabling more accurate and timely traffic management. The integration of mobile data with other data sources, such as GPS and sensor data, enhances the overall effectiveness of traffic data systems. This trend is particularly evident in urban areas where mobile devices are ubiquitous, and the need for efficient traffic management is critical. The ability to harness mobile data for traffic insights is driving innovation and growth in the market, as companies develop new solutions to leverage this valuable resource.
Regionally, North America and Europe are leading the market due to their early adoption of advanced traffic management technologies and significant investments in smart city projects. However, the Asia Pacific region is expected to witness the highest growth rate over the forecast period, driven by rapid urbanization, increasing vehicle ownership, and growing government initiatives to develop smart transportation infrastructure. Emerging economies in Latin America and the Middle East & Africa are also showing promising growth potential, fueled by ongoing infrastructure development and increasing awareness of the benefits of real-time traffic data solutions.
The real-time traffic data market by component is segmented into software, hardware, and services. Each component plays a crucial role in the overall functionality and effectiveness of traffic data systems. The software segment includes traffic management software, route optimization software, and other analytical tools that help process and analyze traffic data. The hardware segment comprises sensors, GPS devices, and other data collection tools. The services segment includes installation, maintenance, and consulting services that support the deployment and operation of traffic data systems
https://www.caliper.com/license/maptitude-license-agreement.htmhttps://www.caliper.com/license/maptitude-license-agreement.htm
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.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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 June 2025.
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. LANE_DESIGNATION_CODE_ID 1 Standard 2 Right Turn 3 Left Turn 4 Thru Only 5 Thru + Right Turn 6 Thru + Left Turn 7 Aggregate Element 8 Anomaly / Special Event 9 Unknown 10 0 11 1 12 2 13 3 14 4 15 5 16 6 TRAFFIC_FLOW_DIR_ID: 1 N 2 S 3 E 4 W 5 NE 6 SE 7 SW 8 NW 9 REV 10 UNKNOWN 11 TOTAL
Annual average daily traffic is the total volume for the year divided by 365 days. The traffic count year is from October 1st through September 30th. Very few locations in California are actually counted continuously. Traffic Counting is generally performed by electronic counting instruments moved from location throughout the State in a program of continuous traffic count sampling. The resulting counts are adjusted to an estimate of annual average daily traffic by compensating for seasonal influence, weekly variation and other variables which may be present. Annual ADT is necessary for presenting a statewide picture of traffic flow, evaluating traffic trends, computing accident rates. planning and designing highways and other purposes.Traffic Census Program Page
A collection of layers maintained by the Traffic Monitoring Unit.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Brazil Highways Statistics: Traffic Tolled: Total Traffic data was reported at 1,834.949 Unit in 2017. This records an increase from the previous number of 1,782.727 Unit for 2016. Brazil Highways Statistics: Traffic Tolled: Total Traffic data is updated yearly, averaging 681.920 Unit from Dec 1996 (Median) to 2017, with 22 observations. The data reached an all-time high of 1,834.949 Unit in 2017 and a record low of 19.564 Unit in 1996. Brazil Highways Statistics: Traffic Tolled: Total Traffic data remains active status in CEIC and is reported by Brazilian Association of Highway Concessionaires. The data is categorized under Brazil Premium Database’s Automobile Sector – Table BR.RAW003: Highways Statistics: Traffic Tolled. The Brazilian Association of Highway Concessionaires-ABCR represents the highway concession sector.
Urban SDK is a GIS data management platform and global provider of mobility, urban characteristics, and alt datasets. Urban SDK Traffic data provides traffic volume, average speed, average travel time and congestion for logistics, transportation planning, traffic monitoring, routing and urban planning. Traffic data is generated from cars, trucks and mobile devices for major road networks in US and Canada.
"With the old data I used, it took me 3-4 weeks to create a presentation. I will be able to do 3-4x the work with your Urban SDK traffic data."
Traffic Volume, Speed and Congestion Data Type Profile:
Industry Solutions include:
Use cases:
Accessibility of tables
The department is currently working to make our tables accessible for our users. The data tables for these statistics are now accessible.
We would welcome any feedback on the accessibility of our tables, please email road maintenance statistics.
TSGB0723 (RDC0310): https://assets.publishing.service.gov.uk/media/676058f7365803b3ac5b5b68/rdc0310.ods" class="govuk-link">Maintenance expenditure by road class (ODS, 1.13 MB)
As of the 2022 release, TSGB now covers primarily cross-modal information. As a result, there are fewer tables in this chapter. Below are the tables that are no longer published with TSGB, but can still be found in the relevant routine DfT statistical collections. The https://maps.dft.gov.uk/transport-statistics-finder/index.html" class="govuk-link">Transport Statistics Finder can also be used to locate these tables, either by table name or code.
Topic | Table information | TSGB tables |
---|---|---|
Road traffic | Road traffic by vehicle type and road class, in Great Britain, by vehicle miles and kilometres. | TSGB0701 (TRA0101), TSGB0702 (TRA0201), TSGB0703 (TRA0102) , TSGB0704 (TRA0202), TSGB0705 (TRA0104), TSGB0706 (TRA0204) |
Vehicle speed compliance | Vehicle speed compliance by road and vehicle type in Great Britain. | TSGB0714 (SPE0111), TSGB0715 (SPE0112) |
Road lengths | Road length by road type, region, country and local authority in Great Britain. | TSGB0708 (RDL0203), TSGB0709 (RDL0103), TSGB0710 (RDL0201), TSGB0711 (RDL0101), TSGB0712 (RDL0202), TSGB0713 (RDL0102) |
Road congestion and travel time | Average delay on the Strategic Road Network, and local ‘A’ roads, in England, monthly and annual averages. | TSGB0716a (CGN0405), TSGB0716b (CGN0504) |
Road conditions | Principal and non-principal classified roads where maintenance should be considered, by region in England. | TSGB0722 (RDC0121) |
Road condition statistics
Email mailto:roadmaintenance.stats@dft.gov.uk">roadmaintenance.stats@dft.gov.uk
Media enquiries 0300 7777 878
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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
Open Data Commons Attribution License (ODC-By) v1.0https://www.opendatacommons.org/licenses/by/1.0/
License information was derived automatically
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...
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Real time data of traffic volume and occupancy of lanes at Brisbane City Council signalised intersections and approaches.
Not all signalised traffic intersections within Brisbane are operated by Brisbane City Council. This dataset contains only the Brisbane City Council operated signalised traffic intersection data.
To gain maximum benefit from this dataset you will have to use it in conjunction with another dataset Traffic Management — Intersection locations — reference.
The Data and resources section of this dataset contains further information for this dataset.
The census count of vehicles on city streets is normally reported in the form of Average Daily Traffic (ADT) counts. These counts provide a good estimate for the actual number of vehicles on an average weekday at select street segments. Specific block segments are selected for a count because they are deemed as representative of a larger segment on the same roadway. ADT counts are used by transportation engineers, economists, real estate agents, planners, and others professionals for planning and operational analysis. The frequency for each count varies depending on City staff’s needs for analysis in any given area. This report covers the counts taken in our City during the past 12 years approximately.