[Tagging] Requiring area=yes with barrier=wall, barrier=hedge and other usually linear features when mapped as an area`1

[Warin]

On 14/04/19 14:15, Phake Nick wrote:
> area=no would also applies to amenity=park or landcover=* if you are 
> tagging them in the same object.

If a were were

tagged barrier=*, area=no

A member of a relation as the outer way tagged amenity=park

Would not the way be both then recognised as

a) a barrier
b) a park - that does not inherit the tags on the way.

????
>
> 在 2019年4月14日週日 05:16，Warin <61sundowner at gmail.com 
> <mailto:61sundowner at gmail.com>> 寫道：
>
>     As a closed way would normally be taken as an area,but in the case
>     of this barrier it is required not to be an area, why not use the
>     tag area=no?
>
>     Tag the unusual rather than the normal?
>
>     Then, as Martin says, use the way of the barrier in a multipolygon
>     relation for a park.
>
>
>
>     On 14/04/19 06:43, Martin Koppenhoefer wrote:
>     >
>     > sent from a phone
>     >
>     >> On 13. Apr 2019, at 19:58, Shawn K. Quinn <skquinn at rushpost.com
>     <mailto:skquinn at rushpost.com>> wrote:
>     >>
>     >> It makes no sense to have to add separate ways for
>     barrier=fence and
>     >> leisure=park when the fence surrounds the entire park.
>     >
>     > you could make the park a multipolygon.
>     >
>     >
>     > Cheers, Martin
>
>
>
>     _______________________________________________
>     Tagging mailing list
>     Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
>     https://lists.openstreetmap.org/listinfo/tagging
>
>
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20190414/cf47c5e7/attachment.html>