Seems like a good idea - It should use the --polygon-size-limits option in an inverted sort of way. Ticker On Wed, 2016-12-21 at 07:48 +0000, Gerd Petermann wrote:
Hi all,
while debugging the problem reported by Arndt Röhrig http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2016q4/025471.html
I noticed that his style adds all polygons with "min resolution 10" like this: landuse=basin [0x53 resolution 10]
Up to now I thought this is just causing more CPU load : The polygon is processed for each (low) resolution and after many calculations it is typically "thrown away" because it is reduced to a single point in the
I think we can easily change mkgmap to calculate a proper "min res" value for shapes depending on the actual size at resolution 24. Probably that would also be useful for lines.
Any thoughts?
Gerd
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev