New data for the EWS Road Distance API

The EWS (“Entfernungswerk Strasse”) mainly consists of precalculated truck distances to quickly access them for different use cases like invoice auditing. Up to now, we provided data versions for the years 2017 to 2022.

In the new version of the PTV Developer EWS Road Distance API V1.3.0 you even have the possibility to use all data from 2016 onwards. And as the new year just started, we also added data version 2023.

The new data for 2023 has been fundamentally revised and offers more detailed content. The reference locations were checked, and their number was significantly increased (region EUROPE now with more than 14,000 and region GERMANY with more than 10,000 reference locations). In addition, toll distances for trucks in Austria take international routes into account.

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.

PTV xServer 2.27 released

The new PTV xServer API version 2.27 is available! Besides a lot of features set from experimental to stable, these are the new highlights:

  • xDima
    • Support to import own content in a new distance matrix
  • xRoute:
    • Support to change vehicle parameters at each waypoint for more accurate results (e.g. considering the impact of loading and unloading during the route)
    • Identification of start and end of traffic incidents like traffic jams in the route event list
  • xTour
    • New optimization mode “Premium” to get higher quality solutions (experimental, special license required)
    • Support to minimize the monetary costs specified for each vehicle (experimental, special license required)

If you are interested in the full list of features and improvements, you can check the corresponding release notes here.

Please note that the PTV Content Update Service 2.27 is also available including the update of several third-party components. Moreover, the handling of combined transports will change in the HERE maps from 2023.2H on. The PTV xServer 2.27.0 is already prepared for this. To get proper combined transport results, you should use this or a newer PTV xServer version for the upcoming HERE maps.

For on-premise solutions you can download the latest version from the PTV xServer Customer Area: https://www.ptvgroup.com/en/solutions/products/ptv-xserver/customer-area/ (login and license required)

For cloud solutions we provide a test and production system based on this release. The production system of PTV xServer internet will be updated following this schedule:

  • 17.01.23: Productive system hosted in Europe
  • 18.01.23: Productive system hosted in US
  • 19.01.23: Productive system hosted in Australia

Check the Cluster Overview page to get more information about existing PTV xServer internet deployments.

And another one! The EWS Road Distance API

Do you need generally accepted distances for tender management or invoice auditing? Then the new EWS Road Distance API could be something for you!

The EWS (“Entfernungswerk Strasse”) mainly consists of precalculated truck distances and is the de facto standard in the transport sector. You have quick and direct access to these distances via relations all over Europe.

Since many years we deliver the EWS data directly to our customers as on-premise solution. Now we also offer a cloud solution integrated as new API in our product PTV Developer!

Detailed information like concepts or the API specification is available in the PTV Developer API documentation. Maybe the best thing to start is exploring the code sample there!

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 vehicle profiles for Africa and Asia

The properties of a vehicle, such as height or weight, are stored in a profile. Up to now we offer predefined profiles for Europe, America and Australia as a simple entry for all routing-related services.

With the new version of the PTV Developer Data API V1.2.0 we added vehicle profiles for the IMEA region. This includes all countries of Africa and Asia including the Middle East but excluding China, Japan, South Korea and North Korea.

Now you can use the new vehicle profiles in all routing-related services:

  • Routing API: IMEA profiles available for the first time and usable in the whole world
  • Matrix Routing API: IMEA profiles available for the first time and usable in the supported countries (see the distance matrix example above) 
  • Route and Sequence Optimization API: IMEA profiles already available since July 2022 and usable in the supported countries

A detailed description of all profiles and supported countries is for example here available.

One last hint: 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.

 

Sometimes length matters ;-)

Usually a route is optimized for travel time. The result is a fast route a real driver would follow accepting a longer distance, if necessary. But there are use cases where you want to optimize a route for distance, for example in case of billing purposes based on distance.

In the new version of the PTV Developer Routing API V1.13.0 you have the possibility to use the new parameter ‘routingMode’ by selecting ‘FAST’ (optimize for travel time) or ‘SHORT’ (optimize for distance).

In the above example there is the orange route with longer distance but lower travel time using mainly the motorway (‘FAST’) compared to the blue route with shorter distance but higher travel time crossing the black forest (‘SHORT’).

Please note that both modes do not calculate the absolutely fastest or shortest route. The results are still meaningful and avoid rural roads and residential areas. If you want to know more, just have a look on the corresponding technical concept or test it with our brand new code sample.

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.

Route violated! But where?

When there is no valid route for your vehicle between two waypoints possible at all, the route is nevertheless calculated and marked as violated. This is typically the case for prohibited areas around waypoints, which have to be entered or exited anyway. Other “obstacles” like weight restrictions on the way are usually bypassed and not part of the calculated route.

Up to now, you can request violation events in such routes containing the position, time and the vehicle property in question. In the new version of the PTV Developer Routing API V1.12.0 we also provide the polylines of the violated route parts by using the new parameter ‘VIOLATION_EVENTS_POLYLINE’.

With this polyline it is easy to display the violated route parts on a map. Illustrated above, the first part of the route is marked in red as this is prohibited for the current vehicle because of the surrounding forest. Of course, there is a new code sample for this feature and you are welcome to play around with it! 

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.