Proposal for an algorithm to guide around unexpected road closures
-
In my opinion, this function would be very useful also in such cases:
- The HERE map is not up to date and the selected road is not accessible for motorbikes in reality (often in cities, mountains, etc.), so I have to find a quick detour.
- The road is not blocked, but the surface condition is not acceptable to me (there is some sand or mud, for example), so I decide to turn back.
-
All very valid, but the common denominator is that you usually do not know in advance for how long you need to block the road. Maybe a more sensible idea is to be able to tap on the map where you want to try to rejoin the route, avoiding the route until that point is reached. Much like already exist while navigating tracks. You can already choose your own point to skip to by long-pressing any point on the track. You just cannot avoid the track being part of the detour.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Check out RideSleepRepeat.eu, a biker community for sharing stays across Europe
-
All very valid, but the common denominator is that you usually do not know in advance for how long you need to block the road. Maybe a more sensible idea is to be able to tap on the map where you want to try to rejoin the route, avoiding the route until that point is reached. Much like already exist while navigating tracks. You can already choose your own point to skip to by long-pressing any point on the track. You just cannot avoid the track being part of the detour.
Hi Con,
Thanks for your post.
Actually, I didn’t want to write anything more on this topic. But now, just a quick note.
Of course, you don’t know how long the road closure ahead of you will be in advance. Now there are two scenarios.
1: The estimated length of the closure (e.g., 10 km) is sufficient. Then the biker reaches the originally planned route and can continue toward the destination.
2: The estimated length of the closure is too short and insufficient. In that case, the biker ends up facing the closed route again and must repeat the detour process. This may continue until he reaches the open originally planned route.
Therefore the uncertainty of the estimation of the length of a closure is no problem in practice.
In any case, skipping via-points on the detoured planned route must be taken into account. Shaping-points can be skipped automatically.
By the way: adding new shaping points by klicking and holding a point on the map during navigation doesn't work on my mobile phone. I tried this several times. Probably I'm doing something wrong.
BMW R 1200 RT
BMW C 650 GT
Tourenorientiert
MRA lifetime member -
Hi Con,
Thanks for your post.
Actually, I didn’t want to write anything more on this topic. But now, just a quick note.
Of course, you don’t know how long the road closure ahead of you will be in advance. Now there are two scenarios.
1: The estimated length of the closure (e.g., 10 km) is sufficient. Then the biker reaches the originally planned route and can continue toward the destination.
2: The estimated length of the closure is too short and insufficient. In that case, the biker ends up facing the closed route again and must repeat the detour process. This may continue until he reaches the open originally planned route.
Therefore the uncertainty of the estimation of the length of a closure is no problem in practice.
In any case, skipping via-points on the detoured planned route must be taken into account. Shaping-points can be skipped automatically.
By the way: adding new shaping points by klicking and holding a point on the map during navigation doesn't work on my mobile phone. I tried this several times. Probably I'm doing something wrong.
@Axel-Härtl said in Proposal for an algorithm to guide around unexpected road closures:
In any case, skipping via-points on the detoured planned route must be taken into account. Shaping-points can be skipped automatically.
Yes, that exactly why I mention my oher view on the matter. If you choose your own point of re-entry, VIA points are no longer an issue, since you can choose a point behind it.
I think what you and I propose is quite similar, but instead of giving a number for the distance in kilometers, of which you cannot see where that ends, you can choose a logical point of re-entry yourself, using an already existing feature. Only thing that needs a change is being able to avoid the use of the originally calculated route (white line) until that point.
@Axel-Härtl said in Proposal for an algorithm to guide around unexpected road closures:
By the way: adding new shaping points by klicking and holding a point on the map during navigation doesn't work on my mobile phone. I tried this several times. Probably I'm doing something wrong.
I don't think you are doing anything wrong, I think you are navigating a track (or route-as-track feature enabled). When you navigate a common route, you can add route points, you cannot add route points to a track.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Check out RideSleepRepeat.eu, a biker community for sharing stays across Europe
-
@Axel-Härtl said in Proposal for an algorithm to guide around unexpected road closures:
In any case, skipping via-points on the detoured planned route must be taken into account. Shaping-points can be skipped automatically.
Yes, that exactly why I mention my oher view on the matter. If you choose your own point of re-entry, VIA points are no longer an issue, since you can choose a point behind it.
I think what you and I propose is quite similar, but instead of giving a number for the distance in kilometers, of which you cannot see where that ends, you can choose a logical point of re-entry yourself, using an already existing feature. Only thing that needs a change is being able to avoid the use of the originally calculated route (white line) until that point.
@Axel-Härtl said in Proposal for an algorithm to guide around unexpected road closures:
By the way: adding new shaping points by klicking and holding a point on the map during navigation doesn't work on my mobile phone. I tried this several times. Probably I'm doing something wrong.
I don't think you are doing anything wrong, I think you are navigating a track (or route-as-track feature enabled). When you navigate a common route, you can add route points, you cannot add route points to a track.
Hi Con,
Thanks for your message.
Question: If I select an entry point beyond a via-point - does MRA skip that via-point automatically? I always thought, that in contrary to a shaping-point, a via-point is forced to be reached or to manually skip it.
I navigate using routes, not tracks. Being a long-time MRA fellow, I'm aware of the difference.
While navigating, the screen doesn’t respond when I tap and hold a point on the map. I have to stop the navigation (or at least pause it). Only then can I add more points to the route. Is that the correct and intended process?
Best, Axel
BMW R 1200 RT
BMW C 650 GT
Tourenorientiert
MRA lifetime member -
Hi Con,
Thanks for your message.
Question: If I select an entry point beyond a via-point - does MRA skip that via-point automatically? I always thought, that in contrary to a shaping-point, a via-point is forced to be reached or to manually skip it.
I navigate using routes, not tracks. Being a long-time MRA fellow, I'm aware of the difference.
While navigating, the screen doesn’t respond when I tap and hold a point on the map. I have to stop the navigation (or at least pause it). Only then can I add more points to the route. Is that the correct and intended process?
Best, Axel
@Axel-Härtl said in Proposal for an algorithm to guide around unexpected road closures:
I always thought, that in contrary to a shaping-point, a via-point is forced to be reached or to manually skip it.
Sure, but choosing a point beyond it equals manually skipping it. Same as in a route, when you are at say RP 10, and you manually set 15 as skip to route point. The VIAs in between are also skipped.
@Axel-Härtl said in Proposal for an algorithm to guide around unexpected road closures:
have to stop the navigation (or at least pause it). Only then can I add more points to the route. Is that the correct and intended process?
Hmm, I tried this to be sure, but my Android lets me press and hold for extra route points while navigating a (real) route. Just when you press exactly on the route line, it does not do anything. No need to place a route point there, since it is already going there I guess.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Check out RideSleepRepeat.eu, a biker community for sharing stays across Europe
-
@Axel-Härtl said in Proposal for an algorithm to guide around unexpected road closures:
I always thought, that in contrary to a shaping-point, a via-point is forced to be reached or to manually skip it.
Sure, but choosing a point beyond it equals manually skipping it. Same as in a route, when you are at say RP 10, and you manually set 15 as skip to route point. The VIAs in between are also skipped.
@Axel-Härtl said in Proposal for an algorithm to guide around unexpected road closures:
have to stop the navigation (or at least pause it). Only then can I add more points to the route. Is that the correct and intended process?
Hmm, I tried this to be sure, but my Android lets me press and hold for extra route points while navigating a (real) route. Just when you press exactly on the route line, it does not do anything. No need to place a route point there, since it is already going there I guess.
-
I’m trying to understand the suggested solution by tapping a point beyond the road closure.
Wouldn’t the algorithm still try to guide me to the new route point via the closed exit, as that would be the quickest way there?
Furthermore, I do not consider this practical, as you are not allowed to stop at the closed motorway exit just to set a new route point on the small display.
In my opinion, there should be a prominent button that tells the algorithm that the exit you have just passed cannot be used and that a route to the planned destination beyond the closure must be found.
-
I’m trying to understand the suggested solution by tapping a point beyond the road closure.
Wouldn’t the algorithm still try to guide me to the new route point via the closed exit, as that would be the quickest way there?
Furthermore, I do not consider this practical, as you are not allowed to stop at the closed motorway exit just to set a new route point on the small display.
In my opinion, there should be a prominent button that tells the algorithm that the exit you have just passed cannot be used and that a route to the planned destination beyond the closure must be found.
Exactly my opinion.
-
I’m trying to understand the suggested solution by tapping a point beyond the road closure.
Wouldn’t the algorithm still try to guide me to the new route point via the closed exit, as that would be the quickest way there?
Furthermore, I do not consider this practical, as you are not allowed to stop at the closed motorway exit just to set a new route point on the small display.
In my opinion, there should be a prominent button that tells the algorithm that the exit you have just passed cannot be used and that a route to the planned destination beyond the closure must be found.
@BMWBiker58, And it should guess which point that is I suppose?
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Check out RideSleepRepeat.eu, a biker community for sharing stays across Europe
-
I’m trying to understand the suggested solution by tapping a point beyond the road closure.
Wouldn’t the algorithm still try to guide me to the new route point via the closed exit, as that would be the quickest way there?
Furthermore, I do not consider this practical, as you are not allowed to stop at the closed motorway exit just to set a new route point on the small display.
In my opinion, there should be a prominent button that tells the algorithm that the exit you have just passed cannot be used and that a route to the planned destination beyond the closure must be found.
@BMWBiker58 said in Proposal for an algorithm to guide around unexpected road closures:
Wouldn’t the algorithm still try to guide me to the new route point via the closed exit, as that would be the quickest way there?
Let’s say the exit is closed and you can’t take that exit; you’ll have no choice but to carry on driving......
The system would then immediately guide you to the point you selected beyond the closure and then continue along the route as standard.
If, by chance, a point has been set on the exit, this is irrelevant, because by manually selecting a point beyond the closure, you have skipped all the previous ones.Your point that you can’t stop on the motorway is correct… so just carry on driving and take the next exit (there you can stop if necessary and start the process to skip the waypoint).
You don’t need to set a new point on the map either; simply select an existing one after the road closure.
Either press and hold the next expected waypoint in the top right-hand corner of the display; this will take you to the next waypoint, and you can repeat this several times.
Alternatively, in the waypoint list, tap a point on the route after the roadworks, and it will navigate you there.
Option 3: Select a existing point on the route on the map after the road closure, and it will navigate you there.
In all 3 cases, the preceding points are skipped.
Personally, I’ve treated myself to the SilverFox C1 Bluetooth controller, which allows me to zoom, skip waypoints and do much more without having to stop.
Find out more on the MRA support page -
Thank you for explaining the options.
My concern (or lack of knowledge), however, is that the algorithm will try again to reach the newly selected next route point via the closed exit. Simply because the route through the closure is the shortest/quickest.
In that case, it would be pointless whether you chose the first, second, third, etc. route point beyond the closure.
In my opinion, there ought to be a way to block the closed exit with a single tap, so that the system doesn’t keep trying to reach the next route points via that exit.
-
@BMWBiker58, And it should guess which point that is I suppose?
@Con-Hennekens The app could simply head for the next waypoint after the roadblock. However, it must not do so via the blocked exit, but must find its own route.
If the next waypoint after the roadblock is also inaccessible, it would simply have to take the one after that. -
Thank you for explaining the options.
My concern (or lack of knowledge), however, is that the algorithm will try again to reach the newly selected next route point via the closed exit. Simply because the route through the closure is the shortest/quickest.
In that case, it would be pointless whether you chose the first, second, third, etc. route point beyond the closure.
In my opinion, there ought to be a way to block the closed exit with a single tap, so that the system doesn’t keep trying to reach the next route points via that exit.
@BMWBiker58 Provided your route doesn’t wind its way around the closed motorway exit like a snail, I don’t see any danger here.
As already described, the app will guide you to the selected waypoint, and it doesn’t matter whether that’s a shaping or a Via point.
In your example, you couldn’t leave the motorway at the closed exit... as soon as you selected the next exit and left the motorway, you’ll be guided to the new selected point, possibly just outside the motorway, passing close to your closed exit, but of course only if your destination is near the closed exit.
If your destination is not next to the closed exit, you will not be guided there.
To be absolutely sure that you are not guided back, please skip one or two more waypoints than might be necessary.
The app will definitely not navigate you to the closed exit...
It is understandable that you would want to inform the app that this exit is closed, but it is absolutely not necessary.
