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 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. Historical traffic is based on the average of observed speeds over the past three years. 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 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 hosted feature layer has been published in RI State Plane Feet NAD 83.This data set was created for the Rhode Island Dept. of Transportation. This data set contains locations for the 24 hour average daily traffic counts on state maintained roads with information containing the station number, the segment of roadway the count was taken on, the city the count location is in and the actual 24 hour average counts for each location.This data set contains the annual 24 Hour Average Daily Traffic Count Locations on State maintained roads in Rhode Island for 2001.

This web map contains traffic point and polygon layers from OSM (OpenStreetMap) in India and contains information about crossing, dam, fuel, lock gate etc.OSM is a collaborative, open project to create a freely available and editable map of the world. Geographic information about streets, rivers, borders, points of interest and areas are collected worldwide and stored in a freely accessible database. Everyone can participate and contribute to OSM. The geographic information available on OSM relies entirely on volunteers or contributors.The attributes are given below:CrossingDamFuelLock GateMarinaMini RoundaboutMotorway JunctionParkingParking BicycleParking MultistoreyParking UndergroundPierServiceSlipwaySpeed CameraStopStreet LampTraffic SignalsTurning CircleWaterfallWeirThese map layers are offered by Esri India Content. The content team updates the map layers quarterly. If you have any questions or comments, please let us know via content@esri.in.

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.

This webmap shows average traffic speed of major roads in Hong Kong. It is made available by the Transport Department under the Government of Hong Kong Special Administrative Region (the “Government”) at https://DATA.GOV.HK/ (“DATA.GOV.HK”). The source data is in XML web service and been processed and converted into Esri File Geodatabase format and then uploaded to Esri’s ArcGIS Online platform for sharing and reference purpose. The objectives are to facilitate our Hong Kong ArcGIS Online users to use the data in a spatial ready format and save their data conversion effort.

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

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

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.

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

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.

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.

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.

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

Interactive map displaying average road traffic volumes for a selection of permanent Roads and Maritime Services roadside collection device stations across NSW. Figures will be updated annually.

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

City and county traffic maps are updated every four years. Statewide vehicular, truck and interstate traffic maps are located here. The interactive statewide maps for traffic for all roadways and the turning movement counts for select intersections can be found here.