Tag: Map Matching API

We are introducing a new showcase that highlights the robust features of the PTV Developer Map Matching API. This demonstration provides a comprehensive look at the differences between map matching and reverse geocoding (Locations by Position), ensuring users can fully leverage the power of our tools.…

Read more

In the new version of the PTV Developer Map Matching API V1.3.23 we added a new feature for the Position Matching endpoint. Position Matching tries to find the best matching road segment in the map for a given position.

Now the Postion Matching return the information as to whether the matched segment is located in a low emission zone.…

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

Do you have a use case, where you need to calculate the toll costs or emmissions for a driven route?

You can calculate toll or emissions for a driven route if you combine the PTV Developer Map Matching API and PTV Developer Routing API. …

Read more

Since we first released our PTV Developer Map Matching API there were a lot of improvements in the API.
All new features and improvements are listed in the API changes.

Today we like to introduce you to the highlights of the latest release of PTV Developer Map Matching API V1.3.6:

• Feature: Providing segment attributes like bridge, tunnel, speed limit, etc.

Read more

A new version of the PTV Developer Map Matching API is now available!

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

Routing API V1.1.0

• Improvement: The street field in the location information now contains additional street numbers, if available.

Read more