TomTom Traffic Incidents - Intermediate Service - Protobuf

Traffic event end time

The feature is represented by the field endTimeUTCSeconds within the message type Event. This field is expressed as a UTC time (e.g. 14:22 UTC). These end times may be created by TomTom or originate from, for example, local road authorities (for journalistic events).

Jam tendency

trafficIncidents {
  [...]
  event {
    trafficCondition: SLOW_TRAFFIC
    [...]
    tendency: TRAFFIC_BUILDING_UP
    [...]
  }
}

Weather-related messages

Jam ahead warnings

An OpenLR point along line reference is used for this traffic incident type. The jam ahead warning is recognized by a location with type POINT in combination with a traffic condition that indicates a congestion event.

trafficIncidents {
  [...]
  location {
    type: POINT
    openlr: "+\251I.\032\250^\001\v\017\002\231\375\203\001]W"
    [...]
  }
  event {
    trafficCondition: STATIONARY_TRAFFIC
    averageSpeedHmph {
      value: 190
    }
    alertCEventCode {
      mainEvent: 101
    }
  }
}

Average speed for journalistic events

Example of a roadworks element with speed and delay information:

trafficIncidents {
  [...]
  event {
    averageSpeedHmph {
      value: 191
    }
    delaySeconds {
      value: 11
    }
    alertCEventCode {
      mainEvent: 701
      additionalEvents: 810
    }
  }
}

Turn-dependent jams

We provide a field called conditionalOffsetMeters within the message type Location. To find the actual affected location, the offset needs to be applied from the end of the location. For more information, see Figure 1.

trafficIncidents {
  [...]
  location {
    type: LINEAR
    openlr: "\v\271\365\312\025\016\374\"\217\b\377\366\376N&E+"
    [...]
    conditionalOffsetMeters {
      value: 131
    }
  }
  event {
    trafficCondition: QUEUING_TRAFFIC
    averageSpeedHmph {
      value: 125
    }
    delaySeconds {
      value: 96
    }
    alertCEventCode {
      mainEvent: 108
    }
  }
}

Incident node name

We provide two fields called fromNodeName and toNodeName within the message type Location.

trafficIncidents {
  [...]
  location {
    [...]
    fromNodeName: "Nord-West-Umfahrung / Gottlieb-Daimler-Straße"
    toNodeName: "Nürtinger Straße (L1205)"
    [...]
  }
  [...]
}

Road number

We provide a field called roadNumber within the message type Location.

Example for the German freeway (Autobahn) A3:

trafficIncidents {
  [...]
  location {
    [...]
    roadNumber: "A3"
    [...]
  }
  [...]
}

Future incidents

We provide the field startTimeUTCSeconds within the message type Event. The start time of future incidents is after the snapshot creation time (see also creationTimeUTCSeconds in Standard information).

metaInformation {
  creationTimeUTCSeconds: 1570000000
  [...]
}
trafficIncidents {
  [...]
  event {
    [...]
    startTimeUTCSeconds: 1575000000
    [...]
  }
}

Map version

metaInformation {
  [...]
  mapVersion: "nam2019.09.011"
}

We provide prediction within the message type TrafficIncident. The prediction is composed of a location element and multiple prediction states.

The location covers the complete extension of the predicted congestion over time. It is represented by the message type Location and the same features are supported as with the regular location field inside TrafficIncident. The location element within TrafficIncident is also set for congestion events that contain prediction. However, this location is only valid for the speed information provided in the Event message.

PredictionState is the message type that represents a prediction state. Each state is identified by a time (the field timeUTCSeconds) that indicates when the state is valid. The list of states is ordered by that prediction time. Furthermore, a prediction state provides:

• the predicted speed (in the field speedHmph),
• an offset value (in the field lengthOffsetMeters) and affected length (in the field lengthAffectedMeters) to localise the affected location along the overall predicted location, and
• the free-flow speed (in the field freeFlowSpeedHmph) along the affected location.

trafficIncident {
  trafficIncidentManagent {
    [...]
  }
  event {
    [...]
  }
  location {
    [...]
  }
  prediction {
    location {
      type: LINEAR
      openlr: "\v\254\r]\030H\242\001\026E\357|\001l\001\t"
    }
    predictionStates {
      timeUTCSeconds: 1575913230
      speedHmph {
        value: 324
      }
      freeFlowSpeedHmph {
        value: 1121
      }
      lengthOffsetMeters {
      }
      lengthAffectedMeters {
        value: 436
      }
    }
    predictionStates {
      timeUTCSeconds: 1575913499
      speedHmph {
        value: 324
      }
      freeFlowSpeedHmph {
        value: 1121
      }
      lengthOffsetMeters {
      }
      lengthAffectedMeters {
        value: 436
      }
    }
    [...]
  }
}