Tag Archives: xtour

xServer API Version 2 – Getting trucks and trailers sorted

Posted on by

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 API Version 2.13 is now available!

Posted on by

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.

PTV xServer API Version 2.12 is now available!

Posted on by

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 2.10 is now available!

Posted on by

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!

Posted on by

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

New PTV xServer Release available!

Posted on by

We proudly present our new PTV xServer release. This release is focused North America Geocoding and Rendering, but there are more features for world wide use.

For details about the services you find the corresponding release notes here.

Here are some feature highlights of API version 2.7:

  • Framework
    • For detailed monitoring it is now possible to send requests to dedicated backend instances.
  • xLocate
    • The geocoding search produces results even if some words were falsely concatenated in the input (e.g. ‘Ruedestrasbourg’ instead of ‘Rue de Strasbourg’).
    • The total score and the address scores (formerly modelled as field scores) are no longer experimental.
  • xMap
    • Country-specific styles for Feature Layer may be configured (e.g. to show country-specific icons for truck attributes in North America).
    • Street names are now drawn along the road considering the street curve.
  • xTour
    • Added a new attribute ‘drivers’ to the fleet. A driver is assigned to a vehicle and may be given exactly one operating interval.
    • In a multi-day planning scenario it is now possible to only plan daily rests if it is necessary, i.e. there may be multiple trips per day without daily rest between them.
    • New possibility in the ‘changeTours’ method to change fixations of an existing tour plan stored on server side.
    • It is now possible to fix a trip to a vehicle in the input plan to make sure such trips are not changed at all.

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

For cloud solutions we provide a test system based on this release. It contains the PTV xServer API version 2.7 release plus all future and finished changes for the next release:

Some notes:

  • The PTV xServer API version 2.x requires a 2017.1 map or newer.
  • The corresponding geocoding data for on-premise solutions is on request. It is not included in the map. This is required for running xLocate. (The data is available for PTV Europe City Map and with this release also for the PTV North America City Map from HERE).
  • PTV xServer internet (test and productive system) provides PTV Europe City Map 2017.2 (HERE). The update to PTV Europe City Map 2018.1 (HERE) is scheduled for the near future. The productive system already provides the API version 2.7.