-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse and handle AIRAC and NAVDATA #13
Comments
I'd recommend getting AIRAC data from FAA NASR subscription. We'll need to parse xsd into json schema and optionally, map it to a custom structure. |
If we're only using the FAA navdata, how would we handle data for aircraft originating within the (300?) mile range, but outside the US? Example: a Boston event with someone originating from Montreal. |
In that case, I guess the optimal solution would be using Navigraph. It's consolidated and well-understood by most flight sim developers. We just need to figure out what kinds of paperwork to sign and how much we'd have to pay. |
https://navigraph.com/community/developer-info |
We’ve been wanting to use Navigraph data for internal use before. @Umar-Ashraf1 Do you want to reach out to them, or should I? |
In order to calculate flight times on airplane routes, we need AIRAC and NAVDATA.
We can get a list of all airports, FIRs and UIRs from vatsim/vatspy-data-project
For AIRAC data, we need to get it from the FAA, or Navigraph?
The text was updated successfully, but these errors were encountered: