<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 all, <br><br>attached is a patch with a modified DouglasPeuckerFilter to <br>solve the problem with "disappearing roads". <br>I see only small differences in the maps, so I hope it doesn't introduce any side effects.<br><br>The problem occured when - due the rounding of coordinates to low resolutions -<br>a line is converted to a straight line with a spike.<br>This is not directly related to mergeLines, but is more likely to happen with it.<br><br>If I hear no complains I'll commit that patch on wednesday. <br>Compiled binary based on trunk r3118:<br><code><a href="http://files.mkgmap.org.uk/download/191/mkgmap.jar" target="_blank">http://files.mkgmap.org.uk/download/191/mkgmap.jar</a><br><br>Gerd<br></code><br><br><br><div><hr id="stopSpelling">From: gpetermann_muenchen@hotmail.com<br>To: mkgmap-dev@lists.mkgmap.org.uk<br>Date: Mon, 24 Mar 2014 19:50:52 +0100<br>Subject: Re: [mkgmap-dev] dissapearing roads<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr">Hi Andrzej,<br><br><div>> <br>> I think you could simply disable merging at lower resolution, since ways <br>> are already merged at layer 0. But if you want to get additional merging <br>> then still processing angle would be beneficial.<br>dont't think so :mkgmap starts to write the lowest resolution, <br>ends with the highest. For each resolution we can see different combinations<br>of lines.<br><br>Anyway, the new algo seems to work, I'll post a patch soon.<br><br>Gerd<br></div> </div>
<br>_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</div> </div></body>
</html>