The world is not enough – PTV xServer internet with API Version 2

We can proudly present you our test system for the PTV World City Map Premium 2019.2H with PTV xServer API Version 2.12. This map cluster is special because it is geo-redundant and provides High Performance Routing (HPR) in the Europe part.

Benefits of the new World City Map Cluster

  • Worldwide coverage for API Version 2 geocoding, rendering, routing and distance matrix calculation
  • Minimal latency because of equal deployments in Europe and North America
  • High Performance Routing Networks for the Europe part available

High Performance Routing

  • HPR graphs available for the geographic region Europe (ZZ_EUR)
  • HPR graph available for the following Profiles including the PTV_Truck_Attributes: tuck40t.xml, truck11_99t.xml and truck7_49t.xml
  • Customers who like to use the HPR graphs need to specify some settings in the xServer requests. See paragraph – How to use HPR – in this blog post below.

URL scheme

You can access the PTV xServer internet World City Map Premium cluster with the following url schemes:

Datacenter URLs :
Datacenter Europe https://xserver2-eu-(test).cloud.ptvgroup.com
Datacenter USA https://xserver2-us-(test).cloud.ptvgroup.com

Routed URL: https://xserver2-(test).cloud.ptvgroup.com

Prefer the datacenter url

  • For stateful xServer tasks you need a datacenter url. Stateful tasks are functions that involve multiple requests that need all to be executed on the same datacenter. For PTV xServer internet these are job requests (start/fetchCalculateTour) and all xTour-request, as xTour internally computes distance matrices that are re-used throughout multiple requests.
  • If your application or middleware is at a fixed location. If your application is hosted at the same region (or even the same Azure data center), we recommend specifying url for the according region.

Benefits of the routed URL

  • Improve responsiveness for interactive clients. If an interactive client accesses xServer internet directly, the requests are routed to xServer internet data center with the best latency, dependent on the location of the client. Typical low-latency use cases are mapping, auto-completion geocoding and drag&drop routing.
  • Domain sharding to bypass browser restrictions. The routed url also supports domain-sharding with the url scheme xserver2-(1-4)(-test).cloud.ptvgroup.com. This allows the web browser to open more connections than allowed for a single domain. This practice is typically used in map controls like OpenLayers or Leaflet to load map tiles from as many connections as possible.

How to use HPR

In order to use the HPR networks, the corresponding profile must be used. In addition, the Truck Attributes and HPR must be activated in the request and the geographical restriction ZZ-EUR must be specified for the HPR graph.
HPR graphs were provided for the following profiles:

  • tuck40t.xml + Truck Attributes + geographic restriction ZZ-EUR
  • truck11_99t.xml + Truck Attributes + geographic restriction ZZ-EUR
  • truck7_49t.xml + Truck Attributes + geographic restriction ZZ-EUR

Example request to list the available HPR graphs:

xdata.listHighPerformanceRoutingNetworks():

{
  "$type": "ListHighPerformanceRoutingNetworksRequest",
  "highPerformanceRoutingNetworkOptions": {},
  "resultFields": {
    "highPerformanceRoutingNetworkOptions": true,
    "profiles": true
  }
}

Example request for a routing using a HPR graph:

xroute.calculateRoute():
 
{
  "$type": "RouteRequest",
  "storedProfile": "truck40t",
  "waypoints": [
    {
      "$type": "OffRoadWaypoint",
      "location": {
        "$type": "OffRoadRouteLocation",
        "offRoadCoordinate": {
          "x": 6.22029,
          "y": 49.61513
        }
      }
    },
    {
      "$type": "OffRoadWaypoint",
      "location": {
        "$type": "OffRoadRouteLocation",
        "offRoadCoordinate": {
          "x": 6.06479,
          "y": 49.62127
        }
      }
    }
  ],
  "routeOptions": {
    "routingType": "HIGH_PERFORMANCE_ROUTING",
    "geographicRestrictions": {
      "allowedCountries": [
        "ZZ-EUR"
      ]
    }
  },
  "requestProfile": {
    "featureLayerProfile": {
      "themes": [
        {
          "id": "PTV_TruckAttributes",
          "enabled": true
        }
      ]
    }
  }
}

Productive system

The productive System is planned for June 3rd 2019.
On this date we will reroute the URL of the actual North/South America and Europe Map Cluster to this new World City Map cluster.

Toll update 2019_05 available

Italy
New tariff table for Italy January 2019. This scenario replaces the previous ‘Italy March 2018’ scenario.

Concerned maps

  • PTV Europe City Map Premium 2019.2H – toll update version 2019_2H_6
  • PTV Europe City Map Premium 2019.1T – toll update version 2019_1T_8
  • PTV Europe City Map Premium 2019.1H – toll update version 2019_1H_9
  • PTV Europe City Map Premium 2018.2T – toll update version 2018_2T_11
  • PTV Europe City Map Premium 2018.2H – toll update version 2018_2H_14

Please note: This and all following toll updates will be only available via automatic update with the PTV Content Update Service.

We recommend to use PTV Content Update Server Version 2.x.
Also your current PTV xServer API Version 1 can work with PTV Content Update Server Version 2.x – using  PTV CUS xServer 1 Adapter.
For PTV Mapserver please use the PTV Toll Update Tool.
PTV xServer internet was updated recently.

If you need further information or support please contact the Support Team.

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.

JAVA – “wind of change” wasn’t just an early 90’s thing

From the beginning of time PTV included Oracle JAVA Runtime Environment (JRE) in xServer. Oracle now changed its license policies and any updates for commercial use are only available with a paid subscription.
This marks a severe change for PTV especially in the xServer context. We want to be as flexible as possible and want to provide our customers a reliable, easy to maintain product.
Our learning from this was, we don’t want to be dependend on one particular JRE provider, but rather work with standard functionality, which is fulfilled by a number of providers.

What will happen?

Starting with the upcoming xServer Versions 1.28 and 2.12, PTV will not ship a JAVA JRE within its xServer products anymore. Instead it relies on a JAVA JRE provided by the operating system environment.

What are the advantages?

  • PTV Customers are not limited to a specific JAVA distribution – reducing potentional license fees.
  • You might just use an already installed JRE – reducing the number of JAVA Versions running on your System.
  • The Server can install security updates for JAVA independent of xServer releases keeping your system security up to date.

What will NOT change?

  • xServer will work just the same – it still uses JAVA to provide its services.
  • xServer Internet will take care of that issue for you.
  • Your integrations doesn’t need any ajustments and will still work and react the same.
  • The xserver performance will be comparable to an integrated JRE – no change in any direction is to be expected.

Things to consider

  • Since a JAVA RE is an additional xServer system requirement, you need to take care of that – just like any other JAVA depending software. But we worked hard to make it as simple as possible.

For more help and advice, contact support.de@xserver.ptvgroup.com

Toll update 2019_04 available

Slovakia
New tariffs 2019 and new toll roads. This scenario replaces the previous ‘Slovakia October 2016’ scenario.

Concerned maps

  • PTV Europe City Map Premium 2019.2H – toll update version 2019_2H_5
  • PTV Europe City Map Premium 2019.1T – toll update version 2019_1T_7
  • PTV Europe City Map Premium 2019.1H – toll update version 2019_1H_8
  • PTV Europe City Map Premium 2018.2T – toll update version 2018_2T_10
  • PTV Europe City Map Premium 2018.2H – toll update version 2018_2H_13

Please note: This and all following toll updates will be only available via automatic update with the PTV Content Update Service.

We recommend to use PTV Content Update Server Version 2.x.
Also your current PTV xServer API Version 1 can work with PTV Content Update Server Version 2.x – using  PTV CUS xServer 1 Adapter.
For PTV Mapserver please use the PTV Toll Update Tool.
PTV xServer internet was updated recently.

If you need further information or support please contact the Support Team.