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.
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.
Routing bug fix: Setting the speed profile of IVehicle::put_SpeedProfile() with a maxSpeed parameter which is not the highest speed compared to all the other speed parameters, resulted in internal interpolated speeds with too low values. This issue is corrected and corresponds to the results obtained by PTV xRoute with the same settings.
InstKit Setup bug fix: Under unclarified circumstances the base DLLs of Mapserver did not install. Via script these DLLs are set explicitly for installation now.
The speed classification in the upcoming maps Europe Premium 2019.1 (and higher) will change. To get better route calculation results, the used profiles have to be adapted. Further details can be found in the method description of IVehicle::put_SpeedProfile() and the ReadMe. More Information about this topic will also be provided later this Year.