Route calculation differences (MGI / xServer api v2)

[jerich]

Hello,

we are having some troubles/questions about route calculation.

we are using "HERE" as provider and the problem seems to occur with every of our calculation profiles.
tested with the profiles truck7_49t and truck40t

so, our problem:

we are implementing the PTV xServer into our solution and we are comparing the routes calculated by our implementation (API) and the results of Map&Guide Internet (further reffered as MGI).

the problem we are running into is that the calculation result (distance, toll distance, ...) are different from the once of Map&Guide Internet.

(results with profile truck7_49t)
e.g.: Route Graz - Vienna - overall distance - MGI 193,3 km / API returns 194,45 km
toll distance - MGI 182,74 km / API returns 180,88 km

our question is now: is there a difference in how the routes are calculated by the PTV xServer V2 compared to MGI ?

[Bernd Welter]

Hello Matthias,

the quick answer to this is that MGI uses

• PTV xServer1 with HERE data

and you may differ in various terms:

• Other API version: xServer 2 engine and profiles are simply different. Some xRoute2 parameters aren't available through xRoute1. And the other way round. For example many "malus" values in xRoute1 aren't available in xRoute2. Another example is the handling of violations.
• Other data provider version
• Other dated version (but equal provider): e.g. map version 2023.1H versus 2023.2H
• ...

There's also this alternative thread How to ensure MAP&GUIDE and xServers return equal results?

Please check it. If there are still open questions I'd kindly ask you to add them to that leading thread.

Best regards,
Bernd