Why Won't MRA Follow the Beartooth Highway

[LennyO]

@Nick-Carthew Nick, that's interesting...
As soon as I saw the post come out, I tried to create the same route and it would not let me. I started adding waypoints and found 2 spots where it wanted to create a bypass. (WP6-WP7 and WP8-WP9)
One of the roads to be used as a bypass was seen as blocked by the gate on Street View (WP8-WP9).
I did not disable seasonal closures, of course and no avoidances selected.
I also searched the Internet and was not able to find any closures posted anywhere.

TomTom and OSM Navigate straight thru the bypasses on HERE.

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

So, I wonder what made you able to do ut without a problem...???
You must have this thing in total submission to you!

I noticed that you did your route on the phone, so I thought hmmm... maybe that's where it is somehow different. So, I just tried my phone and encountered the same issue as on the Route Planner.

[Brian McG]

Hi @Lenny-O it is not magic, it is just old / out of date map data
I think the Here map data that MRA is using for this road still has its winter setting, so it set as closed

if you try to route along this road it will always try & look for an alternative that is not set as closed
at your points WP6-WP7 and WP8-WP9 there are alternatives, even if they are not practical because of gates etc, & the Here routing opts for the alternative that is not closed rather than the closed road

you can make it route along the closed road between WP6-WP7 and WP8-WP9 just by adding additional points

[LennyO]

@Brian-McG You are correct!
I was able to force it to go straight thru by adding waypoints!

But that brings in another interesting point.

I know for sure that when HERE knows some road as "closed", there is no way you can force it to use it, no matter how many waypoints you try and add, unless you activate "disable seasonal closures".
So, the fact that by adding more points I am able to force it to stay on tells me that these spots are NOT designated as "closed" on HERE maps.

Then, in this example Bear Tooth is the main road and with no avoidances selected why in the world would the HERE algorythm start taking you off the main road?
What am I missing here?

[Brian McG]

@Lenny-O-R-Xpert I think it depends on how the closure is set in the map data
sometimes a closure can be set as a single point on the road like a waypoint, other times it can be set as hundreds of points more similar to a track

the routing algorithms are not that clever, it is just a case of is this path greater than or equal to the alternative path

if a closure is set as a single point you can fool the algorithm into routing through the closure by placing your waypoints near/close to the single closure point so the calculation becomes approximately equal to or shorter than the alternative path

if the closure is set like a track you would need to add hundreds of waypoints to overcome each & all of the closure points

another way to confirm if a route is actually passable & prove that the Here map data is poor/bad is to turn on the "Traffic" data & zoom close in, you get a nice green confirmation that the route is open / flowing

[John S Parry]

@Lenny-O-R-Xpert Lenny, I think it's simply a difference between how the respective MRA HERE and other base maps calculate the route. HERE has a preference for calculating across a more major route when available. You can see the same bias in a calculated route crossing the Southern Sierra in California:

Adding additional shaping points gets you the desired results:

In general, it's always best practice to overload shaping points in more rural areas. Especially if the route is going to be exported to a Garmin device that has completely different calculation algorithms.

[LennyO]

@Brian-McG So, assuming that you are correct about how HERE works their maps (I, personally have no idea about that) it's safe to say that the HERE somehow screwed up and we are at the mercy
of their work "under the hood" in designating closures and being up to date, making them not 100% reliable.
That's pretty sad, considering that it is our preferred MRA engine.

[LennyO]

@John-S-Parry Yes, you are correct! I am totally aware of that.

[John S Parry]

@LennyO OK, so do you still believe your previous statement that "HERE somehow screwed up and we are at the mercy"?

If the MRA version of HERE, in many cases, has a different routing algorithm than OSM/TomTom that simply favors more major roads, where is the screw up? I'm asking from the position of understand/learning.

[Brian McG]

@LennyO no Here have not screwed up the world is round & we are all ok

the only issue here is that the map data that MRA is using for the Beartooth Highway is a little bit out of date
the Beartooth highway normally has a closure for the winter & this closure is in the set of map data that MRA is currently using in the planner & app

it is the nature of maps & has been since they were invented, as soon as they are printed they are out of date
I believe MRA takes a snapshot of the Here map data every time they do an MRA update
occasionally you will get cases like this where the map data is a little bit behind & this is why the "Disable Seasonal Closure" option is part of the toolkit

[LennyO]

@Brian-McG That makes sense, absolutely!
So then, HERE-MRA map updates communication should be improved!
I know from some of the previous discussions that HERE is not the fastest to deal with and we all are sort of at their mercy.
I am sure the mothership reads this and will correct the situation!

[John S Parry]

@lennyo It's too much of a diversion to address in this thread, but HERE is HERE. Their maps traditionally have issues with timeliness of updates, accurate road closure information, and even accurately placing roads where they actually should be. It's a simple reality that the MRA developers have to deal with, and that they are forced to deflect from in the various forums.

I mostly use MRA Routeplanner to create routes for GPX export into my Garmin devices. I've given up using HERE as the base map (for the above reasons) and use OSM instead. I've created dozens of critical routes used OSM as the base, and they import correctly into Garmin devices without issue. I'm comfortable that OSM a 100% GPX export solution, and I don't hesitate to use it.

Unfortunately, using NN requires development on the HERE map. It's one of life's inconveniences you'll have to work around. There are many creative (but awkward) solutions that have been presented in the forums for moving forward in most scenarios.

[LennyO]

@John-S-Parry i agree.