GliderGeek
commented
8 years ago Steps for analysis of bug
- [x] check with SeeYou whether same b-record is indicated as outlanding location
- [ ] check whether using the same b_record will provide the same distance
- [ ] check whether different projection is reason for discrepancy (using final bearing instead of initial bearing)
SU flight in SeeYou:
SU outlanding b-record from PySoar: B1444335225612N00621722EA001490023400309
- t = 14:44:33 UTC = 16:44:33 LT
b-record in IGC file which corresponds to SeeYou outlanding location: B1444435225573N00621985EA001250020600309
This is happening for sallandse tweedaagse 2014, club class: http://www.soaringspot.com/en/sallandse-tweedaagse-2014/results/club/task-1-on-2014-06-21/daily
SU gets an outlanding distance of 89.99km on soaringspot, while pysoar gives 91.04. Minor difference, but still strange.
