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

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

Locations where the Los Angeles Department of Transportation has collected traffic information.

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.

This information is updated almost in real time, with a frequency of about 5 minutes, which is the minimum time of several traffic light cycles, necessary to give a real measurement, and that the measurement is not affected in case the traffic light is open or closed. There are other related data sets such as: Oh, traffic. Map of traffic intensity frames, with the same information in KML format, and with the possibility of seeing it in Google Maps or Google Earth. Oh, traffic. Location of traffic measurement points. Traffic data history since 2013 NOTICE: The data structure of the file has been changed by incorporating date, time and coordinates x e and of the measurement. You can view all the traffic information of the City on the Madrid mobility information website, Report: http://informo.munimadrid.es

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.

This dataset contains estimates of the average number of vehicles that used roads throughout the City of Detroit. 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.

Intensity information (vehicles/hour) represented by ranges and with the following colour code: The KML files are updated almost in real time, with a periodicity of 5 minutes. There are two other parameters that indicate the degree of traffic flow such as service level and load. Service level is also a qualitative and immediacy parameter, calculated from speed and occupancy. It is offered in the real-time traffic dataset with 4 levels: fluid, slow, withholding and congestion. It can also be viewed in the Informo portal with color coding. On the other hand, the load parameter is calculated from the intensity (vehicles/hour) and occupation. It can be found in the traffic data historical set. There are other related datasets in the Open Data Portal that offer the aforementioned parameters such as: Traffic. Real-time traffic data Traffic. Location of traffic measurement points. History of traffic data since 2013 In the section “ Associated documentation ” an explanatory document is provided in order to be able to correctly interpret the various fields of the dataset. Recommendations for use and additional information are also included to make them easier to understand. This information can be viewed, along with the rest of the traffic information of the city of Madrid, on the Informo portal: https://informo.madrid.es

The FDOT Historical Annual Average Daily Traffic feature class provides spatial information on Annual Average Daily Traffic section breaks for the state of Florida. In addition, it provides affiliated traffic information like KFCTR, DFCTR and TFCTR among others. It contains five years of AADT data including the most currently available year. This dataset is maintained by the Transportation Data & Analytics office (TDA). The source spatial data for this hosted feature layer was created on: 06/21/2025.Download Data: Enter Guest as Username to download the source shapefile from here: https://ftp.fdot.gov/file/d/FTP/FDOT/co/planning/transtat/gis/shapefiles/aadt_historical.zip

The data included in the GIS Traffic Stations Version database have been collected by the FHWA from the State DOTs. Location referencing information was derived from State offices of Transportation The attributes on the point elements of the database are used by FHWA for its Travel Monitoring and Analysis System and by State DOTs. The attributes for these databases have been intentionally limited to location referencing attributes since the core station description attribute data are contained within the Station Description Tables (SDT). here is a separate Station Description Table (SDT) for each of the station types. The attributes in the Station Description Table correspond with the Station Description Record found in Chapter 6 of the latest Traffic Monitoring Guide. The SDT contains the most recent stations available for each state and station type. This table was derived from files provided UTCTR by FHWA. The Station Description Table can be linked to the station shapefile via the STNNKEY field. Some station where not located in the US, and were beyond available geographic extents causing display problems. These were moved to Lat and Long 0,0. This is in recognition that the locations of these stations where in error, but were moved to a less obtusive area.

This layer is sourced from maps.bts.dot.gov.

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.

Traffic volume of Roadway Blocks. The dataset contains traffic volume data, created as part of the District of Columbia, Department of Transportation (DDOT) Roads and Highways database. A database provided by the District of Columbia, Department of Transportation identified traffic volume. Count data is collected (both direction) at pre-selected locations on Highway Performance Monitoring System (HPMS) Sections on a three-year cycle. These counts are converted to Annual Average Daily Traffic (AADT).

Historical data of traffic measurement points. Each month the data of the previous month are incorporated. 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.

This dataset represents average daily traffic (ADT) and annual average daily traffic (AADT) counts from 2005 until today. More detailed data (excel spreadsheets) and pdf maps for the MSB traffic count program can be found here: https://www.matsugov.us/traffic-data-program

The map layers in this service provide color-coded maps of the traffic conditions you can expect for the present time (the default). The map shows present traffic as a blend of live and typical information. Live speeds are used wherever available and are established from real-time sensor readings. Typical speeds come from a record of average speeds, which are collected over several weeks within the last year or so. Layers also show current incident locations where available. By changing the map time, the service can also provide past and future conditions. Live readings from sensors are saved for 12 hours, so setting the map time back within 12 hours allows you to see a actual recorded traffic speeds, supplemented with typical averages by default. You can choose to turn off the average speeds and see only the recorded live traffic speeds for any time within the 12-hour window. Predictive traffic conditions are shown for any time in the future.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. 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.Data sourceEsri’s typical speed records and 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.Data coverageThe 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. Look at the coverage map to learn whether a country currently supports traffic. The support for traffic incidents can be determined by identifying a country. For detailed information on this service, visit the directions and routing documentation and the ArcGIS Help.SymbologyTraffic 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%To view live traffic only—that is, excluding typical traffic conditions—enable the Live Traffic layer and disable the Traffic layer. (You can find these layers under World/Traffic > [region] > [region] Traffic). To view more comprehensive traffic information that includes live and typical conditions, disable the Live Traffic layer and enable the Traffic layer.ArcGIS Online organization subscriptionImportant Note:The World Traffic map service is available for users with an ArcGIS Online organizational subscription. To access this map service, you'll need to sign in with an account that is a member of an organizational subscription. If you don't have an organizational subscription, you can create a new account and then sign up for a 30-day trial of ArcGIS Online.

Feature layer containing authoritative traffic count points for Sioux Falls, South Dakota.The traffic counts listed 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 of 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 367-8601.

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

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.

Irys specializes in collecting and curating high-quality geolocation signals from millions of connected devices across the globe. Our real-time and historical foot traffic data, categorized under Map Data, is sourced through partnerships with tier-1 mobile applications and app developers. The advanced aggregated location data covers the entire world, providing valuable insights for diverse use-cases related to Transport and Logistic Data, Mobile Location Data, Mobility Data, and IP Address Data.

Our commitment to privacy compliance is paramount. We ensure that all data is collected in accordance with privacy regulations, accompanied by clear and compliant privacy notices. Our opt-in/out management allows for transparent control over data collection, use, and distribution to third parties.

Discover the power of foot traffic data with Irys – where precision meets privacy.

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.