Road networks data integration
Road operators collect traffic, incident, weather and asset data from roadside equipment, partner authorities and vehicles.
Example use case
A motorway operator merges DATEX II incidents, C-Roads messages and road weather forecasts to judge whether winter maintenance routes should start earlier on exposed sections.
Typical sources and transports
DATEX II over HTTPS, AMQP for C-ITS central interconnection, Extended Vehicle (ISO 20078) data, GeoJSON and GeoTIFF layers, Copernicus OData, and Eclipse Dataspace Connector exchanges.
What the data means
Situation records have validity periods and location referencing such as ALERT-C or OpenLR that must be resolved consistently.
Prerequisites
Before connecting road networks sources, prepare an inventory of systems and owners, interface documentation for each one, read-only credentials and approved network paths. Agree identifiers, units and time zones early, and name a person who can confirm values against the source during commissioning.
Limitations
Partner exchanges depend on agreements and specific profiles. Vehicle data access is governed by manufacturers and is validated per case.
ALLINLET reads and normalises data; it does not control equipment.
Catalogue entries for this domain
The connector catalogue lists 46 entries for this domain. A selection is shown below. Listing indicates a possible integration path, not that it is implemented, validated or installed for your environment.
- Batch files
- CDC
- Central interconnection via AMQP (C-Roads)
- Copernicus Data Space (OData)
- DATEX II
- DCAT catalogue
- Dedicated integration
- Eclipse Dataspace Connector (EDC)
- Extended Vehicle (ISO 20078)
- File transfer
- Files
- GBFS (shared mobility)
- GeoJSON
- GeoTIFF / COG
- GTFS-Realtime
- HTTPS download
- IEC 60870-5-104
- IFC / BIM
Further reading
Catalogue listings describe possible integration paths. Implementation and validation status is confirmed for each source during project scoping; no certification, service level or price is implied by this page.
Plan your data integration
Share your devices, protocols and network constraints, and we will propose a first validated connection.