>
> Gerd
>
>
>
>
>
> ____
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Sonntag, 15. Januar 2017 14:41:27
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] [Patch] "Area too small to spl
>
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Sonntag, 15. Januar 2017 14:41:27
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] [Patch] "Area too small to split at " ...
> followed
Sonntag, 15. Januar 2017 14:41:27
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] [Patch] "Area too small to split at " ... followed by
"Too many POIs at location " error message
Hi Gerd
Yes; however, regardless of useNormalSplit, with --order-by... the
shapes
ll to split at " ... followed by
"Too many POIs at location " error message
Hi Gerd
Yes; however, regardless of useNormalSplit, with --order-by... the
shapes need to be split into their correct area.
This bit of code has always troubled me. I wasn't sure if its objective
was to l
Hi Gerd
Yes; however, regardless of useNormalSplit, with --order-by... the
shapes need to be split into their correct area.
This bit of code has always troubled me. I wasn't sure if its objective
was to lessen the chance of empty subdivisions or to lessen the chance
of exceeding maximum data size
Hi all,
attached is a patch to solve this problem.
A binary is here:
http://files.mkgmap.org.uk/download/327/mkgmap.jar
@Ticker: Please review.
I've noticed that with --order-by-decreasing-area
the code in MapArea to set useNormalSplit may not be used because
the condition used[0] != used[1] i
