Hi Frank,
I think I was already using the latest version. Please try this one:
BuildDEMFile.exe -d 09940185.DEM --hgtpath=C:\hgt\ --usedummydata -l
18.1 -t 50.0 -w 0.90 -h 0.60
--dlon=8.333e-4;0.0017;0.0033;0.0067;0.0264
> Therefore
Hi Andrzej,
please try the last version. The version info is the same, but false! It's from
10.11.2017
I get with
builddemfile -O --dem=x.dem --hgtpath=%OSM_DATA%\srtm_zip -l 22.208450317 -t 53.638961792 -w 0.946884155273438 -h 1.9918212891
--dlon=0.0017 --dlon=0.00
Hi Frank,
thanks for great program! I have added DEM to my map and it works well.
I have noticed 2 glitches:
When using option --mt program sometime stops working. No crash, no use
of CPU, it looks stalled. No problem without --mt.
Sometimes program crashes, when DEM raster is too small. Not
Hi Frank,
some years ago I worked for a company which (still) produces software that -
besides others - analyses mainframe data structures, e.g. the data stored by
different schedulers which are
used to plan jobs. These schedulers allow to say e.g. "my job should be
executed every 2nd work day"
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 g
Hi Frank,
during the last days I tried again and again to implement the decoder in
DemDisplay, but somehow I have the impression that
your findings are either too complex or still incomplete. Up to now I found
most of the special encodings used by Garmin somehow
clever, but I don't see that (yet
