Proposal talk:Park boundary/Case studies

Goddard state park - maybe "Internal regions of park land are explicitly tagged with leisure=park." would be better described by adding "manicured" qualifier to be "Internal regions of manicured park land are explicitly tagged with leisure=park." (ambiguity in meaning what "park" means is root of the entire issue) Mateusz Konieczny (talk) 08:50, 10 October 2020 (UTC)

Good catch, I made this correction! ZeLonewolf (talk) 20:07, 10 October 2020 (UTC)

Don’t tag for the renderer

It looks like the problem here is that you want to be able to see the a rendering of the outline of the leisure=park area in the OpenStreetMap Carto style (e.g. on the Standard map layer shown on openstreetmap.org) - but a renderer can really only show one feature in each pixel. Using a narrow line or a semi-transparent area causes other problems.

Changing the tagging of an area to get a rendering that you prefer is called "tagging [incorrectly] for the renderer" and it's a common problem in OpenStreetMap.

Not quite - the problem that I am trying to solve, is that I want to be able to see outline of a park, not a leisure=park. It is incorrect to tag the boundary of a park with both manicured and natural, undeveloped areas as leisure=park, because that tag is for manicured park land. The wiki page for leisure=park states even states "...Forest within a city. This is not a park, as greenery is not fully controlled.". So if I have a park with both manicured and "natural, wild" parts - what tags can I possibly use to tag the boundary of such a property?

It is not specifically a Carto issue, it's a information problem that would impact any renderer. The issue isn't lack of renderer support, the issue is a lack of available tags to represent the information. leisure=park tags an area as manicured parkland. It cannot simultaneously be the boundary of a complex park because that's conflicting meaning. If ke9tv's proposed protection_class=recreation which you just linked is approved, that would certainly solve the problem I'm expressing here. ZeLonewolf (talk) 06:11, 12 October 2020 (UTC)