[mkgmap-dev] Still problems with lakes
From toc-rox easyclasspage at googlemail.com on Wed Sep 19 15:25:10 BST 2012
@GerdP: Some ideas concerning the "huge polygon problem": - huge polygons are rare - a broken polygon leads to an ugly (amateur like) map - it's hard to find all broken polygons in a map manually Some questions concerning a solution: - is it possible to implement a "huge polygon" parameter ? - the parameter acts as threshold and triggers splitter for extra processing - the parameter could be the area (e.g. 2000 sqkm) or circumference (e.g. 1000 km) of an "huge" polygon If the calculating of all polygons has a large negative performance impact: - is it possible to identify the huge polygons in an extra (on demand) splitter run ? - the result could be a list with all identified huge polygons (generated only once) - this list is than the input for the essential splitter run What do you think ? Regards Klaus PS: What is the exactly influence of the overlapping parameter concerning the splitting of (huge) polyons ? -- View this message in context: http://gis.19327.n5.nabble.com/Still-problems-with-lakes-tp5725668p5726209.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
- Previous message: [mkgmap-dev] Still problems with lakes
- Next message: [mkgmap-dev] Still problems with lakes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list