logo separator

[mkgmap-dev] DEM format Questions

From Gerd Petermann gpetermann_muenchen at hotmail.com on Wed Nov 15 09:31:07 GMT 2017

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) in the DEM encoding. All the special cases for hunit calculation seem so arbitrarily.
Of course I could use your c# code and translate it to Java, but I'd prefer to really understand what it does - or better -
I'd like to think that I understand what the programmers at Garmin thought when they developed this.
Example: I still don't understand why 158 (or 0x9e) is a threshold value.
What makes it special?


Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Frank Stinner <frank.stinner at leipzig.de>
Gesendet: Montag, 13. November 2017 12:43:49
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] DEM format Questions

Hi Gerd,

yes this is an error. Fortunately is the copy-constructor not in use.


More information about the mkgmap-dev mailing list