X-Plane data file definitions

Airway data (awy.dat) 640 version


Scope
File structure
Changes from previous file versions
Example data and explanation

Return to the X-Plane File Definition home page


Scope

This document describes the file format and codes used in X-Plane's awy.dat file, 640 version.

File structure

The file structure is similar to all other X-Plane data files.

Here is an example of the two header lines, three airway segments and the file termination line:

I
600 Version - DAFIF data cycle 200502, build 1922, metadata AwyXP640, Copyright © 2005, Robin A. Peel (robin@xsquawkbox.net). This data is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program ("AptNavGNULicence.txt"); if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA. This product was developed using DAFIF (the Defense Aeronautical Flight Information File), a product of the US National Imagery and Mapping Agency (NIMA). NIMA requires the following warranty statements: (A) Under 10 U.S.C. 456, no civil action may be brought against the United States on the basis of the content of a navigational aid prepared or disseminated by either the former Defense Mapping Agency (DMA) or the National Imagery and Mapping Agency (NIMA). (B) The DAFIF product is provided "as is," and no warranty, express or implied, including, but not limited to the implied warranties of merchantability and fitness for particular purpose or arising by statute or otherwise in law or from a course of dealing or usage in trade, is made by NIMA as to the accuracy and functioning of the product. (C): Neither NIMA nor its personnel will be liable for any claims, losses, or damages arising from or connected with the use of this product. The user agrees to hold harmless the United States National Imagery and Mapping Agency. The user's sole and exclusive remedy is to stop using the DAFIF product.

ABCDE  32.283733 -106.898669 ABC    33.282503 -107.280542 2 180 450 J13
ABC    33.282503 -107.280542 DEF    35.043797 -106.816314 2 180 450 J13
DEF    35.043797 -106.816314 KLMNO  35.438056 -106.649536 2 180 450 J13-J14-J15
99

Sequencing of data is conceptually unimportant.  By default the segments are sorted by the initial "from" fix and then by the "to" fix.

Changes from previous file versions

Example data

Here is a simplified data fragment for three airway segments in awy.dat:


ABCDE  32.283733 -106.898669 ABC    33.282503 -107.280542 2 180 450 J13
ABC    33.282503 -107.280542 DEF    35.043797 -106.816314 2 180 450 J13
DEF    35.043797 -106.816314 KLMNO  35.438056 -106.649536 2 180 450 J13-J14-J15

The meaning of this data is (subject to change):

Meaning of example airway data (awy.dat 640 version)
Airway  example Example Usage
ABCDE Name of intersection or nav-aid at the beginning of this segment (the fix ABCDE in this example).
32.283733 Latitude of the beginning of this segment.
-106.898669 Longitude of the beginning of this segment.
ABC Name of intersection or nav-aid at the end of this segment (the nav-aid ABC in this example).
33.282503 Latitude of the end of this segment.
-107.280542 Longitude of the end of this segment.
2 This is a "High" airway (1 = "low", 2 = "high").  If an airway segment is both High and Low, then it should be listed twice (once in each category).  This determines if the airway is shown on X-Plane's "High Enroute" or "Low Enroute" charts.
180 Base of airway in hundreds of feet (18,000 feet in this example).
450 Top of airways in hundreds of feet (45,000 feet in this example).
J13 Airway segment name.  If multiple airways share this segment, then all names will be included separated by a hyphen (eg. "J13-J14-J15")

© Robin Peel, 2005.  Last updated March 29, 2005