-
Notifications
You must be signed in to change notification settings - Fork 884
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post offices and related items need to be in the brands tree, not the operators tree #5613
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
120 changes: 60 additions & 60 deletions
120
data/operators/amenity/post_depot.json → data/brands/amenity/post_depot.json
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be clear, #5561 (comment) described an edit to the
amenity=post_office
documentation that should’ve had little bearing onamenity=post_box
. Conversely, these features were originally moved from thebrands
tree to theoperators
tree in response to feedback in #4925, but that feedback was aboutamenity=post_box
, notamenity=post_office
.I think the back and forth is because post offices and postboxes are being treated identically. But it seems like the expectation – most of the time – is that post offices need the distinction between brands and operators more than postboxes do. Contract post offices are a widespread phenomenon in many countries, but contract postboxes would be much more of an edge case.
(I did argue in gravitystorm/openstreetmap-carto#1023 that postboxes should be labeled based on their
operator
s, but that was before I learned aboutbrand
and before it had become common on postal facilities in the U.S.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh ok - If I'm reading your comment correctly, it sounds like
amenity/post_box
should remain inoperators
tree? That seems ok to me.