We just released an update on the Kurviger website that makes it a lot easier to check closed roads. In addition to the raw OSM data, we also show you a textual representation of the closure so it’s easier to understand when you can use the road.
Tested this new feature and looks good 
1 Like
In general I think this is a real improvement. However, I’m desperately missing an option to avoid such a section or road already at planning time. Instead of inserting shaping points to avoid the section it would be much more convenient to just put a blocker on the particular section. This would also give the router more freedom to calculate a different, more attractive route.
It would be great if you could add such an option to the pop up menu at right mouse click. Thanks!
thanks and I fully agree, does not make much sense calculating a route which includes closed roads.
Those are time restrictions and how are you or Kurviger supposed to know when you want to go that way?
1 Like
Than offer an option to prevent the road blocks and the roads blocks with time restrictions, so make 2 routes, one with the detour and one without. Ofcourse I do not expect Kurviger to know when I want to go that way.
Closed road are taken into account by Kurviger, if the data in OSM are entered correctly. Temporary closures are displayed in the route and I think you can then see for yourself why the area is red on the route.
2 Likes
Sure, but that’s not my point. Planning a route on Wednesday for a tour on Sunday while knowing about roads which are closed for motorbikes on Sunday is currently not supported. Therefore I was just asking for an option to block certain roads or sections manually.
Besides conditionally closed roads there might be other reasons why you would like to avoid certain roads such as bad surface, temporary construction work or frequent congestion.
In OsmAnd you can maintain your own list of blocked roads which works pretty good for me.
That what the potentially closed roads are for, you can check the closures on your route with that feature.
Yes, that is something we want to implement for a long time now 
1 Like
Oh, but it does! 
And this is how I found this discussion, as I’m annoyed by the fact that I can’t make my long route in the winter (4000+ km), when I have the time, and follow it on the summer.
Why this feature can’t be toggled or add an additional option, “departure at”?
Of course you can plan your tour in winter and ride in summer.
Potentially closed does not mean you can’t ride there. The road might be closed for specific hours of a day.
You need to check yourself if you are affected by this closure, that can’t be easily automated.
Kurviger gives you a hint why a road might be closed.
2 Likes
Are there any updates available regarding this topic? I’m desperately waiting for the option to block a road / section, already when planning a route but also during navigation e.g. because of a sudden road blocks due to construction work. Would be great of you could give this feature a priority! Thanks!
Unfortunately no. This is still high on our todo list and we will look into improving this.
Any updates on this topic?
I already gave my opinion partially in another thread (B87 Vollsperre - #5 by t00thl355), but this appears to be the right place.
For me, there are (at least) two cases that can be handled differently:
-
Reactive: when I press “Navigate” (or “export”) and one or more conditional road closures are active (or could be active soon), the user should be asked, if the route should be recalculated avoiding the road closures. This would help in ad-hoc situations, where you do not have time to do a detailed review and would not like to waste more time ending up on a closed road.
-
Preventive: if the route is planned days/weeks/months in advance, for each road closure, the user should be able to select checkboxes “ignore” or “avoid” and the route should be planned accordingly. This would help to avoid distraction by closures where you can decide in advance if they will affect you or not. A different solution with a similar effect (proposed above) would be if the user could enter the intended starting date and time for a route. Then the active closures could be removed automatically.
No, sorry.
Yes, something like this would be possible.
While I agree that this would be nice, this is an extremely difficult to solve topic.
I thought the “preventive” case would be more challenging to implement, but ok.
What is the the actual problem with “reactive” case ? Is it evaluating automatically if the conditions are fulfilled because of data inconsistencies in OSM?
If so, maybe an alternative would be possible. Let’s assume, you found a way to implement the “preventive” case (e.g., by adding two checkboxes (ignore/avoid) in the text-box where the information about the closure is displayed.
At the time when the user clicks on “Navigate” or “Export”, the app already has the list of all conditional road closures. Then, it might be possible to prompt the user like this:
“The planned route contains x conditional road closures. How to proceed?”
- Ignore all
- Avoid all
- Let me choose"
If the user choses to ignore or avoid all, you just blindly mark them accordingly in background like you would do in “preventive case”. Then recalculate the route and proceed to navigation or export.
In case of “let me choose”, the user is “teleported” to the dialog with checkboxes that is used for “preventive” case.
Whichever way the selection is made in this dialog, it remains stored and is handled in the same manner like the data selected in “preventive” case.
Yeah, so some conditions are very hard to evaluate automatically. My favorite example is a road that is closed when a certain football club is playing their home stadium. But there are many other cases like roads that are closed when it snows or many other conditions.
Things get more complicated, so now you have a route that takes longer than 24hours. A road might be closed today but not tomorrw. When will you reach that road? Should Kurviger tell you to wait for an hour until the road can be used.
That is only a quick overview, the devil is in the details here 
.
1 Like
During a ride over the weekend I was again bothered by conditionally closed roads. I understand that an automatic evaluation of the criteria is difficult. However, the simple option to avoid a certain road or section would already be sufficient.
A feature like “Avoid Road” could also be used in other cases and only for conditionally closed roads. I think everyone has roads he does not like for whatever reasons. Possible reasons could be bad surface, high risk of congestion, speed limits and whatsoever…
Due to this missing feature navigation with kurviger is sometimes useless for me. Circumventing roads which are e.g. not allowed for motorcycles on Sundays by setting shaping points is far to complicated and counters the benefits of kurviger’s routing algorithm. Therefore, I’m still desperately waiting for an “Avoid Road” feature to be implemented. Thanks!
1 Like
Yes, this is already on our todo list .