Unfortunately I don't think that is possible.
Multipolygons may only contain ways that have either role as inner or as
outer. It may not contain other relations (still possible to upload, but
not considered right according to the wiki). What should the ways be?
We can't make the separate wetland parts as inner ways, (as areas formed
by the inner ways are subtracted from the multipolygon), and even if we
try it becomes illegal as inner ways cannot share segments with the
outer way. We can't make the parts as outers either as they share
segments. The outer must be the surrounding outline without the shared
segments splitting the wetland in parts, and there are no inners (unless
the parts themselves has inners).
So then we have a multipolygon with just an outer. I could just as well
be a plain polygon made from a single closed way. This would work if
drawing order was defined, and that was the method I tried first. The
container polygon must have a natural tag as well (the logical would be
wetland here without further sub-classification).
However the drawing order is not defined (I think, not 100% sure), so
this is by the renderer interpreted as a wetland lying on top of the
other wetlands. OSM-Carto will still render the insides, but the fill
pattern of the outer polygon is drawn on top.
On 2020-12-11 18:09, Brian M. Sperlongano wrote:
Hello Anders,
I would recommend creating a multipolygon relation (type=multipolygon)
with each of the wetland pieces, and set the name= and appropriate
natural= and wetland= tags on the relation.
On Fri, Dec 11, 2020, 11:11 AM Anders Torger <[email protected]> wrote:
Hello,
I was on this list a while back expressing some frustration over
limitations when tagging nature and thought about getting involved in
a
process for change, but I came to realize that it's not feasible for
me
in my current life situation, so I've decided to continue be a normal
mapper as before, doing what I can do with features that exist today.
Anyway, if to be a mapper at all, I still like to solve some of my
naming issues in the best/least bad ways possible today. I'm currently
mapping a national park in Sweden, Muddus. It's in Laponia and
consists
of mighty wetlands and old forest. These wetlands are named, like is
common in Sweden and Sami lands. For us navigating in wildlife, names
in
nature are important.
A wetland polygon can be named in OSM, so the situation is better than
for example for named slopes (also common). However, a wetland here
can
consist of both bog and marsh (and it's important to make the
difference, since one is easy to walk on, the other not so much).
That's
two different natural types and thus can't be in the same multipolygon
(as outers).
Asking on OSM Help website for a solution I got the answer to make a
new
containing multipolygon and set the name on that. That would be quite
elegant for sure, but JOSM warns about that, can't have a name without
a
type, and if I set the type, say natural=wetland without any subtype,
I
get a JOSM warning that I have natural features on top of eachother.
If
I still upload it OSM-Carto does render out the name but you can see
that the wetland pattern of the outer polygon is drawn on top of the
contained polygons, so it does not seem to be the way to do it.
The least bad way I've come up with is to just name all polygons
belonging to the same wetlands the same, and hope for that in the
future
smart renderers will understand that polygons with shared borders and
shared name is the same named entity.
Any ideas or suggestions?
/Anders
_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging
