Category: PTV Developer

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

Read more

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

Read more

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

Read more

In the new version of the documentation of PTV Developer Geocoding & Places API and Map Matching API you find a new technical concept explaining  the difference between Postion Matching and Location By Position end point.

We often get questions which endpoint should be used for which use case.…

Read more

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.

Read more

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.

Read more