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

Preset and rendering for boundary=protected_area #10176

Open
road-runner-osm opened this issue Mar 27, 2024 · 2 comments
Open

Preset and rendering for boundary=protected_area #10176

road-runner-osm opened this issue Mar 27, 2024 · 2 comments

Comments

@road-runner-osm
Copy link

road-runner-osm commented Mar 27, 2024

Description

boundary=protected_area was introduced to indicate nature conservation areas. It is rendered on Mapnik, but in iD (as in JOSM) it is not defined or displayed by a preset.

The relationship between boundary=protected_area and leisure_nature=reserve is unclear and is also not clear when reading the wiki pages. In practice, both are often used together. Unfortunately the explanations differ also depending on the language of the wiki page. See also https://wiki.openstreetmap.org/wiki/Talk:Tag:leisure%3Dnature_reserve#leisure=nature_reserve_vs._boundary=protected_area

However, if a preset would be created, boundary=protected_area could be better used (for protected areas, as intended). In iD it could be named "Conservation Area" or "Protected Area".

Screenshots

No response

@ZeLonewolf
Copy link

There isn't a strong distinction between these tags. The nature reserve tag is often used with the protected area tag because the protected area tag doesn't render by itself in osm-carto.

@DujaOSM
Copy link

DujaOSM commented Apr 3, 2024

Something weird goes on in Carto: this protected_area (without leisure=nature_reserve) is rendered just fine, while this one is not. The former is just a closed way and the latter a relation, but I don't think this matters. (There are a few other invalid multipolygons in that area, which may affect rendering of so large entity).

iD currently supports boundary=protected_area as a subtype of boundary relation, but it does not have a preset for closed ways. I would argue that protected areas are better off that way, i.e. only as relations, but the practice (and Wiki) says otherwise.

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

No branches or pull requests

3 participants