Re: [Gpsbabel-misc] negative elevations in Topo format

[tsteven4 <tst...@gm...>]

It appears to be a TOPO! bug that the TOPO! created gpx file listed the 
altitude as -32768 for the waypoint with unknown altitude.
This corresponds to the value encoded in the file (0xffce0000), which is 
different from the value checked in the original code (0xfffd000c).
Based on your test case I changed the code to filter out the -32768 
values as unknown altitudes, this results in different gpx output than 
created by TOPO! 4.5.0.

fixes:
for TOPO versions older than 3, and TOPO versions 3 and newer, don't use 
an altitude of zero for unknown as this represents a valid altitude.
for TOPO versions 3 and newer don't truncate the fractional part of 
altitude.
for TOPO versions 3 and newer correctly convert negative altitudes.
for TOPO versions 3 and newer change the value used to check for unknown 
altitudes.


You can either figure out how to build again or wait for the next release.


On 3/26/2016 9:17 PM, SRE wrote:
> At 08:38 AM 3/26/2016, you wrote:
>> can you supply a short tpo file with a waypoint that has unknown altitude?
>>
>> Sure. I don't know of a way to enter one, but if you copy from somewhere
>> else and paste into an open file it remains undefined. (That's why it is
>> quite some distance from my other test waypoints.)
>>
>> Attached are the same three files, but this time the waypoint names are
>> in meters except the new "UnknownElevation" waypoint.