<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>thanks for the explanation. So I'll better use other data for testing ;-)<br><br>Gerd<br><br><div>> Date: Sun, 12 Jan 2014 23:55:20 +0200<br>> From: marko.makela@iki.fi<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] Question regarding duplicated shapes<br>> <br>> On Sun, Jan 12, 2014 at 03:46:30PM +0100, Gerd Petermann wrote:<br>> >while debugging the shape merger I found many duplicated shapes in <br>> >Finland, and I am not sure how mkgmap should handle them.<br>> <br>> Oh, the Corine import by "teollisuus" ("industry" in Finnish) is <br>> hopeless IMO. :( It is based on very inaccurate data, and the converter <br>> is generating duplicate ways and improperly tagged multipolygon <br>> relations, like in your example.<br>> <br>> Instead of defining the area-style tags on the multipolygon relation <br>> itself, this import added the tags to all relation members (both <br>> role=inner and role=outer). JOSM at least used to display this as <br>> intended, IIRC.<br>> <br>> Whenever I have fixed some multipolygon error in Finland, I have tried <br>> to remove the duplicate shapes, and to move the area-style tags to the <br>> multipolygon relation. It is sometimes tricky if someone has already <br>> tried to edit the imported data.<br>> <br>> >Example:<br>> ><br>> >http://www.openstreetmap.org/way/105723026<br>> ><br>> >is tagged landuse=farm and is the role=inner member of<br>> >multipolygon relation<br>> >http://www.openstreetmap.org/relation/1504949<br>> >which has only one role=outer way which also is<br>> >tagged landuse=farm.<br>> >Way http://www.openstreetmap.org/way/105719041<br>> >is a copy of way 105723026, but with reverse order of<br>> >points. It is tagged natural=scrub<br>> <br>> Yes, this is exactly what I have seen many times.<br>> <br>> FWIW, I do not think that mkgmap should spend too much effort in <br>> supporting this broken and redundant way of mapping multipolygons. The <br>> Corine data is very low-resolution, basically useless. Now that we <br>> finally got the license stuff sorted out at <br>> http://www.openstreetmap.org/copyright the import from the National Land <br>> Survey database is "only" a matter of writing and configuring a <br>> converter, and manually resolving conflicts with existing data. In this <br>> process, the Corine landuse imports will probably be deleted.<br>> <br>> Best regards,<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>