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.
we proudly present our PTV xServer 2.1.0 release with seven services in total. In addition to the well-known geographic services xMap, xLocate and xRoute with significant further progress, we offer the brand-new logistics services xDima, xCluster, xTour and xLoad.
For on-premise solutions you have two possibilities to pick up our “Christmas present” at:
The corresponding geocoding data for on-premise solutions is on request as it is not included in the map (for running xLocate). On the other hand this data is installed for cloud solutions.
the test system on xServer internet has PTV Europe City Map 2017.1 (HERE) installed and at the moment we still host the geographic services only. All seven services and a productive system will follow.
Our new PTV xServer 1.22 release is available NOW!
Highlights of the new 1.22 Version:
PTV xServer: With the upcoming Europe City Map 2016.2 we will introduce a new Feature Layer Truck Waiting times. This first version will include the waiting times at toll booths. As soon as the Feature layer is available you can use it for predictive routing and display the waiting times in the map.
PTV xRoute Server: With the new xRoute 1.22, the Belgium Toll valid from 01.04.2016 can be calculated respecting the three different toll regions. The NGA emission factors for Australia are updated to the 2015 version. There is a new way for exception path input using an intersecting line.
PTV xMapMatch Server: Improved global matching by when driving with low speed, comming from off-road or when the GPS tracks ends.
At this point we would like to inform you of our Webinar taking place March, 3th 2016 where we will demonstrate the new features of PTV xServer 1.22.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.