Hello Henning, yes, it got close. The long runtime in the 3rd pass of the MultiTileProcessor is caused by some lazy coded tests. I am optimistic that this can be reduced drastically. I will commit a new version soon, maybe that will already work for you. I found an error in the pseudo-area creation that causes too many problem candidates. With mixed=false, it is possible to replace a large hashmap by two arrays, I am testing this now.
Gerd > Date: Fri, 9 Nov 2012 16:26:23 +0100 > From: [email protected] > To: [email protected] > Subject: Re: [mkgmap-dev] Endless loop with splitter r221 > > Am 08.11.2012 01:42, schrieb GerdP: > > Hi all, > > > > r224 fixes this endless loop and other reported problems: > > - correct creation of pseudo areas > > - correct handling of nodes in relations > > - handle overlapping tiles > > - performance improvements: > > + reduce number of expensive intersects() for ways > > + much faster pseudo area creation (still room for optimization) > > - improved reporting of incomplete relations or ways > > > > Please try it with --keep-complete and --overlap=0 . > > Hi Gerd, > I tried it with planet and all my maps. It seems to work, but there > wasn't enough RAM in my PC, so it tooks to long. I stop splitter after 9 > hours. > > Log: http://www.aighes.de/data/splitter.log > > If it helps you, I could also generate a detailed log. > > Henning > > > _______________________________________________ > 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
