-
Notifications
You must be signed in to change notification settings - Fork 171
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
Add natural=peninsula
preset
#798
Comments
Note the already controversial/problematic handling of bays and their name tagging - especially enormous ones. |
@matkoniecz Are you saying we shouldn't add a preset for this? iD already has presets for bays, capes, islands… lots of similar large features. |
Not entirely sure. If I would be then I would suggest either way. Just mentioning that it is one of controversial tagging topics. |
Thanks for pointing that out @matkoniecz .
Another example for similarly large and fuzzy objects might be mountain ranges (e.g. https://www.openstreetmap.org/relation/2698607), which iD still has no dedicated preset for.
iD should have presets also for this kind of objects. The main question would be whether we want to make it searchable or hidden. But whatever we decide, we should consistently use the same for all "similar" presets. IMHO, it's not a big concern that users of iD (& co) would use this preset to create "enormous" objects which might be considered problematic because of their size. |
If anyone manages to create one of the controversial monstrosities using iD, preset or no, they should win a prize. |
OSM Tag(s)
natural=peninsula
How would you like this tag to see supported?
As a Preset
Label
Peninsula
Aliases
No response
Terms
No response
Link to OSM Wiki page
https://wiki.openstreetmap.org/wiki/Tag:natural=peninsula
Status of the Tag
Approved
Usage of the tag
1600
Replaces other Tag?
No response
Regional Tag?
No response
Further Information
While there are relatively few uses, the tag is used for some large and important features (e.g. the Arabian Peninsula).
The text was updated successfully, but these errors were encountered: