Add support for Avitab NAV data held in a SQLite database #200
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a relatively large feature addition that has been hinted at in several previous PRs, and is finally now being requested, having reached a state of (more-or-less) equivalent behaviour with the existing in-memory NAV data scraped from the simulator installation files on each Avitab startup.
In its current version, the new feature will remain inactive unless the Avitab user installs a compatible SQLite database file with the correct name, in the correct place, and with the correct structure. Since this is unlikely to be done accidentally, this PR should be relatively harmless to incorporate into the Avitab repo, and this PR is really to help tidy-up my fork of the Avitab master, and reduce the size of future updates.
For advanced users who wish to try using the feature, the code base now includes a tool which is able to generate an Avitab-compatible SQLite database file from a Little Navmap database. This is the first (and easiest) technique for database generation. It is planned to support other techniques in the future.