Recalculation of a route

[Bart De Medts]

When deviating from an A to B route, the recalculation does not go so well and the navigation sends me to the original route for a long time, even if there is a logical alternative. I think this is since automatic skipping of waypoints is possible.

[Con Hennekens]

@Bart-DM, There are 2 kinds of A2B routes.

• If you choose the straight line, you are navigating a quickest route, that takes notice of your navigation settings (not allow Highways for example). If you deviate f rom the route, a new quickest route will be calculated, that can be entirely different from the previous one.
• if you choose one of the curvy routes, a route track is calculated and navigated. Deviating from the route wil calculate a way back to the track.

I already suggested a different color of route-line for track-based routes, or another way of indication for track or waypoint based routes. Not sure if it will be picked up.

[Bart De Medts]

@Con-Hennekens Yes I know. I always choose the quickest route with everything allowed. Then, if I deviate from the route, the naviagation tries to send me back to the original route for a long time. Much longer than it used to.

[Con Hennekens]

@Bart-DM, Okay, I have not noticed that yet,

[Con Hennekens]

What I did notice today however, was with a curvy route (track) Truus suddenly told me I reached a waypoint... (?)

[Bart De Medts]

@Con-Hennekens Try it, you might experience it too and then there is a bug after all

[Corjan Meijerink]

I can confirm I thought to have had the same experience. Not entirely sure but this confirms my slight suspicion that something is different.

However, the “return to route” algorithm that is used for this is an HERE SDK feature. At most app updates we update the HERE SDK to the newest version meaning that these things can change to (due to HERE changes ik the SDK).

I’ll investigate when I’m back. Thanks for sharing!

[Bart De Medts]

@Corjan-Meijerink Thx!

[tonyS]

@Bart-DM I noticed similar on a 20 mile A2B route, I could travel for ~5 miles off route whilst being repeatedly told to turn round.

[Bob Harvey]

@Corjan-Meijerink said in Recalculation of a route:

HERE SDK feature

Had to go to the dictionary on that one - Software Developer Kit

I am new to MRA, but suffered with BaseCamp for many years. So it is amazing to see the Here maps available to other applications.

I just bought the Gold and Navigation Next because your MRA software is already so much better than what Garmin provides.

[Con Hennekens]

@Bob-Harvey said in Recalculation of a route:

I just bought the Gold and Navigation Next because your MRA software is already so much better than what Garmin provides.

Not really a Beta-thing but I think many of us are here for the same reason!

@Bob-Harvey said in Recalculation of a route:

Software Developer Kit

Yes. An SDK provides tools for developing software that uses specific services. Some features are therefore bound to the limits the SDK provides. It is good to know that some features are the way they are because of those limits. Sometimes a brilliant developer ( ) can think outside the SDK. E.g. the curvy roads are based on OSM and fed to the Here navigation as a track. But often it is very difficult to circumvent limits posed by the SDK. The MRA team is doing an incredible job.

[Bart De Medts]

@Con-Hennekens said in Recalculation of a route:

Sometimes a brilliant developer ( )

Like @Corjan-Meijerink

[Con Hennekens]

@Bart-DM, inkoppertje voor degenen met voorkennis

[Bart De Medts]

@Con-Hennekens exact

[Corjan Meijerink]

Hahaha oh you @Bart-DM @Con-Hennekens

[MarcM]

@Con-Hennekens Same experience !