add "unknown" as possible value for access fields#316
Closed
matkoniecz wants to merge 1 commit intoopenstreetmap:mainfrom
Closed
add "unknown" as possible value for access fields#316matkoniecz wants to merge 1 commit intoopenstreetmap:mainfrom
matkoniecz wants to merge 1 commit intoopenstreetmap:mainfrom
Conversation
After a conversation at STOM about access keys and the need for unknown to be added as a preset in ID. https://wiki.openstreetmap.org/wiki/Key:access
Member
|
@matkoniecz we should also include the change to the |
Member
|
merged as 0da5e3e |
tyrasd
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
See https://josm.openstreetmap.de/ticket/21705 https://wiki.openstreetmap.org/wiki/Tag:access%3Dunknown
The access conditions are unknown or unclear and indicates that survey is necessary.
For the access key, where users might assume access rights by definition or some default, this makes it explicit that the actual situation is not known (since an absent access tag might also be mistaken by some users as being compliant to an assumed default). These tags should therefore not be removed without replacing them with a better alternative.
For example data consumers typically assume that amenity=parking without access tags is public, and when mapping from aerial imagery some parking will be likely (but not certainly) access restricted, in such cases tagging them unknown would be a good idea.
recreates #196