47
edits
Howto:Add procedures to the route manager: Difference between revisions
Jump to navigation
Jump to search
Howto:Add procedures to the route manager (view source)
Revision as of 18:06, 8 November 2023
, 8 November 2023Added description of Navigraph data extraction, from this post: https://forum.flightgear.org/viewtopic.php?f=11&t=37975&view=unread#p416078
(Remove wall of text, change 10 y.o. procedure file to actively updated one) Tags: Replaced Visual edit |
(Added description of Navigraph data extraction, from this post: https://forum.flightgear.org/viewtopic.php?f=11&t=37975&view=unread#p416078) |
||
| Line 141: | Line 141: | ||
This project uses GitHub Actions in order to automatically update the procedures at the start of a new AIRAC cycle. | This project uses GitHub Actions in order to automatically update the procedures at the start of a new AIRAC cycle. | ||
== References == | == Commercial sources== | ||
A process to import SID/STARs from Navigraph Level D (obtaining this data requires paid subscription to Navigraph) was described in this forum post: https://forum.flightgear.org/viewtopic.php?f=11&t=37975&start=15#p416078 | |||
Quoting here for reference: | |||
# Download Level-D navdata from Navigraph (On the Downloads -> Manual Download page) | |||
# This is ZIP file with a Windows Installer executable inside. If you're on Windows already, run the installer, select a version (Prepar3D/PD3) and then skip to step 4. | |||
# The executable is a Inno Setup executable. In Linux you can extract the contents with `innoextractor -e leveld_2311.exe` for example, which will output a "code$AppName" directory. | |||
# In the extracted directory you'll find a "navdata" folder containing XML files with procedures for all airports for the AIRAC cycle with filenames as "<ICAO>.xml". | |||
# You can either rename in bulk or single file from "<ICAO>.xml" to "<ICAO>.procedures.xml" for desired airports. | |||
# Create a new directory somewhere (anywhere you want) say "AIRAC/2311", and inside it create the "Airports" directory. (camel-case formatted - "airports" with small letter A didn't work for me) | |||
# Inside this "Airports" directory, create new subdirectories for each airport you want to bring in, using the [I]/[C]/[A] format. For example, if you want to add Vienna airport LOWW, create the subdirectories "Airports/L/O/W" - do not create the fourth subdirectory [W] (it won't work) | |||
# Copy the renamed file from step 5 into this last subdirectory. For example, copy "LOWW.procedures.xml" into "AIRAC/2311/Airports/L/O/W" directory, resulting in "AIRAC/2311/Airports/L/O/W/LOWW.procedures.xml". Example 2: for Budapest airport copy "LHBP.procedures.xml" into "AIRAC/2311/Airports/L/H/B", resulting in "AIRAC/2311/Airports/L/H/B/LHBP.procedures.xml" | |||
# In FlightGear, add the "AIRAC/2311" directory to your sceneries paths. | |||
# Reload FlightGear and enjoy SID/STARs in your MCDU | |||
==References== | |||
{{Appendix}} | {{Appendix}} | ||
== Related content == | ==Related content== | ||
=== Wiki articles === | ===Wiki articles=== | ||
* [[Route manager]] | *[[Route manager]] | ||
* [[Flightplan XML formats]] | *[[Flightplan XML formats]] | ||
=== Source code === | ===Source code=== | ||
* {{flightgear source|path=src/Navaids/LevelDXML.hxx}} | *{{flightgear source|path=src/Navaids/LevelDXML.hxx}} | ||
* {{flightgear source|path=src/Navaids/LevelDXML.cxx}} | *{{flightgear source|path=src/Navaids/LevelDXML.cxx}} | ||