Service version: 1
Last edit: 2026.04.29

Data delivery and access

  • Data is provisioned via an Azure storage account owned by TomTom.
  • Access is shared directly with the customer; the customer downloads the data.
  • Traffic Stats Batch data must be downloaded by the customer from the TomTom-managed Azure Storage account and stored in a customer-managed storage environment of their choice.
  • All analysis, processing, and visualization of Traffic Stats Batch data is performed outside of TomTom systems, using the customer's own analytics tools and infrastructure.

File and directory structure

Traffic Stats Batch data is delivered in a directory structure that encodes important metadata. Some information required for correct ingestion (such as date, map version, and segment identifier type) is not present as fields in the Avro records and must be derived from the directory path.

Top-level directories

  • segmentsV6/ - Contains the Road Network files (segment geometry and static attributes).
  • all/ - Contains the Traffic Stats files (hourly aggregated traffic metrics).

These directory names distinguish the two file types and should not be interchanged.

Segment identifier type

  • OPEN_DSEG/ - Indicates TomTom's open directional segment identifier type.

All Traffic Stats Batch deliveries currently use OPEN_DSEG.

Map version (must match for joins)

  • Example directory: 2024.12.1000/
  • Format: year.month.build

Traffic data and road network data must use the same map version to join correctly using dsegId. Mixing versions can result in failed joins or incorrect spatial alignment.

Tile identifiers

  • Numeric directories such as 46548/ or 57472/ represent Morton (Z-order curve) tile IDs at level 8.
  • Tile IDs are used for data partitioning only.
  • No direct geographic mapping for tile IDs is provided in the delivery.

Spatial analysis should always be performed using segment geometry, not tile identifiers.

Date from directory path

  • Example directory: 2025-09-01/
  • The date is not included as a field in the Avro records.
  • It must be parsed from the directory path during ingestion if required for analysis.

Example path breakdown

all/OPEN_DSEG/2024.12.1000/46548/2025-09-01/

This path encodes:

  • Segment type: OPEN_DSEG
  • Map version: 2024.12.1000
  • Tile ID: 46548
  • Date: 2025-09-01

Geographic resolution constraint

Traffic Stats Batch uses Morton tiles at level 8 which defines the minimum deliverable tile size and prevents delivering smaller custom areas via Batch. For smaller areas, use Traffic Stats via API.

Morton tile 8 size depends on the latitude of the area. In the UK, the average size is approximately 88 km x 75 km.