Pressure altitude correction based on takeoff elevation #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jkretz
force-pushed
the
takeoff_elevation_correction
branch
from
f7b4131
to
b8d955a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR picks up #161 in the PySoar repo.
Instead of manually entering takeoff elevation, it reads it from the igc file, as soaringspot writes takeoff elevation into the file (see
LCU::HPELVELEVATION). An altitude correction is calculated by comparing it to the median pre-takeoff pressure altitude. Pre-takeoff fixes are determined via a groundspeed threshold.This correction is subsequently applied to all pressure altitudes in
task_results, resulting in better comparability in altitudes at turnpoints.