<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>I am not surprised, but it seems a clear case of incorrect tagging for the renderer<br></div><div><a href="https://wiki.openstreetmap.org/w/index.php?title=Incorrect_tagging_for_the_renderer">https://wiki.openstreetmap.org/w/index.php?title=Incorrect_tagging_for_the_renderer</a><br></div><div><br></div><div><br></div><div>Feb 3, 2021, 21:29 by zelonewolf@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr">I'm surprised to learn that people are using natural=scrub on landscaped areas. I was under the impression that natural=scrub is used for wild or unmaintained areas, not intentional ornamental landscaping.<br></div><div><br></div><div class=""><div class="" dir="ltr">On Wed, Feb 3, 2021 at 3:06 PM Jeroen Hoek <<a href="mailto:mail@jeroenhoek.nl" rel="noopener noreferrer" target="_blank">mail@jeroenhoek.nl</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=""><div>There are a number of problems with the mapping of greenery in built-up<br></div><div> areas. Most of the time mappers use landuse=grass, natural=scrub, and<br></div><div> barrier=hedge, but landuse=grass is not a landuse, natural=scrub is not<br></div><div> that natural, and barrier=hedge mapped as an area has been broken ever<br></div><div> since this commit landed in Carto:<br></div><div> <br></div><div> <a target="_blank" rel="noopener noreferrer" href="https://github.com/gravitystorm/openstreetmap-carto/issues/4200">https://github.com/gravitystorm/openstreetmap-carto/issues/4200</a><br></div><div> <br></div><div> So quite annoying on the whole, and any attempts to improve the<br></div><div> situation are stymied by the problem of rendering in Carto, which is<br></div><div> effectively the reference rendering style.<br></div><div> <br></div><div> The problem with landuse=bush I see is that it doesn't really improve<br></div><div> much over natural=scrub. I do agree that it fits in better with<br></div><div> landuse=grass, but it just adds another non-landuse landuse.<br></div><div> <br></div><div> I would really like to see a proposal with a set of tags for patches of<br></div><div> grass, shrubs, and hedge area that can be accepted by the community and<br></div><div> the Carto maintainers some day.<br></div><div> <br></div><div> Personally, I would start with a subset of the relevant landcover=*<br></div><div> tags: <a target="_blank" rel="noopener noreferrer" href="https://taginfo.openstreetmap.org/keys/landcover#values">https://taginfo.openstreetmap.org/keys/landcover#values</a><br></div><div> <br></div><div> What I and apparently a number of other mappers do in the mean time is<br></div><div> tag patches of grass and bushes with landuse=grass + landcover=grass and<br></div><div> natural=scrub + landcover=scrub, respectively. This way we can signal<br></div><div> our support for the landcover tags while not breaking rendering for<br></div><div> everybody else, and highlight that we are tagging landcover, not landuse<br></div><div> or natural features.<br></div><div> <br></div><div> _______________________________________________<br></div><div> Tagging mailing list<br></div><div> <a target="_blank" href="mailto:Tagging@openstreetmap.org" rel="noopener noreferrer">Tagging@openstreetmap.org</a><br></div><div> <a target="_blank" rel="noopener noreferrer" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a><br></div></blockquote></div></blockquote><div><br></div> </body>
</html>