Height loss during circling with GPS altitude

[GliderGeek]

GPS altitude might be too inaccurate to yield proper results for this performance indicator (using height difference between two consecutive fixes. Maybe a warning should be shown when the gps height is used instead of the baro height.

[roeles]

Individual fixes might not work, but something like least-squares should work. If you're limited to incremental parsing of the IGC files, you might use a simple kalman-filter or low-pass filter to smoothen data.

On Sun, Jan 3, 2016 at 12:32 AM, GliderGeek [email protected] wrote:

GPS altitude might be too inaccurate to yield proper results for this performance indicator (using height difference between two consecutive fixes Maybe a warning should be shown when the gps height is used instead of the baro height

— Reply to this email directly or view it on GitHub https://github.com/GliderGeek/PySoar/issues/41.