New PTV Mapserver 5.15.0.10

Download MapserverThe new release of PTV Mapserver 5.15.0.10 is now available for download in the Customer Area

  • Traffic information notification: Please be aware that, from May 05, 2020, we
    will no longer provide updates or support for live traffic messages.
    The data provider will stop any live traffic data support to this date and
    therefore we are not able to keep the traffic feed up and running.

Any further questions? Don’t hesitate to contact our PTV Support Team.

PTV xServer API Version 1.30 is now available!

Check out the highlights of the PTV xServer API Version 1.30.

General/All Services:

  • Improvement: By raising the internal size limit of high-performance routing networks it is possible to create them for all current maps (depending on your available memory). Please note that the binary format of the high-performance routing networks has changed and existing ones have to be recalculated.

PTV xTour Server:

  • Feature: Added support for additional restrictions in case of night tours.

See the 1.30 Release Notes for more details.

Download

The PTV xServer 1.30 can be downloaded from the customer area of the PTV Developer Zone. If you need further information or support please contact the Support Team.

Special Driving Times during Corona Crisis

In the current crisis dealing with the corona virus it is vital to especially keep up the supply chain of grocery stores and pharmacies. Several European countries relaxed the driving time regulations for lorry drivers to meet these major logistic challenges. The countries justified the changes by the need to ensure the supply of groceries, medical and health care products.

  • Austria
  • Czech Republic
  • Denmark
  • Great Britain/Ireland
  • Netherlands
  • Norway
  • Poland
  • Sweden

These countries decided on similar relaxations of working and driving hours for lorry drivers transporting groceries, medical and health care products. 

Daily working time of eleven hours

The certain lorry drivers are allowed to work up to eleven hours per day. The standard is nine hours per day. The weekly working time is increased from 56 hours to 60 hours, the maximum working time in two weeks is increased from 90 hours to 96 hours. The weekly rest must now be taken after the seventh day – it was the sixth day before. 

Working for five hours thirty at a stretch

In addition to the changes above, lorry drivers are allowed to work 5 hours 30 before they have to take a 45 minute break. The standard working time is 4 hours 30.

Details per Country

Each of those countries have specified a time frame the exceptional rules are valid in. It will expire April 16th at the latest and have to be extended actively per country if the situation still demands it. 

Austria: From March 14th (retroactively) until April 16th. 

Great Britain, Poland: From March 18th (retroactively) until April 16th.

Netherlands: From March 14th (retroactively) until April 6th.

xServer1 parametrization

The changed driving periods can be parametrized in xServer1, so if you need to, you can plan with the alternate values as shown below.

BreakRule

The periods for breaks that are required after a certain period of driving. After a driving period a driver shall take an uninterrupted break. This break can be replaced by two separate uninterrupted breaks. The rule assumes, that the period of the single breaks equals the sum of both split breaks.
Attribute Name Type Description
drivingPeriod int

Uninterrupted period of time a driver is allowed to drive without a break.

Remark: According to EU regulation : 4h 30min (16200s)
Relaxed Value : 5h 30min (19800s)

breakPeriod1 int

Minimum period of time required for the first break.

Remark: According to EU regulation : 15min (900s)

breakPeriod2 int

Minimum period of time required for the second break.

Remark: According to EU regulation : 30min (1800s)

DailyRestRule

The periods and frequencies needed to obey the daily rest rules of the European Union.
Attribute Name Type Description
regularRestPeriod int

Regular daily rest period.

Remarks: According to EU regulation : 11h (39600s)
firstSplitRestPeriod int

First period of a split regular daily rest period.

Remarks: According to EU regulation : 3h (10800s)
secondSplitRestPeriod int

Second period of a split regular daily rest period.

Remarks: According to EU regulation : 9h (32400s)
reducedRestPeriod int

Reduced daily rest period.

Remarks: According to EU regulation : 9h (32400s)
numberOfReducedRestPeriods int

Number of allowed reduced rest periods between any two weekly rest periods.

Remarks: According to EU regulation : 3
regularDrivingPeriod int

Regular daily driving period.

Remarks: According to EU regulation : 9h (32400s)
Relaxed Value : 11h (39600s)
extendedDrivingPeriod int

Extended daily driving period.

Remarks: According to EU regulation : 10h (36000s)
numberOfExtendedDrivingPeriods int

Maximum number of extended driving periods per week. The maximum allowed value is 2, larger values are not accepted.

Remarks: According to EU regulation : 2
maximumPeriodBetweenEndOfDailyRests int

Within each of this period after the end of the previous daily rest period a driver shall have taken a new daily rest period.

Remarks: According to EU regulation : 24h (86400s)

 

xServer2 parametrisation

To keep the API slim, in xServer2 environments the break and rest rules as well as the driving time regulations are available as a pre-defined rule set. Unfortunately, you are not able to change those values at the current state of development.

Detailed information: 
https://www.verkehrsrundschau.de/nachrichten/polen-lockert-lenk-und-ruhezeiten-von-lkw-fahrern-2583522.html/1605203
https://www.verkehrsrundschau.de/nachrichten/oesterreich-macht-ausnahme-bei-lkw-lenkzeiten-2582394.html/1605203
https://www.verkehrsrundschau.de/nachrichten/article-2584381.html

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.

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

New PTV Mapserver 5.14.0.10

The new release of PTV Mapserver 5.14.0.10 is now available for download in the Customer Area . This release contains following improvements:

  • 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.

Any further questions? Don’t hesitate to contact our PTV Support Team.