PTV Group - Logistics Forum

Posted: **Fri Apr 03, 2020 7:37 am**

I very often receive the message below from a customer with „reference data version: 2019.q4 // provider: HERE, data version: 2019.q2" in the log of the xRoute server.

As far as I know, the "ptv_trafficincidents" run via the content update service. In the case of the feature layers, I only specify the map provider here.
With the TOLL updates, I have the option of specifying the version of the map.
Can you tell me what the message below is all about?
Based on the report with q2 / q4, I suspect the quarters and therefore possibly the map version, which is currently EuroCityPrem2020.1H.

2020-04-02 15:21:08,362;WARN;com.ptvag.xserver.module.xroute.m0004;c255f4f3-d196-4c80-a1f5-56d0e4a77360;;;;The layer tomtom_ptv_trafficincidents_ad_2019.q4.flr (reference provider: HERE, reference data version: 2019.q4) of theme PTV_TrafficIncidents does not fit and_d (provider: HERE, data version: 2019.q2) of your map. Please contact your PTV representative to obtain the proper data.
2020-04-02 15:21:08,362;WARN;com.ptvag.xserver.module.xroute.m0004;c255f4f3-d196-4c80-a1f5-56d0e4a77360;;;;The layer tomtom_ptv_trafficincidents_at_2019.q4.flr (reference provider: HERE, reference data version: 2019.q4) of theme PTV_TrafficIncidents does not fit aut_d (provider: HERE, data version: 2019.q2) of your map. Please contact your PTV representative to obtain the proper data.
2020-04-02 15:21:08,362;WARN;com.ptvag.xserver.module.xroute.m0004;c255f4f3-d196-4c80-a1f5-56d0e4a77360;;;;The layer tomtom_ptv_trafficincidents_be_2019.q4.flr (reference provider: HERE, reference data version: 2019.q4) of theme PTV_TrafficIncidents does not fit bel_d (provider: HERE, data version: 2019.q2) of your map. Please contact your PTV representative to obtain the proper data.
2020-04-02 15:21:08,362;WARN;com.ptvag.xserver.module.xroute.m0004;c255f4f3-d196-4c80-a1f5-56d0e4a77360;;;;The layer tomtom_ptv_trafficincidents_ch_2019.q4.flr (reference provider: HERE, reference data version: 2019.q4) of theme PTV_TrafficIncidents does not fit che_d (provider: HERE, data version: 2019.q2) of your map. Please contact your PTV representative to obtain the proper data.

Posted: **Fri Apr 03, 2020 8:33 am**

Forwarded to DEV (XSERS-1745)

Here's the feedback from DEV - please be aware that it deals with current map- and server versions:

Analysis:

We assume that the customer uses the 2020.1H map which is based on the HERE data versiopn 2019.q2.
IN february 2020 we released the 2020.1H map which is based on the HERE data version 2019.q4.
Since march 2020 the TIS (traffic info servers) are providing the traffic incidents for the 2020.2H map.
xServer 1 always requests the latest version of the incidents from the TIS via the CUS (content update service) which is "2019.q4" (at the moment) - you can't configure this.
This is the reason why there's a WARN entry that the "latest map version incident data" does not match the "servers configured map data". It can happen that some of the incidents are not poperly handeled within this context due to illegal references no wrong or non existing IDs.
The bigger the gap between incident version and server's map version is the bigger is the risk of malicious behaviour.
Since xServer 1.22 we document this in the logfiles as INFO and no longer as WARN.

How old is the server?

Solutions:

Perform an update to 2020.2H map
Migrate to xServer2: the content update service 2 recognices it's local client's map version (e.h.2020.1H) and requests the matching feature layer from the TIS.

Best regards,
Bernd

Posted: **Thu Apr 09, 2020 12:35 pm**

Check... tropic was solved 1:1 based on the generic info I collected here:
https://xserver.ptvgroup.com/forum/view ... =43&t=1241

PTV Group - Logistics Forum

PTV_Trafficincidents - The layer tomtom_ptv_trafficincidents

PTV_Trafficincidents - The layer tomtom_ptv_trafficincidents

Re: PTV_Trafficincidents - The layer tomtom_ptv_trafficincid

Re: PTV_Trafficincidents - The layer tomtom_ptv_trafficincid