Hi Wolfgang,
I've described splitters algorithm as it is now here:
http://gis.19327.n5.nabble.com/Problem-with-splitter-tp886p5561551.html
I am now working on a first approach that looks like this:
pass 1: calculate tile areas
pass 2:
a) for each coord, way: find out all tiles that are
Hi,
I have compiled world bounds using the performance branch. They can be
downloaded from http://www.navmaps.eu/wanmil/bounds_perf_20120313.zip.
I have checked the coverage of different admin_levels with the
BoundaryCoverageUtil. The result for admin_level=2 can be downloaded
from
On Thu, Mar 15, WanMil wrote:
Some countries are missing (USA, Canada, some african countries). I
assume that their boundaries were/are corrupt.
The boundary between USA and Canada was broken, but fixed yesterday.
Thorsten
--
Thorsten Kukuk, Project Manager/Release Manager SLES
SUSE
Hi Gerd,
your description of splitter's algorithm is in accordance to what I
observed when I used some
simple test data.
But beside the mulitpolygon problem there is another issue that results
from the present
algorithm.
If you consider one single tile, splitter writes a certain node to that
