Hi Gerd, another solution from 'nice looking' point of view except not creating DEM would be to also create sea polygons for the whole rectangle. But I guess it's pretty hard as it needs data tiles, am I right? For users of course it would be better to define an poly-file, where DEM should be created, as these poly-files already exists.
Btw.: http://www.hscholland.de/OSM/HGT.7z you can find the 'broken' hgt-files where I got the problem Gerd pointed out. Viewfinder-data are fine so far. Can mkgmap read already compressed hgt-files? I remember previously mkgmap was able to read bzip2 or gz-compressed osm-files. So there are maybe already classes for reading compressed data in mkgmap. Finally I want to thanks all of you for the great work! I even don't know how long I was waiting for this feature!!! Henning On 28.12.2017 11:01, Gerd Petermann wrote: > Hi all, > > see the log message > http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4022 > for details about the changes. > > I've also experimented with code to read a *.poly file and use that to define > an area for which mkgmap should > not calculate DEM data but was not happy with the results so far. Maybe I'll > try again. > > Henning has pointed me to an error: > It seems that mkgmap (and probably also BuildDEMFile) somtimes create invalid > DEM data > for areas where the hgt files contain large holes, esp. when resolution is > low (high dem-dist value). > See e.g. http://files.mkgmap.org.uk/download/377/holes.jpg > I try to find out more now. > > > Gerd > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
