<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Does the actual wetland have a name, or does the area which the
wetland is part of have a name? If the latter is the case, I might
just consider using a node with place=locality+name=(name) to tag
it. It's typically used to tag "an unpopulated location for which
there is no extant feature to which the tag could be associated"
(source: wiki) but the danger is that you might start tagging for
the renderer. I wouldn't use it if the <i>actual</i> wetland is
named, so if that's the case just ignore this.<br>
</p>
<p>Best, Casper</p>
<p><a moz-do-not-send="true"
href="https://wiki.openstreetmap.org/wiki/Tag:place%3Dlocality">https://wiki.openstreetmap.org/wiki/Tag:place%3Dlocality</a><br>
</p>
<div class="moz-cite-prefix">On 2020-12-11 17:07, Anders Torger
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:95500f26da058ecf4660bb6e9d487d7e@torger.se">Hello,
<br>
<br>
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.
<br>
<br>
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.
<br>
<br>
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).
<br>
<br>
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.
<br>
<br>
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.
<br>
<br>
Any ideas or suggestions?
<br>
<br>
/Anders
<br>
<br>
_______________________________________________
<br>
Tagging mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
<br>
</blockquote>
</body>
</html>