Hi, there is a new BuildDEMFile-version with a rectified encoder. This should help on maps with strong changes in height. Example: East 79,335° / North 42,554°, PointDistance 55000 -> 0,004610° Hi Gerd, there seems to be a limitation for my variable "sumH" for the calculation of hunit. Perhaps garmin use only a 2-byte-var. I have included in CodingTypeStd.addValue() after "SumH += dh;": if (SumH + unitdelta + 1 >= 0xFFFF) SumH -= 0x10000; I have no idea, why not "if (SumH + unitdelta > 0xFFFF)" or so. I have done the same with CodingTypePlateauFollowerNotZero.AddValue() and CodingTypePlateauFollowerZero.AddValue(). Frank
Hi Frank, great! I've already noticed it some hours ago and tested the changes in mkgmap. Commetted with r4041. See http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&path=%2F& Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Frank Stinner <frank.stinner@leipzig.de> Gesendet: Dienstag, 9. Januar 2018 11:40:33 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: [mkgmap-dev] one mistake less in DEM Hi, there is a new BuildDEMFile-version with a rectified encoder. This should help on maps with strong changes in height. Example: East 79,335° / North 42,554°, PointDistance 55000 -> 0,004610° Hi Gerd, there seems to be a limitation for my variable "sumH" for the calculation of hunit. Perhaps garmin use only a 2-byte-var. I have included in CodingTypeStd.addValue() after "SumH += dh;": if (SumH + unitdelta + 1 >= 0xFFFF) SumH -= 0x10000; I have no idea, why not "if (SumH + unitdelta > 0xFFFF)" or so. I have done the same with CodingTypePlateauFollowerNotZero.AddValue() and CodingTypePlateauFollowerZero.AddValue(). Frank
participants (2)
-
Frank Stinner -
Gerd Petermann