Author: Isabel Honikel
Senior Technical Product Manager
-
Suggestion by Text Supports Result Language
In the new version of the PTV Developer Geocoding & Places API V1.15.0 we improved the Suggestion by text endpoint.
With this feature, you can now specify the language for the results from the Suggestions by text endpoint, providing more flexibility and accuracy for your geocoding needs. …
-
New Batch Geocoding Service available
We are happy to introduce the new Batch Geocoding Service version 1.0.1.
You now can send several addresses or positions at once. PTV Developer now provides asynchronous batch APIs. The new endpoints by-addresses, by-texts and by-positions provide the same functionality as their corresponding endpoints for single requests.…
-
Improved geocoding when using long postcodes
In the new version of the PTV Developer Geocoding & Places API V1.13.5 we improved the support of long postal codes.
In the Netherlands it’s common to enter just the (long) postcode and house number. In most cases an exact match is possible but in some rare cases a result with exact house number and with partly exact postcode was returned.…
-
Track Matching output now includes time stamp
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.…
-
Find out which vehicle can enter a low emission zone
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.…