Handling Dynamic Time-Bounded Restrictions with access:conditional #7224
Unanswered
avanish724
asked this question in
Q&A
Replies: 1 comment
-
@DennisOSRM @TheMarex @daniel-j-h @oxidase Please help 🙏 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am using OSRM v5.27.1 to create a custom routing solution and have encountered a challenge with time-bounded restrictions.
Problem Description
My goal is to restrict access to a road segment only during a specific time window each day.
Tag Used: I've added the access:conditional = no @ (01:30-03:40) tag to a road segment.
My Understanding: As per my understanding that OSRM evaluates this condition at the time of the osrm-extract command. I ran the full build process (extract, partition, customize) while the current time was within this window.
Observed Behavior: The route correctly avoids the restricted road segment. However, after the time window passes (e.g., at 03:45), the route continues to be blocked. The road does not become routable again.
This seems to indicate that the graph has become a static "snapshot" of the road's state at the time of the build
.Discussion
Is this the expected behavior for access:conditional tags? If so, what is the best practice for handling time-based restrictions that change throughout the day (e.g., a rush hour restriction)?
It seems highly inefficient to have to run a full graph rebuild for every time window change (e.g., one graph for 01:30-03:40, another for 03:41-01:29). I've seen some advanced flags and a time-zone file discussed. Can you provide guidance on the correct workflow for using the --parse-conditional-restrictions and --parse-conditionals-from-now flags for a truly dynamic solution?
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions