Debian Codegraph @

tools/faaairports/README.txt

raw
1 This directory contains the "faaairports" program that parses the U.S. FAA
2 airports data base, as available in textual format from
3
4 https://nfdc.faa.gov/xwiki/bin/view/NFDC
5
6 and generate a valid ACM scenery file for each given range of latitude and
7 longitude.
8
9 Some Bash scripts are also included to create the basic sceneries included in
10 the distributed package.
11
12
13 Syntax of the command
14 =====================
15 Lline continuation char '\' added for readability:
16
17 faaairports.exe \
18 --lat-min LAT_MIN \
19 --lat-max LAT_MAX \
20 --lon-min LON_MIN \
21 --lon-max LON_MAX \
22 --src-dir DIR_FAA_DB
23
24 where:
25
26 LAT_MIN, LAT_MAX, LON_MIN, LON_MAX is the range of latitude and longiture
27 of the items to extract (more about this next). The syntax is that usual,
28 examples: 10.5N 10-30N 10-30-00.000N 96W etc.
29
30 DIR_FAA_DB is the directory containing the FAA data base in its textual
31 format. The following files are read from that directory: APT.txt,
32 ILS.txt, NAV.txt.
33
34 The resulting ACM scenery file is written on standard output, while errors are
35 sent to standard error.
36
37
38 Features
39 ========
40
41 An item located at (lat,lon) is included in the generated output only if lies in
42 the indicated range of latitude and longitude, that is:
43
44 LAT_MIN <= lat < LAT_MAX and
45 LON_MIN <= lon < LON_MAX
46
47 Note that there is no way to include an item if it is located exactly at the
48 north pole; this does not seem to be a severe limitation, though.
49 Items located exactly on the 180E meridian are excluded too, but it seems
50 there are not items there in the U.S. FAA data base.
51
52 VOR and NDB are included if their location is in the range; the possible DME, if
53 any, does not matter as under ACM the location of this latter must coincide with
54 its respective VOR or NDB antenna.
55
56 ILS are included based on the location of the LOCATOR antenna only; the locations
57 of the associate GS and DME attennas do not matter.
58
59 Runways are included if their middle point lies in the range.
60
61 For runways very close to the edges of the zone it may happen some related ILS be
62 missing from the resulting scenery because it falls outside the zone; this is not
63 a problem for acm.exe because nearby zones are loaded (if available!), but it is
64 a problem for the chart program which can "see" only one scenery at a time.
65
66
67 Issues
68 ======
69
70 Precise ILS bearing determination.
71 ----------------------------------
72 For each ILS, its magnetic bearing MH is provided with a very hight accuracy of
73 0.01 DEG, but the corresponding magnetic deviation VAR is given with only 1 DEG
74 of precision; the resulting calculated true bearing TH=MH+VAR is then affected
75 by a quite large error of 1 DEG, which means 32 m of deviation for a runway
76 1 NM long. To fix this issue and allow the airplane to land closer to the middle
77 of the runway, the following heuristic applies:
78
79 The program also calculates the true bearing TH2 as the bearing of the line
80 joining the locator to the served runway end position, if available.
81 If this TH2 differs less than 1 DEG from the nominal TH, the difference is
82 assumed to be due to the issue above only, and this calculated TH2 overrides
83 the nominal value TH.
84 Otherwise, if the calculated TH2 differs more than 1 DEG, the difference cannot
85 be due to a rounding problem of the VAR, and the nominal TH is kept; a warning
86 is displayed for precision approaches ILSs. SDF and LDA are assumed non-precision
87 approaches.
88
89
90 ILS name "I-XXX" silently changed to "IXXX" to comply with ACM requirements.
91 ----------------------------------------------------------------------------
92
93
94 ILSs beams width is mostly missing.
95 -----------------------------------
96 If beam width is missing, 5 DEG is silently assumed.
97
98
99 Cope with current ACM ILS record limitations.
100 ---------------------------------------------
101 In the real world an ILS consists of up to 3 antennas: locator, GS and DME.
102 Each antenna has its own location (latitude and longitude) and its own
103 elevation. Unfortunately, the current format of the ACM ILS record allows to
104 specify the location of the locator and GS and provides only one elevation
105 field; distance is calculated using locator location + available elevation;
106 landing point is calculated using GS location + available elevation.
107 We remedy as follows depending on the type of ILS:
108
109 1. LOCATOR only ILS. No problem at all; the elevation field is set with the
110 elevation of the locator.
111
112 2. LOCATOR + GS. Elevation field is set with the GS elevation for precise
113 touch down point simulation; actual locator altitude is usually very close
114 and does not care too much anyway.
115
116 3. LOCATOR + DME. ACM assumes the DME antenna coincides with the locator,
117 which is already a source of error for precise distance measurement;
118 to mitigate this, the elevation field is set with the actual DME elevation;
119 actual locator altitude is usually very close and does not care too much
120 anyway.
121
122 4. LOCATOR + GS + DME. Just like LOCATOR + GS for precise touch down point.
123
124 Further complication: the elevation field is blank in many cases, so we
125 take the value available in the following order of preference:
126 GS, DME, LOCATOR. If no value available at all, zero is assumed and a
127 warning is displayed.
128
129
130 "VOT" FAA test facility NAVAIDs are not reported.
131 -------------------------------------------------
132
133
134 - Umberto Salsi