Phases and engine runs
| Platform | Status | Where |
|---|---|---|
| iOS | done | vulture-ios/Packages/Flights/Sources/Flights/Enricher/FlightPhasesEnricher.swiftvulture-ios/Packages/Flights/Sources/Flights/Enricher/FlightTimesEnricher.swiftvulture-ios/Packages/Flights/Sources/Flights/Models |
| Android | done | vulture-android/domain/flightvulture-android/feature/flightdetailFIXED(Q1), FIXED(Q2), FIXED(Q3) in the time detection. |
Behaviour
Section titled “Behaviour”- The analysis finds take-off, release, glides, thermals and landing, and lists them as phases.
- Each phase can be centred on the map and selected for the barogram.
- Engine runs are detected from the ENL and MOP extensions of the IGC file and shown as events.
- The thresholds depend on the sport (Sport detection).
Platform differences
Section titled “Platform differences”- Android fixes landing detection (Q1), the release index (Q2) and the midnight UTC wrap (Q3); iOS fixes were requested. Other domain quirks are copied as
PARITY(decisions §1). - Parity between the platforms is checked with golden data exported from iOS.
Related
Section titled “Related”- Thermals on the map, Race ranking
- Flight analysis §5 (times, thermals, glides and legs), §2.5–2.6
- Port decisions §1