tarbat is the man to tell you, but as he's not on the forum at the moment, I'll have a go then he can correct me :-)
Flight Display 6 (link above in tarbat's post) is a clever utility program originally written for the SBS-1 and Planeplotter - now modified to run without the SBS-1 so this version is Flight Display 6 for PlanePlotter (FD6PP)
PlanePlotter is an ADS-B display interface that will display and share data from RadarBox and the SBS-1
- RadarBox is run and a log recording started
- Planeplotter is run and set to display the live aircraft recorded to the log display (the aircraft will be shown in PlanePlotter 5 minutes delayed)
- FD6PP is run
- When you select an aircraft in the PlanePlotter display (double left click), FD6PP looks up the Flight ID in a number of on-line locations and attempts to resolve a route.
- If a route is found, it is displayed on the PlanePlotter screen and FD6PP writes the route to its own SQL database.
- After a whole load of double clicking, the FD6PP SQL database builds up a few routes.
The FD6SQL database can be loaded into an SQL editor such as SQLite Maestro, and the route information exported in a friendly format - I used CSV
The RadarBox NavDat.db3 can now be loaded and the routes csv file exported in the step above, can be imported into NavDat.db3
Phew, I think that's about it. So a fairly complicated way of populating the NavData.db3 routes table - but still much quicker than doing this manually.
So, what AirNav Development needs to do, is to incorporate a nice little routine that populates the route table in much the same way as the GAS database populates the aircraft table.
OK tarbat, that's my best effort, over to you for corrections :-)