> Hi WanMil, > > > > Date: Wed, 8 Feb 2012 18:28:32 +0100 > > From: [email protected] > > To: [email protected] > > Subject: Re: [mkgmap-dev] [PATCH V2] boundary preparer with quadtree > > > > Hi Gerd, > > > > > Would you mind dropping the support for the old format ? > > > > No! > > Would it be a big deal to implement a converter? > > It is already implemented in the BoundaryPreparer when you execute its > main(). > Also, I'll keep the code that writes the old format, because it is used > before preparer starts. > I just drop analysing the mkgmap:lies_in tags. > > 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)? > > b) The recombined boundaries have a few small holes, probably again the > rounding error. > I'll check this tomorrow. > > ciao, > Gerd > > > > > WanMil > > > > > > _______________________________________________ > > mkgmap-dev mailing list > > [email protected] > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
