...
Hence, the Runway.type attribute can take the value 'RWY' or 'FATO'. 'OTHER' shall not be used.
| Info | ||
|---|---|---|
| ||
A change proposal (AIXM-339) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, which adds a new code to the codelist CodeRunwayMarkingBasetype. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-339 Change Proposal. |
Runway (FATO) designator
The Runway.designator attribute is used to code the full textual designator of the runway, used to uniquely identify it at an aerodrome/heliport. E.g. '09/27', '02R/20L', 'RWY 18'.
The attribute value should reflect the local convention for physical runway naming at the Airport. In particular, it is not necessary to concatenate the runway direction designator to form from the physical runway designator, but this is not prohibited.
...
For detailed information about the encoding of the PCN and other the surface characteristic attributes & corresponding rules, please refer to topic Surface Characteristics [SCH].
...
Coding Rules for Basic Data for Runway
...
| Note | ||
|---|---|---|
| ||
For runway no type property is defined by ICAO Annex 15 or PANS-AIM (as FATO and Runway are handled as separate subjects). However, in the AIXM 5 Runway and FATO are modelled as one feature. Hence, it is necessary to identify, if the data is for a Runway or a FATO by using the corresponding type attribute. |
...
Each Runway shall have assigned associatedAirportHeliport value.
...
| Info | ||
|---|---|---|
| ||
In PANS-AIM no accuracy is defined for the FATO width. |
...
TBD
Note: the only thing that can be verified in this case is the use of either FT or M as unit on measurement. A value such as "3000 M" cannot be assumed to break this rule because maybe this is the exact elevation value.
...
If coded, the value of the Runway.nominalWidth shall be published with at least 1m or 1ft resolution.
...
TBD
...
.
Coding Examples
See parent topic Runway [RWY].
...