Commit: r1576: There seems to be a way to show elevation profiles for a route without
Version 1576 was commited by steve on 2010-02-18 17:44:07 +0000 (Thu, 18 Feb 2010) There seems to be a way to show elevation profiles for a route without having the DEM subfiles stored in the map. There is a byte in TDB file's header section which can be set to 1. If set MapSource generates the profile from the contour lines. The result is not as good as having the full information from DEM subfiles but better than nothing. There is a new option "--show-profiles" to enable or disable this feature. Default is disabled. - Ronny Klier
svn commit (svn@mkgmap.org.uk) wrote:
Version 1576 was commited by steve on 2010-02-18 17:44:07 +0000 (Thu, 18 Feb 2010)
There seems to be a way to show elevation profiles for a route without having the DEM subfiles stored in the map. There is a byte in TDB file's header section which can be set to 1. If set MapSource generates the profile from the contour lines. The result is not as good as having the full information from DEM subfiles but better than nothing.
There is a new option "--show-profiles" to enable or disable this feature. Default is disabled.
How does this work? Does it still work if your contours are in a separate layer from the route-able ways? Does it assume that contours are defined by Garmin types 0x20, 0x21 and 0x22? If yes, then if you have a TYP file that uses these codes for something else, this option would go screwy, presumably? -- Charlie
On 18.02.2010 18:58, charlie@cferrero.net wrote:
svn commit (svn@mkgmap.org.uk) wrote:
Version 1576 was commited by steve on 2010-02-18 17:44:07 +0000 (Thu, 18 Feb 2010)
There seems to be a way to show elevation profiles for a route without having the DEM subfiles stored in the map. There is a byte in TDB file's header section which can be set to 1. If set MapSource generates the profile from the contour lines. The result is not as good as having the full information from DEM subfiles but better than nothing.
There is a new option "--show-profiles" to enable or disable this feature. Default is disabled.
How does this work? Does it still work if your contours are in a separate layer from the route-able ways?
No it has to be inside the same layer. Alternative is creating a second transparent contourlines mapset - which will work in Mapsource >6.14.1.
Does it assume that contours are defined by Garmin types 0x20, 0x21 and 0x22? If yes, then if you have a TYP file that uses these codes for something else, this option would go screwy, presumably?
Presumably yes. There is extended types so using fixed lines (0x20-25, 0x19???) for different stuff is a bad idea anyhow.
participants (3)
-
charlieï¼ cferrero.net -
Felix Hartmann -
svn commit