upgrade path for amenity=youth_centre #297
Merged
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.
As promised in #83, here is a follow-up for the upgrade path of deprecated
amenity=youth_centre
->amenity=community_centre
+community_centre=youth_centre
. It looks like another upgrade path was already added in the meantime, but it is not quite correct or at least not consistent with the tagging in #83:community_centre:for
specifies actually rather a property of a community centre/youth centre, whilecommunity_centre
specifies the type of community centre, i.e. is part of what it defines as a map feature. See PR #83I don't know, hypothetical example: There could be a general community centre for bingo-playing and a community centre dedicated to hands-on creating art and music each in a residential complex for old people. Both are for old people, but there are different kinds of community centres. The "for" does not define the type of community centre necessarily and that is why both
community_centre
key exist andcommunity_centre:for
key exist.