Re: [mkgmap-dev] remove splitter option align-for-dem again or change mkgmap?

Hi Andrzej, okay, and this is also true when you use the default resolution 13. I see no reason to use a much higher resolution, it just seems to need more resources. My idea about automatic selection of resolution might start with res 15 and - if memory is a problem - decrease it. The search

Re: [mkgmap-dev] Is dem-tdb branch ready for trunk ?

Hi all, I've noticed that mkgmap cannot process the files that you can download from http://opendem.info/opendemeu_download_4326.html because they are zip files containing a directory that contains the needed file. I've added support for this in r4092 now:

Re: [mkgmap-dev] remove splitter option align-for-dem again or change mkgmap?

Hi Gerd, > Do you think that it can cause trouble when a sub division from tile A > overlaps another from tile B at level 1..7 ? I don't think there is a problem with overlap. I'm only stating, that splitter idea of "resolution" is a clever one, since it can lead to no overlap at all. --

Re: [mkgmap-dev] gmapi reader?

Hi Gerd I'd like to merge first and do any optimisation later. OK, that's good. I've done a few tests reg. memory. I think we should not care much. It would be easy to free the resources allocated in DEMTile directly after the data was written. I think peak memory is reached when

Re: [mkgmap-dev] gmapi reader?

Hi Steve, I'd like to merge first and do any optimisation later. I've done a few tests reg. memory. I think we should not care much. It would be easy to free the resources allocated in DEMTile directly after the data was written. I think peak memory is reached when processing the style, not at

Re: [mkgmap-dev] gmapi reader?

Hi Gerd Is this something that needs to be done before the merge? the DEM header structures are quite special, the headers of the sections are written at the very end of the DEM file, and they point to data that follows the main header. This is probably not mandantory but it's the way

Re: [mkgmap-dev] gmapi reader?

Hi Steve, the DEM header structures are quite special, the headers of the sections are written at the very end of the DEM file, and they point to data that follows the main header. This is probably not mandantory but it's the way Garmin does it, and also DemDisplay uses it to determine the

Re: [mkgmap-dev] gmapi reader?

Hi Gerd A new fs sounds good to me, would be great if you could do that, I am always unsure where to call close(). OK Reg. FileCopier: I have to read the DEM file to make sure that it matches, I just If I didn't miss anything you just need to read the header to do the check. I would do

Re: [mkgmap-dev] Is dem-tdb branch ready for trunk ?

Hi all, I think nobody is unhappy with the idea of merging soon? Is anybody aware of problems with r4091 that should be solved first? Gerd Von: mkgmap-dev im Auftrag von Carlos Dávila

Re: [mkgmap-dev] remove splitter option align-for-dem again or change mkgmap?

Hi Andrzej, sorry, I don't get the idea. What bounding box do you mean? I assume you talk about what is called SubDivision in mkgmp? What rounding errors do you fear? Do you think that it can cause trouble when a sub division from tile A overlaps another from tile B at level 1..7 ? I think this

Re: [mkgmap-dev] gmapi reader?

Hi Steve, A new fs sounds good to me, would be great if you could do that, I am always unsure where to call close(). Reg. FileCopier: I have to read the DEM file to make sure that it matches, I just think that it would be better to store a reference to the existing file instead of copying it