Here Traffic Api
This dataset falls under the category Individual Transport Traffic Control Systems.
It contains the following data: Traffic flow and Traffic incident on road
This dataset was scouted on 2022-02-05 as part of a data sourcing project conducted by TUMI. License information might be outdated: Check original source for current licensing. The data can be accessed using the following URL / API Endpoint: https://developer.here.com/documentation/traffic-api/dev_guide/index.html

Due to unforeseen circumstances, this service is temporarily out of order. We are sorry for the trouble this may cause you. We are working hard to restore the service as soon as possible, but we cannot provide an estimated time of resolution at the moment.Network operations traffic data from Main Roads Western Australia from 01 January 2013. The data from this API includes data collected on the Perth Metropolitan State Road Network (PMSRN) at 15 minute intervals. The network operations traffic data provided here is of variable quality and has not been checked, quality assured or manually corrected. An automated process is used to patch over missing or suspect data with the most representative data available within the database. Patches may be reapplied as new data becomes available and patched data may change over time. Note that you are accessing this data pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes. Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material: “The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.” Instructions and documentation for using this API: Links Reporting Links: publicirisservices.mainroads.wa.gov.au/RoadNetworkPerformanceService/api/ReportingLinks Link Data: publicirisservices.mainroads.wa.gov.au/RoadNetworkPerformanceService/api/LinkData?linkdatadate=2017-9-1

The historical traffic API provides historical data on NSW incidents. Live Traffic NSW allows you to search for a particular date and location.

RMS has permanent and temporary roadside collection devices which continuously collect traffic information data. Through the Traffic Volume Counts API, traffic count data from 2006 is available. There are four datasets (tables) that can be queried: Traffic Collection Station Reference- This table provides a general description of the traffic collection station e.g. Geospatial coordinates, road name, suburb, postcode, device type, road number, road type including the data quality rating. Annual Average Traffic Count Summary - This table provides the general description of traffic station, traffic direction, date of recording and the quality of data. Permanent Hourly Traffic Counts- This table provides hourly traffic count for each permanent station post 2006 at a daily level. Sample Hourly Traffic Counts - This table provides hourly traffic count for each sample station post 2006 at a daily level. The Traffic Volume Viewer map provides average road traffic volumes for a selection of permanent and sample roadside collection device stations at key locations across NSW. Please visit https://www.rms.nsw.gov.au/about/corporate-publications/statistics/traff...

Traffic and road condition information captured in the QLDTraffic system is available for use by external developers via GeoJSON feeds.

These feeds cover Hazards, Crashes, Congestion, Flooding, Roadworks and Special Events and Web Cameras details.

The information provided in these feeds is on an 'as is' basis. Additional details about the available information on the QLDTraffic site can be viewed on our disclaimer page .

Transport and Main Roads (TMR) is constantly striving to ensure that they provide accurate, reliable and timely traffic and road condition information.

Given this, the previously available API has undergone changes in August 2016 with the creation of the QLDTraffic public website.

Details on accessing QLDTraffic’s traffic and road condition information via GeoJSON can be found in the QLDTraffic website application programming interface (API) specification.

This API has been developed to allow improved integration of QLDTraffic traffic and road condition information with external systems.

Please be aware that this specification may be subject to change.

Real time traffic data from the Swedish Transport Administration, API

Explore Serpstat's Backlinks API Insights, providing real-time access to comprehensive backlink data at the lowest possible cost. With pricing starting at just $120 for 1M API Data rows, our API offers unparalleled value for businesses of all sizes.

With seamless integration and no separation between fresh and historical records, our API provides a holistic view of backlink profiles, encompassing 1.7 trillion links and 170 million domains. Plus, with no API credits burnout at the end of the month, you can use the API without constraints.

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

TomTom's Safety Related Traffic Information (SRTI) API is a webservice that delivers anonymized non-personal raw data on hazardous situations directly collected by TomTom's own applications. The content of the API includes anonymized, non-personal, crowd-sourced data from drivers using TomTom's AmiGO application that reports 'hazards' and 'broken down car' incidents on the road. In accordance with EU Regulation 886/2013, this data is accessible to other users and can be integrated in other applications to improve road safety conditions. The access and use of this data are laid out in our terms and conditions. The service delivers safety messages for the area of the European Union in the form of a RESTful web service. The content contains information based on sensor or end-user feedback.

Traffic Flow Data In Ho Chi Minh City, Viet Nam
This dataset falls under the category Traffic Generating Parameters.
It contains the following data: Traffic flow
This dataset was scouted on 2022-02-10 as part of a data sourcing project conducted by TUMI. License information might be outdated: Check original source for current licensing. The data can be accessed using the following URL / API Endpoint: https://www.kaggle.com/thanhnguyen2612/traffic-flow-data-in-ho-chi-minh-city-viet-nam

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.

Experience the power of Serpstat's Website Data API, offering comprehensive insights into key SEO metrics, organic traffic estimation, and semantical structure analysis. With our API, unlock valuable data to identify top-performing industry players, analyze competitor strategies, and optimize content for maximum impact.

Unveil essential SEO metrics such as website visibility, organic traffic estimation, and keywords that websites rank for organically. Additionally, gain insights into keywords that websites are shown in Google Ads, providing valuable intelligence for ad targeting and optimization.

Utilize our API to uncover top-performing content in any industry, enabling you to identify trends, understand user intent, and refine your content strategy accordingly.

Benefit from the most cost-effective API solution, starting at just $120 per million rows. Tailor your queries to extract the most relevant data for your specific use-cases, ensuring that you're equipped with the insights necessary to thrive in today's competitive digital landscape.

This dataset contains historic Route Definitions and Statistics with Geometry of traffic flow. The detailed documentation is included at https://www.data.act.gov.au/dataset/realtime-traffic/cjkg-rvmu. Disclaimer : Even though the real-time API updates the info every 30 seconds, we only sample at every 5 minutes for historical archiving

You can also access a zipped csv file version of this

dataset.TMS

(traffic monitoring system) daily-updated traffic counts CSVData 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

TMS

(traffic monitoring system) traffic – historic quarter hourly

The Traffic and Travel Data System API lets you access real time data on events / incidents that affect traffic conditions across the network of national highways in New Zealand. An example of an event/incident could include road works, an accident, or weather related problems such as ice or snow.Traffic and Travel Data System API services currently include:· Real time data on traffic conditions and congestion on national highways.· Estimates of the time required for vehicles to travel along sections of the state highway and arterial network.· Real time data on events and incidents, including weather and general warnings, that affect traffic conditions across the network of national state highways.· Static images from over 100 cameras across various parts of New Zealand.· Messaging displayed on Variable Message Signs (VMS) across various parts of New Zealand.Available RESTful API services· Endpoint address: https://trafficnz.info/service/traffic/rest/4· WADL: https://trafficnz.info/service/traffic/rest/4?_wadlWe have several SOAP API services available as well. Details are described at this site: https://www.nzta.govt.nz/traffic-and-travel-information/use-our-data/about-the-apis/Usage CaveatsThis information is ONLY for notable events and/or incidents that may cause delays to road users or require caution, and only where the details have been verified by the Waka Kotahi or another official source.Data QualityAs of 3 October 2024, previous known quality issues have been repaired where there were null or missing values. These fields are now showing valid values: - Event Comment - Alternative Route - Event ModifiedResourcesThis data service is intended for data architects and developers that must integrate their applications with the Traffic and Travel Data web services API.Data elements included in each API Service are listed on the NZTA information page: https://www.nzta.govt.nz/traffic-and-travel-information/use-our-data/about-the-apis/ We are happy to have your feedback on this NZTA Open Data product. Please contact us at opendata@nzta.govt.nz.

NOTE: The Historic Traffic Data Dashboard & Feature Hosted Service have been retired.Network operations traffic data from Main Roads Western Australia for 2015 to 2019. The data provided includes data collected on the Perth Metropolitan State Road Network (PMSRN) at 15 minute intervals.

The Historic Traffic Data is provided in CSV format per year. Each table has over 34 million rows and can be linked to the M-Links Road Network using the M-Links ID. A data dictionary for M-Links Road Network and the Historic Traffic Data is at the following link:https://bit.ly/2S86uSnNetwork Operations traffic data can also be accessed via the Daily Traffic Data API at the following link: https://bit.ly/34ZsyAK

The network operations traffic data provided here is of variable quality and has not been checked, quality assured or manually corrected. An automated process is used to patch over missing or suspect data with the most representative data available within the database. Patches may be reapplied as new data becomes available and patched data may change over time.

Note that you are accessing this data pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes.

Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material:- “The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.”

Point layer used to represent the spatial location of all Traffic Count Stations maintained and counted on an annual basis by Miami-Dade County Public Works and Waste Management Department.Updated: Annually The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

You can also access a zipped csv file version of this dataset.TMS (traffic monitoring system) daily-updated traffic counts CSVData 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 TMS (traffic monitoring system) traffic – historic quarter hourly

NOTE: The Historic Traffic Data Dashboard & Feature Hosted Service have been retired.Network operations traffic data from Main Roads Western Australia for 2015 to 2019. The data provided includes data collected on the Perth Metropolitan State Road Network (PMSRN) at 15 minute intervals. The Historic Traffic Data is provided in CSV format per year. Each table has over 34 million rows and can be linked to the M-Links Road Network using the M-Links ID. A data dictionary for M-Links Road Network and the Historic Traffic Data is at the following link:https://bit.ly/2S86uSnNetwork Operations traffic data can also be accessed via the Daily Traffic Data API at the following link: https://bit.ly/34ZsyAK The network operations traffic data provided here is of variable quality and has not been checked, quality assured or manually corrected. An automated process is used to patch over missing or suspect data with the most representative data available within the database. Patches may be reapplied as new data becomes available and patched data may change over time. Note that you are accessing this data pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes. Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material:- “The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.”

In the ACT, we have bluetooth detectors placed in certain roads to monitor traffic flow that provides network-wide performance indicators in real time. Details about congestion & travel time can be accessed via APIs provided in this dataset