Detailed Toll Update for Belgium

We activated the updated detailed toll layers for Belgium, referenced to

  • PTV Europe / World City Map Premium 2023.1H/1aH

on our Layer Delivery Server (LDS). Now, it is possible to download the detailed toll layers via Content Update Service (CUS).

Content: New toll rates valid from 1st of January, 2023 for all trucks in Wallonia and Liefkenshoecktunnel


Using detailed toll on PTV Developer, xServer internet and xServer from version 2.22:

The default toll calculation changed to useDetailedToll = true in the xserver.conf. That means that you get the detailed toll automatically, when requesting toll in the route calculation.


Information for xServer from version 2.18 to 2.21:

Step 1: Activate the detailed toll download via content update service in you xserver.conf.

core {
     contentupdates {
              content {
                  detailedToll {
                      enabled = true
                      providerNames = [ "here" ]
                      countries = [ ]

Step 2: Enable the detailed toll calculation in the xserver.conf or in your request.

xroute {
     tollOptions {
     useDetailedToll = true

The detailed toll is released for PTV xServer from version 2.18.  


Please be aware that from version 2.22 the parameter useDetailedToll is activated automatically. If you like to use the basic toll you need to set it to false.

Calculation of service times enlarged

The new version V1.7.0 of the PTV Developer Sequence Optimization API is now available!

Service time calculation is an important part of time profile calculation. It models the time, which the driver needs to serve transports at a route stop. One component is the service time, which directly is dependent of the quantity of the loaded or unloaded goods. That’s, what was already available by the fields pickupServiceTime resp. deliveryServiceTime.

New functionality is about to consider location-dependent service times, which are independent from the quantity of goods.  The location-dependent service time represents, for example, the time to enter the premises or to register at a customer.

Therefore new fields ‘serviceTimePerTransportStop’ to customerLocationAttributes and ‘serviceTimePerPickupStop’ and ‘serviceTimePerDeliveryStop’ to a new depotLocationAttributes object are available. Additionally this means, that for depot locations the service time at a start depot can be set differently from the service time at an end depot. Intereting for whose, who have a huge fixed service time at the beginning of a trip, but only a small fixed service time at the end, e.g. to hand over backhauls.

Have a look at the API Changes webpage for more details or check the API Reference.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.

Improvements in solution quality for Route Optimization / New API version 1.7.0

New Feature:

With the new version of the PTV Developer Route Optimization API PTV offers a boost for optimization quality called Optimization Premium.

The higher computational capacity allows for searching in distinct search spaces in a parallel manner. Moreover, Optimization Premium uses diverse exclusive neighborhoods that are only enabled within this mode. These diverse neighborhoods enable the algorithm to explore a larger search space and accordingly find better solutions. 

The bigger the instances are, the more improvement can be gained by using Optimization Premium. Although every use case is unique and improvements cannot be guaranteed, customers with Premium Optimization can expect up to 30% fewer unplanned orders, and/or up to 30% smaller fleet size. In cases where all orders are already planned, Optimization Premium delivers up to 10% cost savings.

Optimization Premium is activated on request base by setting query parameter ‘optimizationPremium’ to true  in operation ‘startOptimization’.

To use the feature Optimization Premium productive the usage must be explicitly included in your individual PTV Developer license agreement. Before implementing Optimization Premium please contact our local sales departments.

Security bugfixes:

To ensure security and minimize the chance for attacks, all requests are restricted in the following way:

  • Capacity of all array objects in locations, vehicles, drivers, transports, and route is limited. These limits are less restrictive as the ones set by subscription. 
  • Requests with more than thirty unreferenced locations are not accepted. Unreferenced locations are locations, which are part of request, but neither used as customer or depot locations for transports nor used as vehicle start or end locations. 

This might lead to rejection of requests that were being accepted in previous API versions.

You can check the new features in the list below or use the API Changes webpage for more details.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.

New code sample available for Route Optimization and Sequence Optimization

A new code sample is available for Route Optimization and Sequence Optimization. It’s about transport priorities – how to address them via API and what impact transport priorities have on the result.

Check it out on Route Optimization or Sequence Optimization.

You can test PTV Developer for free by registering a MyPTV account and activating the product on the website.
By doing this you will gain 100k transaction per month for free to directly start testing.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side.

If you got any question do not hesitate to get in contact.

Changing vehicle parameters at waypoints

When calculating a route with more than 2 waypoints, it often happens that logistic events occur at intermediate stops, which can modify some routing-relevant characteristics of the selected vehicle.

The most common use-case is obviously unloading or loading some goods at a stop, which implies a change of the weight of the vehicle. The nature of the transported goods can also be important, for instance when it relates to hazardous materials : some roads should then be either preferred or avoided. Last but not least, adding or removing a trailer will definitely modify the dimensions of the vehicle itself.

Such vehicle adaptions can sometimes have a sensitive impact on the path of the optimal route, or even on toll costs. And more commonly, they also directly affect the quantity of emitted pollutants and the energy consumption for a given route.

While it is of course possible to split a route request in several requests with different input vehicle configurations, it is much more performant and user-friendly to be able to consider these changes in a single request.     

This is why the version V1.14.0 of the PTV Developer Routing API now offers you to (re-)define some of the vehicle parameters directly in your on-road or off-road waypoints, with the POST method : calculateRoutePost.

Our new code sample provides you a fast-and-easy way to evaluate the influence of the change of load weight at waypoints. As shown on the screenshot below, it is preconfigured to test a route where unloading the goods at the second waypoint influences the course of the route. 

Please have a look on our technical concept to get more information about waypoints handling.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.

Emission calculation with alternative drive-trains

The reduction of pollution and the sustainable increase in efficiency of transport chains to improve air quality are important factors in the logistics today. ISO standards therefore have been introduced to standardize the calculation of emissions that are released. Now, with the lately effective ISO/DIS 14083:2022 standard, new factors have been provided also considering alternative drive-trains.

With the new version of PTV Developer Routing API 1.14.0 the emission calculation has therefore been extended by this new standard. It enables now in addition to new factors the calculation of electricity consumption under consideration of new vehicle parameters for alternative drive-trains and can furthermore be combined with the latest factors of HBEFA 4.2.

This example shows the calculated emission consumption of a hybrid truck by using the factors of the ISO/DIS 14083:2022 standard and HBEFA 4.2

If you are interested in more detailed information, please refer to our technical concept – or even better, just try it out in our updated code sample or tutorial.

To keep yourself updated about upcoming releases and news you can use the subscribe function on the right hand side. If you got any question do not hesitate to get in contact.