- mkgmap-dev - The mkgmap lists

mkgmap r4023 supports zipped hgt files
by Gerd Petermann 28 Dec '17

28 Dec '17

See http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4023 for details. Maybe I'll change the code again so that it doesn't extract the hgt file for each zoom level. Might be a bit faster. Gerd

1 0

mkgmap r4022 ready
by Gerd Petermann 28 Dec '17

28 Dec '17

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

5 7

Error BeNeLul
by Arndt Röhrig 26 Dec '17

26 Dec '17

4 9

dem not showing
by nwillink 24 Dec '17

24 Dec '17

Hi Gerd I've come across an issue with mkgmap-dem-tdb-r4013 It involves N51E000.hgt but perhaps any xxxE000.hgt It seems to create an empty dem - I came across the problem after splitting the UK - even with max nodes 800,000 I used this pbf : http://files.mkgmap.org.uk/download/376/maidstone.pbf Interestingly , Frank's program creates the correct DEM. r Nick -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

2 1

r4015 in dem-tdb branch implements --x-overview-dem-dist
by Gerd Petermann 24 Dec '17

24 Dec '17

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

4 3

WG: r4015 in dem-tdb branch implements --x-overview-dem-dist
by Gerd Petermann 23 Dec '17

23 Dec '17

Hi! I've just noticed that I replied to Minko instead of the list. Please see below. Gerd ________________________________________ Von: Gerd Petermann <gpetermann_muenchen(a)hotmail.com> Gesendet: Samstag, 23. Dezember 2017 12:04 An: lig fietser Betreff: AW: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist I am not sure what to think about that. When you use 3'' hgt files (size is ~2.8MB) the resolution in that data is 2^32/(360 * 1200) ~ 9942. When you use 1'' hgt files (size is ~26MB) the resolution in that data is 2^32/(360 * 3600) ~ 3314. The current implementation in mkgmap interpolates the values found in the hgt file. It assumes continous slope between two points at the same lat, so e.g. if one is 123 and the other is 135, it assumes that a point in the middle is at 129. I assumed that the Garmin algo does something similar when calculating the heights, but maybe it doesn't. I did not yet try to find out the best values for dem-dists, so it would be good to hear about results. Gerd ________________________________________ Von: lig fietser <ligfietser(a)hotmail.com> Gesendet: Samstag, 23. Dezember 2017 11:45:21 An: Gerd Petermann Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist Thanks Gerd, the value of 3312 works much better now! ________________________________ Van: Gerd Petermann <gpetermann_muenchen(a)hotmail.com> Verzonden: zaterdag 23 december 2017 02:36:32 Aan: lig fietser Onderwerp: AW: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist Hi Minko, to convert the parms for BuildDEMFile you have to multiply by 2^32/360 : 0.00027761 * 2^32/360 ~ 3312. Gerd ________________________________________ Von: lig fietser <ligfietser(a)hotmail.com> Gesendet: Samstag, 23. Dezember 2017 11:30:20 An: Gerd Petermann; Development list for mkgmap Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist Hi Gerd, Thanks for the good work to implement DEM into mkgmap! I have tested a few tiles, I noticed that BuildDEMFile with--dlon=0.00027761 has a much more detailed relief than the default values x-dem-dists=5520, 16560, 44176, 88368 How can I get the same results as with dlon=0.00027761?

3 2

Hillshading Details
by Arndt Röhrig 23 Dec '17

23 Dec '17

1 0

Re: [mkgmap-dev] r4015 in dem-tdb branch implements --x-overview-dem-dist
by Ervin Malicdem 23 Dec '17

23 Dec '17

Hi Gerd, This is regarding hillshade still being rendered even if the area was excluded in the osm file. As an example, I specifically removed borneo island in the southwest but DEM still showed up. https://www.dropbox.com/s/m6pdz90d3jo1unq/borneo.jpg?dl=0 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 4:08 PM, Gerd Petermann < gpetermann_muenchen(a)hotmail.com> wrote: > Hi Ervin, > > I think there is no longer a need to change splitter since DEM files are > allowed to grow > 16MB with r4016. > 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 > or in a *.DEM, and they contain the text "GARMIN DEM". I guess DEM means > something like "Digital Elevation Model". > Besides that I don't understand what you mean. Is it about the contour > lines created by tools like srtm2osm or phyghtmap? > What could be improved in splitter? > > Gerd > > ________________________________________ > Von: ebmalicdem(a)cxsmedia.com <ebmalicdem(a)cxsmedia.com> im Auftrag von > Ervin Malicdem <schadow1(a)gmail.com> > Gesendet: Samstag, 23. Dezember 2017 06:21:36 > An: Development list for mkgmap; gpetermann_muenchen(a)hotmail.com > Betreff: Re: [mkgmap-dev] r4015 in dem-tdb branch implements > --x-overview-dem-dist > > 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(a)hotmail.com<mailto: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(a)lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > >

5 4

DEM size in Garmin Basemap > 16MB
by Gerd Petermann 23 Dec '17

23 Dec '17

Hi, I've just noticed that the DEM file in my Oregon basemap (gmapbmap.img) is ~ 31MB. Up to now I thought that 16MB is either the limit for a single file in an img or for the whole img file. Both seems to be wrong. @Steve: The value is coded in BufferedImgFileWriter: // The maximum allowed file size. private long maxAllowedSize = 0xffffff; Is that an mkgmap limit or do you think that Garmin uses a special trick for the base map? Gerd

5 7

NullPointerExceptio
by andreas.schmidt.hetschbach＠t-online.de 22 Dec '17

22 Dec '17

Way 341306282 [highway=path, mkgmap:label:1=Path[?], mkgmap:unpaved=1, radweg=?] nach Way 341306281 [highway=path, mkgmap:residential=yes, mkgmap:unpaved=1, radweg=?] vor Way 341306281 [highway=path, mkgmap:label:1=Path[?], mkgmap:residential=yes, mkgmap:unpaved=1, radweg=?] nach Number of MapFailedExceptions: 0 Exception in thread "main" java.lang.NullPointerException at uk.me.parabola.mkgmap.combiners.OverviewBuilder.readPoints(OverviewBuilder.java:284) at uk.me.parabola.mkgmap.combiners.OverviewBuilder.readFileIntoOverview(OverviewBuilder.java:250) at uk.me.parabola.mkgmap.combiners.OverviewBuilder.onMapEnd(OverviewBuilder.java:84) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:588) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:128) at uk.me.parabola.mkgmap.main.Main.mainStart(Main.java:136) at uk.me.parabola.mkgmap.main.Main.main(Main.java:107) I built many maps so far – never got this error. What do I have to obtain for further analysis? java -Xmx1024m -jar ..\bin\mkgmap.jar --tdbfile --gmapi --max-jobs --generate-sea=extend-sea-sectors --add-pois-to-areas --route --latin1 --family-id=7012 --mapname=44000000 --product-id=1 --family-name=Andreas-Austria --index --order-by-decreasing-area --draw-priority=25 --style-file=".\style" .\typ\M07012.typ 6*.pbf C:\Garmin\bin\mkgmap-r3997 Regards Andreas Gesendet von Mail für Windows 10

2 7