[mkgmap-dev] mkgmap:drawLevel and --order-by-decreasing-area

Thu Nov 24 11:25:31 GMT 2016

Hi Gerd

After thinking I'd found the problem and stopping it (horizontal &
vertical flat areas), I thought I'd better test on rheinskipper1000's
data, so I downloaded all of

... from list mail: Fri, 18 Nov 2016 14:58:01 +0100
Here it is:
https://mega.nz/#!VVcjRIIY!r6OT24vLy1KCTaM6ZHJP2VTOdtyaOnF1GenO6xjygyY

Unfortunately is really big. I also tried it with small input but had
no errors then. 
...

(it is >2G)

and discovered other orientations as well. Only 10 occurrences in 141
tiles. His tile 63210102.osm.pbf has 3 examples.

from areas.list
63210102: 2449408,266240 to 2469888,284672
#       : 52.558594,5.712891 to 52.998047,6.108398

I can extract and send you his command line, -c options and style if it
would help. Not sure if his sea.zip is relevant.

Regards
Ticker

On Thu, 2016-11-24 at 06:57 +0000, Gerd Petermann wrote:
> Hi Ticker,
> 
> thanks for the patch. I was not yet able to reproduce the problem
> reported by rheinskipper1000.  Do you have a test case for me?
> 
> Gerd
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag
> von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
> Gesendet: Mittwoch, 23. November 2016 13:39:16
> An: mkgmap-dev at lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] mkgmap:drawLevel and --order-by-decreasing
> -area
>  
> Hi Gerd
> 
> Attached patch stops the errors from shapeMergeFilter. The java2D
> intersect.() / converter used for clipping sometimes generates
> flattened shapes which I now check for and chuck away.
> 
> I've also moved the code that shares common coord.
> 
> The patch is independent of the pending drawLevel patch
> 
> Ticker
> 
> 
> 
> On Sat, 2016-11-19 at 10:46 +0000, Ticker Berkin wrote:
> > Your right - it is big. My system didn't want to download it
> without
> > installing some add-ons which I don't want to do at the moment.
> > 
> > However, I have reproduced the same diagnostic from one of my maps
> > and
> > am investigating that. It is more related to --order-by-.. than
> > mkgmap:drawLevel and the boundaries of different precisions used by
> > mkgmap.
> > 
> > Looking at the map output at a very high resolution in the problem
> > area, I can't see any difference between when I get the error and
> > when
> > I've made it not happen by some trickery.
> > 
> > I should be able to come up with the correct fix in a day or two.
> > 
> > Ticker
> > 
> > _______________________________________________
> > mkgmap-dev mailing list
> > mkgmap-dev at lists.mkgmap.org.uk
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>  _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev