Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

[landcover] Rendering of boundary=protected_area #4249

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Closed

[landcover] Rendering of boundary=protected_area #4249

openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments

Comments

@openstreetmap-trac
Copy link

Reporter: Kozuch
[Submitted to the original trac issue database at 2.42pm, Sunday, 26th February 2012]

Please start to render boundary=protected_area with (protect_id OR protection_class) parameters. The rendering should probably roughly follow the rules originaly written for Kosmos at http://wiki.openstreetmap.org/wiki/Protected_Area_Rendering#Protected_Areas.

@openstreetmap-trac
Copy link
Author

Author: cmuelle8
[Added to the original trac issue at 10.18am, Monday, 26th August 2013]

See also #3102.

Taginfo shows it's heavily used:
http://taginfo.openstreetmap.org/tags/?key=boundary&value=protected_area

Please support rendering these and deprecate the often misused boundary=national_park.

Wishlist (just a start into rendering this comprehensive tag):

boundary=protected_area protect_class=2 -> same as national_park now

boundary=protected_area protect_class=4 -> same as leisure=nature_reserve

boundary=protected_area protect_class=5 -> like as leisure=nature_reserve, but using SR (for state reserve) or LR (for landscape reserve) and a lighter green

boundary=protected_area protect_class=12 -> water protection area (blue translucent color, maybe like military areas, but bluish)

@openstreetmap-trac
Copy link
Author

Author: math1985
[Added to the original trac issue at 4.29pm, Monday, 28th July 2014]

This issue is now being discussed on Github: gravitystorm/openstreetmap-carto#789

Therefore, I will close the issue here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant