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

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.

Historical data of traffic measurement points in the period of the COVID19 pandemic, NOTICE: This dataset is no longer updated. Data are offered from 30-03.2020 to 9-08-2020. There is another set of data in this portal with the historical series: Traffic. History of traffic data since 2013 In this same portal you can find other related data sets such as: Traffic. Real-time traffic data . With real-time information (updated every 5 minutes) Traffic. Location of traffic measurement points. Map of traffic intensity plots, with the same information in KML format, and with the possibility of viewing it in Google Maps or Google Earth. And other traffic-related data sets. You can search for them by putting the word 'Traffic' in the search engine (top right). In the section 'Associated documentation', there is an explanatory document with the structure of the files and recommendations on the use of the data.

2021 Annual Average Daily Traffic figures for state highway traffic count locations. Data represents all directions of travel for the given location.

The CTDOT Historical Traffic Monitoring GIS Data is a curated geospatial dataset integrated into the agency’s enterprise platforms, including the TED Portal and Open Data Hub. It supports transportation planning and safety analysis by providing historical traffic volumes and patterns across Connecticut’s roadway network. Managed by the Enterprise GIS Unit, the data is structured for internal use via ArcGIS Enterprise and selectively published to the public-facing Open Data Portal. It is actively maintained and synchronized through automated replication processes, although recent updates indicate occasional export issues requiring manual intervention. The dataset is also referenced in strategic planning tools and dashboards, and plays a key role in initiatives like the Highway Safety Road Map and the SMART grant application for connected infrastructure.

The Wisconsin Traffic Counts dataset combines traffic count data with GIS mapping technology to display data in a tabular format, on a map, or both. Traffic_Count_AADT is a source of Wisconsin DOT traffic data information for road sections of the State Highways or select Local Federal-Aid roads. Traffic counts are reported as the number of vehicles expected to pass a given location on an average day of the year. This value is called the "annual average daily traffic" or AADT. The AADT is produced for either continuous count sites or short duration count sites. WisDOT collects continuous count data from about 320 permanent data collection locations primarily located on the State Trunk Highway System. Data at continuous count sites are scheduled to be collected in hourly intervals each day of the year. A short duration traffic count usually collects hourly intervals for a 48-hour period, taken at the specific locations throughout the state. Using continuous count data, short duration counts are then adjusted for the variation in traffic volume that occurs throughout the year. Short duration counts are collected over three, six, or ten-year cycles at more than 26,000 rural and urban locations throughout the state. In addition to Wisconsin DOT use for transportation management purposes, Wisconsin DOT is required to collect and report these statistics to the Federal Highway Administration monthly and annually.Related Dataset: Traffic Counts

This is a dynamic traffic map service with capabilities for visualizing traffic speeds relative to free-flow speeds as well as traffic incidents which can be visualized and identified. The traffic data is updated every five minutes. Traffic speeds are displayed as a percentage of free-flow speeds, which is frequently the speed limit or how fast cars tend to travel when unencumbered by other vehicles. The streets are color coded as follows: Green (fast): 85 - 100% of free flow speeds Yellow (moderate): 65 - 85% Orange (slow); 45 - 65% Red (stop and go): 0 - 45%Esri's historical, live, and predictive traffic feeds come directly from TomTom (www.tomtom.com). Historical traffic is based on the average of observed speeds over the past year. The live and predictive traffic data is updated every five minutes through traffic feeds. The color coded traffic map layer can be used to represent relative traffic speeds; this is a common type of a map for online services and is used to provide context for routing, navigation and field operations. The traffic map layer contains two sublayers: Traffic and Live Traffic. The Traffic sublayer (shown by default) leverages historical, live and predictive traffic data; while the Live Traffic sublayer is calculated from just the live and predictive traffic data only. A color coded traffic map image can be requested for the current time and any time in the future. A map image for a future request might be used for planning purposes. The map layer also includes dynamic traffic incidents showing the location of accidents, construction, closures and other issues that could potentially impact the flow of traffic. Traffic incidents are commonly used to provide context for routing, navigation and field operations. Incidents are not features; they cannot be exported and stored for later use or additional analysis. The service works globally and can be used to visualize traffic speeds and incidents in many countries. Check the service coverage web map to determine availability in your area of interest. In the coverage map, the countries color coded in dark green support visualizing live traffic. The support for traffic incidents can be determined by identifying a country. For detailed information on this service, including a data coverage map, visit the directions and routing documentation and ArcGIS Help.

This map contains a dynamic traffic map service with capabilities for visualizing traffic speeds relative to free-flow speeds as well as traffic incidents which can be visualized and identified. The traffic data is updated every five minutes. Traffic speeds are displayed as a percentage of free-flow speeds, which is frequently the speed limit or how fast cars tend to travel when unencumbered by other vehicles. The streets are color coded as follows:Green (fast): 85 - 100% of free flow speedsYellow (moderate): 65 - 85%Orange (slow); 45 - 65%Red (stop and go): 0 - 45%Esri's historical, live, and predictive traffic feeds come directly from HERE (www.HERE.com). HERE collects billions of GPS and cell phone probe records per month and, where available, uses sensor and toll-tag data to augment the probe data collected. An advanced algorithm compiles the data and computes accurate speeds. The real-time and predictive traffic data is updated every five minutes through traffic feeds. The color coded traffic map layer can be used to represent relative traffic speeds; this is a common type of a map for online services and is used to provide context for routing, navigation and field operations. The color coded map leverages historical, real time and predictive traffic data. Historical traffic is based on the average of observed speeds over the past three years. A color coded traffic map can be requested for the current time and any time in the future. A map for a future request might be used for planning purposes. The map also includes dynamic traffic incidents showing the location of accidents, construction, closures and other issues that could potentially impact the flow of traffic. Traffic incidents are commonly used to provide context for routing, navigation and field operations. Incidents are not features; they cannot be exported and stored for later use or additional analysis. The service works globally and can be used to visualize traffic speeds and incidents in many countries. Check the service coverage web map to determine availability in your area of interest. In the coverage map, the countries color coded in dark green support visualizing live traffic. The support for traffic incidents can be determined by identifying a country. For detailed information on this service, including a data coverage map, visit the directions and routing documentation and ArcGIS Help.

A collection of historic traffic count data and guidelines for how to collect new data for Massachusetts Department of Transportation (MassDOT) projects.

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.

At Driver Technologies, we specialize in collecting high-quality, highly-anonymized, driving data crowdsourced using our dash cam app. Our Traffic Light Map Video Data is built from the millions of miles of driving data captured and is optimized to be trained for whatever computer vision models you need and enhancing various applications in transportation and safety.

What Makes Our Data Unique? What sets our Traffic Light Map Video Data apart is its comprehensive approach to road object detection. By leveraging advanced computer vision models, we analyze the captured video to identify and classify various road objects encountered during an end user's trip. This includes road signs, pedestrians, vehicles, traffic signs, and road conditions, resulting in rich, annotated datasets that can be used for a range of applications.

How Is the Data Generally Sourced? Our data is sourced directly from users who utilize our dash cam app, which harnesses the smartphone’s camera and sensors to record during a trip. This direct sourcing method ensures that our data is unbiased and represents a wide variety of conditions and environments. The data is not only authentic and reflective of current road conditions but is also abundant in volume, offering millions of miles of recorded trips that cover diverse scenarios.

Primary Use-Cases and Verticals The Traffic Light Map Video Data is tailored for various sectors, particularly those involved in transportation, urban planning, and autonomous vehicle development. Key use cases include:

Training Computer Vision Models: Clients can utilize our annotated data to develop and refine their own computer vision models for applications in autonomous vehicles, ensuring better object detection and decision-making capabilities in complex road environments.

Urban Planning and Infrastructure Development: Our data helps municipalities understand road usage patterns, enabling them to make informed decisions regarding infrastructure improvements, safety measures, and traffic light placement. Our data can also aid in making sure municipalities have an accurate count of signs in their area.

Integration with Our Broader Data Offering The Traffic Light Map Video Data is a crucial component of our broader data offerings at Driver Technologies. It complements our extensive library of driving data collected from various vehicles and road users, creating a comprehensive data ecosystem that supports multiple verticals, including insurance, automotive technology, and computer vision models.

In summary, Driver Technologies' Traffic Light Map Video Data provides a unique opportunity for data buyers to access high-quality, actionable insights that drive innovation across mobility. By integrating our Traffic Light Map Video Data with other datasets, clients can gain a holistic view of transportation dynamics, enhancing their analytical capabilities and decision-making processes.

This map features near real-time traffic information for different countries in Africa, designed for a night time display. This map contains a dynamic traffic map service with capabilities for visualizing traffic speeds relative to free-flow speeds as well as traffic incidents which can be visualized and identified. The traffic data is updated every five minutes. Traffic speeds are displayed as a percentage of free-flow speeds, which is frequently the speed limit or how fast cars tend to travel when unencumbered by other vehicles. The streets are color coded as follows:Green (fast): 85 - 100% of free flow speedsYellow (moderate): 65 - 85%Orange (slow); 45 - 65%Red (stop and go): 0 - 45%Esri's historical, live, and predictive traffic feeds come directly from HERE (www.HERE.com). HERE collects billions of GPS and cell phone probe records per month and, where available, uses sensor and toll-tag data to augment the probe data collected. An advanced algorithm compiles the data and computes accurate speeds. The real-time and predictive traffic data is updated every five minutes through traffic feeds. The color coded traffic map layer can be used to represent relative traffic speeds; this is a common type of a map for online services and is used to provide context for routing, navigation and field operations. The color coded map leverages historical, real time and predictive traffic data. Historical traffic is based on the average of observed speeds over the past three years. A color coded traffic map can be requested for the current time and any time in the future. A map for a future request might be used for planning purposes. The map also includes dynamic traffic incidents showing the location of accidents, construction, closures and other issues that could potentially impact the flow of traffic. Traffic incidents are commonly used to provide context for routing, navigation and field operations. Incidents are not features; they cannot be exported and stored for later use or additional analysis. The service works globally and can be used to visualize traffic speeds and incidents in many countries. Check the service coverage web map to determine availability in your area of interest. In the coverage map, the countries color coded in dark green support visualizing live traffic. The support for traffic incidents can be determined by identifying a country. For detailed information on this service, including a data coverage map, visit the directions and routing documentation and ArcGIS Help.

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.

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.

Feature layer containing authoritative traffic count points for the traffic model for Sioux Falls, South Dakota. The data in the traffic counts model feature layer is collected for traffic count modeling and transportation planning. This data is collected on a five-to-seven-year basis, with data from 2001, 2008, 2013, 2018, and 2023. The traffic counts are 24-hour, weekday, two-directional counts. Traffic counts are normally collected during the summer months, but may be taken any season, as weather permits. The traffic counts are factored by the day of the week as well as by the month of the year to become an Average Annual Daily Total (AADT). Traffic volumes (i.e., count data) can fluctuate depending on the month, week, day of collection, the weather, type of road surface, nearby construction, etc. All the historical data should be averaged to reflect the "normal" traffic count. More specific count data (time, date, hourly volume) can be obtained from the Sioux Falls Engineering Division at 605-367-8601.

2020 Annual Average Daily Traffic figures for state highway traffic count locations. Data represents all directions of travel for the given location.

Historical Annual Average Daily Traffic Volume datasets (2001 -> 2019) provides annual average daily traffic (AADT) volume data for all vehicles and heavy vehicles in each direction on each road segment on the Victoria declared road network. The data is either estimated through data processes or actual volumes from data collection.

AADT represents current (most recent) Annual Average Daily Traffic on sampled road systems. This information is displayed using the Traffic Count Locations Active feature class as of the annual HPMS freeze in January. Historical AADT is found in another table. Please note that updates to this dataset are on an annual basis, therefore the data may not match ground conditions or may not be available for new roadways. Resource Contact: Christy Prentice, Traffic Forecasting & Analysis (TFA), http://www.dot.state.mn.us/tda/contacts.html#TFA

Check other metadata records in this package for more information on Annual Average Daily Traffic Locations Information.


Link to ESRI Feature Service:

Annual Average Daily Traffic Locations in Minnesota: Annual Average Daily Traffic Locations

Lines that represent historic traffic closures. This dataset includes closures pertaining to trails, sidewalks, and City of Waterloo roads. Note the service that contains this data is only refreshed periodically but the content and data representing closures is updated daily at 7am, 1pm and 5pm.

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: https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_AnnualAverageDailyTraffic/FeatureServer 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.