Firstly, Dave, Great piece of work, thank you, allows so much visibility of the data we have in the track files.
Some enhancement thoughts:
- showing some stats about the file loaded, file name, start time, end time, etc
- showing some more stats about each aircraft as clicked on - 1st point time, last point time.
- showing some info about altitude of each point - colours?
- option to show all points - very useful to see more about when the aircraft *stops* being seen.
It is interesting to think about interpreting the data - it is more about what data *can't* you receive, the idea of trying to create a 'polar' plot is great, but has its limits when trying to think about the relative blind spots of a moving aircraft vs a base station.
Alan - Does the file your loading have any aircraft points in it? I have one 50Mb file that has no aircraft in it (ADSB antenna was not connected and it was on the ground) and I didn't realise it had actually loaded, as it has nothing to show.
An interesting piece of data I found in one of my track files:
$ cat 2016-07-02_10-23.trk | grep BSRI | grep '#G-BSRI#' | wc -l
114
$ cat 2016-07-02_10-23.trk | grep BSRI | grep '#GBSRI#' | wc -l
114
$ cat 2016-07-02_10-23.trk | grep BSRI | grep 'G-BSRI' | wc -l
676
$ cat 2016-07-02_10-23.trk | grep BSRI | grep 'GBSRI' | wc -l
592
I doubt BSRI really has 2 transponders and 2 PAW's, with G-BSRI and GBSRI configured respectivley. A bug somewhere?
Cheers
Kev
