Confusion about algorithms calculation
-
Hi everyone,
I took a road that I know well and I noticed that the Here algorithm proposed a much longer itinerary without meaning, so using the route planner I created the route by choosing the TomTom algorithm instead of the Here one.
When I rode the motorcycle on that stretch via the MRA nav app, I noticed two things:1- the arrival time at the destination was calculated using the route proposed by here and therefore indicated much longer than the route proposed by TomTom.
But if I had chosen TomTom for planning in the route planner, why was the time calculated on the Here route?2- having arrived at waypoint n.12, the MRA nav app instructed me to follow the Here route towards destination n.15 even though I had chosen the TomTom algorithm in the route planner, because it did not indicate to proceed towards waypoints n.13 and 14?
-
@Corrado-Miniati-0 MRA navigation uses HERE for everything. What map you planned on doesn't matter for that (nor any other navigation system, they'll all use their own built-in map). When navigating using a route, the navigation system will completely ignore the planned route and calculate the full route itself using only the waypoints from your route.
This is why the recommendation is to plan using the map (and settings) your navigation system uses, which for MRA Navigation is always the HERE map.
The reason for the difference is that the SS54 is closed going from South to North between the border and Cave del Predil border according to HERE, while TomTom thinks it's open.
TomTom (with traffic flow and incidents, from plan.tomtom.com)
HERE (with traffic, from wego.here.com)
-
@Herko-ter-Horst
Thank you Herko for the feedback.
However, if you already know the road and you know for sure that that stretch of road is open you can decide to proceed like TomTom, but if that stretch of road is not known then you will have followed Here with many more kilometers and more time than necessary, there is there a solution to this?PS: so what's the point of planning with TomTom or OSM in the route planner if the MRA nav always and only uses Here?
-
@Corrado-Miniati-0 said in Confusion about algorithms calculation:
but if that stretch of road is not known then you will have followed Here with many more kilometers and more time than necessary, there is there a solution to this?
No, there is no solution for this, other then doing what you already seem to know is possible. Follow your own brain
EDIT: Hmm, coming to think about it, there actually IS a solution... You can disable traffic aware routing in the settings - functional menu...
@Corrado-Miniati-0 said in Confusion about algorithms calculation:
so what's the point of planning with TomTom or OSM in the route planner if the MRA nav always and only uses Here?
Some people still use TomToms and of course if you plan routes you might use the TomTom map for making your route also fit for your co-riders who use TomToms.
-
@Con-Hennekens
Ok, thanks Con for your support. -
@Corrado-Miniati-0
From my knowledge on the topic, why does TomTom sometimes have more up-to-date information than Here? -
@Corrado-Miniati-0, I think TomTom would hate it if that secret got out
-
@Con-Hennekens
if it's definitely a secret , it's a shame that Here doesn't want to compete seriously with TT on this theme.
Do you know why Here was chosen instead of TT? -
@Corrado-Miniati-0, No I don't, but what I do know is that HERE is (or was at the time) one of few options that had an SDK for the Flutter IDE. Flutter allows simultaneous development for iOS and Android from within one environment. If you look at the old Navigation "Previous", that was basically two separate apps for iOS and Android.
-
@Corrado-Miniati-0
Thanks so much for the explanation, I didn't know that.
So when planning an itinerary on the route planner do you advise me to always and only use the Here algorithm if you use the MRA nav app on the road? -
@Corrado-Miniati-0 yes, that will make the route in the planner most like it will be in the MRA navigation app.
-
@Herko-ter-Horst
Great, thanks a lot yet.