[Tagging] Another multipolygon question

bkil bkil.hu+Aq at gmail.com
Sun Oct 21 11:50:39 UTC 2018

I've seen many usages of tagging the area as desired (restaurant,
playground, etc.) and then only adding the extra tag barrier=fence on it to
mean that the area is surrounded by a fence. It renders perfectly, although
I'm not sure if this is a preferred notation, as it is not discussed on the

The infobox on the right does prohibit usage on areas, but I'm not sure
what kind of consideration went into deciding this. Jojo4u introduced this
restriction on 2015-03-27T21:56 with comment "not defined as an area":

It was not mentioned in the original proposal:

However it was brought up on the talk page in 2008:

And anyway such documentation can become out of date, so my question is
whether this notation is viable?

On Sat, Oct 20, 2018 at 1:22 PM Martin Koppenhoefer <dieterdreist at gmail.com>

> sent from a phone
> > On 20. Oct 2018, at 11:38, Dave Swarthout <daveswarthout at gmail.com>
> wrote:
> >
> > But yesterday I tried something new, new for me anyway, and that was to
> create a single-member multipolygon from the coastline way and then tag the
> resultant relation with natural=wood in order to reduce the number of nodes
> used. I was pleased that JOSM didn't complain and that the island seemed to
> render okay but I'm not sure this is a legitimate procedure
> I also do this, for example if there’s a fence but I also want to tag the
> area it delimits. Or for buildings and things that are there, in some cases.
> Cheers, Martin
> _______________________________________________
> 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/20181021/7d369242/attachment.html>

More information about the Tagging mailing list