Skip to content
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 boundary=protected_area to park layer #760

Closed
zstadler opened this issue Jan 6, 2020 · 1 comment · Fixed by #773
Closed

Add boundary=protected_area to park layer #760

zstadler opened this issue Jan 6, 2020 · 1 comment · Fixed by #773
Milestone

Comments

@zstadler
Copy link
Contributor

zstadler commented Jan 6, 2020

Currently, boundary=protected_area areas are not included in the park layer.

The OSM wiki pages for boundary=national_park and leisure=nature_reserve say under "Similar tags":

boundary=protected_area is a more recently introduced tag with a more verbose tagging scheme which can deal with all kind of protections and protection levels. It attempts to encompass both nature reserves and national parks, and is used more and more.

Back in 2016, @lukasmartinelli said:

In the park layer we would then have leisure=natural_reserve, boundary=national_park and boundary=protected_area.

I have enhanced the park layer to include the missing areas, as this is the OSM mapping standard in my country.

Here is the new description of the class field where an attempt was made to unify the different tagging options:

Use the class to differentiate between different parks.
The class for boundary=protected_area parks is the lower-case of the protection_title value with blanks replaced by _.
national_park is the class of protection_title=National_park and boundary=national_park.
nature_reserve is the class of protection_title=Nature Reserve and leisure=nature_reserve.
The class for other protection_title values is similarly assigned.

I will be happy to share this enhancement using a PR for this issue.

@TomPohys
Copy link
Member

Hello @zstadler, your PR is very welcome. Can be part of v3.12 release.

Connection to #773 and #776

@TomPohys TomPohys added this to the v3.12 milestone Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants