To obtain the best results date and time will be considered for calculating the route, the travel time and toll.
Many roads cannot be used by trucks at any time. The Routing API will automatically consider roads prohibited for the selected vehicle and the selected date and time to find the best allowed route.
To calculate the travel time an average speed for every single road is taken into account. For more accurate results the average and the live traffic situation will be considered.
The average traffic situation means that for each road the average speed at that day of the week and that time of day will be considered. The rush hours in the mornings and evenings with lower average speeds will be considered that way.
The live traffic situation comprises traffic jams, road works and other disturbances which usually have a short validity of only a few hours. Route calculations in the future will not be affected by them apart from long-term blockings because of road works.
In many countries toll prices depend on when the toll roads, in particular bridges, tunnels or mountain passes, are passed. The Routing API will calculate the correct price depending on the date and time of the route.
For best results the start or arrival time of the route should be within one month in the past and six months in the future. Otherwise, the response will contain a warning as the resulting toll prices may not be correct due to the lack of proper data.
Specifying Date and Time
When the route will be started now, it is not necessary to specify date and time, the current date and time will be used automatically. When the route will take place at a different date and time, specify either options[startTime] or options[arrivalTime] in a format according to RFC 3339. When both are specified, an error will be returned.
It is not necessary to specify an offset to Coordinated Universal Time (UTC) as in the example above, instead the time is treated as local time at start (when options[startTime] is specified) or destination (when options[arrivalTime] is specified) and the offset to UTC is determined automatically.
Note that options[arrivalTime] cannot be specified when requesting the results SCHEDULE_REPORT and SCHEDULE_EVENT nor when openingIntervals, serviceTime or workingHoursPreset are specified.
All times present in the response will have the offset to UTC which is specified or determined from the request.