Route calculation differences (MGI / xServer api v2)
Posted: Wed Jul 12, 2023 12:16 pm
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 ?
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 ?