PTV xServer API Version 2.12 is now available!

We proudly present our new PTV xServer API Version 2.12 Release. For the full list of Features and Improvements you can check the corresponding release notes here.

xTour – Group ID’s

Here are some feature highlights of API Version 2.12:

  • Framework
    • Added support for external Java installations (64-bit Java 8 required. We recommend the use Amazon Corretto or Orcale Java). Please note that the Java Runtime Environment is no longer integrated in the PTV xServer and need to be installed separately. You find more information on the according Manual Page.
    • Updated the stored profiles to DataCompatibilityVersion 2 as all current maps are also based on this version. Please ensure that your profiles and map data have the same version. Otherwise the PTV xServer won’t start
  • xLocate
    • The representation of the country results (Name, ISO-2, ISO-3 or license plate code) can be specified in the request
  • xMap
    • Improved the rendering performance especially when using Feature PTV_(Truck-)SpeedPatterns
  • xRoute
    • Introduced a REST-API for xRoute (Note that the method is experimental)
  • xTour
    • Added support to plan precombined trips by specifying the attribute ‘groupId’ for each order and the attribute ‘orderGroupConsideration’ in the planning options. (Note that this is experimental)
    • Alternative depots are also supported for the methods ‘changeTours’ and ‘findChangeToursProposals’. (Note that this is experimental)
    • Added attribute ‘legReports’ to the element ‘TourReport’ to return information for each leg between two consecutive stops. (Note that this is experimental)
  • xLoad
    • Unloading sequence support
    • Added stackability restrictions by ItemTypes

For on-premise solutions you can download the latest version from the Customer Area at the Developer Zone.

For cloud solutions we will provide test and production systems based on this release. The Europe test cluster already contains the PTV xServer API version 2.12 release plus all future and finished changes for the next release.

  • Check the General Information page to get more information about existing PTV xServer internet deployments.

PTV xServer API Version 1.28 is now available!

Check out the highlights of the PTV xServer API Version 1.28.

featurelayer

General/All Services:

  • Added support for external Java installations (64-bit Java 8 required, Amazon Corretto and Oracle Java recommended). Please note that the Java Runtime Environment is no longer integrated in the PTV xServer and must be installed separately. You find more Information on the according Manual Page.
  • Updated the stored profiles to version 2 as all current PTV maps are also based on version 2. Please ensure that your profiles and map data have the same version as otherwise the PTV xServer won’t start.
  • In case of inconsistent map and Feature Layer data (e.g. mixing different providers or versions by mistake) the PTV xServer won’t start.

PTV xTour Server:

  • Feature: Added new parameter ‘mergeTransportPointCountPerSite’ that counts all transport points at the same site as single transport point regarding the restriction ‘maxTransportPointCountPerTour’.

See the 1.28 Release Notes for more details.

Download

The PTV xServer 1.28 can be downloaded from the customer area of the PTV Developer Zone. If you need further information or support please contact the Support Team.

PTV xServer API Version 2.11 is now available!

We proudly present our new PTV xServer API Version 2.11 Release. For details about the services you can find the corresponding release notes here.

Reverse Geocoding with PTV xLocate

Here are some feature highlights of API Version 2.11:

  • Framework
    • Support of dynamic Feature Layer based toll updates using Content Update Service (CUS) for PTV xRoute and PTV xMap
  • xLocate
    • Introduced Reverse Geocoding for localities, post code points, streets, interpolated and exact addresses (Please note that a Europe City Map 2019.2H or newer is required)
    • Support of long postal codes in Great Britain and Ireland for exact and interpolated addresses
      (Please note that a Europe City Map 2019.2H or newer is required)
  • xMap
    • New thinned rendering profile “Amber” is now available.
  • xDima
    • Introduced a new time consideration scenario “MultipleTravelTimes” to create distance matrices containing multiple travel times using Feature Layer PTV_SpeedPatterns
  • xTour
    • Consider multiple travel time distance matrices in optimization
    • Added support for working time of EU directive 2002/15/EC. Note that this is only usable together with multiple travel time distance matrices
    • Alternative depots can be considered within the tour planning

For on-premise solutions you can download the latest version from the Customer Area at the Developer Zone.

Note that the Customer Area has been relaunched. You can find more information in a previous blog post.

For cloud solutions we will provide test and production systems based on this release. The Europe test cluster already contains the PTV xServer API version 2.11 release plus all future and finished changes for the next release.

  • Check the General Information page to get more information about existing PTV xServer internet deployments.

PTV xServer API Version 2.10 is now available!

We proudly present our new PTV xServer API Version 210 Release. For details about the services you  find the corresponding release notes here.

Here are some feature highlights of API Version 2.10:

  • xLocate
    • The query parameter ‘mapLanguage’ in the REST-API is no longer experimental
  • xMap
    • The query parameters ‘mapLanguage’ and ‘contentType’ in the REST-API are no longer experimental
    • The Feature Layer ‘PTV_TruckAttributes’ supports restrictions for vehicles with trailer exceeding a given length or width
    • The attribute ‘mappingProfile‘ has been renamed to ‘renderingProfile‘. It has been revised completely and is no longer experimental. Please use the revised profiles in the folder conf/profiles/rendering/featurelayer. Furthermore the use case of the profiles is now called ‘rendering’ instead of ‘mapping’.
      To make it more easy for you to react to the adjustments of the experimental API, we provide a FromMappingToRendering PDF document with all the changes
  • xRoute
    • The Feature Layer ‘PTV_TruckAttributes’ supports restrictions for vehicles with trailer exceeding a given length or width
    •  Added support to export a route that can be used for guided navigation. The attribute ‘guidedNavigationRoute’ returns a string that can be imported into PTV Navigator. Please note that this is experimental
    • Some API elements like route report, toll summary and waypoint names at legs are no longer experimental
  • xTour
    • The performance in the method ‘changeTours’ is improved for all available actions

For on-premise solutions you can download the latest version from the Developer Zone.

Note that the Customer Area has been relaunched. You can find more information in a previous blog post.

For cloud solutions we provide systems based on this release. It contains the PTV xServer API version 2.10 release plus all future and finished changes for the next release.

  • Check the General Information page to get more information about existing PTV xServer internet deployments

New PTV xServer Release available!

Toll Report in Florida using Feature Layer toll

We proudly present our new PTV xServer release. For details about the services you  find the corresponding release notes here.

Here are some feature highlights of API Version 2.9:

  • xLocate
    • Geocoding Data for North America (including Mexico and Canada) is now available
    • City results are now listed by population
  • xMap
    • Introduced rendering of toll roads
      Note that this feature requires new toll data in Feature Layer format which is currently only available for the US
  • xRoute
    • New way of toll calculation using Feature Layer toll data
    • Introduced multiple payment methods at toll locations (including electronic toll collection)
    • Determine when a vehicle enters or exists a toll road by using the new toll events
  • xTour
    • Support for EU drivers’ working hours in case of multi-day tours with daily rests anytime and anywhere necessary.
    • Added method ‘findChangeToursProposals’ to get proposals for modifying an existing tour plan stored on server side
    • The method ‘planTours’ can be stopped during computation getting an intermediate but valid response that usually differs from the final response.
    • Additional order relocation and swap moves are executed to improve the tour planning results

For on-premise solutions you can download the latest version from the Developer Zone.

For cloud solutions we provide systems based on this release. It contains the PTV xServer API version 2.9 release plus all future and finished changes for the next release.

  • Check the General Information page to get more information about existing PTV xServer internet deployments

How to handle (individual) profiles with the new speed adaptation

As mentioned in two earlier blog posts there will be adjustments in the profiles of PTV xServer to gain more realistic travel times when calculation routes. See the blog posts below for more information:

Precise, accurate, reliable – new static speeds for better route calculation within PTV xServer

New Static Speeds – FAQ PTV xServer


In the following you can find more detailed information about the changes and usage of individual profiles when it comes to the new maps with adapted initial speed values.

Where can I find information about the dependencies from map and profiles?

You can check the online documentation of the respective PTV xServer Version.There you can find a table which shows our currently supported maps and their related profile version.

API Version 1 – Profiles and Map Versions
API Version 2 – Profiles and Map Versions

I want to use one of the new maps, where can I obtain the new profiles?

Within the shipment of the map data you will receive a download link for zip-file containing the necessary profiles and a installation guide for the PTV xServer API Version you are using.

Shipped Profile Directory API Version 1

Shipped Profile Directory API Version 2

Check the READ_ME.txt within your directory for detailed information about the different folders.

Which profiles are affected?

All XML-based PTV xServer profiles need to adapted/replaced. This also includes the rendering xml-profiles and Feature Layer profiles.

In general we recommend to fully replace the conf/profiles folder of your PTV xServer by the ones you receive via the download link (see pictures above).
Don’t forget to make a local backup of your actual and customized profiles if you want to switch back again.

Which parameters of the profiles are affected?

<dataCompatibilityVersion> (API Version 1 & 2)

This new parameter was introduced in both PTV xServer API versions to check if the map- and profile versions are compatible. It is placed in the root node of all xml-based profiles. If the version differ, your PTV xServer won’t start up and leave a message in the log files. Check the links about profile and map dependencies above to get  information about the data version of your map.

Affected parameters of API Version 1 & 2

The values of the following paramaters were changed to fit to the new inital speed values of the basemap with dataCompatibilityVersion 2. You can click on the parameter names in the table below to directly jump into the API documentation.

API Version 1 API Version 2
<SpeedRangeByNetworkClass maximumSpeed> <maximumSpeeds>
<SpeedRangeByNetworkClass minimumSpeed> <minimumSpeeds>
<LevellingScopeByNetworkClass> <minimumDistancesFromWaypoint>
<MalusByNetworkClass> <penaltiesByNetworkClass>

Note, that even though there are a lot of routing profiles, there are four “classes” of routing relevant parameters (see table above). These relevant parameter “classes” are used in the profiles truckfast, truckslow, carfast and carslow for API Version 1 and truck and car for API Version 2. Every other profile inherits those values of one of the four mentioned.
A detailed overview of the parameters and their values for PTV xServer API Version 1 & 2 as well as the differences between the DataCompatibilityVersion 1 & 2 can found in the PDF NewSpeedValues.

Check the Online-Manuals for detailed information about profile handling basics within PTV xServer.
API Version 1 – Profiles & Inheritance
API Version 2 – Profiles & Inheritance

I created an own individual profile, what do I have to do?

If you changed the values of one of the parameters above, we highly recommend to use the new values provided in the profiles with DataCompatibilityVersion 2 when using a map with the same version. Check the PDF mentioned above. You also have to set the new parameter <dataCompatibilityVersion = “2”/> in the root node of your individual profile, when you want to use it with one of the maps with adapted speed values.

If you only adjusted physical attributes in your individual profile and inherit the values above from a profile provided by PTV, you only have to set the parameter <dataCompatibilityVersion = “2”/> within the root knot of the profile.

What about the folders “VehicleProfiles_Australia” and “VehicleProfiles_NorthAmerica”?

In this folders you can find more routing profiles which are based on national regulations of the regarding regions. Furthermore the routing relevant parameters are adjusted to the national conditions. Check the “READ_ME.txt” fore more details.

I have some more questions, who can I contact?

If you got more questions related to the speed adaptations, feel free to contact the PTV xServer Support Team (support.de@xserver.ptvgroup.com).