On Wed, 5 Feb 2020 at 14:48, Christoph Hormann <[email protected]> wrote:
> > 1) remove all rendering of barrier tags on polygons > 2) mappers in a concerted effort resolving the semantic ambiguity of the > >350k cases where barrier tags are currently used as a secondary tag on > landuse/leisure/etc. polygons to incidate the polygon is enclosed by a > linear barrier. > 3) (re-)introducing the rendering of barrier polygons with a fill where > this is consistently used tagging. > 4) Where the only tags are barrier=hedge + area=yes then render as before, a hedge that has area. This would exclude the cases like leisure=park + barrier=hedge which is a non-preferred way of mapping a park with a hedge around it. Maybe that's what you meant in your point 3, but it didn't read that way to me. 5) Introduce, and render, landcover=hedge so we can tag an object as landcover=hedge + barrier=hedge. It would be sub-optimal to use landcover=scrub or landcover=heath because the bushes in those are not so close together as to form a barrier. You might be able to squeeze through a gap in a hedge and then walk through scrubland or heathland, but you're not going to be able to do that here: https://goo.gl/maps/52wy5CAAVgXeMfXZ6 Not only are there no spaces between the bushes, they have thorns. -- Paul
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
