Real-time information on transit times at border crossings

To contain the corona virus, many states have reintroduced border controls or closed borders completely.
This resulted in long queues and long transit times at the borders during the week of 16-22.03.2020, which also led to long transit times. As of today, the situation has improved again, but should be closely monitored.

Therefore we have joined forces with our customers and partners to find solutions to reduce the uncertainty caused by the long transit times at borders.

We now offer you the possibility to use real-time data of the start-up Sixfold GmbH on our cloud Solution PTV xServer internet. This gives you an overview of all relevant border crossing times for trucks in real time and allows you to use them for visualization and routing in our PTV xServer. This function helps dispatchers understand the extended transit times for border crossings and even automatically avoid crowded border crossings.

How to use the Feature Layer containing the Sixfold data about transit times at borders?

The Border Transit Times are included in the PTV Traffic Incidents Feature Layer available for the PTV World City Map 2020.2H with API version 2 on PTV xServer internet. On-premise solutions with PTV World City Map 2020.2H and PTV Europe City Map 2020.2H will get the updated PTV Traffic Incidents by end of next week April, 16th 2020.
You can recognize the transit times by the square-icon, these show a truck and a clock placed above it. Transit times are only available on motorways and main roads in Europe with enough recent data to display estimates.
To avoid detours around transit times, non-passable border crossings for >7.49t will be blocked in PTV Traffic Incidents from now on.
For use cases such as strategic planning, you can use PTV Traffic Incidents and a time span of one week. This takes into account the information of the closed border crossings, but ignore the transit times at the borders.

Even the border transit time information and the border blocking information has not a 100% coverage it improves the PTV xServer use cases with PTV Traffic Incidents a lot.
The closed / blocked border information for trucks >7.49t collected by PTV is only available on the marked points shown in this map on the right.

Configuration for cloud solutions:

  • Activate the Feature Layer Theme PTV_TrafficIncidents in your PTV xMap and PTV xRoute service request.
  • To calculate a route with the border transit times in PTV xRoute service you need to set additionally the time consideration and plan your route. 
  • It is also possible to deactivate / activate the transit times and blocked borders separately (default is activated). Therefore you can deactivate / activate the layers in the country specific parameters. The transit times with rule id “ptvTIx_AS_42” and border blockings with rule id “ptvTIx_AS_53”.
  • For strategic planning, you can use PTV_TrafficIncidents and a time span of one week. This takes into account the information of the closed border crossings, but ignore the transit times at the borders.

PTV xMap request configuration:

"requestProfile": {
   "featureLayerProfile": {
     "themes": [
       {
        "id": "PTV_TrafficIncidents",
        "enabled": "true"
       }
     ]
   }
 }

PTV xRoute request configuration:

{
    "storedProfile": "truck40t",
    "requestProfile": {
      "featureLayerProfile": {
        "themes": [
             {
               "id": "PTV_TrafficIncidents",
               "enabled": true,
               "countrySpecificParameters": [
               {
                "id": "*",
                "rules": [
                   {
                     "id": "ptvTIx_AS_42",
                     "enabled": true
                   },
                   {
                    "id": "ptvTIx_AS_53",
                    "enabled": true
                   }
                ]
              }
            ]
          }
        ]
      }
    },
    "waypoints": [
      {
        "$type": "OffRoadWaypoint",
        "location": {
          "offRoadCoordinate": {
            "x": 7.552546425579699,
            "y": 47.64452813831258
          }
        }
      },
      {
        "$type": "OffRoadWaypoint",
        "location": {
          "offRoadCoordinate": {
            "x": 7.78418857855105,
            "y": 47.47614532115144
          }
        }
      }
    ],
    "resultFields": {
      "polyline": true
    },
    "routeOptions": {
      "timeConsideration": {
        "$type": "ExactTimeConsiderationAtStart",
        "referenceTime": "2020-04-08T12:01:59+02:00"
      }
    }
  }

Important information about quality and availability
This started as an impromptu project at Sixfold because they “want to do good”. Sixfold have refrained for now to put a license on the data, because they want to focus their efforts on helping and not commercializing this.
Therefore the use of the data in our PTV Traffic Incidents is for free. Sixfold and we at PTV did develop this at a pretty rapid pace, therefore please do not expect 100% uptime, reliability, stability etc.
However, the border transit time information and the border blocking information has not a 100% coverage, we decided to integrate the Sixfold data because it best reflects the current situation.

If you need further information or support please contact the PTV xServer 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

Toll Update (2020_03) France

France

This scenario contains the current toll charges, i.e. mainly the motorway network on the basis of the last available tariffs from ASFA dated Feb. 2020.

PTV xServer internet will be updated on Wednesday, March 25th 2020.

Concerned maps

  • PTV Europe City Map Premium 2019.2H – toll update version 2019_2H_21
  • PTV Europe City Map Premium 2019.2T – toll update version 2019_2T_11
  • PTV Europe City Map Premium 2020.1H – toll update version 2020_1H_13
  • PTV Europe City Map Premium 2020.1T – toll update version 2020_1T_7
  • PTV Europe City Map Premium 2020.2H – toll update version 2020_2H_2

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.

If you need further information or support please contact the support team.

 

PTV xServer internet update – Update of PTV xServer to API Version 2.16

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

PTV World City Map [Here]- production/test/integration – cluster with API version 2:

  • PTV xServer update from version 2.14 to version 2.16
  • This update includes some changes in time out handling:
    We deactivated the computationTimeout (https://bit.ly/2PZE2gG) for requests.
    This will have the effect that all requests even on long lasting requests will be executed until the computation is finished, or for asynchronous requests until they will be stopped on request of the client.

Please test your application and report any problem immediately.

Toll update (2019_07) Slovenia, Czech Republic and Poland available

Slovenia
This scenario contains the current toll charges on the basis of the last available tariffs valid from 06 February, 2018. Toll charges apply to trucks from a gross vehicle volume of more than 3.5 t. Discounts for vehicles with emission category EURO IV and higher, which are granted for payment by electronic media, are incorporated as well.

Cezech Republic
This scenario contains the current toll charges in Czech Republic on the basis of the last available tariffs, valid from August 2018.

Poland
New tariffs for Via Toll, A2, A4. This scenario replaces the previous ‘Poland 2017’ scenario.

Concerned maps

  • PTV Europe City Map Premium 2019.1T – toll update version 2019_2T_2
  • PTV Europe City Map Premium 2019.2H – toll update version 2019_2H_8
  • PTV Europe City Map Premium 2019.1T – toll update version 2019_1T_10
  • PTV Europe City Map Premium 2019.1H – toll update version 2019_1H_11
  • 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 will be updated on July, 31st 2019.

If you need further information or support please contact the Support Team.

 

 

PTV xServer API Version 2.10 is now available!

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