erratic routing instructions

[paul69]

afternoon all,

This isn’t a complaint, just some information for others in case anyone experiences something similar.

Route used: https://www.myrouteapp.com/route/open/10218580

I rode the above route on Thursday. The first part of the ride is mostly motorway and dual carriageway, mainly to get away from the city before reaching the more enjoyable winding roads.
While riding on the motorway between points 2 and 3, the app constantly tried to direct me off at every junction, onto an A road, and then back onto the motorway at the next junction. This continued the whole way until I reached point 3. Obviously I ignored the instructions as I knew how to get to point 3.
I had already passed through points 1 and 2 correctly, so there shouldn’t have been any need for the app to reroute me to pass a missed point.
For the first time in a long while, my phone also became extremely hot, and the app crashed several times during both the outward and return journeys. which was the same route in reverse.
I’ve sent the log files to support in the hope it helps identify the issue and possibly improves a future update.

For reference, I’m using an iPhone 12 Pro with a Carpuride CP. I normally use this setup for commuting and single-day rides. For multi-day tours, I use an RT3 rugged tablet with navigation next installed.

offline maps in offline mode

5:2:0 473

[RetiredWingMan]

77 kms is a long way between waypoints. Allows the navigation software an opportunity to select a shorter route. Add a few more waypoints and that will likely solve the issue.

[paul69]

hi @retiredwingman
think you may have misunderstood the post.
I know the way to waypoint 3. the fastest route will always be motorway, hence why I do not need more points.
I was merely pointing out that I was directed off and back on the motorway at every junction.
I have ridden this same route a number of times, it was only on this occasion, interestingly since the latest update, that it behaved like this.

[LE DIZES Freddy]

Hello
Are motorways permitted?

[paul69]

@le-dizes-freddy
yep, but even if they were not permitted, it would not explain the fact of instructing me back on to the motorway.
I could see the route highlighted ahead, on my screen. attempting to take me off then back on.
I am not new to this app, and I would consider myself quite an experienced user, I was just pointing out the behaviour, and as stated above, the same route has been done previously without this issue.
I think it was having a bad day, as my phone got really hot, not done this for a long time, and the app crashed a couple of times later in the ride.

[Marinus van Deudekom]

I would say it's in the settings of your Navigation Next.
Although the route has not that many shaping points that doesn't explain why it tries to get you of the motorway.
That could be the result of the settings in NN.
Could you share your settings

[John S Parry]

It's just a guess, but if could be HERE map behavior. More than once, I've experienced strange things directly attributable to HERE itself. Again, this is just a guess, but something to consider.

[Marinus van Deudekom]

Did you make the route with the webplanner. I see that the route is with the Here map.
Did you by any change made it with the OSM and then later on concerted it to Here.
I know that OSM does tricks like you've explained with motorways.
If you started with OSM you can't het rid of that behaviour

[John S Parry]

@Marinus-van-Deudekom interesting observation on OSM. I do sometimes change the base map from OSM to HERE if I decide I need to execute the route on the phone. I haven't experienced issues, but good to know it's a possibility.

What I have experienced is a route on a long/straight USA interstate (think I-5 in California), where HERE will have me exit and re-enter the freeway for no apparent reason. I had no waypoints that would have triggered the behavior, but it's happened more than once. The response in the past when I've reported it that it's HERE doing it under the covers and MRA has no control over that behavior. That was of course comforting.

My solution over time has been to develop using OSM as the base map, which I've found far more stable/predictable than HERE. It works well most of the time, because I export the GPX and use a Garmin Zumo XT for most of my route executions. This won't work with the app execution since the route must be developed using the HERE map as base. Again, just something to consider.