logo separator

[mkgmap-dev] mkgmap splitter --resolution broken?

From Felix Hartmann extremecarver at googlemail.com on Tue Oct 27 15:29:40 GMT 2009

David wrote:
> To Felix Hartmann
> Resolution 24 contains the most detailed leveol of details you can use 
> in a map. Resolution 23 is a bit less detailed, and so on. That is why 
> resolution 13 contains far less data than resolution 16. But if you mean 
> by "24-13" all resolutions included in the interval [24;13], it is 
> probably a bug.
I don't really understand what your response has to do with the original 
question of why memory increases largely when running the splitter for 
say resolution=16 instead of resolution=13. Of course I know that 24 is 
the most detailed resolution. Resolution 24 has to be included in any 
map, all other additional resolutions are optional. I don't understand 
why the splitter needs crazy high memory requirements if splitting for 
16 instead of resolution 13, as a map with the lowest resolution of 13 
could include resolution 16 as second level, therefore I would assume 
that splitting with resolution=13 should use more memory than splitting 
with resolution=16. The splitter can't know what intermediary 
resolutions will be used.
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

More information about the mkgmap-dev mailing list