Search for content

API Changes

This list shows all changes of the API between releases like new features, significant improvements and bug fixes. We recommend that API developers periodically check it for updates.

Version 1.6.4

  • Bugfix: Superfluous nullable tags for simple parameters that are optional are now removed from the API definition.

Version 1.6.0

  • Feature: Providing toll information with affected vehicle categories.

Version 1.5.1

  • Bugfix: Recalculating a circular matched track via routeId will now produce valid results for toll and/or emissions.

Version 1.5.0

  • Feature: Providing vehicle-based restriction information for low emission zones.

Version 1.4.0

  • Feature: Providing low emission zones containing zone name, approvals, vehicle categories and fuel types.

Version 1.3.14

  • Improvement: Position matching now also takes into account segments that are blocked for cars.
  • Improvement: The coverage of segment attributes has been improved for position matching.

Version 1.3.6

  • Improvement: The preferred default languages used to return the result attributes 'countryName', 'city' and 'street' depend on the region of the matched segment instead of the complete country.
  • Improvement: Renamed error codes 'GENERAL_ACCESS_DENIED' to 'GENERAL_UNAUTHENTICATED' and 'GENERAL_UNAUTHORIZED' to 'GENERAL_FORBIDDEN'.

Version 1.3.0

  • Feature: Providing segment attributes like bridge, tunnel, speed limit, etc. for a complete matched GPS track.
  • Improvement: When requesting lower-level result elements such as segment attributes or route ids, the associated higher-level results are now automatically provided.

Version 1.2.0

  • Feature: Providing segment attributes like bridge, tunnel, speed limit, etc. for a single matched GPS position.
  • Improvement: The street field in the location information now only contains entries for the best fitting language.

Version 1.1.0

  • Improvement: The street field in the location information now contains additional street numbers, if available.
  • Improvement: Added warning if there is no location information for a matched position.
  • Bugfix: The country field in the location information is now optional and no more required. THIS IS INCOMPATIBLE TO PREVIOUS VERSIONS.
  • Bugfix: The stability of requesting SEGMENT_LOCATION_DESCRIPTORS in position matching is improved.

Version 1.0.0

  • Feature: Recalculating a matched GPS track using the Routing API.
  • Feature: Providing location information (country, city, street and postal code) for a single matched GPS position.
  • Feature: Controlling the quality and performance of the matching by using predefined parameter sets.
  • Feature: Matching a complete GPS track to the road network of the PTV map.
  • Feature: Matching a single GPS position to the road network of the PTV map.