Different route calculations between Java-API and Map&Guide
Posted: Wed Apr 18, 2018 9:30 am
Hallo,
I am facing a problem in route calculation. The use case is: calculate the route from D-49401 Damme to D-73431 Aalen.
First I calculated a route in PTV Map&Guide Internet using only default values:
- optimization: 50%
- use truck restriction = yes
- speed profile "RF LKW (truck_02-00)"
- route options all zero (only ferries 100, no trains)
- truck: lenght: 16.5, width: 2.55, height: 4, axles: 5, weight per axle: 11.5, total weight: 40000
Using this options PTV Map&Guide Internet calculates a route of 522 km with travel time 8h 27min.
When calculating with the same options using the Java API I get 554 km and a travel time of 8h 4min.
The first difference is at the start of the route. Map&Guide Internet travels directly down from Damme to Bohmte not using the highway A1. The Java-API goes directly to highway A1. Why is there such a difference in the route calculation and what could be the difference in the settings?
After setting the optimization to 40% also the Java-API calculates the first part of the route from Damme to Bohmte. But the Java-API then avoids to travel through cities. while Map&Guide Internet uses cities... What could be the cause of the different calculation of the routes?
Thanks in advance!
Best Regards,
Florian
I am facing a problem in route calculation. The use case is: calculate the route from D-49401 Damme to D-73431 Aalen.
First I calculated a route in PTV Map&Guide Internet using only default values:
- optimization: 50%
- use truck restriction = yes
- speed profile "RF LKW (truck_02-00)"
- route options all zero (only ferries 100, no trains)
- truck: lenght: 16.5, width: 2.55, height: 4, axles: 5, weight per axle: 11.5, total weight: 40000
Using this options PTV Map&Guide Internet calculates a route of 522 km with travel time 8h 27min.
When calculating with the same options using the Java API I get 554 km and a travel time of 8h 4min.
The first difference is at the start of the route. Map&Guide Internet travels directly down from Damme to Bohmte not using the highway A1. The Java-API goes directly to highway A1. Why is there such a difference in the route calculation and what could be the difference in the settings?
After setting the optimization to 40% also the Java-API calculates the first part of the route from Damme to Bohmte. But the Java-API then avoids to travel through cities. while Map&Guide Internet uses cities... What could be the cause of the different calculation of the routes?
Thanks in advance!
Best Regards,
Florian