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.

PTV xServer 2.26.1 released

The PTV xServer 2.26.1 is released! With this version we provide two important bug fixes for the xRoute service:

  • Bugfix: When the vehicle profile is not supported by the selected emission scenario, a result limitation instead of an exception is returned like in all versions before 2.26.0.
  • Bugfix: When using the ISO 14083 emission calculation together with hybrid vehicles, all following requests provide correct emission values.

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:

  • 12.07.22: Productive system hosted in Europe
  • 13.07.22: Productive system hosted in US

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

Traffic events

Do you remember the traffic delay introduced in one of the last versions of the PTV Developer Routing API? For the delay we compare the travel time with and without live traffic on the same route (see this blog post).

In the new version of the PTV Developer Routing API V1.11.0 the request parameter ‘TRAFFIC_EVENTS’ provides traffic events chronologically along the route in the event list, together with all other events like waypoints, maneuvers or toll (see this concept). Then you know exactly where and why there is a delay.

Check out the traffic events in the code sample for recalculating a route with events. Do you need a RouteId? Just create one with the code sample for RouteIds.

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.

Guided navigation

With guided navigation you have the possibility to use a calculated route from PTV Developer in our truck app PTV Navigator. For this we offer in the new version of the PTV Developer Routing API V1.11.0 the request parameter ‘GUIDED_NAVIGATION’ to get the calculated route in an additional format easy to import in PTV Navigator.

Detailed information is available in the corresponding concept. In addition you can test it in our 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.