Open tobiz opened 9 years ago
In development. I've used a single Track table. Each entry for a flight has a unique 'flight_no', the flight_no being held in the flights table entry for a flight. The track points for a flight are added to the table as they are received from flarmnet. It is then possible to select all the track points from the Track table for a specific flight using the flight_no. The selected track points are then used to create a .gpx file using a simple API. The file name is then added to the end of each row for a flight in the .csv file. It is likely the Track table will be large for each days set of flights, this may be a problem.
I've made some progress on this enhancement. It now produces a track for each flight saving them in .gpx files. I've checked that the .gpx files display correctly using a gpx file viewer. There are still a few issues and tests to run, I don't plan to upload this enhancement to github until I'm more confident it's ok.
I've had a request from my CFI to add tracks to each flight. This is possible but is a significant enhancement; I propose to investigate this when the basic system stabilises. My first thought is it will require a "Track" table to the database schema. Each (potential) flight table entry will have a Track table entry set up the sequence of records specifying time and position data entered when received from the server. Processing for real 'flights' should remain the same, the track data being pointed to from the flight record. Initial thoughts.