r4015 in dem-tdb branch implements --x-overview-dem-dist
Hi, okay, so we now have three new (still undocumented options) to enable hillshading and calculation of elevation data in routes. Here is a summary of the new options: --x-dem=path_to_dir[,path_to_other_dir,...] gives one or more directories containing *.hgt files. --x-dem-dists=n1,n2,n3,... Sample from a Garmin Demo map: --x-dem-dists="5520, 16560, 44176, 88368" should contain one number for each level in case you want to use the DEM data in a gmapsupp, the values give the number of DEM units between two points. A DEM unit is 360° / 2 ^32. The higher the numbers the smaller the DEM file. Useful values for level 0 start 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 level based on the resolution of the hgt files. --x-overview-dem-dist=n Use this option to add DEM also to the overview map. The value again gives the distance between two DEM points. 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 are already close to 16MB . Useful are probably values > 100000, e.g. 256000 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." 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 require much more space compared to flat areas like the netherlands. If you have contour lines in your overview map try without. 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. Gerd
Getting better each time! Great! A suggestion once you will be working with splitter is for the dem to be cut using a poly file as well. Ervin M. *Schadow1 Expeditions* - A Filipino must not be a stranger to his own motherland. http://www.s1expeditions.com On Sat, Dec 23, 2017 at 12:11 AM, Gerd Petermann < GPetermann_muenchen@hotmail.com> wrote:
Hi,
okay, so we now have three new (still undocumented options) to enable hillshading and calculation of elevation data in routes. Here is a summary of the new options:
--x-dem=path_to_dir[,path_to_other_dir,...] gives one or more directories containing *.hgt files. --x-dem-dists=n1,n2,n3,... Sample from a Garmin Demo map: --x-dem-dists="5520, 16560, 44176, 88368" should contain one number for each level in case you want to use the DEM data in a gmapsupp, the values give the number of DEM units between two points. A DEM unit is 360° / 2 ^32. The higher the numbers the smaller the DEM file. Useful values for level 0 start 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 level based on the resolution of the hgt files. --x-overview-dem-dist=n Use this option to add DEM also to the overview map. The value again gives the distance between two DEM points. 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 are already close to 16MB . Useful are probably values > 100000, e.g. 256000
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." 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 require much more space compared to flat areas like the netherlands. If you have contour lines in your overview map try without.
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.
Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, after thinking a while about overview-dem and it's not really logical to me. Mainly the proposed x-overview-dem-dist=0 isn't really intuitive. I should have thought more better before proposing it. It would be better to have a separate parameter -x-dem-overview=yes/no, where yes is default when DEM is activated. I will try to find a value for overview DEM with my maps. Keep you posted. Henning
Hi Henning, currrent implememtation is that DEM is only added to the overview map if x-overview-dem-dist is given and has a value > 0. My Oregon 600 basemap has multiple levels : 276160,552336,1104672 the older 450t only one with 276160. So, maybe I should change the default so that DEM is added to the overwview map with 276160 and the option allows to use a smaller value (=higher resolution) ? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Henning Scholland <osm@hscholland.de> Gesendet: Sonntag, 24. Dezember 2017 05:50:35 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist Hi Gerd, after thinking a while about overview-dem and it's not really logical to me. Mainly the proposed x-overview-dem-dist=0 isn't really intuitive. I should have thought more better before proposing it. It would be better to have a separate parameter -x-dem-overview=yes/no, where yes is default when DEM is activated. I will try to find a value for overview DEM with my maps. Keep you posted. Henning _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (4)
-
Ervin Malicdem -
Gerd Petermann -
Gerd Petermann
-
Henning Scholland