November 2017 - mkgmap-dev - The mkgmap lists

Re: [mkgmap-dev] Issues generating DEM
by Frank Stinner 27 Nov '17

27 Nov '17

Hi builddemfile users, in the versions from 23. and 26.11.2017 was an error in the encoder. I have it amended. Frank

2 1

Issues generating DEM
by Carlos Dávila 26 Nov '17

26 Nov '17

I have done some tests with BuildDEMFile (thanks Frank for providing it!), but with some problems. I have followed the procedure described by Gerd at [1]. What I have done is the following: 1-Try to generate a DEM for my Western-Sahara map with command wine ../../../../DEM/BuildDEMFile.exe --usedummydata=true -d 55132001/55132001.DEM --hgtpath=../../../../DEM/hgt/ --tre=55132001/55132001.TRE --dlon=0.00027761 Result: Daten aus der TRE-Datei '55132001/55132001.TRE' gelesen Höhen für -18° .. -17° / 20° .. 21° eingelesen ... 1 Zoomlevel erzeuge 31594 x 25790 interpolierte Höhenwerte für den Abstand 0,00027761° x 0,00027761°... Out of memory BuildDEMFile was using about 1 GB RAM when it stopped, while there was ~2 GB free available on system. How can I allocate more memory for BuildDEMFile? Western Sahara is very low mapped, so that a large area fits in a single img, but it covers 80 hgt files. Is there a size limit for DEM files and thus large areas should be split for img generation? 2-Try to generate a DEM for my region (Extremadura, Spain) with command wine ../../../../DEM/BuildDEMFile.exe --usedummydata=true -d 55113002/55113002.DEM --hgtpath=../../../../DEM/hgt/ --lastcolstd --tre=55113002/55113002.TRE --dlon=0.00027761 Result: Daten aus der TRE-Datei '55113002/55113002.TRE' gelesen Höhen für -8° .. -7° / 37° .. 38° eingelesen ... 1 Zoomlevel erzeuge 10560 x 9339 interpolierte Höhenwerte für den Abstand 0,00027761° x 0,00027761°... Daten 10560 x 9339, Min. 70, Max. 2577 für Zoomlevel 0 Value cannot be null. Parameter name: destinationArray What does it mean and how to fix it? 3-Try to generate a DEM for an small portion of my region (only 4 hgt files required) with the same command as previous Result: DEM created. [1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2017q4/027176.html

5 13

Re: [mkgmap-dev] BuildDEMFile problem
by Frank Stinner 23 Nov '17

23 Nov '17

Hi Nick, there are 2 little problems in your map mapdem.gmap. #1: I have rebuild your DEM file. Maybe, builddemfile had the N50E000.hgt.zip or N50E000.hgt not found and you have only "dummydata" in your file. "dummydata" means a valid DEM with "no data"-points. builddemfile --hgtpath=yourpath --dem=87827699.dem --tre=87827699.tre --dlon=0.00027777;0.00055555;0.00111110;0.00222221;0.00888884 create a DEM file with 23781 Byte. #2: Like Andrzej wrote: you need also a new TDB. I have used a quick but very dirty method: I have only for TDB-build temporary created the Tile IMG's ov.img and 87827699.img. gmtool -i mapdem\*.* --join=tile -o ov.img gmtool -i 87827699\*.* --join=tile -o 87827699.img gmtool -i *.img --mapsource=pid:1;fid:3927;cp:1252;ov:ov.img;tdb:neu.tdb;noov;notyp;nomdx;nomdr;noinst --mapfamilyname=mapdem --mapseriesname=mapdem --description="Test preview map" --routable=1 --highestroutable=24 --maxbits4overview=18 --hasdem=1 --hasprofile=1 --copyright=*I* -o . --overwrite ren mapdem.tdb mapdem.tdb_ ren neu.tdb mapdem.tdb del *.img Of course, in your little demo we can not see a shading. But we can see the values for N, E and height in the basecamp status line. By the way, be careful wit --usedummydata. It's only interest for sea-areas, where don't exist a HGT. But if a HGT for land is absent, we have a hole in our map without an error message! Frank

3 2

Re: [mkgmap-dev] BuildDEMFile problem
by Frank Stinner 23 Nov '17

23 Nov '17

Hi Nick, it's a really small piece. But 0,157° x 0,0685° and dlon=0,00027761 are about 565 x 246 points. That are a lot of 64x64 DEM tiles. I don't think, that's a problem. Can you put the ready card (still without DEM's) to http://www.pinns.co.uk/errs/ or whereever? What say mapsource to your map? Frank

3 4

BuildDEMFile problem
by nwillink 22 Nov '17

22 Nov '17

@ Frank I think I've come across a problem with the DEM subfile not being read by Basecamp. I've come across this whilst creating a map of the south east coast of the UK - the same may apply to Calais When I split the UK it does not show the dem files of Dover area - I created a small map.osm which may point to the problem http://www.pinns.co.uk/errs/map.zip <http://www.pinns.co.uk/errs/map.zip> DEM files are created but ignored by Basecamp Any ideas? r Nick -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

1 0

Re: [mkgmap-dev] DEM format Questions
by Frank Stinner 19 Nov '17

19 Nov '17

Hi Gerd, at first the good news. In the meantime i have build maps for Czech Republik, Germany, Austria, Switzerland and Italy, ever with 6 zoomlevels. I don't found an error. Of course, this is no evidence for the algorithm. And yes, there are a few mysterious things. I'm sure, what ever the garmin programmers done, they have found a very good compression for this special case. They don't waste a bit. But perhaps they think also to confuse all the snoopy guys on the world. Perhaps they say: hey let us take a special case, if the compression is not worse. I have no idea for the 158. I belief, we can see this as parameter. Perhaps garmin have found with trial and error, that 158 give smallest DEM's for a lot of areas on earth. Then it is more a "statistical" reason. By the way, the worst thing in my opinion is the rule for "Längencodierung". It is rather a "descriptiv" solution. Perhaps behind this is a more "mathematical theory", but i don't found it. Frank

2 2

Re: [mkgmap-dev] BuildDEMFile
by Frank Stinner 16 Nov '17

16 Nov '17

Hi Andrzej, i have the prog a little bit changed. Just it should be run. I don't know, what's going on with only 1 subtile column and a width < 64. If this not worked, i change it, so that we have in this case 64 points. If you have -w 0.90 and --dlon=0.0266666666666664, than there are only 34 points. Frank

2 1

BuildDEMFile
by Frank Stinner 16 Nov '17

16 Nov '17

Hi, there is a new version (8.11.2017), https://github.com/FSofTlpz/Garmin-DEM-Build/blob/master/BuildDEMFile/bin/B…. This version should be assume less memory. Reading HGT's should be faster. It seems, --lastcolstd isn't more necessary (?). By the way, the programm runs also with linux mint 18.2 and mono. Main options: -d, --dem=arg name of DEM-file, (e.g. 70210001.DEM) --hgtpath=arg directory for HGT's (zipped or not) --tre=arg name of TRE-file (e.g. 70210001.TRE) -o, --dlon=arg distance between DEM-Point (multiple usage for more zoomlevels) --usedummydata=arg use 'without-value' (0x8000), if one or more HGT's not present --lastcolstd=arg last subtile column has ever a width of 64 (need a little bit more memory on disk) -O, --overwrite=arg overwrite existing destination files or not -f, --foot=arg DEM data in foot or meter Frank --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

4 6

Re: [mkgmap-dev] DEM format Questions
by Frank Stinner 15 Nov '17

15 Nov '17

Hi Gerd, yes this is an error. Fortunately is the copy-constructor not in use. Frank

2 1

hgt2osm questions
by nwillink 13 Nov '17

13 Nov '17

@ Frank What a great tool for creating contour lines! 1) I'm having some success with your other great program,osm2hgt , however I fail to merge two or more .hgt files into a single osm . Am I doing something wrong? C:\Users\Owner\Desktop>E:\hgt2osm.exe --HgtPath=E:\Dem\All_UK_HGT_Data\ --Lat=49 --Lon=-3 --Outfile=e:\dev1.osm --Mergefile=e:\devonall2.osm C:\Users\Owner\Desktop>E:\hgt2osm.exe --HgtPath=E:\Dem\All_UK_HGT_Data\ --Lat=49 --Lon=-4 --Outfile=e:\dev2.osm --Mergefile=e:\devonall2.osm devonall2.osm doesn't seem to have merged both files. 2) I'm having to enter longitude data into --Lat and latitude into --Lon . Any reason why? 3) It hangs when there is no data , ie Hgt2Osm, 26.4.2017, FSofT 64 Bit-OS: ja Programmodus 64 Bit: ja MinorDistance: 20 MediumFactor: 5 MajorFactor: 5 HGT-Verzeichnis: E:\Dem\All_UK_HGT_Data\ Mergefile: e:\devonall2.osm OutputOverwrite: False Höhenkorrektur: -0.5 MinVerticePoints: 3 MinBoundingbox: 0.0005 Douglas-Peucker: 0.04 1. OSM-ID: -1 mit OSMBound: False mit OSMBounds: True mit OSMTimestamp: True mit OSMVersion: 1 mit OSMVisible: False max. Punktanzahl je Weg: 500 mit 'contour_ext'-Tag: True ==> Lese Ausgangsdaten 49° -4° ... Daten übernehmen ... Startzeit: 17:13:29 8 Threads übernehme 1201x1201 Werte für neue Matrix 1201x1201 ungültige Originalwerte: 0 (0.00%) berechne alle Strecken für Höhenlinien in 1440000 Rechtecken mit je 4 Dreiecken ... Laufzeit: 00:00:00 führe alle Strecken je Höhenebene eindeutig in einer Liste zusammen ... Laufzeit: 00:00:00 0 Höhenebenen von 2147483647 bis -2147483648 mit insgesamt 0 Strecken gebildet . .. -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

3 3