<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>Forgot to mention - the issue you linked is a good example of the problem with having both a node and relation representing the same feature. The bug wouldn't exist if the app didn't ignore the label role on the boundaries. If it rendered the relations' name at the label node (which is the duplicate place=*), or skipped rendering the name of relations where the label node has duplicate tags, or if the place node were deleted entirely, then there wouldn't be 2 names visible.<br></div><div><br></div><div><br></div><div>Sep 30, 2021, 05:57 by tagging@openstreetmap.org:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="auto">Whole (bad and unwanted) point of label role is to manually map where label<br></div><div dir="auto">should be placed on a rendered map.<br></div><div dir="auto"><br></div><div dir="auto">See for example <a target="_blank" rel="noopener noreferrer" href="https://github.com/organicmaps/organicmaps/issues/1134">https://github.com/organicmaps/organicmaps/issues/1134</a><br></div><div dir="auto">requesting to do exactly this.<br></div><div dir="auto"><br></div></blockquote><div dir="auto"><br></div> </body>
</html>