...
For detailed information about the encoding of the PCN and other the surface characteristic attributes & corresponding rules, please refer to topic Surface Characteristics [SCH].
| Excerpt |
|---|
Coding Rules for Basic Data for Runway| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|
| RWY-101 | The Runway.type attribute is mandatory. | Data consistency | TBD | | 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. |
| | RWY-102 | The Runway.designator attribute is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1A3387 |
| | RWY-103 | The Runway.nominalLength attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-104 | The Runway.nominalWidth attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-105 | The Runway.lengthAccuracy attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-106 | The Runway.widthAccuracy attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-108 | For Runway, the SurfaceCharacteristics.composition attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-109 | For Runway, the SurfaceCharacteristics.classPCN attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-110 | For Runway, the SurfaceCharacteristics.pavementTypePCN attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-111 | For Runway, the SurfaceCharacteristics.pavementSubgradePCN attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-112 | For Runway, the SurfaceCharacteristics.maxTyrePressurePCN attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-113 | For Runway, the SurfaceCharacteristics.evaluationMethodPCN attribute is mandatory. | Minimum AIP data set | TBD |
| | RWY-114 | The distance between the first and the last RunwayCentrelinePoint associated to the same Runway cannot exceed 10 KM. | EAD | TBD |
| | RWY-115 | A Runway of type 'RWY' cannot be associated with an AirportHeliport with type ''HP'. | AIXM 4.5 Business Rules / Data consistency rule | AIXM-5.1_RULE-E8E90 |
| | RWY-116 | Each Runway shall have assigned associatedAirportHeliport value. | AIXM 4.5 / Minimal data rule | AIXM-5.1_RULE-1A33AC |
| | RWY-117 | If coded, the value of the Runway.lengthAccuracy shall be 1 M or less. | PANS-AIM | TBD |
| | RWY-118 | If coded, the value of the Runway.widthAccuracy shall be 1 M or less. | PANS-AIM | TBD | | Info |
|---|
| In PANS-AIM no accuracy is defined for the FATO width. |
| | RWY-119 | If coded, the value of the Runway.nominalLength shall be published with at least 1m or 1ft resolution. | PANS-AIM | 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. |
| | RWY-120 | If coded, the value of the Runway.nominalWidth shall be published with at least 1m or 1ft resolution. | PANS-AIM | 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 "40 M" cannot be assumed to break this rule because maybe this is the exact elevation value. |
|
|
Coding Examples
See parent topic Runway [RWY].
...