<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta name="x_Generator" content="Microsoft Word 15 (filtered medium)">
<style>
<!--
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:x_link, span.x_MsoHyperlink
{color:blue;
text-decoration:underline}
a:x_visited, span.x_MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
.x_MsoChpDefault
{}
div.x_WordSection1
{}
-->
</style>
<div lang="DE" link="blue" vlink="#954F72">
<div class="x_WordSection1">
<p class="x_MsoNormal">Hi Ticker,</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">I thought you have a small test case. It would be great if you can reproduce it with only one tile</p>
<p class="x_MsoNormal">and post a link to the needed package.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Gerd</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="x_MsoNormal" style="border:none; padding:0cm"><b>Von: </b><a href="mailto:rwb-mkgmap@jagit.co.uk">Ticker Berkin</a><br>
<b>Gesendet: </b>Donnerstag, 24. November 2016 12:25<br>
<b>An: </b><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<b>Betreff: </b>Re: [mkgmap-dev] mkgmap:drawLevel and --order-by-decreasing-area</p>
</div>
<p class="x_MsoNormal"> </p>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi Gerd<br>
<br>
After thinking I'd found the problem and stopping it (horizontal &<br>
vertical flat areas), I thought I'd better test on rheinskipper1000's<br>
data, so I downloaded all of<br>
<br>
... from list mail: Fri, 18 Nov 2016 14:58:01 +0100<br>
Here it is:<br>
<a href="https://mega.nz/#!VVcjRIIY!r6OT24vLy1KCTaM6ZHJP2VTOdtyaOnF1GenO6xjygyY">https://mega.nz/#!VVcjRIIY!r6OT24vLy1KCTaM6ZHJP2VTOdtyaOnF1GenO6xjygyY</a><br>
<br>
Unfortunately is really big. I also tried it with small input but had<br>
no errors then. <br>
...<br>
<br>
(it is >2G)<br>
<br>
and discovered other orientations as well. Only 10 occurrences in 141<br>
tiles. His tile 63210102.osm.pbf has 3 examples.<br>
<br>
from areas.list<br>
63210102: 2449408,266240 to 2469888,284672<br>
# : 52.558594,5.712891 to 52.998047,6.108398<br>
<br>
I can extract and send you his command line, -c options and style if it<br>
would help. Not sure if his sea.zip is relevant.<br>
<br>
Regards<br>
Ticker<br>
<br>
On Thu, 2016-11-24 at 06:57 +0000, Gerd Petermann wrote:<br>
> Hi Ticker,<br>
> <br>
> thanks for the patch. I was not yet able to reproduce the problem<br>
> reported by rheinskipper1000. Do you have a test case for me?<br>
> <br>
> Gerd<br>
> Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag<br>
> von Ticker Berkin <rwb-mkgmap@jagit.co.uk><br>
> Gesendet: Mittwoch, 23. November 2016 13:39:16<br>
> An: mkgmap-dev@lists.mkgmap.org.uk<br>
> Betreff: Re: [mkgmap-dev] mkgmap:drawLevel and --order-by-decreasing<br>
> -area<br>
> <br>
> Hi Gerd<br>
> <br>
> Attached patch stops the errors from shapeMergeFilter. The java2D<br>
> intersect.() / converter used for clipping sometimes generates<br>
> flattened shapes which I now check for and chuck away.<br>
> <br>
> I've also moved the code that shares common coord.<br>
> <br>
> The patch is independent of the pending drawLevel patch<br>
> <br>
> Ticker<br>
> <br>
> <br>
> <br>
> On Sat, 2016-11-19 at 10:46 +0000, Ticker Berkin wrote:<br>
> > Your right - it is big. My system didn't want to download it<br>
> without<br>
> > installing some add-ons which I don't want to do at the moment.<br>
> > <br>
> > However, I have reproduced the same diagnostic from one of my maps<br>
> > and<br>
> > am investigating that. It is more related to --order-by-.. than<br>
> > mkgmap:drawLevel and the boundaries of different precisions used by<br>
> > mkgmap.<br>
> > <br>
> > Looking at the map output at a very high resolution in the problem<br>
> > area, I can't see any difference between when I get the error and<br>
> > when<br>
> > I've made it not happen by some trickery.<br>
> > <br>
> > I should be able to come up with the correct fix in a day or two.<br>
> > <br>
> > Ticker<br>
> > <br>
> > _______________________________________________<br>
> > mkgmap-dev mailing list<br>
> > mkgmap-dev@lists.mkgmap.org.uk<br>
> > <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
> _______________________________________________<br>
> mkgmap-dev mailing list<br>
> mkgmap-dev@lists.mkgmap.org.uk<br>
> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
</div>
</span></font>
</body>
</html>