PTV xServer 2.16 available

The new PTV xServer API Version 2.16 is available for download. For the full list of features and improvements you can check the corresponding release notes here.

Here are some feature highlights of API Version 2.16:

  • General:
    • A first draft of OpenAPI documents describing all JSON and REST operations is available
    • The Bill Of Materials (BOM) for third-party licenses can be downloaded form the PTV xServer
  • xMap:
    • Support for client-side rendering of Feature Layer icons (experimental)
  • xRoute:
    • Support for monetary cost routing including toll costs (experimental)
    • Detailed Toll and EU/US driving time regulations are no longer experimental
  • xTour:
    • Support for new types to specify the vehicle position for a tour in execution (experimental)
    • EU Driving time regulation and working time directive are no longer experimental

For on-premise solutions you can download the latest version from the Customer Area at the Developer Zone. http://xserver.ptvgroup.com/de/nc/developer-zone/customer-area/ (login and license required)

For cloud solutions we provide a test and production system based on this release. The PTV World City Map test cluster contains the PTV xServer API version 2.16 release plus all future and finished changes for the next release.
The PTV World City Map production cluster on PTV xServer internet was updated with version 2.16 resently.

Check the Cluster Overview page to get more information about existing PTV xServer internet deployments.

 

PTV xServer internet update – Update of PTV xServer to API Version 2.16

We plan to perform maintenance on January, 20th 2020 that does not require any downtime.
The following tasks will be completed in the scope of this maintenance.

PTV World City Map [Here]- production/test/integration – cluster with API version 2:

  • PTV xServer update from version 2.14 to version 2.16
  • This update includes some changes in time out handling:
    We deactivated the computationTimeout (https://bit.ly/2PZE2gG) for requests.
    This will have the effect that all requests even on long lasting requests will be executed until the computation is finished, or for asynchronous requests until they will be stopped on request of the client.

Please test your application and report any problem immediately.