-
Notifications
You must be signed in to change notification settings - Fork 661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Honor access mode while matching OSMRestriction with graph #2849
Conversation
e243bc1
to
935e4b8
Compare
{gurka::way_member, "EF", "from"}, | ||
{gurka::way_member, "FB", "via"}, | ||
{gurka::way_member, "BA", "to"}, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EF
and FG
edges have the same way_id
. So GetGraphIds
return GFBA
instead of EFBA
. We must look at the access mode in my opinion. Let me know if the suggested solution is correct or not: it's the first that came to my mind
I compared the number of restrictions between master and this branch: the PR "removes" some of the restrictions(5-10 restrictions of ~2700). So need more time to investigate it |
see comment here |
0b29351
to
bf5ee6e
Compare
Checked master vs pr diff in restrictions in the Florida. Looks good List of restrictions that are removed due to access flags: The last two restrictions are actually buggy: the via way is incorrect |
3f8f63f
to
10720cd
Compare
Issue
What issue is this PR targeting? If there is no issue that addresses the problem, please open a corresponding issue and link it here.
Tasklist
Requirements / Relations
Link any requirements here. Other pull requests this PR is based on?