Matthijs
Matthijs
now HC is not analyzed, because then the rank will not be an int, can be solved with string ranking edit: maybe better to use ints 0, -1, -2 etc...
there is a slight discrepancy between SeeYou and PySoar on the calculation of outlanding distance: http://www.soaringspot.com/en_gb/cae-nls-nederlandse-kampioenschappen-zweefvliegen-2012/results/club/task-10-on-2012-05-26/daily
http://www.soaringspot.com/en_gb/34th-wgc2016/results/club/task-9-on-2016-08-12/daily flight 6 DC has seemingly too high excess distance values. main source is leg 1. pilot notes that the logger is rebooted in flight, but that seeyou doesnt show...
http://www.soaringspot.com/en_gb/34th-wgc2016/results/club/task-2-on-2016-08-02/daily ranking 7MF, leg 3 pilot received warning on logger interval?
In this competition: http://www.soaringspot.com/en_gb/54th-australian-nationals-ozglide-benalla-gld-2016/results/18-meter/task-5-on-2016-01-10/daily No 20 - V2 incorrect values: cruise speed 570, avg LD 122 etc
on analysis check whetheter there is a valid internet connection: http://stackoverflow.com/questions/3764291/checking-network-connection#3764660
This is only possible with ctrl-c, ctrl-v. Right click doesn't work, but should.
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...