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.

Release of Route Optimization API V1.5.1

A new version of the PTV Developer Route Optimization API is now available!

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

Route Optimization API V1.5.1

  • Improvement: Streamlined database interaction.
  • Feature: Ready for US deployment for American customers.
  • Bugfix: When working hours presets differ between any two drivers, a proper exception message is returned.
  • Bugfix: When multiple drivers availabilities or multiple locations opening intervals have a total span of more than 14 days, a proper exception message is returned.

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 have any question do not hesitate to get in contact.

Release of Sequence Optimization API V1.3.2

A new version of the PTV Developer Sequence Optimization API is now available!

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

Sequence Optimization API V1.3.2

  • Improvement: Streamlined database interaction.
  • Feature: Ready for US deployment for American customers.

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 have 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.

Release of Sequence Optimization API V1.3.0

A new version of the PTV Developer Sequence Optimization API is now available!

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

Sequence Optimization API V1.3.0

  • Feature: New vehicle profiles for region IMEA available.
    For Africa, Middle East and Asia there are four vehicle profiles available.
    Check details about vehicle profiles and supported countries in the concept page.
  • Feature: Added functionality for “Drivers’ Working Hours” to specify restrictions on working time and driving time of drivers and enforce breaks periods. Therefore added fields ‘workingHoursPreset’ and ‘breakRule’ to ‘Driver’.
    Note that from this release on, the working and driving time will be unlimited, unless specified otherwise.
    Previously, EU driving time regulations were applied as the default. To achieve the same behavior as before, set workingHoursPreset to EU_DRIVING_TIME_REGULATION.
  • Feature: Added functionality for restricting the maximum travel time and driving time of drivers. Therefore added fields ‘workLogbook’, ‘maximumDrivingTime’ and ‘maximumTravelTime’ to ‘Driver’.
    Note that from this release on, the travel and driving time will be unlimited, unless specified otherwise.
    Previously, EU driving time regulations were applied as the default. To achieve the same behavior as before, set workingHoursPreset to EU_DRIVING_TIME_REGULATION.
  • New concept page and code sample for “Drivers’ Working Hours” available

Plus several Bugfixes

  • Bugfix: Coordinates containing 0.0 as latitude or longitude are now correctly processed.
  • Bugfix: Improved handling of empty strings as start and end location ids for input vehicle.
  • Bugfix: When latitude or longitude is set as not a number (NaN), a proper exception message is returned.
  • Bugfix: When using an empty list of quantities a proper response instead of an error is returned.

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.