[mkgmap-dev] splitter - performance and memory

Tue Jul 21 07:52:20 BST 2009

It is good to have a more accurate mechanism for determining the optimal 
tile size but, imho, it is better to have a splitter that can handle the 
planet dump on more moderate machines. The advantages of more people 
providing Garmin maps outweigh the little extra handwork to get all the 
tiles rendered and still have reasonable large tile sizes. So I would 
really welcome a version of splitter that uses less memory.

People who are looking for (partially) hand optimized area lists can 
download them form http://garmin.na1400.info/routable.php (down to the 
bottom of that page).

Steve Ratcliffe wrote:
> Hi
> 
>> What do people think? I'm happy to work on the above though I must
>> confess up front that my spare time is quite limited so please don't
>> expect too much too soon!
> 
> It all sounds good. Well worth trying each idea out to see if it
> makes an improvement.
> 
> Although the .get() is not used at the moment I thinks that counting
> the ways in each area may be more accurate, in which case you will
> need the node-ids again.
> 
> I also have plans to remove the limitation that an element
> can only be in four areas.
> 
> Regards,
> 
> ..Steve
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev