<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>HI Marko,<br><br>I agree that this should be flagged. <br>I tried it with the data for Netherlands and I see no other problems besides the one<br>in my example, so it doesn't see to happen that often.<br><br>Attached small patch changes mkgmap so that repeated<br>elements are ignored (the first one is used, ignoring differences in roles)<br><br>If I hear no complains I will commit it next weekend.<br><br>Gerd<br><br><div>> Date: Sun, 19 Jan 2014 00:16:15 +0200<br>> From: marko.makela@iki.fi<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] type=multipolygon relations<br>> <br>> On Sat, Jan 18, 2014 at 10:58:58PM +0100, Minko wrote:<br>> >Good luck for correcting them, there are tons of those faulty mp's all <br>> >over the place in NL's ;-)<br>> >I wouldnt spend too much time for this, better ignore it.<br>> <br>> I have found the existing multipolygon and coastline warnings very <br>> useful. The check for duplicate member ID in a multipolygon relation is <br>> cheap and has to be done anyway. There is really no good reason not to <br>> warn about them.<br>> <br>> By default, the log output is not enabled. You have to specify <br>> -Dlog.config=logging.properties in order to enable the diagnostic. Even <br>> after doing so, you could filter out these particular messages either by <br>> grep -vf or by configuring the logging.properties file appropriately.<br>> <br>> Marko<br>> _______________________________________________<br>> mkgmap-dev mailing list<br>> mkgmap-dev@lists.mkgmap.org.uk<br>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<br></div> </div></body>
</html>