parking/orientation: update and deprecate key #673
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.
This PR is for next week when the voting was officially concluded.— Update: The proposal was accepted. All related documentation is updated and the manual data migration is on it's way.Following the successful street parking revision proposal https://wiki.openstreetmap.org/wiki/Proposed_features/street_parking_revision#Summary:_What_is_proposed,_changed_and_deprecated? the tag for orientation on separately mapped parking spaces is now just
orientation
.I added duplicated the deprecation rule for
orthogonal
to handle both the old and new key because I was not sure about the order (cardinality) of the rules / if the key deprecation would then in turn still trigger the value deprecation. Having all three should not be an issue I guess.FYI @SupaplexOSM
Update:
fields/parking/orientation.json
right now. Following the tag convention, we should move it tofields/orientation.json
. However, maybe we should move all parking related fields to this folder instead (especiallyfields/parking.json
? I think that would be a good idea so its to see the parking-scope in the preset-jsons.