Fleet Telematics Toll Costs Developer's Guide

Calculating Toll Costs

The toll cost calculation resource (tollcost.json) has two main parameters for input:
  • route – Road segments, optionally with date or time information
  • vspec – Profile of the vehicle to determine applicable toll costs

Routes for Toll Cost Calculation

To calculate the toll costs for a particular route, the Fleet Telematics Toll Costs expects a route as a sequence of permanent link IDs. You can construct this route by using the HERE Routing API or the HERE Route Match Extension API.

Alternatively, you can also obtain the link IDs for your route via reverse geocoding with the HERE Geocoder API.

Vehicle Specifications

Toll costs are given for specific vehicle categories because the usage fee required to use a specific road network or to use a toll booth depends on what kind of vehicle is using the route. Therefore, the API needs to know all the specifications of a vehicle to be able to determine the fees correctly when computing the toll costs for a route. You need to provide the specifications of the vehicle as a string, summing up different attributes:
  • Category: motorcycle, truck, auto or other vehicle category
  • Trailer type: none, trailer, caravan
  • Number of axles in the vehicle and other technical specifications

Types of costs

The total cost due for road usage can be divided into two categories:
  • Road section costs – Fees that the driver must pay to use a specific road, section of road or to go through a specific toll booth
  • Administrative area admission costs – Fees that the driver must pay in order to gain access to the road network of a specific area
  • Ferry costs – Fees that the driver must pay for using the ferry for himself including his vehicle
The total cost for these two categories are returned separately in the response to a request. Note that ferry costs are currently only averages and hence taken into consideration for route optimization, but not returned as explicit cost items.