<div dir="ltr"><div><div><div>Hi everyone<br><br></div>Looks like a challenge. We have discussed this before and there were lots of very thoughtful and knowledgeable opinions, but no decisions on any actions. I kind of got the consensus that many were uncomfortable with the spread of heathland landuse data but we never decided to do anything about it. It would be great in my opinion if we moved on as a community and actually decided to act on our discussions.<br><br></div>Regards<br><br></div>Brian<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 8 February 2017 at 10:37, Marco Boeringa <span dir="ltr"><<a href="mailto:marco@boeringa.demon.nl" target="_blank">marco@boeringa.demon.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p><font size="-1">Hi David,</font></p>
<p><font size="-1">I know the opinions about the need to create
multipolygons are as diverse as there are political opinions. It
was just one example where these features cause issues. My main
question is simply if there are any plans or ideas by the
British community of how to deal with these features, or if there
is any consensus whether they are desired or not. If not, would
the community oppose someone else removing them?<br>
</font></p>
<p><font size="-1">Marco<br>
</font></p><span class="">
<p><font size="-1">On 07/02/17 19:19, Marco Boeringa wrote:
<br>
> Lastly, the lack of proper multipolygon creation, means
that other types
<br>
> of renderers and styles than Carto, and GIS's like QGIS and
ArcGIS, that
<br>
> do not stack features based on size but need multipolygons
to deal with
<br>
> polygon-within-polygon problems, have many older detailed
features
<br>
> covered up by these new ones, as the original data may be
hidden beneath
<br>
> the newly added ones.
<br>
<br>
That' a problem with the renderers. Multipolygons are difficult
for <br>
both (human) editors and (machine) renderers, so only be used
where <br>
strictly necessary.
</font><br>
</p>
<br> </span><table style="border-top:1px solid #d3d4de">
<tbody><tr>
<td style="width:55px;padding-top:18px"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" style="width:46px;height:29px" height="29" width="46"></a></td>
<td style="width:470px;padding-top:17px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virusvrij. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" style="color:#4453ea" target="_blank">www.avast.com</a> </td>
</tr>
</tbody></table>
</div>
<br>______________________________<wbr>_________________<br>
Talk-GB mailing list<br>
<a href="mailto:Talk-GB@openstreetmap.org">Talk-GB@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-gb" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/talk-gb</a><br>
<br></blockquote></div><br></div>