logo separator

[mkgmap-dev] Performance with zipped hgt files

From Gerd Petermann gpetermann_muenchen at hotmail.com on Mon Jan 8 20:20:27 GMT 2018

Hi Andrzej,

I think with unzipped hgt files the only limit is the memory that is needed to store the data for the tiles before they are written to img.
So, with --max-jobs=4 or higher  and all jobs with large tiles containing large amounts of data for RGN,NOD,NET etc. it is much more likely that the additional data for DEM causes trouble. I've not yet tried to reduce the memory for this temp. data, a possible alternative is to write it to temp files instead of storing it in buffers. This is esp. true for large tiles were DEM can be > 100MB while the other files cannot grow > 16MB.


Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej at poczta.onet.pl>
Gesendet: Montag, 8. Januar 2018 21:04:48
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Performance with zipped hgt files

Hi Gerd,

I decided for 11.25 (=360/32) because of memory limits in early
BuildDemFile. Maybe this is not a problem for mkgmap?

Best regards,

mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk

More information about the mkgmap-dev mailing list