Route made through roadworks and blocked roads

[Metalhead]

@Con-Hennekens this is what I question.
Why does it make a route through a well known roadblock?
Why does it not offer an alternative?
Why does ik keep on trying to get me back to the routepoint I supposedly missed for far longer than 3 attempts.

[Marinus van Deudekom]

The question is if that known roadblock is known at Here. Do you see that roadblock on your map. If not, it’s not known at Here.

[Metalhead]

The road block was visible in the map, the route info said there was a route violation due to the road block and the app kept telling me about the roadblock. The thing it did not do was not plan a route through the roadblock or provide an alternative.

[Benjamin Ralston]

I've experienced this as well. During my long road trip last month there was at least one location where the app stated there was a known route violation road closure, yet it directed me through that violation anyway without offering a detour. I don't know if it would have tried redirecting me back through it, because I manually looked up the best detour route and changed the route to account for it.

[Herman Veldhuizen]

I might be wrong but I think that MRA does this "by design", but only if you navigate a route as track.
The reason behind: Closures are temporary and MRA sort of assumes that by the time you start riding the closure should be gone. If not, follow the signs on the road to guide you around.

But there are 2 reasons why I think this is not how it should be :
1st : MRA cannot know when you start riding and simply cannot make any assumption about whether the closure is gone or not.
2nd : if the road is for example a mountain road then the detour starts long before the closure, there will be no signs for you to follow.

Navigating a route as route might help out here. but honestly I think that mra should reconsider the design too.

[Aiello antonino]

The roadblocks reported aren't always real, sometimes they may already be over, or you can get through on a motorbike but not on a car. It's happened several times, including last week, that MRA reported a roadblock but then in reality there was nothing on the road...

[Herman Veldhuizen]

@Aiello-antonino Sure, but ignoring them (in route-as-track navigation) isn't really solving the issue either.

[Peter Zehentreiter]

@Herman-Veldhuizen I have noticed the following...

When I’m navigating online and Here is aware of a road closure, the app automatically creates a detour to bypass it.

However, when I navigate the exact same route offline, a message does appear to indicate the closure on the route, but the app does not automatically bypass it.

[Herman Veldhuizen]

@Peter-Zehentreiter Road closures come from online information not from the latest map update. Thats why you get different results. Why you in your example still can see that the road is closed, while being offline, is something I dont know. Just guessing: it might be that HERE cashes road closure info (so it downloaded it for you when you were online) or the road in your example is marked as closed in different ways in online and offline map data. The road is closed in both but the app maybe only checks one way and therefore the inconsistency.
In your example you navigate a route as route. If you navigate a route as track the closure (i think) is always ignored and no alternative road is presented to you.

[Peter Zehentreiter]

@Herman-Veldhuizen said:

If you navigate a route as track the closure (i think)

Yes, I agree... a route saved as a track should work like that too.

My point was to show that, using the offline function, you can more or less follow road closures on the Here map as they are (though you should check first whether the closure is actually shown on Here).
Online, you then have the familiar issue of skipping waypoints in roadworks, and so on.