Adapt capacity tags for camp sites etc.
#107
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
mbrzakovic
approved these changes
Nov 10, 2021
There was a problem hiding this comment.
The change is reasonable given that capacity tag is indeed ambiguous in these cases.
I observed the wiki-page that is inline with this statement https://wiki.openstreetmap.org/wiki/Key:capacity
source_strings.yaml should be updated, thought I don't consider this a pr blocker (usually this is done via: npm run build)
Additionally, it would be great if wiki pages for new fields could be created, so the field info in iD can link back to appropriate information.
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.
Recently there was an improvement to the capacity tagging for camp sites.
capacitygot replaced bycapacity:caravans,capacity:personsandcapacity:tents. So this PR adapt to that.What do you think?