Render lcn routes tagged on ways directly #430
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
LCN routes are often tagged with a simple lcn=yes tag on the ways, rather than with route relations, especially because they often aren't numbered/named.
lcn='s second-most-common value is 'proposed', which presumably means the same thing as state=proposed on a relation-based LCN route.
brainwad
changed the title
Don't render the negative tagging of lcn on ways.
|
Hi! Sorry, this one slipped out of my focus. Looks good to me, merging! Thanks! |
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.
LCN routes are often tagged with a simple
lcn=tag on the ways, rather than with route relations, especially because they often aren't numbered/named. Other tiers of cycle routes are much-less-often tagged this way, see taginfo: lcn rcn ncn icn.The most common value is
yes, but the next most common isproposed, which should be rendered similarly to relation-based routes withstate=proposed, presumably.