updated private access logic. #1960
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kevinkreiser
previously approved these changes
Oct 15, 2019
|
@dnesbitt61 noted that we should maybe not do this change and see if in fact the tagging is just incorrect at airports. I am going to confirm the maybe the tag should be |
|
checked a few airports. all use |
kevinkreiser
approved these changes
Oct 30, 2019
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
toss way where access=private and highway=service and service != driveway
Issue
Seeing issues where we are routing on roads where access is private. For example, service roads at airports. Logic tosses them if access=private and highway=service and service != driveway.
Before
After
Tasklist
Requirements / Relations
Link any requirements here. Other pull requests this PR is based on?