<html><head></head><body><div dir="auto">Hi Gerd,<br></div>
<div dir="auto">So far I understand you have implemented already cutting the DEM to the map area and just looking for another way to have some larger area for DEM data? I don't see a use case for that. Probably the reason why I first didn't realised the beginning of your svn comment.<br></div>
<div dir="auto">Henning </div>
<div class="gmail_quote" >On 28 Dec 2017, at 11:01, Gerd Petermann <<a href="mailto:GPetermann_muenchen@hotmail.com" target="_blank">GPetermann_muenchen@hotmail.com</a>> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="blue">Hi all,<br><br>see the log message <a href="http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4022">http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4022</a> <br>for details about the changes.<br><br>I've also experimented with code to read a *.poly file and use that to define an area for which mkgmap should <br>not calculate DEM data but was not happy with the results so far. Maybe I'll try again.<br><br>Henning has pointed me to an error:<br>It seems that mkgmap (and probably also BuildDEMFile) somtimes create invalid DEM data <br>for areas where the hgt files contain large holes, esp. when resolution is low (high dem-dist value).<br>See e.g. <a href="http://files.mkgmap.org.uk/download/377/holes.jpg">http://files.mkgmap.org.uk/download/377/holes.jpg</a><br>I try to find out more now.<br><br><br>Gerd<br><hr><br>mkgmap-dev mailing list<br>mkgmap-dev@lists.mkgmap.org.uk<br><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br><br></pre></blockquote></div></body></html>