erratic routing instructions

[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.

[Brian McG]

Hi @paul69 I have tried simulating driving your route multiple times & can't repeat the behaviour your seeing,
in fact I get the exact opposite, at every junction it is telling me to stay ON the m-way or main A-road

My guess is somehow when you started the route MRA glitched & changed a navigation setting in the background so the route was recalculated to do something abnormal
As @marinus-van-deudekom says this effect has been know in the past when someone created a route with the OSM route calculator but we can see in this case you have selected the Here route calculator so it is odd

I think the only way to try & figure out what is occurring is if you can re-ride the route & get a repeat of the issue then save the app log file for the devs
It looks like a decent ride to Hawick so should not be to much of a hard task

[Lenny O]

@Brian-McG That's a nice screen! What device is this?

[Brian McG]

@Lenny-O its an android simulator on PC, not a mobile device

[Marinus van Deudekom]

@Brian-McG hi Brian. Could you share the name of the program on your pc

[paul69]

@Marinus-van-Deudekom said:

Did you make the route with the webplanner. I see that the route is with the Here map.

I always plan my routes on the web planner, and use Here, I do compare with OSM and tom tom while making them. I also use the Michelin overlay as the Here is very wishy washy, and bad contrast.
perhaps I inadvertently changed it, but I do not know why I would do that.

@Brian-McG said:

I think the only way to try & figure out what is occurring is if you can re-ride the route & get a repeat of the issue then save the app log file for the devs

as stated above, I have ridden the route previously (3-4 times) without issue. I have sent the logs.

@Brian-McG said:

in fact I get the exact opposite, at every junction it is telling me to stay ON the m-way or main A-road

when I have ridden the route before, that is what normally happens.

For info to all, I merely put this on here as discussion point, and to highlight the behaviour, although it is good to read the differing points of view.
I am touring around Ireland from Thursday, no motorway to speak of so may not see this again.

@Brian-McG said:

It looks like a decent ride to Hawick so should not be to much of a hard task

it is a very nice route, although the road between Middleton and Alston is very uneven, not great on my K1600, almost throws me out of the seat in places, enjoyed it more when I had the GSA

@marinus-van-deudekom,

@Marinus-van-Deudekom said:

That could be the result of the settings in NN.
Could you share your settings

I use fastest route in optimisation, the rest is below