Calculate Route

Service version: 1
Last edit: 2023.07.19

Purpose

The Calculate Route service calculates a route between an origin and a destination, passing through waypoints if they are specified.

  • The route will take into account factors such as current traffic and the typical road speeds on the requested day of the week and time of day.
  • Information returned includes the distance, estimated travel time, and a representation of the route geometry.
  • Additional routing information such as optimized waypoint order or turn by turn instructions is also available, depending on the options selected.

Run this endpoint

You can easily run this and other endpoints. Go to the TomTom API Explorer page and follow the directions.

Request data

HTTPS method: GET   POST

Constants and parameters enclosed in curly brackets { } must be replaced with their values.

Generic request format

The following request URL contains all of this endpoint's respective parameters. For their details, please see the Common Routing Parameters page. In addition this endpoint supports guidance functionality that is collectively described in the Guidance Instructions page.

GET
Generic request format
1

2```shell [type=get] [title=Generic request example]
3https://{baseURL}/routing/{versionNumber}/calculateRoute/{routePlanningLocations}/{contentType}?key={Your_API_Key}
4&callback={callback}
5&maxAlternatives={alternativeRoutes}
6&alternativeType={alternativeType}
7&minDeviationDistance={integer}
8&minDeviationTime={integer}
9&supportingPointIndexOfOrigin={integer}
10&computeBestOrder={boolean}
11&routeRepresentation={routeRepresentation}
12&computeTravelTimeFor={trafficTypes}
13&vehicleHeading={integer}
14&sectionType={sectionType}
15&report={effectiveSettings}
16&departAt={time}
17&arriveAt={time}
18&routeType={routeType}
19&traffic={boolean}
20&avoid={avoidType}
21&prefer={preferType}
22&travelMode={travelMode}
23&hilliness={hilliness}
24&windingness={windingness}
25&vehicleMaxSpeed={vehicleMaxSpeed}
26&vehicleWeight={vehicleWeight}
27&vehicleAxleWeight={vehicleAxleWeight}
28&vehicleLength={vehicleLength}
29&vehicleWidth={vehicleWidth}
30&vehicleHeight={vehicleHeight}
31&vehicleCommercial={boolean}
32&vehicleLoadType={vehicleLoadType}
33&vehicleAdrTunnelRestrictionCode={vehicleAdrTunnelRestrictionCode}
34&vehicleEngineType={vehicleEngineType}
35&handsFreeDrivingCapability={handsFreeDrivingCapability}
36&constantSpeedConsumptionInLitersPerHundredkm={CombustionConstantSpeedConsumptionPairs}
37&currentFuelInLiters={float}
38&auxiliaryPowerInLitersPerHour={float}
39&fuelEnergyDensityInMJoulesPerLiter={float}
40&accelerationEfficiency={float}
41&decelerationEfficiency={float}
42&uphillEfficiency={float}
43&downhillEfficiency={float}
44&consumptionInkWhPerkmAltitudeGain={float}
45&recuperationInkWhPerkmAltitudeLoss={float}
46&constantSpeedConsumptionInkWhPerHundredkm={ElectricConstantSpeedConsumptionPairs}
47&currentChargeInkWh={float}
48&maxChargeInkWh={float}
49&auxiliaryPowerInkW={float}
50&chargeMarginsInkWh={commaSeparatedFloats}
51&extendedRouteRepresentation={extendedRouteRepresentation}

GET URL example

Note: Linebreaks are designated by "\".

GET
Request URL example
1https://api.tomtom.com/routing/1/calculateRoute/\
252.50931,13.42936:52.50274,13.43872/json?\
3&vehicleHeading=90&sectionType=traffic\
4&report=effectiveSettings&routeType=eco\
5&traffic=true&avoid=unpavedRoads\
6&travelMode=car&vehicleMaxSpeed=120\
7&vehicleCommercial=false&vehicleEngineType=combustion\
8&key={Your_API_Key}

GET curl command example

Note: Linebreaks are designated by "\".

GET
Request curl command example
1curl -X GET "https://api.tomtom.com/routing/1/calculateRoute/\
252.50931,13.42936:52.50274,13.43872/json?\
3vehicleHeading=90&sectionType=traffic
4&report=effectiveSettings\&routeType=eco\
5&traffic=true&avoid=unpavedRoads&travelMode=car\
6&vehicleMaxSpeed=120&vehicleCommercial=false\
7&vehicleEngineType=combustion&key={Your_API_Key}" -H "accept:*/*"

POST URL example

POST
Request URL example
https://api.tomtom.com/routing/1/calculateRoute/52.50931,13.42936:52.50274,13.43872/json?key={Your_API_Key}

POST curl command example

POST
Request curl command example
1curl -X POST "https://api.tomtom.com/routing/1/calculateRoute/52.50931,13.42936:52.50274,13.43872/json?key={Your_API_Key}" -H "Content-type:application/json" -d \
2'{
3  "supportingPoints": [
4    {
5      "latitude": 52.5093,
6      "longitude": 13.42936
7    },
8    {
9      "latitude": 52.50844,
10      "longitude": 13.42859
11    }
12  ],
13  "avoidVignette": [
14    "AUS",
15    "CHE"
16  ]
17}'

Types

The following data table describes a subset of the types that can be used in the Calculate Route service; the remaining types are listed on the Common Routing Parameters page.

Type

Description

circle

A circle with a center point and a radius (in meters). The radius must be a positive integer with the maximum value of 135000.
Example: circle(52.37245,4.89406,10000)

generalizedLocation

A location or a circle.
Examples:

  • 52.37245,4.89406
  • circle(52.37245,4.89406,10000)
commaSeparatedFloats

Comma-separated list of floats.
Example: 1.23,0

point

To be used in the POST data only.
Please refer to the

Common Routing Parameters

page.

Request headers

There currently are no additional headers specific to the Calculate Route service. The common headers are listed on the Common Routing Parameters page.

Base path parameters

The following table describes a subset of the parameters that can be used in the Calculate Route service. The remaining parameters are listed on the Common Routing Parameters page.

  • Required parameters must be used or the call will fail.
  • The order of the required parameters is important and must be followed.
  • There are no optional parameters.

Required parameters (Base path)

Description

versionNumber
integer

The service version number.
Value: The current value is 1.

routePlanningLocations
string

Locations through which the route is calculated. The following constraints apply:

  • At least two locations must be provided.

  • The first location in the sequence defines the origin and must be a location.

  • The last location in the sequence defines the destination and must be a location.

  • One or more optional intermediate generalizedLocations (known as waypoints in this context) may be provided:

    • The maximum allowed number of waypoints is 150.

    • A waypoint of type location results in an extra leg in the response, a waypoint of type circle does not.

    • Circle waypoints cannot be used when computeBestOrder is true.

Values: Colon-delimited generalizedLocations, with the constraints mentionned above.

Request parameters

The following table describes a subset of the parameters that can be used in the Calculate Route service; the remaining parameters are listed on the Common Routing Parameters page.

  • There are no required parameters. All of the following parameters are optional.
  • The order of these optional request parameters is not important.

Optional parameters

Description

maxAlternatives
integer

Number of desired alternative routes to be calculated. The value provided:

  • Must be an integer in the range 0-5.

  • Using a value greater than 0 in conjunction with computeBestOrder set to true is not allowed.

  • Fewer alternative routes may be returned if either fewer alternatives exist, or the requested number of alternatives is larger than the service can calculate.

Default value: 0
Maximum value: 5

alternativeType
string

When maxAlternatives is greater than 0, allows to specify the objective of computing alternative routes: finding routes that are significantly different than the reference route, or finding routes that are better than the reference route. Possible values are:

  • anyRoute: returns alternative routes that are significantly different from the reference route.

  • betterRoute: only returns alternative routes that are better than the reference route, according to the given planning criteria (set by routeType). If there is a road block on the reference route, then any alternative that does not contain any blockages will be considered a better route. The summary in the route response will contain information (see the planningReason parameter) about the reason for the better alternative.

Note: This optional parameter can only be used when reconstructing a route.
Default value: anyRoute
Other values: betterRoute

minDeviationDistance
integer

All alternative routes returned will follow the reference route (see the POST data parameters section) from the origin point of the calculateRoute request for at least this number of meters.

  • Can only be used when reconstructing a route.

  • The minDeviationDistance parameter cannot be used in conjunction with arriveAt.

Default value: 0

minDeviationTime
integer

All alternative routes returned will follow the reference route (see the POST data parameters section) from the origin point of the calculateRoute request for at least this number of seconds.

  • Can only be used when reconstructing a route.

  • The minDeviationTime parameter cannot be used in conjunction with arriveAt.

Default value: 0

supportingPointIndexOfOrigin
integer

Largest index in the supportingPoints array (see the POST data parameters section) for which supportingPoints[supportingPointIndexOfOrigin] lies on or before the origin point.
The Routing API uses this index as a hint to disambiguate situations where the supportingPoints in the POST data are not planar, or where they come back close to the origin at a later point in the reconstructed route. In these cases, the supportingPointIndexOfOrigin can explicitly identify if the origin is meant to be on the later part of the route, or not.

  • Can only be used when reconstructing a route.

  • Cannot be used in conjunction with arriveAt.

Minimum value: 0
Maximum value: Size of supportingPoints array - 1.

computeBestOrder
boolean

Re-orders the route waypoints with a fast heuristic algorithm to reduce the overall route length. Note that based on the heuristic nature of the algorithm, optimality is not guaranteed. Yields best results when used in conjunction with routeType shortest.
Possible boolean values are:

  • true: compute a better order, if possible

    • Not allowed to be used in conjunction with a maxAlternatives value greater than 0.

    • Not allowed to be used in conjunction with circle waypoints.

    The response will include the reordered waypoint indices in the field optimizedWaypoints.

  • false: use the locations in the given order.

    • Not allowed to be used in conjunction with routeRepresentation=none.

Default value: false

routeRepresentation
string

Specifies the representation of the set of routes provided as a response.
Possible values are:

  • polyline: includes routes in the response.

  • summaryOnly: as per polyline, but excluding the points elements for the routes in the response.

  • none: only includes the optimized waypoint indices but does not include the routes in the response. This parameter value can only be used in conjunction with computeBestOrder=true.

Default value: polyline
Other values:

  • summaryOnly
  • none

computeTravelTimeFor
string

Specifies whether to return additional travel times using different types of traffic information (none, historic, live) as well as the default best-estimate travel time.
Possible values are:

  • none: do not compute additional travel times.

  • all: compute travel times for all types of traffic information, specifying all results in the fields:

    • noTrafficTravelTimeInSeconds
    • historicTrafficTravelTimeInSeconds
    • liveTrafficIncidentsTravelTimeInSeconds

    being included in the summaries in the route response.

Default value: none
Other value: all

vehicleHeading
integer

The directional heading of the vehicle, in degrees starting at true North and continuing in a clockwise direction.

  • North is 0 degrees.
  • East is 90 degrees.
  • South is 180 degrees.
  • West is 270 degrees.

Maximum value: 359
Other values: 0-359

sectionType
string

Specifies which of the section types is reported in the route response. sectionType can be specified multiple times (e.g., ...&sectionType=tollRoads&sectionType=tollVignettes&...).
Possible values are:

  • carTrain: sections of the route that are car trains.

  • ferry: sections of the route that are ferries.

  • tunnel: sections of the route that are tunnels.

  • motorway: sections of the route that are motorways.

  • pedestrian: sections of the route that are only suited for pedestrians.

  • tollRoad: sections of the route that require a toll to be payed.

  • tollVignette: sections of the route that require a toll vignette to be present.

  • country: sections indicating which countries the route is in.

  • travelMode: sections in relation to the request parameter travelMode.

  • traffic: sections of the route that contain traffic information.

  • carpool: sections of the route that require use of carpool (HOV/High Occupancy Vehicle) lanes.

  • urban: sections of the route that are located within urban areas.

  • unpaved: sections of the route that are unpaved.

  • lowEmissionZone: sections of the route that are located within low-emission zones.

Default value: travelMode
Other values:

  • carTrain
  • country
  • ferry
  • motorway
  • pedestrian
  • tollRoad
  • tollVignette
  • traffic
  • tunnel
  • carpool
  • urban
  • unpaved
  • lowEmissionZone

chargeMarginsInkWh
commaSeparatedFloats

Specifies a list of margins in kilowatt-hours (kWh) for computing reachableRouteOffsets.

  • Can only be used when all of constantSpeedConsumptionInkWhPerHundredkm, maxChargeInkWh, and currentChargeInkWh are specified.

  • The items in the list must be in strictly decreasing order.
  • The list is restricted to exactly one item.

Minimum value: 0
Maximum value: 0

extendedRouteRepresentation
string

Specifies the extended representation of the set of routes provided as a response. <extendedRouteRepresentation> can be specified multiple times (e.g., ...&extendedRouteRepresentation=distance&extendedRouteRepresentation=travelTime&... ). <extendedRouteRepresentation> can only be specified when contentType is json and routeRepresentation is polyline.
Possible values are:

  • distance: Includes distances to route polyline points in the response.

  • travelTime: Includes travel times to route polyline points in the response.

Values:
  • distance
  • travelTime

Further parameters not contained in the preceding table can be specified. A complete list is located in the Common Routing Parameters page. This page also includes the parameters used to define a detailed vehicle consumption model.

Using the detailed consumption model has two consequences for a calculateRoute request:

  • When the parameter routeType is set to eco, then the Consumption Model will be taken into account for route planning.
  • When constantSpeedConsumption* is specified, the response will include either fuelConsumptionInLiters or batteryConsumptionInkWh (for vehicleEngineType set to combustion or electric, respectively) as an additional field in each summary element.

POST data parameters

The supportingPoints field is used to reconstruct a route. This route is then used as a reference route for route reassessment, or calculating zero or more alternative routes.

  • The provided sequence of supporting points is used as input for route reconstruction.
  • The pointWaypoints field is used to represent waypoints when reconstructing a route.
  • The alternative routes are calculated between the origin and destination points specified in the routePlanningLocations, passing through all intermediate locations specified in the pointWaypoints field.
  • If supportingPointIndexOfOrigin is not used, and both minDeviationDistance and minDeviationTime are set to zero, then these origin and destination points are expected to be at (or very near) the beginning and end of the reference route, respectively.
  • The reference route may contain traffic incidents of type ROAD_CLOSURE, which are ignored for the calculation of the reference route's travel time and traffic delay.

Using supportingPointIndexOfOrigin, or setting at least one of minDeviationDistance or minDeviationTime to a value greater than zero, has the following consequences:

  • The origin point of the calculateRoute request must be on (or very near) the input reference route.
    • If this is not the case, an error is returned.
    • However, the origin point does not need to be at the beginning of the input reference route (it can be thought of as the current vehicle position on the reference route).
    • If used, supportingPointIndexOfOrigin must precisely indicate the location of the origin point in relation to the supportingPoints.
  • The reference route, returned as the first route in the calculateRoute response, will start at the origin point specified in the calculateRoute request. The initial part of the input reference route up until the origin point will be excluded from the response.
  • The values of minDeviationDistance and minDeviationTime determine how far alternative routes will be guaranteed to follow the reference route from the origin point onwards.
  • The route must use departAt.
  • The vehicleHeading is ignored.

The following table describes a subset of the parameters that can be used in the Calculate Route service; the remaining parameters are listed on the Common Routing Parameters page.

Parameter

Description

supportingPoints

An array of point objects, to be used as input for route reconstruction.

pointWaypoints

An array of pointWaypoint objects, to be used to represent waypoints when reconstructing a route.

  • If specified, the array must not be empty.
pointWaypoint

Contains one waypointSourceType and one supportingPointIndex object.

waypointSourceType

Denotes the source of the waypoint. Possible values:

  • USER_DEFINED: a waypoint that was explicitly defined by the user.

supportingPointIndex

An index into the supportingPoints array that denotes the location of the waypoint on the reference route.

  • Must be inside supportingPoints array boundaries.

reassessmentParameterSets

An array of reassessmentParameterSet objects, to be used as input for route reassessment.

  • Route reassessment provides information on how some properties of the route would be different with different input values (note that reassessment does not affect the shape of the route). For example, route reassessment can be used to quantify the impact of air conditioning use on total power consumption.

  • If specified, the array must contain exactly one entry.

  • A reassessmentParameterSet object is a set of parameters used together to reassess the planned route. Such an object must contain at least one parameter; currently the only supported parameter is auxiliaryPowerInkW.

Request content example

POST
Request content example
1{
2  "supportingPoints": [
3    {"latitude": 52.50930, "longitude": 13.42936},
4    {"latitude": 52.50844, "longitude": 13.42859}
5  ],
6  "pointWaypoints": [
7    {
8      "waypointSourceType": "USER_DEFINED",
9      "supportingPointIndex": 0
10    }
11  ],
12  "avoidVignette": [
13    "AUS",
14    "CHE"
15  ],
16  "reassessmentParameterSets": [
17    {
18      "auxiliaryPowerInkW": 0.3
19    }
20  ]
21}

Response data

Response headers

There currently are no additional response headers specific to the Calculate Route service; the common response headers are listed on the Common Routing Parameters page.

Response codes

There currently are no additional response codes specific to the Calculate Route service; the common response codes are listed on the Common Routing Parameters page.

Example of a successful response

The routes in a successful response are listed in the order of decreasing optimality. In case the request includes the supporting points supportingPoints field, the response will specify the reconstructed route before any alternative routes.

A response could look like this: (Note: Comments are contained within ... ....)

Response body - JSON
1{
2  "formatVersion": "0.0.12",
3  "routes": [
4    {
5      "summary": {
6        "lengthInMeters": 1147,
7        "travelTimeInSeconds": 161,
8        "trafficDelayInSeconds": 15,
9        "trafficLengthInMeters": 147,
10        "departureTime": "2015-04-02T15:01:57+02:00",
11        "arrivalTime": "2015-04-02T15:04:38+02:00",
12        "noTrafficTravelTimeInSeconds": 120,
13        "historicTrafficTravelTimeInSeconds": 157,
14        "liveTrafficIncidentsTravelTimeInSeconds": 161,
15        "batteryConsumptionInkWh": 0.155,
16        "deviationDistance": 1735,
17        "deviationTime": 127,
18        "deviationPoint": {
19          "latitude": 52.50904,
20          "longitude": 13.42912
21        },
22        "reachableRouteOffsets": [
23          {
24            "chargeMarginInkWh": 0.0,
25            "routeOffsetInMeters": 1147,
26            "point": {
27              "latitude": 52.51565,
28              "longitude": 13.43979
29            },
30            "pointIndex": 50
31          }
32        ]
33      },
34      "routeReassessments": [
35        {
36          "batteryConsumptionInkWh": 0.2,
37          "reachableRouteOffsets": [
38            {
39              "chargeMarginInkWh": 0.0,
40              "routeOffsetInMeters": 1147,
41              "point": {
42                "latitude": 52.51565,
43                "longitude": 13.43979
44              },
45              "pointIndex": 50
46            }
47          ]
48        }
49      ],
50      "legs": [
51        {
52          "summary": {
53            "lengthInMeters": 108,
54            "travelTimeInSeconds": 11,
55            "trafficDelayInSeconds": 0,
56            "trafficLengthInMeters": 0,
57            "departureTime": "2015-04-02T15:01:57+02:00",
58            "arrivalTime": "2015-04-02T15:02:07+02:00",
59            "noTrafficTravelTimeInSeconds": 10,
60            "historicTrafficTravelTimeInSeconds": 11,
61            "liveTrafficIncidentsTravelTimeInSeconds": 11,
62            "batteryConsumptionInkWh": 0.1
63          },
64          "points": [
65            {
66              "latitude": 52.50931,
67              "longitude": 13.42937
68            },
69            {
70              "latitude": 52.50904,
71              "longitude": 13.42912
72            },
73  ...further points...
74          ]
75        },
76  ...further legs...
77      ],
78      "progress": [
79        {
80          "pointIndex": 0,
81          "travelTimeInSeconds": 0,
82          "distanceInMeters": 0
83        },
84        {
85          "pointIndex": 5,
86          "travelTimeInSeconds": 7,
87          "distanceInMeters": 74
88        },
89  ...further progresses...
90        {
91          "pointIndex": 87,
92          "travelTimeInSeconds": 161,
93          "distanceInMeters": 1147
94        }
95      ],
96      "sections": [
97        {
98          "startPointIndex": 0,
99          "endPointIndex": 3,
100          "sectionType": "TRAVEL_MODE"
101          "travelMode": "other"
102        },
103        {
104          "startPointIndex": 3,
105          "endPointIndex": 7,
106          "sectionType": "TRAVEL_MODE"
107          "travelMode": "car"
108        },
109        {
110          "startPointIndex": 2,
111          "endPointIndex": 5,
112          "sectionType": "TOLL_ROAD"
113        },
114        {
115          "startPointIndex": 3,
116          "endPointIndex": 4,
117          "sectionType": "TUNNEL"
118        },
119        {
120          "startPointIndex": 0,
121          "endPointIndex": 1,
122          "sectionType": "PEDESTRIAN"
123        },
124        {
125          "startPointIndex": 3,
126          "endPointIndex": 4,
127          "sectionType": "TRAFFIC",
128          "simpleCategory": "JAM",
129          "effectiveSpeedInKmh": 40,
130          "delayInSeconds": 158,
131          "magnitudeOfDelay": 1,
132          "tec": {
133            "effectCode": 4,
134            "causes": [
135              {
136                "mainCauseCode": 1
137              },
138              {
139                "mainCauseCode": 26,
140                "subCauseCode": 2
141              }
142            ]
143          }
144        },
145  ...further sections...
146      ]
147    }
148  ...further routes...
149  ],
150  "optimizedWaypoints": [
151    {
152      "providedIndex": 0,
153      "optimizedIndex": 1
154    },
155    {
156      "providedIndex": 1,
157      "optimizedIndex": 0
158    }
159  ...further optimized waypoints...
160  ],
161  "report": {
162    "effectiveSettings": [
163      {
164        "key": "avoid",
165        "value": "motorways"
166      },
167      {
168        "key": "computeBestOrder",
169        "value": "true"
170      },
171  ...further settings...
172    ]
173  }
174}

Example of an error response

If an error occurs, the response contains the description of the error. The error response would look like this:

Error response example - JSON
1{
2  "formatVersion": "0.0.12",
3  "detailedError": {
4    "code": <error code>,
5    "message": "Error message"
6  }
7}

Special behaviour for content type jsonp (JSON with Padding)

When the contentType=jsonp is used, the returned HTTP status code is always OK (200).

  • This ensures that the jsonp callback will be invoked on the client side regardless of the outcome of the request.
  • In order to provide the client with the actual status of the request, a field called statusCode is added to the response body.

Currently, the preceding statement is not true for certain types of errors described below.

Special behavior of certain types of errors (authentication errors, request quota related errors, etc.)

  • For those errors the HTTP status code is returned as normal (400, 500, ...) and the response content type is text/xml independent from the request content type.
  • For those errors, the content doesn't follow the documented format for error responses.
  • Note: This imperfection should not cause problems during normal use of the API.

Structure of a successful response

Note that some names are implicitly defined. One example is the name leg when describing legs as an array of leg objects.

JSON field

Description

formatVersion
string

The format version.

routes
array of route objects

The request may return more than one route.
Each object has at least a summary field and a legs field. It may contain other fields depending on the request parameters.

summary
summaryobject

The summary of a route, or of a route leg.
The summary object may be extended with new fields in the future; clients should ignore fields they do not recognize.

routeReassessments
array of objects

  • Included if reassessmentParameterSets is specified.

  • Each object in the array corresponds to the entry with the same index in reassessmentParameterSets (see the POST data parameters) and contains the results of a reassessment using the corresponding reassessmentParameterSet.

  • The objects describe particular aspects of the route as a whole. Their values may differ from those reported in the route summary.

  • If the reassessmentParameterSet contains auxiliaryPowerInkW, then the corresponding object may contain the following fields (see individual field descriptions for details):

    • batteryConsumptionInkWh
    • reachableRouteOffsets

  • The objects in this array may be extended with new fields in the future; clients should ignore fields they do not recognize.

legs
array of leg objects

A description of a part of a route, comprised of an array of points.

  • Contains the summary and points fields.

  • Each additional waypoint provided in the request will result in an additional leg in the returned route.

points
array of objects

Each object in the array is a location on the surface of the globe defined by its latitude and longitude fields.

sections
array of section objects

This array is available inside routeobjects.

  • Contains one or more section objects.

  • The structure of section objects is given below.

startPointIndex
number

Index of the first point (offset 0) in the route this section applies to (only included for a routeRepresentation polyline).

endPointIndex
number

Index of the last point (offset 0) in the route this section applies to (only included for a routeRepresentation polyline).

countryCode
string

A 3-character

ISO 3166-1 alpha-3

country code.

simpleCategory
string

Type of the incident.

  • Can currently be JAM, ROAD_WORK, ROAD_CLOSURE, or OTHER.

  • See the tec field for detailed information.

effectiveSpeedInKmh
number

The effective speed of the incident in km/h, averaged over its entire length.

delayInSeconds
number

The delay in seconds caused by the incident.

magnitudeOfDelay
number

The magnitude of delay caused by the incident.
Possible values:

  • 0: unknown

  • 1: minor

  • 2: moderate

  • 3: major

  • 4: undefined, used for road closures and other indefinite delays

These values correspond to the values of the response field magnitudeOfDelay

tec
object

Details of the traffic event. It uses the definitions in the

TPEG2-TEC

standard. It can contain the effectCode and causes fields.

effectCode
number

The effect on the traffic flow. Contains a value in the tec001:EffectCode table, as defined in the

TPEG2-TEC

standard. Can be used to color-code traffic events according to severity.

causes
array of objects

Each object in the array describes one cause of the traffic event.

  • It can contain mainCauseCode and subCauseCode fields.

  • It can be used to define iconography and descriptions.

mainCauseCode
number

The main cause of the traffic event. Contains a value in the tec002:CauseCode table, as defined in the

TPEG2-TEC

standard.

subCauseCode
number

The subcause of the traffic event. Contains a value in the sub cause table defined by the mainCauseCode, as defined in the

TPEG2-TEC

standard.

lengthInMeters
number

The route or leg length in meters.

travelTimeInSeconds
number

The estimated travel time in seconds. Note that even when traffic=false, travelTimeInSeconds still includes the delay due to traffic.

trafficDelayInSeconds
number

The delay in seconds compared to free-flow conditions according to real-time traffic information.

trafficLengthInMeters
number

The portion of the route or leg, expressed in meters, that is affected by traffic events which cause the delay.

noTrafficTravelTimeInSeconds
number

The estimated travel time in seconds calculated as if there are no delays on the route due to traffic conditions (e.g., congestion). Included if requested using the computeTravelTimeFor parameter.

historicTrafficTravelTimeInSeconds
number

The estimated travel time in seconds calculated using time-dependent historic traffic data. Included if requested using the computeTravelTimeFor parameter.

liveTrafficIncidentsTravelTimeInSeconds
number

The estimated travel time in seconds calculated using real-time speed data. Included if requested using the computeTravelTimeFor parameter.

deviationDistance
number

The distance (in meters) from the origin point of the calculateRoute request to the first point where this route forks off from the reference route.

  • If the route is identical to the reference route, then this field is set to the length of the route.

  • Included in all alternative (but not reference) route summary fields.

deviationTime
number

The travel time (in seconds) from the origin point of the calculateRoute request to the first point where this route forks off from the reference route.

  • If the route is identical to the reference route, then this field is set to the estimated travel time of the route.

  • Included in all alternative (but not reference) route summary fields.

deviationPoint
object

The coordinates of the first point following the origin point of the calculateRoute request where this route forks off from the reference route.

  • If the route is identical to the reference route, then this field is set to the coordinates of the last point on the route.

  • Included in all alternative (but not reference) route summary fields.

fuelConsumptionInLiters
number

The estimated fuel consumption in liters using the Combustion Consumption Model. Included if:

  • The vehicleEngineType is set to combustion .

  • The constantSpeedConsumptionInLitersPerHundredkm is specified.

  • The value will be non-negative (i.e., positive).

batteryConsumptionInkWh
number

The estimated electric energy consumption in kilowatt hours (kWh) using the Electric Consumption Model.

  • Included if:

    • vehicleEngineType is set to electric.

    • constantSpeedConsumptionInkWhPerHundredkm is specified.

  • The value of batteryConsumptionInkWh includes the recuperated electric energy and can therefore be negative (which indicates gaining energy).

  • If both maxChargeInkWh and currentChargeInkWh are specified, recuperation will be capped to ensure that the battery charge level never exceeds maxChargeInkWh.

  • If neither maxChargeInkWh nor currentChargeInkWh are specified, unconstrained recuperation is assumed in the consumption calculation.

reachableRouteOffsets
array of objects

This field is included if chargeMarginsInkWh is specified. It is not present in the leg summary field. Each object in the array corresponds to an entry in chargeMarginsInkWh, and describes the reachable point on the route with respect to the charge margin specified there. Effectively, the farthest the vehicle can go on the route on its current charge, without depleting the battery beyond the specified margin.

  • Objects in the array contain the following fields:

    • chargeMarginInkWh: the charge margin this reachable point is calculated for.

    • point: location of the reachable point defined as a latitude longitude pair.

    • pointIndex: largest index in the polyline of the route for which points[pointIndex] lies on or before point.

    • routeOffsetInMeters: the distance from the start of the route to the reachable point.

  • Note that:

    • If currentChargeInkWh is less than or equal to chargeMarginInkWh, routeOffsetInMeters is zero.

    • routeOffsetInMeters is at most lengthInMeters.

    • Charging stops are ignored in the computation so that e.g., live traffic is used as if driving past any charging station.

optimizedWaypoints
array of objects

A description of an optimized sequence of waypoints. It shows the index from the user-provided waypoint sequence for the original and optimized list. For instance, a response:

1{
2  "optimizedWaypoints": [
3    {
4      "providedIndex": 0,
5      "optimizedIndex": 1
6    },
7    {
8      "providedIndex": 1,
9      "optimizedIndex": 2
10    },
11    {
12      "providedIndex": 2,
13      "optimizedIndex": 0
14    }
15  ]
16}

means that:

  • The original sequence is [0, 1, 2].

  • The optimized sequence is [1, 2, 0].

Since the index starts by 0 the original is "first, second, third", while the optimized is "second, third, first".

departureTime
string

The estimated departure time for the route or leg. Specified as a dateTime.

arrivalTime
string

The estimated arrival time for the route or leg. Specified as a dateTime.

effectiveSettings
array of objects

Each object in the array represents an effective parameter or a data used when calling the Calculate Route API. Each object has fields key and value both containing a string describing the input and its value.

statusCode
number

The original HTTP status code as listed in the response codes (note: included for content type jsonp only).

planningReason
string

The reason for a better route proposal. Can currently be:

  • Blockage in case the reference route contains road blockages. The returned value is implementation-defined in case both reasons for a better proposal are applicable to the same route.

  • Better_Proposal in case the alternative type is better than the reference route, according to the given planning criteria (set by routeType).

This field is included in the response only if the route is requested with alternativeType=betterRoute. This field is not present in the leg summary field.

progress
array of progress pointobjects

This field is included if extendedRouteRepresentation is used.

  • It always contains entries for the first and the last point in the route.

  • For any pair of consecutive entries in the progress array, progress for pointIndex values that are not explicitly present and are enclosed by said pair, can be linearly interpolated by summing up straight line distances of the leg points.

  • The

    Haversine formula

    is precise enough to compute such distances.

A progress point object may contain the following members:

  • pointIndex: index of the point (offset 0) in the route this object applies to.

  • distanceInMeters: distance (in meters) from the start of the route to this point. This field is included if extendedRouteRepresentation value distance is used.

  • travelTimeInSeconds: travel time (in seconds) from the start of the route to this point. This field is included if extendedRouteRepresentation value travelTime is used.

Structure of the section object

Each section object contains additional information about parts of a route. A section object contains at least the fields startPointIndex, endPointIndex, and sectionType.

JSON field

Description

sectionType
string

Contains the response section type.

Request section type Response section type
carTrainCAR_TRAIN
countryCOUNTRY
ferryFERRY
motorwayMOTORWAY
pedestrianPEDESTRIAN
tollRoadTOLL_ROAD
tollVignetteTOLL_VIGNETTE
trafficTRAFFIC
travelModeTRAVEL_MODE
tunnelTUNNEL
carpoolCARPOOL
urbanURBAN
unpavedUNPAVED
lowEmissionZoneLOW_EMISSION_ZONE

The COUNTRY sections span between country border crossings, from the departure, or to the destination.

  • The section additionally contains countryCode.

  • If the route has disjointed parts in the same country, there will be several sections with the same countryCode.

  • If no country can be assigned to a part of the route, as for example in international waters, there may be no country section for this part.

    • A TOLL_VIGNETTE section additionally contains a countryCode since toll vignettes are often specific to a country.

    • A TRAFFIC section may additionally contain any of the following: simpleCategory, effectiveSpeedInKmh, delayInSeconds, magnitudeOfDelay, tec.

    • TRAVEL_MODE sections cover the whole route. Each section's travel mode is reported in travelMode .

    • CARPOOL sections contain parts of the route that are only open to HOV (high-occupancy vehicles) at the time of traversal. Roads with at least one unrestricted lane are not part of a CARPOOL section.

travelMode
string

This field is either set to the value given to the request parameter travelMode, if this travel mode is possible, or to other which indicates that the given mode of transport is not possible in this section. This field can only be used within sections of type TRAVEL_MODE.

Structure of an error response

JSON field

Description

detailedError
object

This object provides a representation of the error message. It contains a code and a message field.

JSON field

Description

code
string

The (non-complete) list of error codes is:

Error code

Description
MAP_MATCHING_FAILURE

One of the input points (Origin, Destination, Waypoints) could not be matched to the map because there is no known drivable section near this point. This error code is always followed by a description of one point that was not matchable:

  • Origin (Latitude, Longitude)
  • Destination (Latitude, Longitude)
  • Waypoint N (Latitude, Longitude)
NO_ROUTE_FOUND

No valid route could be found.

CANNOT_RESTORE_BASEROUTE

The route reconstruction using supportingPoints failed.

BAD_INPUT

Some input parameter combination was not valid.

COMPUTE_TIME_LIMIT_EXCEEDED

The request exceeded the internal compute time limit and was canceled.

message
string

A human readable error message.

  • It is a freeform string which may be extended in the future, so it is recommended to only match substrings of the description.

  • The string always contains an error code.

Example of a description string:

Engine error while executing route request: MAP_MATCHING_FAILURE: Origin (54.3226, 3.11463)

Engine error while executing route request: MAP_MATCHING_FAILURE: Origin (54.3226, 3.11463)

Engine error while executing route request: MAP_MATCHING_FAILURE: Waypoint 3 (54.3226, 3.11463)

statusCode
number

The original HTTP status code as listed in response codes (included for content type jsonp only).