aoi - World Traffic 3 Airport Operations Importer tool

[snomhf 14]

Here is a little utility that creates an airport operations file for World Traffic 3.  It requires an install of Python 3.7 to run.  It builds on the fine work done by Markus Ferrer (markus@mfurrer.de).  Many thanks Markus!

#  World Traffic Airport Operations File Importer
#
#      This program starts with the ICAO of the airport you wish to create an AO file for
#      then scans your 'Custom Scenery' folder for the airport and if not found it will search the
#      'Custom Scenery/Global Airports'.  In no flow rules exist for the airport, a basic "skeleton"
#      AO file is generated and the program will simply terminate.
#
#      Note:
#       The new file 'icao'.txt will be written to
#       'X-Plane 11'/ClassicJetSimUtils/WorldTraffic/AirportOperations
#
#       If an existing 'icao'.txt file is found, it will be renamed to a time-stamped version
#       (e.g. KSAN.txt --> KSAN_1562810149.87901.txt) before creating the file.  This assures that
#       even if you run this program over and over, nothing will get lost.
#
#      In addition to the flow rules extracted from the apt.dat file,
#      the Navigraph data that is included in the WT3 product is used to determine the various
#      "Supported Approaches" in the Runway table.  Each approach name is preceded by a three-letter
#      code that describes the approach type.   Scanning all the files in the
#      "ClassicJetSimUtils/NavigraphData" directory yielded 14 unique codes.  A degree of quessing
#      produced the following table used to fill in the "Supported Approaches" portion of the Runway
#      table:
#               Code    Approach Type   WT3 Code                Code    Approach Type    WT3 Code
#               --------------------------------                ---------------------------------
#               GLS     ILS/DME             2                   NDB     Non-precision       1
#               GPS     RNAV                3                   NDM     Non-precision       1
#               IGS     ILS/DME             2                   RNV     RNAV                3
#               ILS     ILS/DME             2                   SDF     Non-precision       1
#               LBC     Non-precision       1                   TAC     Non-precision       1
#               LDA     Non-precision       1                   VDM     Non-precision       1
#               LOC     Non-precision       1                   VOR     Non-precision       1
#
#
#      The following data structures are created in which to extract the information necessary to
#      build the airport operations file.
#
#           flowRules - Built from apt.dat and consists of a list indexed by "Ops Index".  This
#                       structure is used to create the "OPERATIONS", "RUNWAY OPERATIONS" and the
#                       "Runway" and "Supported AC Types" sections of the "RUNWAYS" tables.
#
#           These structures were built from the ClassicJetSimUtils/NavigraphData files:
#
#           APPRs -     Contains the Approach Procedures.  The first three letters of the procedure
#                       name (e.g. "ILS08L") is used to create columns "1 2 3" of the
#                       "Supported Approaches" portion of the "RUNWAYS" table.  Columns "4 5 6" (CAT
#                       II/III) were created by reading the "CAT_II_III.txt" file. Columns "7 8" are
#                       always set to 0.  The "Final Approach Angle" and "Final Approach Distance Nm"
#                       portion of the "RUNWAYS" table are left blank.
#
#                       APPRs is also used to create the Navigraph "APPROACH SETTINGS" table.
#
#           STARs -     Contains the STAR procedures.
#
#           SIDs -      Contains the SID procedures.
#
#       The "PCT GATES USED" table is created from the Percentage variable in aoi.ini.
#
#       The "TIME BUFFERS" table gets the runway information from the  flowRules structure and the
#       "TIME BUFFERS" comes from the TimeBuffers variable in aoi.ini.   The same value is used for
#       all runways.   This table will need to be modified if times are different for the different
#       runways.   Not enough information is available to make this more useful.
#
#       The "FLIGHTS PER DAY" table is left blank.
#
#   NOTES:
#       No "Catch-All" rule was added because it could not be reasonably determined which runways to
#       use.  If you find that the rules read from the apt.dat file are not adequate, you may need to
#       "close the gap" either with tighter rules or add your own catch-all rule.  Most airport authors
#       who bother to include airport rules usually take care of this.
#
#       Great care was taken to make sure no data gets lost because of running this program.  Before
#       a new Airport Ops file is created,  if an old one already exists, it gets renamed using a
#       unique time stamp.   If you see AO files with really long numbers in their names, these are
#       backup files and can be deleted if your AO file looks good.
#
#       Though this program tries hard to get everything right, there may still be the need to edit
#       the AO file by hand and fix anything it doesn't get right.   One example is KATL.  The
#       Navigraph data does not appear to contain any non-precision approach procedures for KATL.
#       This is because the approach plates for ILS approaches also cover the localizer non-precision
#       approach.  Since the Navigraph data for ILS approaches do not mention this, there is no way in
#       a program to tell these approaches do this double duty. One of these is named "ILS OR LOC RWY 08L"
#       in the approach plate but the Navigraph procedure is simply named "ISL08L" therefore there is no
#       way to know this procedure also covers a non-precision approach.  Thus the program leaves
#       column 1 of the "Supported Approaches" portion of the "RUNWAYS TABLE" set to 0 instead of 1.
#       Hand editing is required to fix this.

Enjoy

-mark

http://snomhf.exofire.net/data/aoi_v1.0.zip