You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While navigating in a car with Maps.me, I've stumbled upon a conditional turn restriction that was not enforced. I even actually took that in front of a nice policeman : you can imagine the mess :D
Apparently, this is only due to a few flags that should be set up when using OSRM - because OSRM does support conditional turn restriction. It shouldn't be so complicated, as far as I understand.
However, I do not understand the details of the implementation. In particular, I'm curious to know if the condition is enforced at departure time or at the time you're supposed to reach that turn.
Thanks you for your recommendation, but we stoped using OSRM one and half year ago when we implemented traffic jam. We had to do it to be able to change the weight of edges dynamically.
For the time being we don't support any conditional restriction, but probably we'll implement time conditional restriction (including turn conditional) in the future.
While navigating in a car with Maps.me, I've stumbled upon a conditional turn restriction that was not enforced. I even actually took that in front of a nice policeman : you can imagine the mess :D
Apparently, this is only due to a few flags that should be set up when using OSRM - because OSRM does support conditional turn restriction. It shouldn't be so complicated, as far as I understand.
See more details here
Project-OSRM/osrm-backend#4366 (comment)
However, I do not understand the details of the implementation. In particular, I'm curious to know if the condition is enforced at departure time or at the time you're supposed to reach that turn.
danpat has a few words about it, but I'm not sure if it still applies.
Project-OSRM/osrm-backend#3414
I'm sure you can figure it out though, now that you reached that level of expertise with OSRM :)
The text was updated successfully, but these errors were encountered: