<html><head></head><body><div dir="auto">Hi, <br></div>
<div dir="auto">it would be my expected behaviour if you just delete the OSM data and keep the area still in your map area. <br><br></div>
<div dir="auto">Henning <br><br></div>
<div dir="auto"><!-- tmjah_g_1299s -->Sent from <!-- tmjah_g_1299e --><a href="http://www.bluemail.me/r?b=11327"><!-- tmjah_g_1299s -->BlueMail<!-- tmjah_g_1299e --></a><!-- tmjah_g_1299s --> <!-- tmjah_g_1299e --></div>
<div class="gmail_quote" >On 23 Dec 2017, at 10:12, Ervin Malicdem <<a href="mailto:schadow1@gmail.com" target="_blank">schadow1@gmail.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;">
<div dir="ltr">Hi Gerd,<br><br>This is regarding hillshade still being rendered even if the area was excluded in the osm file.<br>As an example, I specifically removed borneo island in the southwest but DEM still showed up.<br><br><a href="https://www.dropbox.com/s/m6pdz90d3jo1unq/borneo.jpg?dl=0">https://www.dropbox.com/s/m6pdz90d3jo1unq/borneo.jpg?dl=0</a><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Ervin M.<br><b>Schadow1 Expeditions</b> - A Filipino must not be a stranger to his own motherland.<div><a href="http://www.s1expeditions.com" target="_blank">http://www.s1expeditions.com</a></div></div></div></div>
<br><div class="gmail_quote">On Sat, Dec 23, 2017 at 4:08 PM, Gerd Petermann <span dir="ltr"><<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Ervin,<br>
<br>
I think there is no longer a need to change splitter since DEM files are allowed to grow > 16MB with r4016.<br>
Just to make that clear: When I write about DEM files I mean the files in the Garmin DEM format, they are either contained in a *.img<br>
or in a *.DEM, and they contain the text "GARMIN DEM". I guess DEM means something like "Digital Elevation Model".<br>
Besides that I don't understand what you mean. Is it about the contour lines created by tools like srtm2osm or phyghtmap?<br>
What could be improved in splitter?<br>
<br>
Gerd<br>
<br>
______________________________<wbr>__________<br>
Von: <a href="mailto:ebmalicdem@cxsmedia.com">ebmalicdem@cxsmedia.com</a> <<a href="mailto:ebmalicdem@cxsmedia.com">ebmalicdem@cxsmedia.com</a>> im Auftrag von Ervin Malicdem <<a href="mailto:schadow1@gmail.com">schadow1@gmail.com</a>><br>
Gesendet: Samstag, 23. Dezember 2017 06:21:36<br>
An: Development list for mkgmap; <a href="mailto:gpetermann_muenchen@hotmail.com">gpetermann_muenchen@hotmail.<wbr>com</a><br>
Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist<br>
<span class=""><br>
Getting better each time! Great!<br>
A suggestion once you will be working with splitter is for the dem to be cut using a poly file as well.<br>
<br>
Ervin M.<br>
Schadow1 Expeditions - A Filipino must not be a stranger to his own motherland.<br>
<a href="http://www.s1expeditions.com" rel="noreferrer" target="_blank">http://www.s1expeditions.com</a><br>
<br>
</span><div><div class="h5">On Sat, Dec 23, 2017 at 12:11 AM, Gerd Petermann <<a href="mailto:GPetermann_muenchen@hotmail.com">GPetermann_muenchen@hotmail.<wbr>com</a><mailto:<a href="mailto:GPetermann_muenchen@hotmail.com">GPetermann_<wbr>muenchen@hotmail.com</a>>> wrote:<br>
Hi,<br>
<br>
okay, so we now have three new (still undocumented options) to enable hillshading and calculation of elevation data in routes.<br>
Here is a summary of the new options:<br>
<br>
--x-dem=path_to_dir[,path_to_<wbr>other_dir,...]<br>
gives one or more directories containing *.hgt files.<br>
--x-dem-dists=n1,n2,n3,...<br>
Sample from a Garmin Demo map: --x-dem-dists="5520, 16560, 44176, 88368"<br>
should contain one number for each level in case you want to use the DEM data in a gmapsupp, the values give<br>
the number of DEM units between two points. A DEM unit is 360° / 2 ^32.<br>
The higher the numbers the smaller the DEM file. Useful values for level 0 start<br>
at 1600 if you have 1'' hgt data and a small area, for large areas consider to use 8000 or more. If this option is missing mkgmap will calculate one DEM<br>
level based on the resolution of the hgt files.<br>
--x-overview-dem-dist=n<br>
Use this option to add DEM also to the overview map. The value again gives the distance between two DEM points.<br>
It the option is not given or the value is 0 the creation of DEM data for the overview map is disabled. This might be needed for large areas and for overview img files which<br>
are already close to 16MB .<br>
Useful are probably values > 100000, e.g. 256000<br>
<br>
Expect to see "There is not enough room in a single garmin map for all the input data. The .osm file should be split into smaller pieces first."<br>
when experimenting with these options. The additional amount of bytes for the DEM files depend on the above options, and the relief of the area. Mountains<br>
require much more space compared to flat areas like the netherlands.<br>
If you have contour lines in your overview map try without.<br>
<br>
I'll try to add code to splitter so that it creates smaller tiles for areas with many mountains. I don't know yet how to store that info.<br>
<br>
Gerd<br>
______________________________<wbr>_________________<br>
mkgmap-dev mailing list<br>
</div></div><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><wbr><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.<wbr>mkgmap.org.uk</a>><br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">http://www.mkgmap.org.uk/<wbr>mailman/listinfo/mkgmap-dev</a><br>
<br>
</blockquote></div><br></div>
<pre class="blue"><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></pre></blockquote></div></body></html>