Tag: Map Matching API

In Version 1.7.0 of PTV Developer Map Matching API time stamps are supported in input and output.

This allows you to use the timestamp from the response for better toll calculation in the case of time-based tolls. You can easily get the “startTime” for each path and use it together with the “routeId” in the PTV Routing API to calculate the toll.…

Read more

The newest version of our Map Matching API version 1.6.0 now supports toll road information for Position Matching.

This information helps our customers to decide if a road is a toll road or not. The toll road information is vehicle category based.…

Read more

The newest version of our Map Matching API version 1.4.0 now supports vehicle-based restriction information for low emission zones.

This information helps our customers to decide which vehicle can enter a low emission zone and when.

We added a new show case to see the new vehicle-based low emission zone information.…

Read more

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