...
The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information:
| Info | ||
|---|---|---|
| ||
A change proposal (AIXM-561) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, where the helicopterPerformanceClass attribute is added to AircraftCharacteristics and the association between TouchDownLiftOff and AircraftCharacteristic is established. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-561 Change Proposal. |
TLOF Designator
The TouchDownLiftOff.designator attribute represents the textual designator of the TLOF, used to distinguish physical TLOFs at an Aerodrome/Heliport that has more than one. The attribute value should reflect the local convention for physical TLOF naming at the Aerodrome/Heliport.
...
PANS-AIM requires the centre point of the TLOF to be provided including its elevation and geoid undulation.
| Warning | ||||
|---|---|---|---|---|
| In AIXM only the aiming point of a TLOF can be coded.
| |||
The aiming point is not the same position as the centre point of a TLOF. According to ICAO Annex 14, Volume II,
Currently in AIXM 5, it is not possible to define the two different points for a TLOF. Anyhow, it seems that the The relationship hasAimingPoint and the property TLOF.aimingPoint is not correct. It should be rather hasCentrePoint and TLOF.centrePoint. Also, an aiming point may be independent from a TLOF and may also be marked and lighted.Workaround for were incorrectly named in AIXM, as the real intention was to model the TLOF centre point. The aiming point is more appropriately modelled as a RunwayCentrelinePoint, because it is always on a FATO (which in AIXM is modelled as a Runway of type FATO). Therefore, the following workaround is used in AIXM 5.1(.1):
|
The ElevatedPoint class provides also dedicated attributes for elevation and geoidUndulation.
...
In addition, a TLOF may be situated on a Runway. In this regard a runway may be of type Runway or FATO (see also topic Runway [RWY]).
Coding Rules for Basic Data for TLOF
...
AIXM-5.1_RULE-D6D8E
(rule does not take into account PinS approach constraint)
The aimingPoint property is used to actually code the centre point, see also AIXM 5.1(.1) issue above.
...
AIXM-5.1_RULE-D9C62
Note: the only think that can be verified in this case is the use of either FT or M as unit on measurement. A value such as "200 M" cannot be assumed to break this rule because maybe this is the exact elevation value.
...
AIXM-5.1_RULE-4611A
Note: the only think that can be verified in this case is the use of either FT or M as unit on measurement. A value such as "200 M" cannot be assumed to break this rule because maybe this is the exact elevation value.
...
AIXM-5.1_RULE-E681,
AIXM-5.1_RULE-E682
...
This association should also be used in order to associate a TLOF with a Runway that is used for final approach by helicopters, while the TLOF itself is located somewhere else on the airport surface. In this regard a runway may be of type Runway or FATO (see also topic Runway [RWY]).
Coding Examples
Coding examples can be found in the AIP Data Set - Specimen (DONLON):
...