Another Erratic Routing Incident

[John S Parry]

I was out yesterday putting some miles on my new BMW 1300GSA for break-in. I put together a route in an area I've ridden often.

Here it is: https://www.myrouteapp.com/route/open/13878114

As I approached waypoint #8, I noticed that it was going to have me turn left off the main road to a parallel side road (Calamigos Rd) that wasn't part of my route. below is a screen shot that I stopped and took:

Again, I know the area, and I know this scenic diversion wasn't intentionally part of the route. I ignored the left-hand turn, and the route continued without incident. When I got home, I double checked the route for anything that obviously would have caused this but came up empty on both the route created in Routeplanner and the route synced to my phone. BTW, the route executed online.

Any thoughts would be appreciated.

[RetiredWingMan]

It looks to me like you missed a waypoint and MRA is routing back to the missed waypoint.

[John S Parry]

@RetiredWingMan Interesting. Indeed, it seems to be showing reference to waypoint #7. The problem is that #7 is on the same road (Mulholland Hwy) as #8, and I 100% passed it just a few minutes before. It's a rural area, and even if Dementia due to advanced age is kicking in there is no other road option where #7 could have been missed, which again, I'm positive didn't happen.

The only thing I can speculate is that the terrain for #7 is very twisty/technical, so maybe HERE didn't calculate it correctly. But the waypoint is square on the road, so I don't know what I could have done different. I guess I could delete waypoint#7 and re-ride that segment to verify.....

[John S Parry]

Update: I went back out today to see if I could repeat the behavior related to waypoint#7. I fired up the route and followed it without deviation. Just like I did the first time around.

And I got the exact same result. It's repeatable! MRA/HERE thought I had missed waypoint #7 (I didn't) and I was directed to turn around at Calamigos Rd to return.

In preparation for this expected outcome, I copied the route and moved #7 further up the road (closer to #8) to see if it would change HERE calculation behavior.

https://www.myrouteapp.com/route/open/13885843

I re-ran the modified route, the new #7 calculated correctly, and I reached #8 without incident.

This isn't the first time I've encountered this kind of behavior in MRA -- Both with the Routeplanner (using HERE as the base) and the phone app. I love MRA Routeplanner and will continue to use it with OSM as the base map. It's very stable. Since I mostly use Garmin GPS units for route execution, no problems. As far as the app, I'm out. I can't have this strange HERE behavior mess a route up. Especially when I'm leading a larger group ride. Hopefully, it can be dealt with at some future point.