Opened 9 years ago

Closed 5 years ago

#3102 closed enhancement (duplicate)

[landcover] Unified rendering of protected areas

Reported by: jajcus@… Owned by: mapnik-team@…
Priority: major Milestone:
Component: mapnik Version:
Keywords: protected_area nature_reserve Cc: Olli, R

Description

There are multiple different kinds of protected areas and even more ways to tag them in OSM:

boundary=national_park leisure=nature_reserve boundary=protected_area

The last one, IMHO the best, does not seem rendered at all now (except the name label along the invisible boundary). E.g.: http://www.openstreetmap.org/?lat=50.30635&lon=18.59541&zoom=16&layers=B000FTF

'leisure=nature_reserve' seems wrong to me by definition of 'leisure' and 'nature reserve'. And its rendering had some, already reported problems, too.

I suggest to define rendering rules of 'boundary=protected_area' and apply them to 'boundary=national_park' and 'leisure=nature_reserve', as the special cases, too.

I guess only the boundary and label needs rendering – filling the area may hide other features (probably the protected ones) there.

Change History (5)

comment:1 in reply to:  description Changed 8 years ago by Olli R

Cc: Olli R added
Priority: minormajor

We have have imported protected area data, including national parks, from Finnish authorities to OSM. Where have used boundary=protected_area tagging, because it is very comprehensive and represents different types of protection areas. But Mapnik does not seem to render these areas well, e.g.: http://osm.org/go/1gGgqG4U ,

It would be great, if you could consider implementing rendering as jajcus earlier suggests.

comment:2 Changed 8 years ago by moreton

I support this request. Rendering of national_park boundaries in mapnik seems to require an area=yes tag, but even that does not result in rendering of protected_area boundaries. (osmarender does render national_park boundaries without need for area=yes, but it also fails to render protected-area boundaries). Once over this hurdle, rendering of national_park boundaries is great: distinctive green dashed lines.

Could we please have something similar for protected_area boundaries: perhaps yellow or tan dashed lines?

I suggest that closed ways in these two categories be automatically filled. The ideal fill might be a green mesh for National Parks and a yellow mesh for other Protected Areas. A bit like the current osmarender ‘transparent mesh effect’ used for the leisure:nature reserve tag; but preferably with a different mesh pattern.

Explanation:

  1. Boundaries. National Parks and Protected Areas are very important information for map users, for their combination of ‘responsible recreation’ and conservation uses (and penalties for incorrect use even through ignorance of their existance). Typically these designations by governments indicate different levels of rules for users. For example, in my area of Australia a marine National Park means no fishing whereas a marine Conzervation Park means that certain types of non-commercial fishing are allowed. Maps are very important indicators that these zones are likely to have different types of restrictions (then users can check local rules).
  1. Fill: These are often big areas over other details important to map users, but hard to follow from the boundary alone, so a ‘transparent mesh’ fill works very well. At present, some people are tagging both types of zones with ‘lesiure:nature reserve’ (possibly to get them rendered on default maps). It seems better to fill these two zone types automatically and allow the leisure tag to be used for all kinds of other purposes like private nature reserves.

comment:3 Changed 8 years ago by moreton

On reflection it would be better if closed ways in these two categories were automatically filled if tagged area=yes; that would leave the option for rendering boundary only if appropriate.

comment:4 Changed 5 years ago by math1985

Summary: Unified rendering of protected areas[landcover] Unified rendering of protected areas

comment:5 Changed 5 years ago by math1985

Resolution: duplicate
Status: newclosed

This is now being discussed on Github: https://github.com/gravitystorm/openstreetmap-carto/issues/603 Therefore, I will close the issue here.

Note: See TracTickets for help on using tickets.