XPNAV1100, 11, as explained further down.ARINC 424 supplements 18 up to 20, with the exceptions noted in the FAA/Aeronautical Information Services CIFP Readme.X-Plane 11 and 12 support two formats in which the global database can be provided: X-Plane enforces integrity of this unique index, because it is needed to build the graph of the airway network. Only then it is possible to build the layered structure. See ICAO document No 7910 for details.īy classification into terminal vs global items and assigning the correct parent terminal area or ICAO region, each item in the database is addressable by a globally unique identifier. Note especially the seven regions defined for the continental United States. All fixes and navaids must specify the region ICAO code according to the 424.20 5.14 ICAO code. Terminal fixes and navaids must specify the arpt/heli ident of their terminal area, according to the 424.20 5.6 Airport/Heliport Identifier. X-Plane 11 and 12 distinguish between global and terminal fixes and navaids. If you find an airport with these values missing or incorrect, use WED 1.5 or later to add/edit these values and upload your change to the scenery gateway.Īs of X-Plane 12, the airport data is located in $X-Plane/Global Scenery/Global Airports/Earth nav data/apt.dat and is the one and only source for both scenery and GPS data, so what you see is what you get. Note that this data is already populated for most airports in the scenery gateway. transition_level, this must specify the transition level in feet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |