Update on Layer Delivery Service (LDS) for PTV Content Update Service

featurelayerThe new release of the Layer Delivery Service (LDS) replaces the previous version delivering the Feature Layer Traffic Incidents and Toll updates. The LDS supplys this data via Content Update Service (CUS) into the products automatically. But with the update there is something to take care of:

Please check your Content Update Service (CUS) version. If you use CUS 1.24.0.4 or 2.8 and later there ist nothing to do.
Otherwise please update you CUS to 1.24.0.4 or 2.8 and later.
From this versions on the connection to the LDS will be automatically refreshed.

For all older CUS versions, the CUS has to be restarted manually to refresh the connection to LDS. This has to be done with every LDS update and should only be used as a short term solution until the update to the newer CUS version is done.

The old version of LDS will be disabled on Thursday September 30th 2021. All content update service instances need to be updated or restarted until then or do no longer get Feature Layer Traffic incidents updates.

The CUS Version 2.8 can also be used with PTV xServer API Version 1 when using the PTV CUS xServer1 Adapter.

The PTV Content Update Service 2.8 and the respective PTV CUS xServer1 Adapter can be downloaded from the customer area of the PTV Developer Zone (login required).

For any further information or support please contact the Support Team.

PTV xServer internet update – PTV Europe City Map [TomTom] with API Version 1 – new date

We would like to inform you that rescheduled the update on the PTV Europe City Map [TomTom] production cluster with API Version 1.

The new update slot is on September 28th between 1 pm and 2 pm UTC+2. The following tasks will be completed in the scope of this maintenance:

  • Operating system change from Windows Server to Ubuntu Linux
  • PTV xServer update to version 1.32.
  • Map update from PTV Europe City Map 2021.1T to PTV Europe City Map 2021.2T

With the last update some of the customers had problems with xTour service performance. Please pre-calculate your distance matrices on the already updated test / integration cluster.
This cluster will become the new production cluster on the update date. We will scale up the cluster to production scale and switch the production ULRs to route all production traffic to the new production cluster.

With PTV xServer 1.32 it is possible to enforce High Performance Routing.

Please have in mind that we don´t guarantee the stability of our IP addresses, so please only use the URLs to address our service.

We kindly ask you to please test your application on the provided test system and report any problem immediately.

Detailed Toll Update for Austria

We activated the updated detailed toll layers for Austria, referenced to

                   PTV Europe / World City Map Premium 2021.2H,

on our Layer Delivery Server (LDS). Now, it is possible to download the detailed toll layers via Content Update Service (CUS).

Content: New tariffs for electric vehicles, valid from 1st of September 2021.

 

Using detailed toll on xServer internet and xServer from version 2.22:

The default toll calculation changed to useDetailedToll = true in the xserver.conf. That means that you get the detailed toll automatically, when requesting toll in the route calculation.

 

Information for xServer from version 2.18 to 2.21:

Step 1: Activate the detailed toll download via content update service in you xserver.conf.

core {
     contentupdates {
              content {
                  detailedToll {
                      enabled = true
                      providerNames = [ "here" ]
                      countries = [ ]
                  }
          }
      }
 }

Step 2: Enable the detailed toll calculation in the xserver.conf or in your request.

xroute {
     tollOptions {
     useDetailedToll = true
     }
 }

The detailed toll is released for PTV xServer from version 2.18.  
Please be aware that from version 2.22 the parameter useDetailedToll is activated automatically. If you like to use the basic toll you need to set it to false.

Detailed Toll Update for North America package 6

We activated the updated detailed toll layers for Maryland, New York, South Carolina, Washington and West Virginia referenced to

                   PTV North America / World City Map Premium 2021.2H,

on our Layer Delivery Server (LDS). Now, it is possible to download the detailed toll layers via Content Update Service (CUS).

 

Using detailed toll on xServer internet and xServer from version 2.22:

The default toll calculation changed to useDetailedToll = true in the xserver.conf. That means that you get the detailed toll automatically, when requesting toll in the route calculation.

 

Information for xServer from version 2.18 to 2.21:

Step 1: Activate the detailed toll download via content update service in you xserver.conf.

core {
     contentupdates {
              content {
                  detailedToll {
                      enabled = true
                      providerNames = [ "here" ]
                      countries = [ ]
                  }
          }
      }
 }

Step 2: Enable the detailed toll calculation in the xserver.conf or in your request.

xroute {
     tollOptions {
     useDetailedToll = true
     }
 }

Detailed toll is released for PTV xServer from version 2.18.  
Please be aware that from version 2.22 the parameter useDetailedToll is activated automatically. If you like to use the basic toll you need to set it to false.

PTV xServer internet update – PTV Europe City Map [TomTom] with API Version 1 – new date

We would like to inform you that rescheduled the update on the PTV Europe City Map [TomTom] production cluster with API Version 1.

The new update slot is on September 15th between 10 am and 12 noon UTC+2. The following tasks will be completed in the scope of this maintenance:

  • Operating system change from Windows Server to Ubuntu Linux
  • PTV xServer update to version 1.32.
  • Map update from PTV Europe City Map 2021.1T to PTV Europe City Map 2021.2T

With the last update some of the customers had problems after the switch. Therefor we kindly ask you to please test your application on the provided test system and report any problem immediately.

  • Please have in mind that map updates imply recalculation of distance matrices.
  • Please have in mind that we don´t guarantee the stability of our IP addresses, so please only use the URLs to address our service.
  • If you use the profile snippet with PTV xRoute server, you may have a look at this blog post regarding the reported issues.

PTV xServer internet technical information – Reported issues for PTV Europe City Map [TomTom] with API Version 1

On September 1st 2021 we did the update on the PTV Europe City Map [TomTom] with API Version 1. After the switch to production some customers had problems.

Here are the issues reported and the corresponding solution:

  • There was a report that a customer could no longer connect to the service. After an analysis we found out that he used the IP address instead of URL.
    Please have in mind that we don´t guarantee the stability of our IP addresses, so please only use the URLs to address our service.

  • There was an issue with an error of dataCompatibilityVersion does not match.
    After the analysis of the issue we found out that the error message was misleading. Instead of data compatibility it is a profile schema validation error.

    In our documentation we note that the schema validation for the profile snippet should only be used for development or debugging issues, because of the performance. It is not meant for productive usage, nevertheless it should work like intended.

    Do not use http://localhost:500×0 as schema url since this internal url might or will not work. We documented in our manual that we support the following notation for the schema location:

    <Profile xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:noNamespaceSchemaLocation=

      "../../schema/XRouteProfile.xsd">

      <Common language="de" coordinateFormat="PTV_GEODECIMAL" majorVersion="1" minorVersion="0"/>

    </Profile>

    What also works is the notation like specified in our RawRequestRunner samples:

    <Profile xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:noNamespaceSchemaLocation=\http:///xroute/schema/XRouteProfile.xsd\>   

    We see that is a minor change if you used that differently before. Nevertheless, this is the documented and supported way and should be used accordingly.

 

We kindly ask you to please always test your application on the provided test system and report any problem immediately.