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

Fri Nov 25 08:42:57 GMT 2016

Hi Ticker,

OK, I think you found a flaw in the Area code which I introduced with the
highprec stuff.
I think it would be better to change class Area to store high prec values,
but for now 
your work around seems okay to me.

Gerd

Ticker Berkin wrote
> 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 .org

>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev at .org

> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 
> emptyArea_v2.patch (6K)
> <http://gis.19327.n8.nabble.com/attachment/5886418/0/emptyArea_v2.patch>

--
View this message in context: http://gis.19327.n8.nabble.com/Spurious-points-Basecamp-blank-tiles-tp5885434p5886483.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.