[mkgmap-dev] Performance with zipped hgt files

Mon Jan 8 14:30:08 GMT 2018

Hi Gerd,

at last you need the data uncompressed in a buffer, right? That's why i 
see no difference between using compressed or uncompressed hgt files. 
Compressed files need a little bit more time for uncompressing, but after 
that the data need the same size in memory. That's why i see no vantage 
for mkgmap if the data are stored in an other form. It can only save disc 
space, no heap space.

What speaks against a limitation for the extent of a maptile? This limited 
the count of hgt's for one maptile too.

You have the option --max-areas for splitter. We need only an additional 
option like --maxextent or whatever. Perhaps we have then maptiles without 
points, lines or areas (on oceans, deserts or so), but why not?

Frank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20180108/fc6d9fdd/attachment.html>