[Tagging] How to tag sub-areas?

[Martin Koppenhoefer]

Am Mo., 11. Apr. 2022 um 09:50 Uhr schrieb Steve Lee <stevel2520 at gmail.com>:

> The whole of the farm, campus, and park I'm talking about is one unit, but
> their parts are relatively closed physically, so they have a name. In fact,
> the overall name is mainly used. It's a bit like an administrative
> hierarchy, but doesn't seem to have usage outside of administrative
> boundaries.
> Some lakes may be suitable for natural=bay, but other lakes are divided
> into separate waters by dikes, and some mappers write the name of each
> water area in the format "<overall name> <part name>", which I think is not
> acceptable.
>


for the farm, you could map the individual parts (landuses with "farmyard",
buildings etc.) and tie it all together with a polygon place=farm

For the campus we are still lacking a specific tag, a workaround, not
really satisfying, is with landuse=education or amenity=university on a
polygon (neither of these tags states it is a campus). Maybe place=campus
could make sense?

For bays, it will depend what the area is. E.g. one can imagine a bay
inside a bay, but it could also be a different kind of object, like a tidal
channel.

For groups in general, there is a proposed relation type=group which let's
you add a name (and other common attributes) for a group of same-kind
objects.

Surely you are aware of building and building:part, in theory this system
could be applied to other types of things as well?

For parks I have never seen this (besides "gardens" inside parks) but a
similar situation could be found with cemeteries? There the tag
cemetery=sector seems popular:
https://wiki.openstreetmap.org/wiki/Tag:cemetery%3Dsector (not the kind of
tag that I believe fits best, because cemetery=* would lead to expecting a
type of cemetery with the typical tagging logics).

Cheers,
Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20220411/db9dae75/attachment-0001.htm>