GraphHopper Open Traffic Collection

Collections of URLs pointing to traffic information portals which contain open data or at least data which is free to use

Australia

• Victoria

Canada

• British Columbia

Europe

• Austria: Various data sets in Datex-II format. Requires registration; some packages are free of charge, others only for a fee. There is also an open rss feed. See #25.
• Belgium:
  • Brussels Region: real-time traffic counting
  • Roadworks in Datex-II format. Relies on Alert-C for location decoding; ignore the alertCLocationTableNumber indicated in the Datex-II stream and use the default table for Belgium.
• Catalonia: traffic events, custom XML format.
• Czechia: Feeds for common traffic information, restrictions and weather. Available in both Datex-II and a custom format called DDR XML. Requires registration (free of charge) and running a server, to which the service will then push updates as they occur.
• Estonia: road safety, traffic restrictions and real time traffic flow in Datex-II format. Location referencing seems to rely mainly on distance markers (on which data on OSM is scarce); WGS84 is used for single-point locations only; Alert-C is not used. Requires registration, free of charge.
• Finland:
  • Digitraffic has several data sets, some in a custom JSON format, others in Datex-II level C
  • Roadworks in Datex-II and InfoXML format. The Datex-II set relies on Alert-C for location referencing.
  • Weight restrictions in Datex-II, relies on Alert-C for location referencing.
• France
  • Traffic count
  • Datex-II live traffic data
  • Datex-II event data
  • Paris: Road traffic data from permanent counters
• Germany:
  • Cologne, CC BY 3.0, traffic flow. See this blog post
  • Düsseldorf traffic interruptions, DL-DE->Zero-2.0
  • Jena
  • Darmstadt
  • Hamburg, WFS Daten
  • Nordrhein-Westfalen, DE and other data.
  • Entire DE (broken) traffic count only
  • Entire DE BASt traffic count only
  • German Mobilithek which replaces the MDM platform and mCLOUD.
  • Entire DE - inofficial API to get construction and traffic information on motorways
• Italy:
  • Bolzano documentation here, repo here. See #1
  • South Tyrol: traffic reports, mountain pass conditions and closures, roadworks and closures. They also advertise reports from neighboring regions but the feed seems to be empty. Available custom GML, JSON or CSV formats.
  • Turin, Italy documentation here. See #13
• Lithuania:
  • traffic count
  • restrictions: Roadworks, road closures and restrictions, incidents; JSON-based format similar to Waze CIFS. More information at http://eismoinfo.lt > Open data/Atviri duomenys.
  • intensity: Real-time traffic flow data. More information at http://eismoinfo.lt > Open data/Atviri duomenys (note that the URL has changed since). Note that coordinates for road segments are in LKS94 (EPSG:3346).
• Luxembourg: Traffic events in Datex-II format. Relies on Alert-C for location referencing.
• Netherlands via the NDW. FTP-Server for data and measurements is ftp://83.247.110.3/ , see #2. Feeds are also available at http://opendata.ndw.nu/. Specifically:
  • brugopeningen has time tables for movable bridges, indicating when they are opened (i.e. raised) and thus impassable for road traffic
  • gebeurtenisinfo: traffic messages, e.g. traffic jams, wrong-way drivers, closures, detours and weather conditions
  • incidents: Breakdowns and accidents
  • srti has safety-related traffic information
  • wegwerkzaamheden: roadworks and event-related traffic measures
  • There are also various measured data publications, indicating traffic flow, speed, travel times and queues. The Datex-II situation reports rely heavily on Alert-C for location encoding. However, they do not use the regular Alert-C location code list for the Netherlands, but the VILD, which has incompatible lcoation codes. It can be downloaded from https://www.ndw.nu/documenten/nl/#cat_2. A semi-automatic process to convert the VILD to a Location Table Exchange Format, as understood by Alert-C toolchains, is described here.
• Norway: Various data sets in Datex-II format, requires registration. Relies on Alert-C for location referencing, the LCL can be downloaded from the site.
• Poland:
  • Traffic events in a custom XML format. Georeferencing is based on distance markers along the road; the WGS84 coordinate pair which accompanies the message is only suitable for display and can be significantly off. traff-gddkia is an attempt at a FOSS Java library which parses the data.
  • The NAP has Datex-II traffic data; registration is required to get access.
• Slovenia: various data sets in Datex-II format, requires registration.
• Spain
  • Madrid: Historical and real-time traffic data at city of Madrid's Open data portal
• Sweden:
  • Gothenbury
  • Various data sets in Datex-II, registration required
• Switzerland traffic count only
• UK:
  • England: various Datex-II data sets, registration required.
  • Scotland: various Datex-II data sets, registration required.
  • Entire UK traffic count only
  • Traffic flow data

Europe Misc

• traffic data set of several cities https://github.com/ambuehll/UTD19/ under CC BY-NC-SA 4.0
• Many EU data sets are available at the European Data Portal
• EU authorities rely heavily on the Datex-II format for data exchange. Many of these data sets use Alert-C for location referencing and require a location code list (LCL) for location lookup.
• In most cases the LCL can be obtained free of charge (at least for the countries which rely on Alert-C in their Datex-II feeds) and can be incorporated in applications, devices and information services, but some impose restrictions on redistribution of the raw tables. The OSM Wiki has a list of sources where LCLs can be obtained.
• A FOSS Java library for location decoding is available here: traff-libalertclocation Decoding an Alert-C location requires the country code, location table number (LTN) and location code.
• Some sources supply an incorrect LTN; ignore the alertCLocationTableNumber elements in the data and use the correct one instead. (The only exception being the Netherlands, see above.)
• UNECE Traffic Census (updated every 5 years), showing AADT for segments of E-Roads within the UNECE region UNECE traffic census 2020

USA

Several entries are take from this stackexchange answer

• nationwide
• Alabama
• Arizona
• Arlington
• California
• Chicago or one specific set
• Colorado
• Delaware Valley
• Florida
• Indiana
• Maine
• Massachusetts
• Michigan (seems to be no longer available)
• Minnesota
• New York City and New York
• North Carolina
• Ohio
• Oregon
• South Carolina
• Tennessee (seems to be no longer available)
• Washington
• Wisconsin

Misc

• Datex2 Portal, See more information about the UK data here
• EU - Historic Road data
• MDM-Portal (coverage will be Europe, free to use): Düsseldorf Germany, NRW Germany, ...
• NYC Taxi and Limousine Commission: NYC taxi data, dating back to 2009. See also this blog post and this github repository
• Open Traffic Data project
• OpenTraffic.io -> seems inactive
• Telraam: traffic count in several places of the whole world; general documentation; API docs; limitations.