Thread: iGO route calculation logic

And, in addition, the way calculations and routes differ when map provider changes.
E.g., what is short route for Here could be easy for TT. Only an example, does not have to be exactly this instance.
Using hnr files slightly aligns the situation, but personally I prefer the routing without them. And somehow it's more "natural" with the TT publisher.
But that's just my subjective experience, in "my" part of the world.

It's hard for anyone to answer this question. Only those who created algorithms know it.

And also different programs are calculating different routes with same maps.

iGO Primo Israel, Israel NG, PAL and World calculated different local (city) routes with exact same settings and same (HERE) maps in few specific situations.

Route created with Israel NG seems to me as most logical and optimal, for those situations I tested.
It was not "shorter" but it was using less left-right turns, which is simpler and could save some time.

I use Avic, Pal and Israel, in my situation (TT and region) routes are the same

Well, I think it's even more than 'only' a different routing from app version to app version or map provider to map provider.
Watch this:
[Only registered and activated users can see links. ]

As you see, iGO nextgen on Android is able to calculate a good and smart route BUT it is only provided if you calculate alternatives. So the second route on demand is not only 5 kilometers shorter, it is even 5 minutes faster

So next observation: The routes themselves differs from selected 'maximum speed' in vehicle profile AND so is the sorting of which route is number 1. If I set maximum speed to lowest = 50km/h I get always the second best from screenshot shown as first one. If I set it to highest = 200km/h (no speed limit in my country), everything is totally fu**** up, iGO thinks I will drive 200 all the time and the ETA is 3 minutes for the same route...

I will try it with teleatlas then.

EDIT: Only small changes with teleatlas, the main 'bug' in not showing me the fastest route like above still persist and the strange dependence of vehicle maximum speed too. Also 'correctness=100' or enable/disable histspeed won't change anything.

Yes, I can replicate that behavior on my devices all the time
But 50 km/h is not the best if you plan long routes. And even if we find a best value, which will give us tomtom like navigation (or better), there remains the ETA bug then. iGO uses this value for time of arrival calculation.

Well then you did not test it the right way.
As I told you, set it to 50 km/h and the routes won't use highways, set it to 200 km/h and it won't use city streets. Also the time of arrival is mainly calculated depending on that setting.

Edit: Proof
[Only registered and activated users can see links. ]
Both calculated at the same time at the same location for same destination.

Conclusion: The faster the car/higher the tempo limit in your country (interpretation of 'maximum speed' in your vehicle profile) the slower the routes iGO calculates will be. Takes the 9 km detour to be able to drive fast while being slower at all. This doesn't make sense.