| Meaning of example airport data (apt.dat) |
| Airport
header |
Example
Usage |
| |
1 1157 0 1 KSBD San Bernardino Intl
|
| 1 |
Identifies
this as an airport header line. Note that a code 16 will identify this as a
seaplane/float plane base, and a code 17
will identify it as a heliport. |
| 1157 |
Airport elevation (in feet above MSL).
|
| 0 |
Airport
has a control tower (1=yes, 0=no). Used by
X-Planes ATC
system. Not used to draw the default ATC tower building
(despite what is stated in WorldMaker!). |
| 1 |
Display
X-Planes default airport buildings (1=yes, 0=no). (No longer used) |
| KSBD |
Identifying code for the airport (the ICAO code, if one
exists). Must be unique
within an apt.dat file. If additional apt.dat files are being
used in custom scenery folders, then this ICAO code is used to match
airports between the files. Up to 6 characters are now supported,
but valid 4-character ICAO airport codes must be used if they are
available (PROPOSED FOR 9xx). |
| San
Bernadino Intl |
Airport
name. Can contain spaces Do not use special characters or single / double
quotation marks and apostrophes. Just plain text! |
| Runways |
Example
Usage |
| |
100 54.86 01 02 0.25 1 3 1 06 34.09073300 -117.25038500 0 304.8 3 0 1 2 24 34.099952 -117.219353 0 304.8 3 0 1 2
|
| 100 |
Identifies
this as a data line for a runway. |
| 54.86 |
Runway
width in metres (not feet). |
| 01 |
Runway
surface code for the
runway. The leading zero is optional. |
| 02 |
Runway
shoulder code. Here,
code 02 implies that there is a concrete runway
shoulder. |
| 0.25 |
Runway
smoothness. Used to cause bumps when taxiing or
rolling along the
runway in X-Plane. It is on a scale of 0.0 to 1.0, with 0.0 being
very smooth, and 1.0 being very, very rough. X-Plane determines a
baseline smoothness based upon the runway surface type, and then uses
this factor to determine the 'quality' of the runway surface. The
default value is 0.25. (Not yet supported in
X-Plane & proposed for 9xx) |
| 1 |
Runway
centre-line lights:
0 = No centre-line lights
1 = Has centre-line lights |
| 3 |
Runway
edge lighting. If any runway edge lighting exists, it also
implies that there is runway threshold lighting (red
towards a departing aeroplane, green towards
an landing aeroplane). Codes used are:
0 = No edge lights
1 = Low intensity runway lights (LIRL) (PROPOSED FOR 9xx)
2 = Medium intensity runway lights (MIRL)
3 = High Intensity Runway Lights (HIRL) (PROPOSED FOR 9xx) |
| 1 |
'Distance
remaining' signs. These
are the white letters on a black background on little illuminated signs
along a runway, indicating the number of thousands of feet of usable
runway that remain. They are inappropriate at small airports or
on most dirt, gravel or grass runways.
0 = No distance remaining signs
1 = Show distance remaining signs |
| |
|
| |
The
following rows are repeated for each end of the runway |
| 06 |
Runway
number for this end (eg 08 or 24R).
- If there is
no runway suffix (eg. L, R, or
C), then leave a blank.
- Always use leading zeros for single digit numbers (ie. "09", not "9").
- Runway numbers must always be
assigned. A future enhacement may allow "xxx" to be used in the
rare cases where no runway number
is assigned (nust be in lower case). Nothing will be displayed in
X-Plane.
(Proposed for 9xx)
|
| 34.09073300 |
Latitude
(in decimal degrees) of runway threshold at centreline. Up to
eight decimal places of precision are used. |
| -117.25038500 |
Longitude
(in
decimal degrees) of runway threshold at centreline. Up to eight decimal
places of precision are used. |
| 0 |
Length of
displaced threshold in metres. Note that the
displaced threshold length is included in the implied overall runway length
(ie. between the lat/lon of each runway end). |
| 304.8 |
Length
of stopway/blastpad/over-run at the approach end of runway 08 in metres. The stopway/blastpad/over-run is
usually marked with large yellow chevrons, and aeroplane movements are
not permitted. Note that the stopway length is excluded
from the implied overall runway length.
(ie. between the lat/lon of each runway end). |
| 3 |
Runway markings for the this end of the
runway (the white painted markings on the surface of the runway),
runway 08 in our example. Here, code 3 implies precision runway
markings (ie. there is an associated precision approach for the runway,
either an ILS or MLS). |
| 0 |
Approach lighting code for this end of the
runway. |
| 1 |
Runway touchdown-zone
lights (TDZL):
0 = No touchdown-zone lights
1 = Has touchdown-zone lights |
| 2 |
Runway End
Identifier Lights (REIL), white strobe lights at the threshold
to help identify the runway in an urban environment:
0 = No REIL.
1 = Has omni-directional REIL
2 = Has unidirectional REIL |
| Water
runway |
Example
Usage |
| |
101 49 1 08 35.04420900 -106.59855700 26 35.04420911 -106.59855711 |
| 101 |
Identifies this
as a data line for a water runway. |
| 49 |
Runway
width in metres (not feet). |
| 1 |
Indicates
if the runway should be marked with buoys bobbing in the water.
0 = No buoys
1 = Show buoys |
| |
The
following rows are repeated for each end of the runway |
| 08 |
Runway
number for this end (eg 08 or 24R).
This will not be used to display anything in X-Plane, but can be used
to position an aeroplane ready for takeoff on the runway.
- If there is
no runway suffix (eg. L, R, C
or "S"), then leave a blank.
- "XXX" can be used in the rare cases where no runway number
is assigned.
|
| 35.04420900 |
Latitude
(in decimal degrees) of runway threshold at centreline. Up to
eight decimal places of precision are used. |
| -106.59855700 |
Longitude
(in
decimal degrees) of runway threshold at centreline . Up to
eight decimal places of precision are used. |
| |
|
| Helipad |
Example
Usage |
| |
102 H1 34.10547800 -117.24249700 150.0 30.48 30.48 02 0 0 0.25 1
|
| 102 |
Identifies this
as a data line for a helipad. |
| H1 |
Designator for
this helipad. Must be unique at each airport in the format "Hn"
where n is an integer. |
| 35.10547800 |
Latitude
(in decimal degrees) of helipad centre. Up to
eight decimal places of precision are used. |
| -117.2429700 |
Longitude
(in
decimal degrees) of helipad centre. Up to
eight decimal places of precision are used. |
| 150.0 |
Heading
of the helipad in true decimal degrees. The helipad marking (eg.
the yellow "H") will be aligned with this heading. |
| 30.48 |
Helipad
length in metres (not feet). |
| 30.48 |
Helipad
width in metres (not feet). |
| 02 |
Helipad
surface code for the
runway. The leading zero is optional. |
| 0 |
Helipad markings. |
| 0 |
Helipad
shoulder code. Here,
code 0 implies that there is a no shoulder. |
| 0.25 |
Helipad
smoothness. Used to cause bumps when taxiing or
rolling along the
runway in X-Plane. It is on a scale of 0.0 to 1.0, with 0.0 being
very smooth, and 1.0 being very, very rough. X-Plane determines a
baseline smoothness based upon the runway surface type, and then uses
this factor to determine the 'quality' of the runway surface. The
default value is 0.25. |
| 1 |
Helipad
edge lighting:
0 = No edge lights
1 = Yellow edge lights
2 = White edge lights (PROPOSED FOR 9xx)
3 = Red edge lights (PROPOSED FOR 9xx) |
| |
|
| Pavement |
Example
Usage |
| |
110 1 0.25 70.0 Main Apron (asphalt)
|
| 110 |
Identifies this
row as a pavement chunk header, used to define chunks of pavement for
taxiways and aprons. Pavement can have holes included, and straight or curved line segments defining its
boundaries. There are important rules that
define how complex shapes must be structured. |
| 1 |
Pavement surface code. |
| 0.25 |
Pavement
roughness. Used to cause bumps when taxiing or rolling along the
runway in X-Plane. It is on a scale of 0.0 to 1.0, with 0.0 being
very smooth, and 1.0 being very, very rough. X-Plane determines a
baseline smoothness based upon the surface type, and then uses
this factor to determine the 'quality' of the runway surface. The
default value is 0.25. (PROPOSED FOR 9xx) |
| 70.0 |
Pavement texture
grain direction in true degrees - orientation of the texture applied to
this pavement chunk |
| Main Apron
(asphalt) |
Optional name for
this chunk. Not used by X-Plane, but can help organise the file. |
| Linear feature |
Example
Usage |
| |
120 Curve E->NW from alpha to echo
|
| 120
or 130 |
Identifies this
row as a linear feature header, used to define objects such as lines or
light strings, comprised of nodes that define one or more straight
or curved line segments. The type of linear feature might
vary along its length. If this is an airport boundary (code 130)
then it must be followed by segments that form a closed loop (ie.
terminate in segments with a line codes of type 113 or 114). There are important rules that
define how complex shapes must be structured.
|
| Curve E->NW from alpha to echo |
Optional name for
this linear feature. |
| Nodes |
Example
Usage |
| |
111 34.104321 -117.241397 3 102
|
| 111 |
Identifies
this row as a node. Possible codes are::
- 111 = Node (simple point).
- 112 = Node with Bezier control point.
- 113 = Node (close loop) point (to close a
pavement
boundary).
- 114 = Node (close loop) point with Bezier
control
point (to close a pavement boundary).
- 115 = Node (end) point to terminate a linear
feature (so has no descriptive codes).
- 116 = Node (end) point with Bezier control
point,
to terminate a linear feature (so has no descriptive codes).
Each set of nodes defining a pavement chunk must:
- Contain at least two nodes (111 - 114, 117).
- Terminate with a node type 113 or 114 or 118.
- Have only one terminating row.
Each set of nodes defining a linear feature must:
- Contain at least one node (111-112 or 115-116 or 117 or 119).
- Terminate with a node type 113 - 116 or 118 - 119.
- Have only one terminating row.
|
| 34.105357 |
[All]: Latitude of this node in decimal degrees. North is positive. |
| -117.240001 |
[All]: Longitude of
this node in decimal degrees. East is positive. |
| 34.105726 |
[112, 114, 116 ONLY, so
not in example data]: Latitude of Bezier control point in decimal degrees.
|
| -117.240006 |
[112, 114, 116 ONLY, so
not in example data]: Longitude of Bezier control point in decimal degrees. |
| |
[NOT for 115 or
116]: The following of parameter(s) can be repeated as often
as necessary to define multiple attributes of the linear feature
(eg. taxiway centre line and green centreline lights, or fences on airport boundaries). |
| 3 |
[NOT for terminating node, 115 or
116]: Code for a linear feature.
If we are defining a pavement boundary, then this might be a yellow
edge line (as in this example). If it's a linear feature, then this could be anything
(eg. a taxiway centre line, green centre-lights ...). |
| 102 |
[NOT for terminating node, 115 or
116]: Additional linear feature definition (102 = blue
taxiway edge lights). |
|
|
| VASI / PAPI / Wig-Wag |
Example
Usage |
| |
21 34.09186800 -117.24858100 2 070.36 3.0 16L VASI |
| 21 |
Identifies this
as a row for a VASI, PAPI or Wig-Wag. |
| 34.09186800 |
Latitude of
VASI/PAPI/Wig-Wag in decimal degrees. For PAPIs and Wig-Wags,
this is the centre of the display. For VASIs, this is the mid
point between the two VASI light units (or the centre unit for a
three-box VASI). |
| -117.24858100 |
Latitude of
VASI/PAPI/Wing-Wag in decimal degrees. For PAPIs and Wig-Wags,
this is the centre of the display. For VASIs, this is the mid
point between the two VASI light units (or the centre unit for a
three-box VASI). |
| 2 |
Indicator
type
type. Here,
code 2 corresponds to a VASI. If VASI/PAPI/Wig-Wag is required on
both
sides of a runway or taxiway, then two lines (with code 21) must be
created. |
| 070.36 |
Heading of
VASI/PAPI/Wig-wag in true decimal degrees. This is the heading of
an
aeroplane flying directly towards the VASI/PAPI, and should therefore
match the true heading of the associated runway. |
| 3.0 |
Visual glidepath
angle in degrees (typically 3.00). Use a value of 0.00 for Wig Wags. |
| 16L |
Runway number
to which this object relates. Used in the master database to
ensure objects are assigned to the appropriate runway. Ignored by
X-Plane, but is required to import data to the master database. (PROPOSED FOR 9xx - enforce / populate in WED) |
| VASI |
Description of type of lighting object represented. Ignored by X-Plane. |
| Taxiway signs |
Example
Usage |
| |
20 34.09210700 -117.25062000 0.00 0 2 {@L}A |
| 20 |
Identifies this
as a row for a taxiway sign. |
| 34.09210700 |
Latitude |
| -117.25062000 |
Longitude |
| 0.00 |
Orientation in
true degrees - heading of someone looking towards the front of the sign..
|
| 0 |
Taxiway sign style
(Not yet supported in X-Plane)
- use a default value of "0" for now
0 = Default value |
| 2 |
Taxiway sign size.
1 = Small taxiway sign
2 = Medium taxiway sign
3 = Large taxiway sign
4 = Large distance remaining sign
5 = Small distance remaining sign
|
| {@L}A |
Text of sign (specifications
for signs are here)
|
| Startup locations |
Example
Usage |
| |
15 34.09800200 -117.24417400 0.00 Stand 1
|
| 15 |
Identifies
this as a data line for an airport
location (code 15). Multiple locations
are allowed as separate data lines. Locations are used in X-Plane to
define gate positions, ramp locations etc. at which the simulator can be
started. |
| 35.09800200 |
Latitude
(in decimal degrees) of the location. |
| -117.24417400 |
Longitude
(in
decimal degrees) of the location. |
| 0.00 |
Heading
(in true degrees) of the aeroplane when placed at the location. |
| Stand 1 |
Name of location (will be displayed in X-Plane menus).
|
| Tower viewpoints |
Example
Usage |
| |
14 34.09726500 -117.24283100 200.00 1 ATC |
|
 |
| 14 |
Identifies
this as a data line for a tower viewpoint (code
14). Only a single tower viewpoint is permitted. |
| 35.09726500 |
Latitude
(in decimal degrees) of the viewpoint. |
| -117.24283100 |
Longitude
(in
decimal degrees) of the viewpoint. |
| 200.0 |
Height
(in feet) above ground level of viewpoint. |
| 1 |
Flag
to indicate if a control tower object should be drawn at this location
in X-Plane. 0=no tower, 1=draw tower. (No longer used, but retain for backward compatibility) |
| ATC |
Name
of this viewpoint.
|
| Airport light beacons |
Example
Usage |
| |
18 34.10110500 -117.24326600 1 BCN
|
| 18 |
Identifies
this as a data line for an airport light beacon (code
18). Note that if custom data is not defined, then
appropriate data will be generated automatically and included in
apt.dat. The light beacon types available (see list below) are in
accordance with the US AM (Aeronautical Information Manual) - other
types may be added to cater for other light beacons used in other
countries. |
| 34.10110500 |
Latitude
(in decimal degrees) of the light beacon. |
| -117.24326600 |
Longitude
(in
decimal degrees) of the light beacon. |
| 1 |
Identifies the
colours of the light beacon. Here
code 1 implies a standard
white-green flashing light. A beacon of type 0 (= no beacon) can
be used to suppress the automatic generation of a default beacon. |
| Light
beacon |
Name for this
light beacon (not used by X-Plane, but might be useful for file
documentation). |
| Airport windsocks |
Example
Usage |
| |
19 34.09270300 -117.24790700 1 WS
|
| 19 |
Identifies
this row as an airport windsock (code 19).
Note that:
- If custom data is not defined, then appropriate data will
be generated automatically by my data export algorithms and included
in apt.dat alongside the threshold of each runway.
- If at least one windsock is explicitly defined at an
airport, then no 'automatic' windsocks will be generated at that
airport.
- Multiple windsocks are allowed.
- If you do not want any windsocks at an airport,
then let me know in an e-mail and I will
suppress the generation of all automatic windsocks at that
airport.
|
| 34.09270300 |
Latitude
(in decimal degrees) of the airport windsock. |
| -117.24790700 |
Longitude
(in
decimal degrees) of the airport windsock. |
| 1 |
Windsock
lighting (1=illuminated, 0=not illuminated). |
| Windsock |
Name
for this windsock (not used by X-Plane but might be useful for file
documentation). |
| ATC
frequencies |
Example
Usage |
| |
51 12297 CTAF/UNICOM
|
| 51 |
Identifies
this as an airport ATC frequency line. Codes
in the 50 - 59 range are used to identity different ATC types. |
| 12297 |
Airport
ATC frequency, in Megahertz multiplied by 100 (ie. 122.97 MHz in this
example). |
| CTAF/UNICOM |
Name
of the ATC frequency. This is often an abbreviation (such as GND
for "Ground"). |
