Tag: API Version 2
-
Important Information: Migration of the PTV Customer Area
We would like to inform you that the PTV Customer Area for PTV xServer will be migrated to a new technological platform by the end of October 2025. This transition aims to significantly improve the user experience and administration capabilities.
The previous Customer Area served as a self-service portal, allowing you to download PTV xServer products and add-ons.…
-
PTV xServer 2.38 released
The new PTV xServer API version 2.38 is available! Besides several improvements and bugfixes there is also a new feature for routing:
xRoute
- Continuing the route in the same direction in which the waypoint was reached
If you are interested in the full list of changes, you can check the corresponding release notes here.…
-
PTV xServer 2.37 released
The new PTV xServer API version 2.37 is available! Besides several improvements and bugfixes there are also new features for routing:
xRoute
- Providing tour events of type ‘DRIVING’ to ensure the same behavior as for xTour
- Relaxing Feature Layer attributes with custom Feature Layer like raising the height of a bridge
If you are interested in the full list of changes, you can check the corresponding release notes here.…
-
Migration required: New URL for dynamic content
The PTV xServer 1 and 2 get dynamic content like the current traffic situation or toll updates via the PTV Content Update Service (CUS). This CUS is usually installed and running in the same local network as the PTV xServer and gets the content from the PTV Layer Delivery Server (LDS) hosted by PTV.…
-
PTV xServer 2.36 released
The new PTV xServer API version 2.36 is available! Main reason is the filtering of results without a street name introduced with PTV xServer 2.35 in reverse geocoding. Due to performance reason, now this must be switched on explicitly:
xLocate
- Activating the filtering of results without a street name in reverse geocoding
xData
- Preventing border crossings when creating a high-performance routing network (experimental)
xDima
- Preventing border crossings when creating a distance matrix (experimental)
xRoute
- Preventing border crossings when calculating a route (experimental)
If you are interested in the full list of features and improvements, you can check the corresponding release notes here.…
-
PTV xServer 2.35 released
The new PTV xServer API version 2.35 is available! Besides several improvements and bugfixes we provide these main features:
General
- Providing Java and C# clients generated by OpenAPI Generator
xMatch
- Setting and returning time stamps to use them in a route request considering time-dependent toll tariffs (experimental)
xRoute
- Providing additional information for low-emission zones like required badges (experimental)
Please note that we recommend using the new JSON clients based on OpenAPI documents and now generated by OpenAPI Generator as soon as possible.…