Hi WanMil,
> > Today I've written the code to read & write the new format and to
> > recombine the boundaries.
> > There are two open problems:
> > a) Some boundaries with equal admin levels intersect, and
> > BoundaryQuadtree.merge() removes the intersection from one of the both.
> > This can cause different results compared to trunk because the
> > LocationHook in trunk can sort
> > them in different order. I think one cannot expect correct results for
> > this case, but it makes
> > testing difficult.
>
> Is it possible to create a rule which boundary is preferred (e.g. with
> lower id)?
>
Yes, that sounds like a good idea. I am not yet sure at what places the locator
may be involved in this. Something else for tomorrow ,-)
Gerd
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
