
Great to see that a simple log can be so helpful. :) Would be nice for splitter to be much faster with only a single pass on a moderate pc (i.e. 8 gb ram), but I'm not complaining as it is... Running splitter r247 with the added logging parameters on my dev pc now, will send the results tomorrow. On 29-11-12 22:16, GerdP wrote:
Oh oh! I looked again at this logs and wondered why some numbers did not change during the different passes. I found out that the 7 passes in the ProblemListProcessor are more or less nonsense. The intention was to save memory by processing only a set of writers in each pass, but in fact all 7 passes store the node informations for all writers. In short: splitter requires either much less memory whhen this bug is corrected, or you can run everything in one pass if you specify --max-areas=2048 I hope I can fix this soon.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/splitter-r247-tp5737673p5738287.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev