xServer API Version 2 – Getting trucks and trailers sorted

In xServer API Version 1 there are several truck profiles available:

  • truckfast, truckslow:
    3 axles, length 12m, without a separate trailer (actually based on a 7,5t box truck
  • several product specific truck40t profiles:
    5 axles, length 18m, with a separate trailer (a 3axle box truck with a 2 axle trailer)

With xServer API Version 2 we provide two 40t truck vehicle profiles:

  • truck40t:
    5 axles, length 16,5m, without a separate trailer (tractor with semi-trailer)
  • trailertruck:
    articulated train with 5 axles, total length 18,75m, tractor with a separate trailer

The default vehicle is defined as the most common vehicle in this weight category – the semi-trailer. This corresponds with the “truck40t” vehicle profile.

Unfortunately we didn’t notice until now, that especially the description of the truck40t differs in these two xServer API versions.
To be more consistent we now swapped these two profile names “trailertruck” and “truck40t” in xServer API Version 2 – starting from the current Version 2.13.

So now, with xServer API Version 2.13 the two 40t truck vehicle profiles are:
– truck40t: articulated train with 5 axles, total length 18,75m, 3 axle tractor with a separate 2 axle trailer
– trailertruck: 5 axles, total length 16,5m, without a separate trailer (tractor with semi-trailer)

 

So what will happen to my application?

Presumably not much, since the speed profile and most physical attributes and dimensions are equal in both profiles. The only things which changed are:
– total length of the vehicle (very few truck attributes refer to this)
– number of Trailers
– Separate empty weights of tractors and trailer

When you use “default” nothing changes. Since the default stays a semi-trailer. Now equivalent to the “trailertruck” vehicle profile instead of the “truck40t”.

When you refer to “truck40t”, it is now an articulated truck with a trailer.

When you refer to “trailertruck”, it is now a semi-trailer.

PTV xServer internet update on all API Version 2 Clusters

We plan to perform maintenance on July, 8th 2019 that does not require any downtime.
The following tasks will be completed in the scope of this maintenance.
PTV xServer update from version 2.12 to version 2.13 on the listed map clusters:

The PTV World City Map test system was already updated. Please test you application on the test system and report any problem immediately.

PTV xServer internet update on PTV North/South America City Map cluster with API Version 1

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

Improved Geocoding in Bazil on test, integration and production:

The geocoding response from the xServer now contains the two-digit abbreviation of the state, as it was specified in the request.
This update also effects the reverse geocoding. The state will be returned as a two-digit abbreviation in the response.

PTV xServer API Version 2.13 is now available!

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

Taking the European driving regulations into account with PTV xRoute

Here are some feature highlights of API Version 2.13:

  • Framework
    • Swapped the stored profile names ‘truck40t.xml’ and ‘trailertruck.xml’ to harmonize it with all other PTV products. Please note that the default routing profile keeps all values, but now refers to the correctly named ‘trailertruck’.
      Please check this addtional Blog Post for detailed information
  • xLocate
    • Support for address interpolation using single-field input
    • Improved the performance for using single-field input
    • Added support for addresses given by only a long postal code using single-field input, which is especially relevant for Ireland
      Please note that features mentioned above require a 2020.1H map or newer.
  • xMap
    • Improved the rendering performance when using Feature Layer (in particular PTV_TruckAttributes)
  • xRoute
    • Added support to calculate tour restrictions including EU drivers’ working hours and working time of EU directive 2002/15/EC. Please note that this is experimental
    • Added support to consider alternative near-by roads by using the new attribute ‘considerAlternativeNearByRoads’ together with an ‘OnRoadWaypoint’. Please note that this is experimental
    • Introduced ‘ManipulateRouteWaypoint’ to manipulate the course of a route by passing a location within a radius. Please note that this is experimental
  • xTour
    • Added attribute ‘orderGroupIds’ to the element ‘Vehicle’ to specify which order groups can be served by the vehicle
    • The tour planning results for orders of type ‘OrderWithAlternativePickupDepots’ or ‘OrderWithAlternativeDeliveryDepots’ are improved
  • xLoad
    • It is possible to combine stacking restrictions with the maximum allowable surface load on items
    • Reversed the order of the attribute ‘unloadingSequence’. The first items will be unloaded first (and loaded last)

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.13 release plus all future and finished changes for the next release.

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

Toll update 2019_06 available

Belgium
This scenario includes the toll charges from July 2019, for trucks from a maximum authorised mass over 3.5 t in the three Belgian regions: Wallonia, Flanders and Brussels.
Toll roads include motorways, additional main roads and the local road network in Brussels. Toll charges are calculated based on kilometre factors and depend on the road type and further depend on the emission class and total weight of the vehicle. This scenario replaces the previous ‘Belgium January 2019’ scenario.
Type of calculation: By approximation with an average factor per kilometer.

Concerned maps

  • PTV Europe City Map Premium 2019.2H – toll update version 2019_2H_7
  • PTV Europe City Map Premium 2019.1T – toll update version 2019_1T_9
  • PTV Europe City Map Premium 2019.1H – toll update version 2019_1H_10
  • PTV Europe City Map Premium 2018.2T – toll update version 2018_2T_12
  • PTV Europe City Map Premium 2018.2H – toll update version 2018_2H_15

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.

Discontinuation of various versions of PTV xServer, add-ons and maps

To ensure a smooth transition, we kindly ask you, to notice the following information. PTV Group will be terminating following products, plugins, maps and more:

  1. All versions of PTV World Map based on AND as of 1st April 2019
  2. PTV BCR Converter versions 1.0.1.0 and 1.0.0.0 as of 1st January 2020
  3. PTV xServer add-ons AJAX Maps versions 3.5.25-3.5.30 as of 1st January 2020
  4. PTV xServer .NET version 1.5 as of 1st January of 2020
  5. All other PTV Map versions 2018 as of 1st January 2020
  6. PTV xServer API version 1.24 and PTV xServer API versions 2.7-2.11 as of 1st April 2020
  7. PTV Content Update Service all versions of API 1 (1.28 and all previous versions) as well as version 2.11 and all previous versions of API 2 as of 1st April 2020

Please notice

  • that the Content Update Service of API 2 (currently version 2.12) is available. This service is also compatible to PTV xServer API 1 and very efficient.
  • The PTV World Map based on AND is replaced by an extracted version of PTV World City Map from TomTom. The contract with the data provider AND was terminated as of 31.03.2019. Therefore, maps based on AND may not be used in licensed PTV products. Consequently, PTV has stopped the processing and supply of PTV maps based on AND.

We have already provided the following upgrade paths to updating to the latest versions of:

From this date onwards, we will no longer provide updates or support for the versions as listed below.

Discontinuation notice for PTV xServer API version 1.24 effective from 1st April 2020:

PTV xServer Version Operating System
PTV xCluster Server 1.24.0.0 – 1.24.0.4 Windows and Linux distributions
PTV xDima Server 1.24.0.0 – 1.24.0.4 Windows and Linux distributions
PTV xLoad Server 1.24.0.0 – 1.24.0.3 Windows and Linux distributions
PTV xLocate Server 1.24.0.0 – 1.24.0.3 Windows and Linux distributions
PTV xMap Server 1.24.0.0 – 1.24.0.4 Windows and Linux distributions
PTV xMapmatch Server 1.24.0.0 – 1.24.0.4 Windows and Linux distributions
PTV xRoute Server 1.24.0.0 – 1.24.0.4 Windows and Linux distributions
PTV xTerritory Server 1.24.0.0 – 1.24.0.4 Windows and Linux distributions
PTV xTour Server 1.24.0.0 – 1.24.0.4 Windows and Linux distributions
PTV xServer bundle 1.24.0.0 – 1.24.0.5 Windows and Linux distributions

Discontinuation notice for PTV xServer API versions 2.7-2.11 effective from 1st April 2020:

PTV xServer Version Operating System
PTV Server 2.7.0 – 2.11.2 Windows and Linux distributions

Discontinuation notice for PTV xServer plugins effective from 1st April 2020:

PTV xServer plugins Version Operating System
Content Update Service 1.20.0.0 – 1.28.0.0
2.0.0 – 2.11.0
Windows and Linux distributions
Content Update Service Adapter 2.0.0 – 2.11.0 Windows and Linux distributions

Discontinuation notice for PTV xServer add-ons effective from 1st January 2020:

PTV xServer add-ons Version Comment
AJAX Maps 3.5.25.0 – 3.5.30.0 Java Servlet in combination with PTV xMap Server
BCR Converter 1.0.0.0 and 1.0.1.0 Windows and Linux distributions

Discontinuation notice for PTV xServer .NET effective from 1st January 2020:

PTV xServer Version Comment
PTV xServer .NET 1.5 Framework for .NET applications in combination with PTV xServer

Discontinuation notice for PTV Maps version 2018 effective from 1st January 2020:

PTV Maps Version Map & Data Provider
PTV Europe City Map Premium 2018.1H, 2018.2H, 2018.1T, 2018.2T Here, TomTom
PTV North America City Map 2018 Here
PTV South America City Map 2018 Here
PTV Australia City Map 2018 Here
PTV World City Map Premium 2018.1T, 2018.2T TomTom (+AND)
PTV Africa City Map 2018 TomTom
PTV South Asia City Map 2018 TomTom
PTV Arabia City Map 2018 Here
PTV India City Map 2018 Here

Discontinuation notice for PTV World Map effective from 1st April 2019:

PTV xServer Version Comment
PTV World Map 2018 Contract was terminated effective from 31.03.2019 with data supplier AND.
It is not permitted to use AND data in PTV products from that time.
Please use the extracted PTV World Map from TomTom instead.

In accordance with PTV Group’s product discontinuation policy, we are providing you notice of this phase-out so that you have adequate time to replace the solutions via updating to the latest software versions available.

PTV Group is committed to providing the highest level of quality and service to you. Based on your requests, we constantly enhance our software and keep integrating new and improved functions and contents. Therefore, we strongly advise you to partake in our maintenance contract, as it integrates extended functions and ensures their systems always remain up-to-date – a basic prerequisite for their day-to-day operations.

To meet the growing requirements, PTV Group, like other software providers, needs to limit the number of software versions available. This way, we can always make sure that our resources stay focused on further improving PTV xServer, PTV xServer add-ons and PTV Maps as the current software solutions create the perfect conditions for your business applications to excel.

In case you have further questions, please don’t hesitate to contact your representative sales partner.