The waypoint sequence resource (
findsequence allows you to optimize for distance covered in a journey or for travel time. Use the parameter
improvefor (available values:
time). By default, the Fleet Telematics Waypoints Sequence optimizes waypoints for travel time.
The Fleet Telematics Waypoints Sequence does not include route details in its responses. To request a route, use the HERE Routing API .
Requests to the Routing API must include the route travel mode and two consecutive waypoint coordinates from the response from the Fleet Telematics Waypoints Sequence. If the route includes traffic information, departure time is also required. The response from the Fleet Telematics Waypoints Sequence provides this information in the element
Time window constraints define opening hours or deadlines for product delivery points or appointments specific to each waypoint. Successful responses contain an optimized waypoint sequence that observes all the time constraints specified in the request in the parameter
destinationN. Where this is not possible, the service generates a response without a way point sequence, but hints at conflicting or problematic constraints or waypoints. You must then resubmit the request with relaxed or modified constraints or waypoints. For an example, see Time Constraints Waypoint Sequence.
Sequence constraints between pairs of waypoints define a partial order which is strictly obeyed. Add
;before:destination13 to the waypoints in the request parameters to define sequence constraints. Several 'before's are allowed per way point.
Service time is specific to each waypoint and defines the amount of time to be spent at the waypoint. In other words, it indicates the length of time between arrival at the waypoint and departure from it, for example, to complete the delivery of goods. Service times are taken into account in the optimized waypoint sequence. For an example with rest times at waypoints, see Traffic Info and Rest Time Constraints Waypoint Sequence.
The Fleet Telematics Waypoints Sequence may take several minutes to calculate a response depending on the parameters specified. Specifically, this calculation time depends on the following:
- whether traffic mode (
mode=...;traffic:enabled) is enabled
- the number of waypoints
- the distances between the individual waypoints
truckmode is used (
The timeout after which the network connection is closed is set to 300 seconds on the HERE Fleet Telematics Waypoints Sequence systems.