Question/Issue on Altitude - something seen on V2 and V3 Beta.
Why do some get logged in MyLog with leading zeros, and some that don't
Example, I have Start Altitude of 00095 on 19/06/09 for D-ABIM then 20 on 19/6/09, and then on 14/7/09 I have this as 01100.
Then in MyFlights, if I filter on Altitude < 5000, I get everthing, and just worked out that that needs to be < 05000, but in the Altitude field in MyFlights they don't have a leading zero.
I would assume Altitude is logged in the database as a numeric field, so should be fairly straight forward to program this, and any Altitude to have 'ToNum' applied to it, regardless of what comes from the ADSB info.
Rick