Here Maps not Recognizing Road is now Open

[Brian McG]

@John-S-Parry "Offline" mode refers to navigating with the MRA mobile app so it does not apply to your use case

In my previous post you can see that using TomTom & OpenStreetMap as the routing options they clearly route along the road between Cedar Springs & Big Pines
If I export those routes as GPX1.1 they will be GPX files containing those routes & tracks following that path

When you import them into the Zumo & depending on your settings it may re-calculate the route so it detours away from the CA-2 but if you selcect the track it should follow the path from Cedar Springs to Big Pines

[K De Weerd]

I tested @Brian-McG's suggestion of exporting the track using the OSM map and he's correct, as can be seen here:
https://www.gpsvisualizer.com/display/map/20250902125300-05119-map.html

The red line is the track, the blue line is the route (or rather routing points) that have been exported. Using the Track, the XT should calculate the correct route on its own.

This however does NOT work if you set one of the shaping points to off-road.
When exporting, it appears that in the background the route is calculated, ignoring the 'Skip' setting of the waypoint. If I set the 4th shaping point to skip, it draws a straight line in the routing, but when I export it using the OSM-maps, I still get a nicely routed track (which in some cases is not what you cant)

[John S Parry]

@Brian-McG Garmin GPS devices always recalculate when imported. Always. There is no way to turn that off. I intentionally turn off all GPS avoidance settings so that the Garmin calculation algorithms won't be influenced beyond my waypoints.

I don't know what we're doing different. If I create a new named route to start and immediately go into the OSM and/or TomTom layer, I can't create a route anywhere along the closure. The web MRA Routeplanner simply won't don't it.

I normally don't deal with tracks in my routing. I create routes with an abundance of waypoints to ensure directional behavior. In the case of using the MRA skip function, the track created along the closed section gets recalculated into the rest of the route.

How you're getting OSM to route the closed section is still a mystery to me.

[Brian McG]

@John-S-Parry the routing calculations in MRA are controlled in this drop down

The map layers are just graphic overlays they just show you where the roads are, they are not responsible for calculating the routing, it is irrelavant what Map Layer you use, they just make the screen look nice

[John S Parry]

@Brian-McG We have a block between each other that I don't know how to reconcile. The "skip" function works for my purposes. I'm OK at this point.

[Adrian Avram]

@Brian-McG said in Here Maps not Recognizing Road is now Open:

with Here each edit is reviewed before acceptance

As I said .... With HERE, I reported an issue more than one year ago, and nothing changed ...
Nowadays you can check on Google Maps that a new street was built, if I add it to HERE, but nobody cares even to check and one years passes ?
So I will stick to supporting and editing on OpenStreetMap !

[Con Hennekens]

@Adrian-Avram said in Here Maps not Recognizing Road is now Open:

So I will stick to supporting and editing on OpenStreetMap !

Totally fine, but not helpful for MRA Navigation.
I have heard much quicker acceptance of feedback from HERE too, by the way.

[Adrian Avram]

@Con-Hennekens well what can I say ... I tried, but its useless unless they will leave people to change the map and improve it. Here map is much limited than OSM map unfortunately ...

[Con Hennekens]

@Adrian-Avram, I understand what you are saying, but MRA Navigation happens to use HERE maps, not OSM.

[Adrian Avram]

@Con-Hennekens yes I know ... unfortunately

[John S Parry]

@Brian-McG I now understand what you did. I missed where you actually changed the calculation map from HERE to OSM. I had in my head that you were simply changing to the OSM overlay on a HERE calculation map.

So yes, that method works. Thanks.