EntityAttributeRelationshipRule
ADDRESS
 TXT_ADDRESS If CODE_TYPE = 'EMAIL' than the value of this attribute must have the format '[name]@[server].[registered domain]'
[ Data plausibility rule  -  Source:   AIXM ]
  required for FPL-MSG concerning - AIRSPACEThis relationship can only occur for instances of the ADDRESS entity which are also related to a UNIT
[ Consistency rule  -  Source:   AIXM ]
  required for FPL-MSG concerning - AIRSPACEThe value of the CODE_TYPE of the related ADDRESS must be 'AFS'
[ Data plausibility rule  -  Source:   AIXM ]
AD_HP
   For every aerodrome/heliport there must be at least one postal address and one telephone number defined
[ Minimal data rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'AH' or 'HP', there must exist at least one related TLOF or FATO.
[ Minimal data rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'AD', then there may not exist any related TLOF or FATO.
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'HP', there may not exist any runway specified for the heliport (no relationship to RWY is allowed)
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE  If CODE_TYPE = 'LS', then it may not exist any PASSENGER_FACILITY, AD_HP_GND_SER [Ground service], FUEL or OIL related to the landing site
[ Consistency rule  -  Source:   AIXM ]
 [CODE_TYPE_MIL_OPS] If CODE_TYPE_MIL_OPS = 'MIL', then both CODE_SKED and CODE_NON_SKED must have the value 'N' (No)
[ Consistency rule  -  Source:   AIXM ]
 [CODE_TYPE_MIL_OPS] If CODE_TYPE='AD' (aerodrome only) or 'AH' (aerodrome with helipads), then CODE_TYPE_MIL_OPS is mandatory
[ EAD specific rule  -  Source:   AIXM ]
 [CODE_INTL_TFC] If CODE_INTL_TFC = 'Y' (yes), there must exist a ground service of type customs and immigration (mandatory relationship to AD_HP_GND_SER with CODE_TYPE = 'CUST')
[ Minimal data rule  -  Source:   AIXM ]
 [CODE_VFR]  If CODE_VFR = 'Y', than TXT_DESCR_LDI is mandatory
[ Minimal data rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO annex 15, item 3.4.4.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV  If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY  VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION  VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_MAG_VAR  If VAL_MAG_VAR is specified, then DATE_MAG_VAR is mandatory
[ Minimal data rule  -  Source:   AIXM ]
 VAL_MAG_VAR_CHG VAL_MAG_VAR_CHG may be specified only if VAL_MAG_VAR has been specified
[ Minimal data rule  -  Source:   AIXM ]
 VAL_REF_T  If VAL_REF_T is specified, then UOM_REF_T is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_TRANSITION_ALT If VAL_TRANSITION_ALT is specified, then UOM_TRANSITION_ALT is mandatory
[ Technical rule  -  Source:   AIXM ]
  affected by - AD_HP_OBSTACLEThe geographical distance between the position of the related OBSTACLE and the position of the ARP of the related AD_HP must be less than 50 KM
[ Data plausibility rule  -  Source:   AIXM ]
AD_HP_COLLOCATION
   An aerodrome/heliport cannot be co-located with itself.
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'F', then the aerodrome/heliport designated by the relationship "hosting one and only one AD_HP" should have no associated RWY, TWY, TLOF, FATO, Apron or obstacles. All these facilities shall be described and related to the aerodrome/heliport designated by the relationship "hosted by one and only one AD_HP". Due to the full co-location, all these facilities are equally available to the hosted aerodrome/heliport
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'F' or 'R' , then the position of the reference points of the two airports, as given by the attributes GEO_LAT and GEO_LONG, must be identical
[ Consistency rule  -  Source:   AIXM ]
 TXT_DESCR  If the value of the CODE_TYPE is anything else than 'F' (i.e. full collocation), a textual description of the shared parts has to be given. Therefore the TXT_DESCR is mandatory in this case
[ Consistency rule  -  Source:   AIXM ]
AD_HP_GND_SER
 CODE_TYPE  If the value of CODE_TYPE = 'FUEL', there must be at least one fuel type specified for the related aerodrome/heliport (entity FUEL)
[ Minimal data rule  -  Source:   AIXM ]
 CODE_TYPE  If the value of CODE_TYPE = 'FIRE' , then CODE_CAT is mandatory
[ Consistency rule  -  Source:   ICAO Annex 15, Appendix 1, AD 2.6 ]
 CODE_CAT_REFERENCE If CODE_CAT = 'A10' then CODE_CAT_REFERENCE must have the value 'NATO'.
[ Consistency rule  -  Source:   AIXM ]
AD_HP_NAV_AID
  also - SIGNIFICANT_POINTThe related SIGNIFICANT_POINT cannot be of type 'DESIGNATED POINT' (cannot have the relationship 'at DESIGNATED_POINT')
[ Technical rule  -  Source:   AIXM ]
  also - SIGNIFICANT_POINTThe position of the related SIGNIFICANT_POINT must be plausibly close to the position of the ARP (within 20 KM)
[ Data plausibility rule  -  Source:   AIXM ]
  also - SIGNIFICANT_POINT If the related SIGNIFICANT_POINT is of type VOR or TACAN, thus having a specified VAL_MAG_VAR and DATE_MAG_VAR, these values have to coincide with those of the related AD_HP
[ Data plausibility rule  -  Source:   AIXM ]
AD_HP_OBSTACLE
AD_HP_SURFACE_BORDER
   If the AD / HP Surface Border is describing the geometry of a RWY_PROTECT_AREA, then the position given by GEO_LAT, GEO_LONG of the related vertex must be plausibly close (less than 10 KM) to that of the centre line points of the related RWY
[ Data plausibility rule  -  Source:   AIXM ]
   If the AD / HP Surface Border is describing the geometry of a TLOF_SAFE_AREA, then the position given by GEO_LAT, GEO_LONG of the related vertex must be plausibly close (less than 10 KM) to that of the related TLOF centre
[ Data plausibility rule  -  Source:   AIXM ]
   If the AD / HP Surface Border is describing the geometry of a TLOF, then the position given by GEO_LAT, GEO_LONG of the related vertex must be plausibly close (less than 1 KM) to that of the centre line points of the related TLOF centre
[ Data plausibility rule  -  Source:   AIXM ]
   If the AD / HP Surface Border is describing the geometry of an APRON, then the position given by GEO_LAT, GEO_LONG of the related vertex must be plausibly close (less than 20 KM) to that of the ARP of the related AD_HP
[ Data plausibility rule  -  Source:   AIXM ]
   If the AD / HP Surface Border is describing the geometry of an FATO_PROTECT_AREA, then the position given by GEO_LAT, GEO_LONG of the related vertex must be plausibly close (less than 20 KM) to that of the centerline points of the related FATO.
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if at least one VAL_ELEV is specified in the related AD_HP_SURFACE_VERTEX
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if at least one VAL_ELEV is specified in the related AD_HP_SURFACE_VERTEX
[ Consistency rule  -  Source:   AIXM ]
 UOM_DIST_VER If at least one VAL_ELEV is specified in the related AD_HP_SURFACE_VERTEX, then UOM_DIST_VER is mandatory
[ Consistency rule  -  Source:   AIXM ]
AD_HP_SURFACE_VERTEX
 CODE_TYPE If CODE_TYPE = 'CCA' or 'CWA', then GEO_LAT_ARC and GEO_LONG_ARC are mandatory and indicate the centre of the arc or circle
[ Technical rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'ABE', then GEO_LAT_ARC and GEO_LONG_ARC are mandatory and indicate a point situated on the arc edge between the current shape point and the shape point with the following sequence number
[ Technical rule  -  Source:   AIXM ]
AD_HP_USAGE
AD_HP_USAGE_CONDITION
   Each AD_HP_USAGE_CONDITION must be related to at least one of the AIRCRAFT_CLASS and FLIGHT_CLASS entities
[ Technical rule  -  Source:   AIXM ]
   If a related FLIGHT_CLASS has CODE_ORIGIN = 'INTL', then it must exist an AD_HP_GND_SER (ground service) having CODE_TYPE = 'CUST' (customs and immigration) for the related aerodrome/heliport
[ Minimal data rule  -  Source:   AIXM ]
   If a related FLIGHT_CLASS has CODE_RULE = 'V' or 'IV', then the TXT_DESCR_LDI attribute of the related aerodrome/heliport is mandatory.
[ Minimal data rule  -  Source:   AIXM ]
AD_HP_USAGE_LIMITATION
AERO_GND_LGT
 CODE_TYPE  If CODE_TYPE = 'HBCN', 'IBN', 'SIG' or 'ABN' then it must be related to an AD_HP and the position given by GEO_LAT, GEO_LONG must be plausibly close (less than 20 KM) to that of the ARP of the related AD_HP
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_TYPE  If CODE_TYPE = 'ABN' (Aerodrome Beacon), then CODE_TYPE of the referenced AD_HP must be 'AD' or 'AH'
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE  If CODE_TYPE = 'HBCN' (Heliport Beacon), then CODE_TYPE of the referenced AD_HP must be 'HP'
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE  If CODE_TYPE = 'HBCN', 'IBN', 'SIG' or 'ABN then TXT_NAME and TXT_NAME of the related AD_HP must match
[ Consistency rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV is specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV is specified
[ Consistency rule  -  Source:   AIXM ]
AIRCRAFT_CLASS
AIRSPACE
   An AIRSPACE that is not related to any AIRSPACE_BORDER or AIRSPACE_CORRIDOR must be 'defined by' one and only one AIRSPACE_DERIV_GEOMETRY
[ Consistency rule  -  Source:   AIXM ]
   If CODE_TYPE='PART', then the airspace must be used as AIRSPACE_AGGREG_COMP
[ Consistency rule  -  Source:   AIXM ]
   An AIRSPACE for which the lower and upper limit are not specified, must be defined by aggregation (it must be related to an AIRSPACE_DERIV_GEOMETRY, which is related to one or more instances of AIRSPACE_AGGREG_COMP).
[ Consistency rule  -  Source:   AIXM ]
    Adjacent airspace of type FIR, UIR and/or NO-FIR should be contiguous (no gaps, no overlapping)
[ Consistency rule  -  Source:   AIXM ]
   An AIRSPACE instance, which has a geometry defined by aggregation (the related AIRSPACE_DERIV_GEOMETRY is related to one or more instances of AIRSPACE_AGGREG_COMP), cannot have any value specified for VAL_DIST_VER_LOWER, VAL_DIST_VER_UPPER, VAL_DIST_VER_MNM and VAL_DIST_VER_MAX.
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE is 'ICAO', 'ECAC', 'CFMU', 'IFPS', 'FIR', 'FIR-P', 'UIR', 'UIR-P', 'CTA', 'CTA-P', 'OCA', 'OCA-T', 'UTA', 'UTA-P', 'TMA', 'TMA-P', 'NO-FIR', then the airspace may not be part of an AIRSPACE_ASSOCIATIONS of type 'TIME-DIST'
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE This attribute is non-updateable. This means, for example, that an FIR cannot change into a sector or a danger area and vice-versa
[ Consistency rule  -  Source:   EAD ]
 CODE_TYPE If CODE_TYPE has the value 'FIR' or 'UIR', than CODE_LOC_IND is mandatory
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE='CLASS', then attribute CODE_CLASS is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), the value of VAL_DIST_VER_UPPER must be higher than VAL_DIST_VER_LOWER and VAL_DIST_VER_MNM
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_UPPER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_LOWER If VAL_DIST_VER_LOWER is specified, then UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER are mandatory
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_LOWER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 CODE_DIST_VER_MAX CODE_DIST_VER_MAX should have the value 'HEI' [The distance measured from GND].
[ Consistency rule  -  Source:   AIXM ]
 VAL_DIST_VER_MAX If VAL_DIST_VER_MAX is specified, then UOM_DIST_VER_MAX and CODE_DIST_VER_MAX are mandatory.
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_MAX If the unit of measurement as the value 'FL' or 'SM', then the attribute CODE_DIST_VER_MAX must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_MAX CODE_DIST_VER_MNM should have the value 'HEI' [the distance measured from the GND].
[ Consistency rule  -  Source:   AIXM ]
 VAL_DIST_VER_MNM If VAL_DIST_VER_MNM is specified, then UOM_DIST_VER_MNM and CODE_DIST_VER_MNM are mandatory
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_MNM If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_MNM must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_LOWER_LIMIT This value may be specified only if CODE_TYPE = 'FIR'
[ Data plausibility rule  -  Source:   AIXM ]
AIRSPACE_AGGREG_COMP
 NO_SEQ If CODE_OPR = 'BASE', then NO_SEQ must be '1' (first)
[ Technical rule  -  Source:   AIXM ]
AIRSPACE_ASSOCIATION
AIRSPACE_BORDER
    The closed path that defines an airspace border, as described using the related AIRSPACE_VERTEXes, cannot intersect itself
[ Consistency rule  -  Source:   AIXM ]
   All related AIRSPACE_BORDER_VERTEX should have the same value in CODE_DATUM.
[ Data plausibility rule  -  Source:   AIXM ]
AIRSPACE_BORDER_CROSSING
AIRSPACE_BORDER_VERTEX
... see as well the rules of the super-type entity AIRSPACE_VERTEX
AIRSPACE_CIRCLE_VERTEX
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, than UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_RADIUS The radius of the arc shall not exceed 500 NM (plausibility value)
[ Data plausibility rule  -  Source:   AIXM ]
  using as center - SIGNIFICANT_POINTThe position of the related SIGNIFICANT_POINT must be identical to that of the AIRSPACE_CIRCLE_VERTEX centre.
[ Consistency rule  -  Source:   AIXM ]
AIRSPACE_CLINE_VERTEX
... see as well the rules of the super-type entity AIRSPACE_VERTEX
 CODE_TYPE The vertex with the highest NO_SEQ must have CODE_TYPE = 'END'
[ Technical rule  -  Source:   AIXM ]
AIRSPACE_CORRIDOR
   All related AIRSPACE_CLINE_VERTEX should have the same value in CODE_DATUM.
[ Data plausibility rule  -  Source:   AIXM ]
AIRSPACE_DERIV_GEOMETRY
  the aggregation of - AIRSPACE_AGGREG_COMPThere must exist exactly one related AIRSPACE_AGGREG_COMP having CODE_OPR = 'BASE'
[ Technical rule  -  Source:   AIXM ]
AIRSPACE_VERTEX
    If CODE_TYPE = 'CCA' or 'CWA', then GEO_LAT_ARC and GEO_LONG_ARC are mandatory and indicate the centre of the arc
[ Technical rule  -  Source:   AIXM ]
   If CODE_TYPE = 'ABE', then GEO_LAT_ARC and GEO_LONG_ARC are mandatory and indicate a point situated on the arc edge between the current vertex and the vertex with the following sequence number
[ Technical rule  -  Source:   AIXM ]
   IF CODE_TYPE = 'FNT', then the relationship 'based on a portion of GEO_BORDER' is mandatory
[ Technical rule  -  Source:   AIXM ]
   IF CODE_TYPE has any other value than 'FNT', then the relationship 'based on a portion of GEO_BORDER' is not allowed
[ Consistency rule  -  Source:   AIXM ]
   IF CODE_TYPE = 'FNT', then the position given by GEO_LAT and GEO_LONG must be situated, with a tolerance of 30 M, on a segment of the related GEO_BORDER
[ Data plausibility rule  -  Source:   AIXM ]
   IF CODE_TYPE='FNT', 'GRC' or 'RHL', then GEO_LAT_ARC, GEO_LONG_ARC, VAL_RADIUS_ARC and UOM_RADIUS_ARC cannot be specified
[ Consistency rule  -  Source:   AIXM ]
   IF CODE_TYPE = 'FNT', then the position given by GEO_LAT and GEO_LONG of the next AIRSPACE_VERTEX must be situated, with a tolerance of 30 M, on a segment of the related GEO_BORDER
[ Data plausibility rule  -  Source:   AIXM ]
   If CODE_TYPE='ABE', then VAL_RADIUS_ARC and UOM_RADIUS_ARC cannot be specified
[ Consistency rule  -  Source:   AIXM ]
   If CODE_TYPE='CWA' or 'CCA', then the distance between the centre of the arc and the two ends (the one specified by the current vertex and the one specified by the next vertex) shall not differ by more than 1%
[ Data plausibility rule  -  Source:   AIXM ]
   If CODE_TYPE='ABE', 'CWA' or 'CCA', then the (calculated) radius of the arc shall not exceed 500 NM (plausibility value)
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, than UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_RADIUS_ARC If VAL_RADIUS_ARC is specified, than UOM_RADIUS_ARC is mandatory
[ Technical rule  -  Source:   AIXM ]
  located at - SIGNIFICANT_POINTThe position of the related SIGNIFICANT_POINT must be identical to the position of the AIRSPACE_VERTEX.
[ Consistency rule  -  Source:   AIXM ]
  using as arc - SIGNIFICANT_POINTThis relationship can only occur for instances of AIRSPACE_VERTEX that have CODE_TYPE = 'CWA', 'CCA' or 'ABE'.
[ Technical rule  -  Source:   AIXM ]
  using as arc - SIGNIFICANT_POINTThe position of the related SIGNIFICANT_POINT must be identical to the position given by the GEO_LAT_ARC, GEO_LONG_ARC attributes of the AIRSPACE_VERTEX.
[ Consistency rule  -  Source:   AIXM ]
ANGLE_INDICATION
 VAL_ANGLE_BRG The clockwise measured angle defined by the North, the position of the navaid (VOR, NDB or TACAN) providing the bearing and the SIGNIFICANT POINT or the NAV_SYS_CHECKPOINT to which it refers must be consistent (within 5 degrees) with the value of the VAL_ANGLE_BRG.
[ Data plausibility rule  -  Source:   AIXM ]
APRON
 [CODE_STRENGTH] If CODE_STRENGTH has the value 'PCN', then the value of TXT_DESCR_STRENGTH shall conform to the rules for the PCN-ACN method, as specified in ICAO Annex 14, item 2.2.6.
Examples:
- '80/R/B/W/T'
- '40/ F/ B /0.80 MPa /T'
- '50/F/A/Y/U Note: - Composite construction'
- '50/F/A/Y/U Note: - The reported PCN is subject to a B747-400 all-up mass limitation of 390 000 kg.'
If no method is indicated in the 'Surface strength method' field, then there are no restrictions with regard to the content of this field. For example: 'LCN 72, h= 56'
[ Standard  -  Source:   ICAO Annex 14, item 2.6 ]
APRON_LGT_SYS
... see as well the rules of the super-type entity SURFACE_LGT_SYS
AUTH_FOR_AIRSPACE
CALLSIGN_DETAIL
DESIGNATED_POINT
   If CODE_TYPE = 'ICAO' or 'OTHER', then there should not exist any other designated point with CODE_TYPE = 'ICAO', 'COORD' or 'OTHER' located within 1 NM.
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_ID If CODE_TYPE='ICAO', then CODE_ID should be unique world-wide
[ Standard  -  Source:   ICAO ]
 CODE_ID If CODE_TYPE='ADHP', then CODE_ID should be unique in the context of the related AD_HP
[ Consistency rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE='ADHP', then one of the following relationships is mandatory:
· DESIGNATED_POINT associated with AD_HP
· DESIGNATED_POINT at the centre of TLOF
· DESIGNATED_POINT located at RWY_CLINE_POINT
· DESIGNATED_POINT located at FATO_CLINE_POINT
· DESIGNATED_POINT the reference point of AD_HP
[ Consistency rule  -  Source:   AIXM ]
  at the centre of - TLOFOver the same time period, the values of the GEO_LAT, GEO_LONG, CODE_DATUM, VAL_GEO_ACCURACY and UOM_GEO_ACCURACY attributes must be equal with those of the similarly named attributes in the related TLOF
[ Consistency rule  -  Source:   AIXM ]
  the reference point of - AD_HPOver the same time period, the values of the GEO_LAT, GEO_LONG, CODE_DATUM, VAL_GEO_ACCURACY and UOM_GEO_ACCURACY attributes must be equal with those of the similarly named attributes in the related AD_HP
[ Consistency rule  -  Source:   AIXM ]
  located at - RWY_CLINE_POINTOver the same time period, the values of the GEO_LAT, GEO_LONG, CODE_DATUM, VAL_GEO_ACCURACY and UOM_GEO_ACCURACY attributes must be equal with those of the similarly named attributes in the related RWY_CLINE_POINT
[ Consistency rule  -  Source:   AIXM ]
  located at - FATO_CLINE_POINTOver the same time period, the values of the GEO_LAT, GEO_LONG, CODE_DATUM, VAL_GEO_ACCURACY and UOM_GEO_ACCURACY attributes must be equal with those of the similarly named attributes in the related FATO_CLINE_POINT
[ Consistency rule  -  Source:   AIXM ]
DIRECT_FLIGHT
DIRECT_FLIGHT_CLASS
... see as well the rules of the super-type entity DIRECT_FLIGHT
DIRECT_FLIGHT_SEGMENT
... see as well the rules of the super-type entity DIRECT_FLIGHT
DISTANCE_INDICATION
 VAL_DIST The calculated distance between the position of the navaid (DME or TACAN) providing the distance indication and the SIGNIFICANT POINT or the NAV_SYS_CHECKPOINT to which it refers must be consistent (within 1 KM) with the value of VAL_DIST.
[ Data plausibility rule  -  Source:   AIXM ]
DME
 CODE_ID CODE_ID shall not be duplicated within 600 NM of the location of the DME (see Annex 11, Appendix 2, paragraph 2.2.2)
[ Standard  -  Source:   ICAO Annex 11, Appendix 2, paragraph 2.2.2 ]
 CODE_CHANNEL If CODE_CHANNEL is not specified, then VAL_GHOST_FREQ must be specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GHOST_FREQ  VAL_GHOST_FREQ cannot be specified if the DME is collocated with a VOR or is part of an ILS or MLS system
[ Consistency rule  -  Source:   AIXM ]
 VAL_GHOST_FREQ VAL_GHOST_FREQ must be consistent with the CODE_CHANNEL value, according to Table A, ICAO Annex 10, Vol. 1
[ Standard  -  Source:   ICAO Annex 10, Table A, Vol. 1 ]
 VAL_GHOST_FREQ If VAL_GHOST_FREQ is specified, then UOM_GHOST_FREQ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DISPLACE If VAL_DISPLACE is specified, then UOM_DISPLACE is mandatory
[ Technical rule  -  Source:   AIXM ]
 CODE_EM The type of the DME radio signals is always pulse, therefore CODE_EM must be 'PON'.
See ICAO Annex 10, Vol. 1, section 3.5.3.3
[ Standard  -  Source:   ICAO Annex 10, Vol. 1, Section 3.5.3.3 ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
  co-located with - VORThe CODE_ID of the DME must be the same with the CODE_ID of the related VOR
[ Consistency rule  -  Source:   AIXM ]
  co-located with - VORThe value of the CODE_CHANNEL must be paired with the VAL FREQ of the related VOR, as described by Table A, ICAO Annex 10, Vol.1
[ Standard  -  Source:   ICAO Annex 10, Vol.1, Table A ]
  co-located with - VORThe geographical distance between the position of the DME and the position of the related VOR must be:
a) less than 30 metres if the VOR is located at an aerodrome/heliport (connected through the SIGNIFICANT_POINT and AD_HP_NAV_AID entities) and has CODE_TYPE='VOR';
b) less than 80 metres if the VOR is located at an aerodrome/heliport (connected through the SIGNIFICANT_POINT and AD_HP_NAV_AID entities) and has CODE_TYPE='DVOR';
c) less than 600 metres if the VOR is not located at an aerodrome/heliport (not connected through the SIGNIFICANT_POINT and AD_HP_NAV_AID entities)
(See ICAO Annex 10, Vol. 1, section 3.5.2.6.1)
[ Standard  -  Source:   ICAO Annex 10, Vol.1, section 3.5.2.6.1 ]
DME_USAGE_LIMIT
 CODE_TYPE If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory
[ Consistency rule  -  Source:   AIXM ]
EN_ROUTE_RTE
   The route should not have gaps: not more than 2 significant points should be the start or the end of a single segment of the same route.
[ Data plausibility rule  -  Source:   AIXM ]
   The route should not have branches: no significant point should be the start or end of more than tzo segments of the same route.
[ Data plausibility rule  -  Source:   AIXM ]
   The related route segments should be described in order: no significant point should be the start of more than one segment of the same route; no significant point should be the end of more than one segment of the same route.
[ Consistency rule  -  Source:   AIXM ]
 TXT_DESIG The route designator has to be compliant with the rules defined by ICAO Annex 11, Appendix 1, section 2. The rule consists therefore of the following parts:
- The route designator consists at most of 6 uppercase characters and ciphers.
- The designator starts with one or two uppercase characters and is followed by a number between 1 and 999 without leading zeros and may end with an additional character.
- Of the three possible characters the first one is optional and may be 'K', 'U' or 'S'.
- Of the three possible characters the second one is mandatory and may be 'A', 'B', 'G', 'H', 'J', 'L', 'M', 'N', 'P', 'Q', 'R', 'T', 'V', 'W', 'Y' or 'Z'.
- Of the three possible characters the third one (after the number) is optional and may be 'F', 'G', 'Y' or 'Z'.
- The following characters are not allowed in any position: 'C', 'D', 'E', 'I', 'O' and 'X'
[ Standard  -  Source:   ICAO Annex 11, Appendix 1, section 2 ]
FATO
 VAL_LEN If VAL_LEN is specified, then UOM_DIM is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_WID If VAL_WID is specified, then UOM_DIM is mandatory
[ Technical rule  -  Source:   AIXM ]
 [CODE_STRENGTH] If CODE_STRENGTH has the value 'PCN', then the value of TXT_DESCR_STRENGTH shall conform to the rules for the PCN-ACN method, as specified in ICAO Annex 14, item 2.6.
Examples:
- '80/R/B/W/T'
- '40/ F/ B /0.80 MPa /T'
- '50/F/A/Y/U Note: - Composite construction'
- '50/F/A/Y/U Note: - The reported PCN is subject to a B747-400 all-up mass limitation of 390 000 kg.'
If no method is indicated in the 'Surface strength method' field, then there are no restrictions with regard to the content of this field. For example: 'LCN 72, h= 56'
[ Data plausibility rule  -  Source:   ICAO Annex 14, item 2.6 ]
FATO_CLINE_POINT
   The distance between the first and the last FATO_CLINE_POINT associated to the same FATO cannot exceed 1 KM
[ Data plausibility rule  -  Source:   AIXM ]
   The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 20km) to that of the ARP of the related AD_HP.
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If an occurrence of this entity is at the same time threshold of a FATO, then this attribute is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
FATO_DIRECTION
 TXT_DESIG TXT_DESIG must have between 2 and 3 characters, of which the first 2 may be only digits, which indicate an integer value between 01 and 36, inclusive. Examples: 09, 09L, 09R, 09C, 09T, etc...
[ Technical rule  -  Source:   AIXM ]
 VAL_MEHT If VAL_MEHT is specified, then UOM_MEHT is mandatory
[ Technical rule  -  Source:   AIXM ]
  having as threshold - FATO_CLINE_POINTThe FATO_CLINE_POINT used as threshold must be related to the same FATO as the
current FATO_DIRECTION
[ Consistency rule  -  Source:   AIXM ]
FATO_DIRECTION_ALS
 CODE_TYPE If CODE_TYPE = 'ALSAF', then CODE_SEQUENCED_FLASH cannot have the value 'N'.
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'ALSAF', then CODE_INTENSITY cannot have the value 'LIM'.
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'MALS' or 'MALSR', then CODE_INTENSITY cannot have the value 'LIH' or 'LIL'.
[ Consistency rule  -  Source:   AIXM ]
 VAL_LEN If VAL_LEN is specified, then UOM_LEN is mandatory
[ Technical rule  -  Source:   AIXM ]
FATO_DIRECTION_DECL_DIST
   For the same FATO_DIRECTION (and from the same intersection with a TWY and within the same time period - day/night, if applicable), VAL_DIST (considering the UOM_DIST information) of the 'RTODAH' must be equal with or greater than that of the 'TODAH'
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE is 'LDAH', then VAL_DIST (considering the UOM_DIST information) must be smaller than or equal to VAL_LEN of the related FATO
[ Data plausibility rule  -  Source:   AIXM ]
FATO_DIRECTION_LGT_SYS
... see as well the rules of the super-type entity SURFACE_LGT_SYS
FATO_DIRECTION_OBSTACLE
 VAL_DIST_THR This value must correspond (within 5 meters) to the value calculated using the coordinates of the related OBSTACLE and the coordinates of the threshold of the related FATO_DIRECTION
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_THR If VAL_DIST_THR is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_ALONG_CLINE This value must correspond (within 5 meters) to the value calculated using the coordinates of the related OBSTACLE and the coordinates of the related FATO_CLINE_POINT(s)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_ALONG_CLINE If VAL_DIST_ALONG_CLINE is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_TO_CLINE This value must correspond (within 5 meters) to the value calculated using the coordinates of the related OBSTACLE and the coordinates of the related FATO_CLINE_POINT(s)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_TO_CLINE If VAL_DIST_TO_CLINE is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_BRG_THR This value must correspond (within 1 degree) to the value calculated using the coordinates of the related OBSTACLE and the coordinates of the threshold of the related FATO_DIRECTION, taking into consideration the actual value of the magnetic variation at the aerodrome site (attributes VAL_MAG_VAR, DATE_MAG_VAR and VAL_MAG_VAR_CHG of the related AD_HP entity)
[ Data plausibility rule  -  Source:   AIXM ]
FATO_DIRECTION_STAR
FATO_PROTECT_AREA
... see as well the rules of the super-type entity LANDING_PROTECTION_AREA
FLIGHT_CLASS
FLOW_COND_COMBINATION
   Any FLOW_COND_COMBINATION must have at least one operand (which may be a FLOW_COND_ELEMENT or a FLOW_COND_COMBINATION)
[ Consistency rule  -  Source:   AIXM ]
   If the FLOW_COND_COMBINATION is 'used (as operand) in' another FLOW_COND_COMBINATION, then the attribute NO_SEQ is mandatory
[ Consistency rule  -  Source:   AIXM ]
   NO_SEQ of all FLOW_COND_ELEMENTs and FLOW_COND_COMBINATIONs that are 'used (as operands) in' one FLOW_COND_COMBINATION must be unique and shall indicate their order in the combination
[ Consistency rule  -  Source:   AIXM ]
   If one FLOW_COND_COMBINATION has CODE_OPR = 'NONE', then it must 'have as operand' exactly one FLOW_COND_ELEMENT and cannot 'have as operand' any other FLOW_COND_COMBINATION
[ Consistency rule  -  Source:   AIXM ]
   If one FLOW_COND_COMBINATION is 'having as operand' exactly one FLOW_COND_ELEMENT and not 'having as operand' any other FLOW_COND_COMBINATION then it must have the value 'NONE' in CODE_OPR
[ Consistency rule  -  Source:   AIXM ]
   A FLOW_COND_COMBINATION cannot be related to itself (through the 'having as operand/used in' relationship
[ Consistency rule  -  Source:   AIXM ]
 CODE_OPR The value of CODE_OPR cannot be 'OR' for occurrences of the FLOW_COND_COMBINATION which are related to two or more FLOW_COND_ELEMENTs having different values for their CODE_REF_LOC
[ Consistency rule  -  Source:   AIXM ]
 CODE_OPR The value of CODE_OPR may be 'SEQ' only for occurrences of the FLOW_COND_COMBINATION which are related to FLOW_COND_ELEMENTs of type AD_HP, AIRSPACE, AIRSPACE_BORDER_CROSSING or SIGNIFICANT_POINT or to FLOW_COND_COMBINATIONs with CODE_OPR = 'SEQ'
[ Consistency rule  -  Source:   AIXM ]
FLOW_COND_ELEMENT
   In the set of FLOW_COND_ELEMENT which belong to one TFC_FLOW_RESTR, there must be at least one with CODE_REF_LOC = 'Y'
[ Consistency rule  -  Source:   AIXM ]
 CODE_REF_LOC CODE_REF_LOC cannot have the value 'Y' for occurrences of the FLOW_COND_ELEMENT entity which are related to FLIGHT_CLASS, AIRCRAFT_CLASS, ORG_AUTH, DIRECT_FLIGHT_CLASS.
[ Consistency rule  -  Source:   AIXM ]
 CODE_REF_LOC CODE_REF_LOC cannot have the value 'Y' if CODE_REL_WITH_LOC has the value 'ACT' or 'AVB'
[ Consistency rule  -  Source:   AIXM ]
 CODE_REL_WITH_LOC CODE_REL_WITH_LOC may have the value 'DEP' or 'ARR' only for occurrences of the FLOW_COND_ELEMENT which are related to AD_HP or AIRSPACE
[ Consistency rule  -  Source:   AIXM ]
 CODE_REL_WITH_LOC CODE_REL_WITH_LOC may have the value 'XNG' (crossing) only for occurrences of the FLOW_COND_ELEMENT which are related to AIRSPACE, BORDER_CROSSING, SEGMENT, DIRECT_FLIGHT_SEGMENT, SID, STAR, ROUTE_PORTION or SIGNIFICANT_POINT
[ Consistency rule  -  Source:   AIXM ]
 CODE_REL_WITH_LOC CODE_REL_WITH_LOC may have the value 'ACT' only for occurrences of the FLOW_COND_ELEMENT which are related to AIRSPACE
[ Consistency rule  -  Source:   AIXM ]
 CODE_REL_WITH_LOC CODE_REL_WITH_LOC may have the value 'AVB' only for occurrences of the FLOW_COND_ELEMENT which are related to RTE_PORTION
[ Consistency rule  -  Source:   AIXM ]
  based on - ORG_AUTHThe related ORG_AUTH (through ORG_AUTH) must have CODE_TYPE = 'AOA' (Aircraft Operating Agency)
[ Consistency rule  -  Source:   AIXM ]
FLOW_COND_ELEMENT_LVL
 VAL_DIST_VER_LOWER When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), VAL_DIST_VER_LOWER must be between VAL_DIST_VER_LOWER and VAL_DIST_VER_UPPER of the related RTE_SEG
[ Data plausibility rule  -  Source:   AIXM ]
 UOM_DIST_VER_LOWER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), the value of VAL_DIST_VER_UPPER must be between VAL_DIST_VER_LOWER and VAL_DIST_VER_UPPER of the related RTE_SEG
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), the value of VAL_DIST_VER_UPPER must be higher than the value of VAL_DIST_VER_LOWER
[ Data plausibility rule  -  Source:   AIXM ]
 UOM_DIST_VER_UPPER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
FREQUENCY
FUEL
GATE_STAND
   The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 20 KM) to that of the ARP of the related AD_HP
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY  If VAL_GEO_ACCURACY is specified , then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
GEO_BORDER
   All GEO_BORDERs must be open shapes. Therefore, each GEO_BORDER must have one and only one related GEO_BORDER_VERTEX having CODE_TYPE='END'
[ Consistency rule  -  Source:   AIXM ]
   The open path that defines a geographical border, as described using the related GEO_BORDER_VERTEXes, cannot intersect itself
[ Consistency rule  -  Source:   AIXM ]
   All related GEO_BORDER_VERTEX should have the same value in CODE_DATUM.
[ Data plausibility rule  -  Source:   AIXM ]
GEO_BORDER_VERTEX
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, than UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
HOLDING_PROCEDURE
  established at - SIGNIFICANT_POINTThe related SIGNIFICANT_POINT must be also related ("a fix for") to one of the PROCEDURE_LEGs that are "part of" the HOLDING_PROCEDURE
[ Consistency rule  -  Source:   AIXM ]
  composed of - PROCEDURE_LEGThe value of NO_SEQ of all PROCEDURE_LEG that are related to the same HOLDING_PROCEDURE must be unique
[ Technical rule  -  Source:   AIXM ]
  composed of - PROCEDURE_LEGAll PROCEDURE_LEG that are 'part of' a HOLDING_PROCEDURE must have CODE_TYPE='HM'
[ Consistency rule  -  Source:   AIXM ]
IAP
  composed of - PROCEDURE_LEGThe value of NO_SEQ of all PROCEDURE_LEG that are related to the same IAP must be in a sequence, either ascending or descending (at one moment in time). This inherently implies uniqueness
[ Technical rule  -  Source:   AIXM ]
IAP_USAGE
ILS
 CODE_CAT An ILS without ILS_GP must have CODE_CAT='NOCAT'
[ Consistency rule  -  Source:   AIXM ]
ILS_GP
   The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 1 KM) to that of the threshold of the related (through ILS) RWY_DIRECTION
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_FREQ The value of the VAL_FREQ has to lie between 328.6 MHz and 335.4 MHz. (see ICAO Annex 10, Vol. 1, section 3.1.5.2)
[ Standard  -  Source:   ICAO Annex 10, Vol. 1, section 3.1.5.2 ]
 VAL_SLOPE The value of the VAL_SLOPE has to lie between 1 and 5 degrees
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_RDH The value of the VAL_RDH has to lie between 10 and 25 metres (see ICAO Annex 10, Vol. 1, section 3.1.5.1.4)
[ Standard  -  Source:   ICAO Annex 10, Vol. 1, section 3.1.5.1.4 ]
 VAL_RDH If VAL_RDH is specified, then UOM_RDH is mandatory
[ Technical rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
ILS_LLZ
   The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 1 KM) to that of the end of the related (through ILS) RWY_DIRECTION
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_FREQ The value of the VAL_FREQ has to lie between 108 MHz and 111.975 MHz (see ICAO Annex 10, Vol. 1, section 3.1.3.2)
[ Standard  -  Source:   ICAO Annex 10, Vol. 1, section 3.1.3.2 ]
 VAL_MAG_BRG The difference between VAL_MAG_BRG of the ILS_LLZ and VAL_MAG_BRG of the related RWY_DIRECTION cannot exceed 10 degrees (see ICAO Doc 8168, PANS OPS, Chapter 23, 'Offset Localizer')
[ Data plausibility rule  -  Source:   ICAO Doc 8168, PANS OPS, Chapter 23, 'Offset Localizer' ]
 VAL_TRUE_BRG The difference between VAL_TRUE_BRG and VAL_MAG_BRG has to be consistent with the value VAL_MAG_VAR in the referred AD_HP, taking in consideration the current date and the annual rate of change (VAL_MAG_VAR_CHG in the referred AD_HP)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_MAG_VAR If VAL_MAG_VAR is specified, then DATE_MAG_VAR is mandatory.
[ Technical rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY VAL_GEO_ACCURACY may be specified only if GEO_LAT and GEO_LONG have been specified and, in this situation, UOM_GEO_ACCURACY is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
LANDING_PROTECTION_AREA
 VAL_WID If VAL_WID is specified, then UOM_DIM is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_LEN If VAL_LEN is specified, then UOM_DIM is mandatory
[ Technical rule  -  Source:   AIXM ]
MKR
 CODE_ID The only allowable characters are '.' (#002E) and '-' (#002D). For example, '-.-' meaning 'dash-dot-dash', '-' meaning 'dashes', etc..
[ Technical rule  -  Source:   AIXM ]
 VAL_FREQ The value of the VAL_FREQ must be 75 (MHz)
[ Standard  -  Source:   ICAO ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
  part of - ILSThe value of the CODE_PSN_ILS must be different for each MKR that is related to the same ILS (within the same time period)
[ Consistency rule  -  Source:   AIXM ]
  co-located with - NDBThe geographical distance between the position of the MKR and the position of the related NDB must be less than 100 metres
[ Data plausibility rule  -  Source:   AIXM ]
  co-located with - NDBCODE_PSN_ILS of the MKR must have the same value as CODE_PSN_ILS of the related NDB
[ Consistency rule  -  Source:   AIXM ]
MLS
  having - DMEThe value of the CODE_CHANNEL of the related DME must be paired with the CODE_CHANNEL of MLS, as described by Table A, ICAO Annex 10, Vol.1
[ Standard  -  Source:   ICAO Annex 10, Vol.1, Table A ]
  having - MLS_AZIMUTHIf a given occurrence of entity MICROWAVE LANDING SYSTEM "is having" one occurrence of MLS AZIMUTH, the attribute CODE_TYPE must indicate "forward" (viz. Approach Azimuth - AZ)
[ Consistency rule  -  Source:   AIXM ]
MLS_AZIMUTH
   The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 1 KM) to that of the end of the related (through MSL) RWY_DIRECTION
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_TRUE_BRG The difference between VAL_TRUE_BRG and VAL_MAG_BRG has to be consistent with the value VAL_MAG_VAR in the related AD_HP, taking into consideration the current date and the annual rate of change (VAL_MAG_VAR_CHG in the related AD_HP)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_MAG_BRG The difference between VAL_MAG_BRG of the MLS_AZIMUTH and VAL_MAG_BRG of the related RWY_DIRECTION cannot exceed 10 degrees (see ICAO Doc 8168, PANS OPS, Chapter 23, 'Offset Localizer')
[ Data plausibility rule  -  Source:   ICAO Doc 8168, PANS OPS, Chapter 23, 'Offset Localizer' ]
 VAL_MAG_VAR If VAL_MAG_VAR is specified, then DATE_MAG_VAR is mandatory.
[ Technical rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_ANGLE_COVER_LEFT VAL_ANGLE_COVER_LEFT must be greater than VAL_ANGLE_PROP_LEFT
[ Consistency rule  -  Source:   AIXM ]
 VAL_ANGLE_COVER_RIGHT VAL_ANGLE_COVER_RIGHT must be greater than VAL_ANGLE_PROP_RIGHT
[ Consistency rule  -  Source:   AIXM ]
MLS_ELEVATION
   The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 1 KM) to that of the threshold of the related (through MLS) RWY_DIRECTION
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_ANGLE_NML VAL_ANGLE_NML must be greater than VAL_ANGLE_MNM
[ Consistency rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
MSA
   Two Minimum Sector Altitudes defined using VAL_ANGLE_FM, VAL_ANGLE_TO, VAL_DIST_INNER, and VAL_DIST_OUTER should not intersect each other
[ Consistency rule  -  Source:   AIXM ]
 VAL_ANGLE_FM VAL_ANGLE_FM must have a value between 0 and 360 (degrees)
[ Consistency rule  -  Source:   AIXM ]
 VAL_ANGLE_TO VAL_ANGLE_TO must have a value between 0 and 360 (degrees)
[ Consistency rule  -  Source:   AIXM ]
 VAL_DIST_INNER If specified, VAL_DIST_INNER must be smaller than VAL_DIST_OUTER
[ Consistency rule  -  Source:   AIXM ]
 VAL_DIST_OUTER The radius of a sector (VAL_DIST_OUTER) can not be more than 50 NM.
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_VER The value of VAL_DIST_VER cannot be less than 300 metres
[ Data plausibility rule  -  Source:   AIXM ]
 UOM_DIST_VER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
MSA_GROUP
NAVAID_LIMITATION
   If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory
[ Consistency rule  -  Source:   AIXM ]
   If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_DIST_INNER If VAL_DIST_INNER is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_OUTER If VAL_DIST_OUTER is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_OUTER VAL_DIST_OUTER must be greater than VAL_DIST_INNER
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_UPPER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_LOWER If VAL_DIST_VER_LOWER is specified, then UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER are mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_LOWER If both VAL_DIST_VER_LOWER and VAL_DIST_VER_UPPER are specified, then the value of the lower limit must be smaller than or equal to the value of the upper limit (when converted to a common unit of measurement and reference system)
[ Consistency rule  -  Source:   AIXM ]
 UOM_DIST_VER_LOWER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_ANGLE_SCALLOP VAL_ANGLE_SCALLOP may be specified only for VOR or TACAN.
[ Consistency rule  -  Source:   AIXM ]
 VAL_ANGLE_SCALLOP VAL_ANGLE_SCALLOP may be specified only if CODE_TYPE is 'SCL' or 'CVR'
[ Consistency rule  -  Source:   AIXM ]
NAV_SYS_CHECKPOINT
NDB
 CODE_ID If CODE_CLASS = 'B' [en-route NDB], then CODE_ID shall not be duplicated within 600 NM of the location of the NDB.
[ Standard  -  Source:   ICAO Annex 11, Appendix 2, paragraph 2.2.2 ]
 VAL_FREQ The value of the VAL_FREQ must be in the interval 190 to 1750 kHz. (see ICAO Annex 10, Vol. 1, section 3.4.4.1)
[ Standard  -  Source:   ICAO Annex 10, Vol. 1, section 3.4.4.1 ]
 CODE_PSN_ILS The value 'I' (inner marker position) is not allowed for NDB (CODE_CLASS = 'B')
[ Consistency rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
NDB_USAGE_LIMIT
 CODE_TYPE If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory
[ Consistency rule  -  Source:   AIXM ]
NITROGEN
OBSTACLE
 CODE_LGT If CODE_LGT ='Yes', then TXT_DESCR_LGT is mandatory
[ Consistency rule  -  Source:   AIXM ]
 CODE_LGT If CODE_LGT ='No', then TXT_DESCR_LGT cannot be specified
[ Consistency rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
OCA_OCH
   At least one of the two values VAL_OCA or VAL_OCH must be specified
[ Technical rule  -  Source:   AIXM ]
 VAL_OCA If VAL_OCA is specified, than UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_OCH If VAL_OCH is specified, then CODE_REF_OCH is mandatory
[ Technical rule  -  Source:   AIXM ]
OIL
ORG_AUTH
   For every organisation/authority having CODE_TYPE = 'O', 'IO', 'AOA', 'HA', 'A' or 'ATS', there must be at least one postal address and one telephone number defined
[ Minimal data rule  -  Source:   AIXM ]
ORG_AUTH_ASSOC
OXYGEN
PASSENGER_FACILITY
PREDEFINED_LVL
PREDEFINED_LVL_COLUMN
PREDEFINED_LVL_TABLE
 UOM_DIST_VER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
PROCEDURE_LEG
 CODE_PHASE This attribute is not applicable for Holding Procedures
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_TYPE For each value of CODE_TYPE, a list of mandatory attributes for the PROCEDURE_LEG may be found in item 1.5, Attachment 5, ARINC 424 Specification
[ Consistency rule  -  Source:   AIXM ]
 CODE_DESCR_DIST_VER If CODE_DESCR_DIST_VER = 'L', 'LA' or 'B' then VAL_DIST_VER_LOWER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 CODE_DESCR_DIST_VER If CODE_DESCR_DIST_VER = 'BH' or 'B' then VAL_DIST_VER_UPPER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_UPPER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_LOWER If VAL_DIST_VER_LOWER is specified, then UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER are mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_LOWER When translated to use the same unit of measurement and the same vertical reference, VAL_DIST_VER_LOWER must be lower than VAL_DIST_VER_UPPER
[ Data plausibility rule  -  Source:   AIXM ]
 UOM_DIST_VER_LOWER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_VER_ANGLE VAL_VER_ANGLE should have a value between -10 and +50 degrees
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_SPEED_LIMIT If VAL_SPEED_LIMIT is specified, then UOM_SPEED and CODE_SPEED_REF are mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST If VAL_DIST is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DUR If VAL_DUR is specified, then UOM_DUR is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_RHO If VAL_RHO is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_BANK_ANGLE VAL_BANK_ANGLE should have a value between 5 and 35 degrees
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_ROLE_FIX This attribute may be specified only for a procedure leg that is 'part of a IAP'
[ Consistency rule  -  Source:   AIXM ]
 CODE_ROLE_FIX This attribute may be specified only if there is an associated fix for the procedure leg, through the relationship 'using as fix one and only one SIGNIFICANT_POINT'
[ Consistency rule  -  Source:   AIXM ]
  using as fix - SIGNIFICANT_POINTIf the PROCEDURE_LEG is 'part of' a HOLDING_PROCEDURE, then the related SIGNIFICANT_POINT must be the same as the one which is 'the holding point for' that HOLDING_PROCEDURE
[ Consistency rule  -  Source:   AIXM ]
  using as arc centre - SIGNIFICANT_POINTIf the PROCEDURE_LEG is 'part of' a HOLDING_PROCEDURE, then this relationship cannot exist
[ Consistency rule  -  Source:   AIXM ]
RTE_PORTION
RTE_SEG
   At the border (defined as a buffer area of 2 km on each side) between two areas of responsibility , route segments should be continued by route segments of the same or another EN_ROUTE_RTE
[ Data plausibility rule  -  Source:   AIXM ]
   CODE_REP_ATC_START and CODE_REP_ATC_END of any two consecutive segments of the same route must be consistent
[ Consistency rule  -  Source:   AIXM ]
   The angle between two consecutive segments of the same route cannot exceed 90 degrees
[ Data plausibility rule  -  Source:   AIXM ]
   Two consecutive route segments (of the same EN_ROUTE_RTE) should have vertical limits that, if not overlapping, should not be further away than 1000 FT. For example, if segment 1 is FL245 to FL295 and segment 2 is FL310 to FL490, than a warning message should be triggered. (this rule will need to be adjusted based on operational experience
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_TYPE If the first letter of the TXT_DESIG of the related EN_ROUTE_RTE is 'S', then CODE_TYPE must have the value 'SSN' (see ICAO Annex 11, Appendix 1, item 2.3)
[ Standard  -  Source:   ICAO Annex 11, Appendix 1, item 2.3 ]
 CODE_TYPE If CODE_TYPE = 'ADV' (advisory), there has to exist a related (via the RTE_SEG) SERVICE_ON_RTE_SEG with the CODE_TYPE of the related SERVICE having the values 'ADVS' or 'EFAS (advisory)
[ Minimal data rule  -  Source:   AIXM ]
 CODE_CLASS_ACFT If the first letter of the TXT_DESIG of the related EN_ROUTE_RTE is 'K', then CODE_CLASS_ACFT must have one of the values 'H', 'HP' or 'ALL' (see ICAO Annex 11, Appendix 1, item 2.3)
[ Standard  -  Source:   ICAO Annex 11, Appendix 1, item 2.3 ]
 VAL_DIST_VER_UPPER If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_UPPER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_LOWER If VAL_DIST_VER_LOWER is specified, then UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER are mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_LOWER When translated to use the same unit of measurement and the same vertical reference, VAL_DIST_VER_LOWER must be lower than or equal to VAL_DIST_VER_UPPER
[ Data plausibility rule  -  Source:   AIXM ]
 UOM_DIST_VER_LOWER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_MNM If VAL_DIST_VER_MNM is specified, then UOM_DIST_VER_MNM and CODE_DIST_VER_MNM are mandatory
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_MNM If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_MNM must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_LOWER_OVRDE If VAL_DIST_VER_LOWER_OVRDE is specified, then UOM_DIST_VER_LOWER_OVRDE and CODE_DIST_VER_LOWER_OVRDE are mandatory
[ Technical rule  -  Source:   AIXM ]
 UOM_DIST_VER_LOWER_OVRDE If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER_OVRDE must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 CODE_DIST_VER_LOWER_OVRDE The only allowable value for CODE_DIST_VER_LOWER_OVRDE is 'HEI' (height above ground)
[ Consistency rule  -  Source:   AIXM ]
 VAL_WID If VAL_WID is specified, then UOM_WID is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_WID VAL_WID must have a value between 1 (NM) and 20 (NM)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_TRUE_TRACK The difference between the VAL_TRUE_TRACK in the RTE_SEG and the (calculated) VAL_TRUE_TRACK of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 2 (degrees)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_MAG_TRACK The difference between the VAL_MAG_TRACK in the RTE_SEG and the (calculated) VAL_MAG_TRACK of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 3 (degrees)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_REVERS_TRUE_TRACK The difference between the VAL_REVERS_TRUE_TRACK in the RTE_SEG and the (calculated) VAL_REVERS_TRUE_TRACK of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 2 (degrees)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_REVERS_MAG_TRACK The difference between the VAL_REVERS_MAG_TRACK in the RTE_SEG and the (calculated) VAL_REVERS_MAG_TRACK of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 3 (degrees)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_LEN The difference between the VAL_LEN in the RTE_SEG and the (calculated) VAL_LEN of the related SEGMENT having the same CODE_TYPE as CODE_TYPE_PATH of the route segment cannot exceed 5 (KM)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_LEN If VAL_LEN is specified, then UOM_DIST is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_COP_DIST VAL_COP_DIST must be lower than VAL_LEN
[ Data plausibility rule  -  Source:   AIXM ]
RTE_SEG_USE
   For every possible combination of level and time there may be not more than one entry defined for one direction in the RTE_SEG_USE entity
In other words: We define a Cartesian co-ordinate system with the time of the week (as specified by relation 'available according to TIMETABLE') on the x-axis and the level (as specified in the RTE_SEG_USE_LVL entity) on the y-axis. Now all entries of a specific route segment and direction (CODE_DIR) are drawn in this co-ordinate system using all their levels and timesheets. Level bands result in rectangles and single levels and level series result in lines (zero extension on y-axis). In the resulting image no figure (rectangle, line) may overlap with another figure
[ Consistency rule  -  Source:   AIXM ]
RTE_SEG_USE_LVL
 VAL_DIST_VER_LOWER If VAL_DIST_VER_LOWER is specified, then UOM_DIST_VER_LOWER and CODE_DIST_VER_LOWER are mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_LOWER When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), VAL_DIST_VER_LOWER must be higher than or equal to VAL_DIST_VER_LOWER and lower than or equal to VAL_DIST_VER_UPPER of the related RTE_SEG
[ Data plausibility rule  -  Source:   AIXM ]
 UOM_DIST_VER_LOWER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), VAL_DIST_VER_UPPER must be higher than or equal to VAL_DIST_VER_LOWER and lower than or equal to VAL_DIST_VER_UPPER of the related RTE_SEG
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER  When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), the value of VAL_DIST_VER_UPPER must be higher than or equal to the value of VAL_DIST_VER_LOWER
[ Data plausibility rule  -  Source:   AIXM ]
 UOM_DIST_VER_UPPER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
  associated with - PREDEFINED_LVL_COLUMNIf a connection to the PREDEFINED_LVL_COLUMN exists (definition of level series), then VAL_DIST_VER_LOWER, UOM_DIST_VER_LOWER, CODE_DIST_VER_LOWER, VAL_DIST_VER_UPPER, UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Consistency rule  -  Source:   AIXM ]
  associated with - PREDEFINED_LVL_COLUMN If a connection to the PREDEFINED_LVL_COLUMN exists (definition of level series), then VAL_DIST_VER_UPPER and VAL_DIST_VER_LOWER have to occur as values in VAL_DIST_VER of the related PREDEFINED_LVL
entity
[ Data plausibility rule  -  Source:   AIXM ]
  associated with - PREDEFINED_LVL_COLUMNIf a connection to the PREDEFINED_LVL_COLUMN exists (definition of level series), then UOM_DIST_VER_UPPER and UOM_DIST_VER_LOWER must have the same value as UOM_DIST_VER of the related PREDEFINED_LVL_TABLE
[ Data plausibility rule  -  Source:   AIXM ]
  associated with - PREDEFINED_LVL_COLUMNIf a connection to the PREDEFINED_LVL_COLUMN exists (definition of level series), then CODE_DIST_VER_UPPER and CODE_DIST_VER_LOWER must have the same value as CODE_DIST_VER of the related PREDEFINED_LVL_TABLE
[ Data plausibility rule  -  Source:   AIXM ]
RWY
 VAL_LEN If this value is specified, then UOM_DIM_RWY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_WID If this value is specified, then UOM_DIM_RWY is mandatory
[ Technical rule  -  Source:   AIXM ]
 [CODE_COMPOSITION] If CODE_COMPOSITION is 'WATER', then CODE_COND_SFC, CODE_STRENGTH and TXT_DESCR_STRENGTH may not be specified
[ Consistency rule  -  Source:   AIXM ]
 [CODE_STRENGTH] If CODE_STRENGTH has the value 'PCN', then the value of TXT_DESCR_STRENGTH shall conform to the rules for the PCN-ACN method, as specified in ICAO Annex 14, item 2.2.6.
Examples:
- '80/R/B/W/T'
- '40/ F/ B /0.80 MPa /T'
- '50/F/A/Y/U Note: - Composite construction'
- '50/F/A/Y/U Note: - The reported PCN is subject to a B747-400 all-up mass limitation of 390 000 kg.'
If no method is indicated in the 'Surface strength method' field, then there are no restrictions with regard to the content of this field. For example: 'LCN 72, h= 56'
[ Standard  -  Source:   ICAO Annex 14, item 2.6 ]
 VAL_LEN_STRIP VAL_LEN_STRIP must exceed VAL_LEN with at least 60 M
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_LEN_STRIP If this value is specified, then UOM_DIM_STRIP is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_WID_STRIP VAL_WID_STRIP must exceed VAL_WID
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_WID_STRIP VAL_WID_STRIP must be at least 150 M
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_WID_STRIP If this value is specified, then UOM_DIM_STRIP is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_LEN_OFFSET If this value is specified, then UOM_DIM_STRIP is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_WID_OFFSET If this value is specified, then UOM_DIM_STRIP is mandatory
[ Technical rule  -  Source:   AIXM ]
RWY_CLINE_POINT
   The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 20 KM) to that of the ARP of the related AD_HP
[ Data plausibility rule  -  Source:   AIXM ]
   The points on the centre line of one Runway must define a straight line (with a tolerance of 50 M)
[ Data plausibility rule  -  Source:   AIXM ]
   The distance between the first and the last RWY_CLINE_POINT associated to the same RWY cannot exceed 10 KM
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If an occurrence of this entity is at the same time threshold of a runway, this attribute is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
RWY_DIRECTION
   At least one of the values VAL_MAG_BRG or VAL_TRUE_BRG must be specified
[ Minimal data rule  -  Source:   AIXM ]
 TXT_DESIG TXT_DESIG must have between 2 and 3 characters, of which the first 2 may be only digits, which indicate an integer value between 01 and 36, inclusive. Examples: 09, 09L, 09R, 09C, 09T, etc..
[ Technical rule  -  Source:   AIXM ]
 VAL_TRUE_BRG This value must match (or differ exactly by 180°) with the value calculated using the geographical coordinates (GEO_LAT and GEO_LONG) of the associated RWY_CLINE_POINTs (through the associated RWY)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_MAG_BRG The difference between VAL_TRUE_BRG and VAL_MAG_BRG has to be consistent with the value VAL_MAG_VAR in the referred AD_HP, taking in consideration the current date and the annual rate of change (VAL_MAG_VAR_CHG in the referred AD_HP)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_ELEV_TDZ If VAL_ELEV_TDZ is specified, then UOM_ELEV_TDZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_TDZ_ACCURACY VAL_ELEV_TDZ_ACCURACY may be specified only if VAL_ELEV_TDZ has been specified
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE_VASIS The value 'HAPI' (helicopter approach path indicator) cannot be used here
[ Consistency rule  -  Source:   AIXM ]
 [TXT_DESCR_PSN_VASIS] A description of the position may be given, only if the type of Visual Approach Slope Indicator System (CODE_TYPE_VASIS) has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_SLOPE_ANGLE_GP_VASIS This value may be specified only if the CODE_TYPE_VASIS has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_MEHT This value may be specified only if the CODE_TYPE_VASIS has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_MEHT If VAL_MEHT is specified, then UOM_MEHT is mandatory
[ Technical rule  -  Source:   AIXM ]
  having as threshold - RWY_CLINE_POINTThe RWY_CLINE_POINT used as threshold must be related to the same RWY as the
current RWY_DIRECTION
[ Consistency rule  -  Source:   AIXM ]
RWY_DIRECTION_ALS
 CODE_TYPE If CODE_TYPE = 'ALSAF', then CODE_SEQUENCED_FLASH cannot have the value 'N'.
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'ALSAF', then CODE_INTENSITY cannot have the value 'LIM'.
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE = 'MALS' or 'MALSR', then CODE_INTENSITY cannot have the value 'LIH' or 'LIL'.
[ Consistency rule  -  Source:   AIXM ]
 VAL_LEN If VAL_LEN is specified, then UOM_LEN is mandatory
[ Technical rule  -  Source:   AIXM ]
RWY_DIRECTION_DECL_DIST
   For the same RWY_DIRECTION (and from the same intersection with a TWY and within the same time period - day/night, if applicable), the VAL_DIST (considering the UOM_DIST information) of the 'TODA' must be equal with or greater than that of the 'TORA'
[ Data plausibility rule  -  Source:   AIXM ]
   For the same RWY_DIRECTION (and from the same intersection with a TWY and within the same time period - day/night, if applicable), the VAL_DIST (considering the UOM_DIST information) of the 'ASDA' must be equal with or greater than that of the 'TORA'
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE is 'LDA', 'TORA' or 'DPLM', then VAL_DIST (considering the UOM_DIST information) must be smaller than or equal to VAL_LEN of the related RWY
[ Data plausibility rule  -  Source:   AIXM ]
RWY_DIRECTION_LGT_SYS
... see as well the rules of the super-type entity SURFACE_LGT_SYS
RWY_DIRECTION_OBSTACLE
 VAL_DIST_THR This value must correspond (within 5 meters) to the value calculated using the coordinates of the related OBSTACLE and the coordinates of the threshold of the related RWY_DIRECTION
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_THR If VAL_DIST_THR is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_ALONG_CLINE This value must correspond (within 5 meters) to the value calculated using the coordinates of the related OBSTACLE and the coordinates of the related RWY_CLINE_POINT(s)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_ALONG_CLINE If VAL_DIST_ALONG_CLINE is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_TO_CLINE This value must correspond (within 5 meters) to the value calculated using the coordinates of the related OBSTACLE and the coordinates of the related RWY_CLINE_POINT(s)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_TO_CLINE If VAL_DIST_TO_CLINE is specified, then UOM_DIST_HORZ is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_BRG_THR This value must correspond (within 1 degree) to the value calculated using the coordinates of the related OBSTACLE and the coordinates of the threshold of the related RWY_DIRECTION, taking into consideration the actual value of the magnetic variation at the aerodrome site (attributes VAL_MAG_VAR, DATE_MAG_VAR and VAL_MAG_VAR_CHG of the related AD_HP entity)
[ Data plausibility rule  -  Source:   AIXM ]
RWY_DIRECTION_STAR
RWY_PROTECT_AREA
... see as well the rules of the super-type entity LANDING_PROTECTION_AREA
   If the value of CODE_TYPE is 'OFZ' (Obstacle Free Zone), 'OFS' (Obstacle Free Surface) or 'ILS' (ILS Protection Area), then no values for the attributes CODE_COMPOSITION may be specified as the area is not on the ground
[ Consistency rule  -  Source:   AIXM ]
   If the value of CODE_TYPE is 'ILS' (ILS Protection Area), then no values for the attributes TXT_LGT may be specified
[ Consistency rule  -  Source:   AIXM ]
   If the value of CODE_TYPE is 'OFZ' (Obstacle Free Zone), 'OFS' (Obstacle Free Surface) or 'ILS' (ILS Protection Area), then the value of the attribute CODE_STS may only be 'PARKED' or 'WIP'
[ Consistency rule  -  Source:   AIXM ]
SEGMENT
   If the ending point of a segment is starting point of another segment, the ending point of the second segment cannot be the starting point of the first one
[ Consistency rule  -  Source:   AIXM ]
   The position of the SIGNIFICANT_POINT used as the beginning of the SEGMENT must be separated by at least 60 m (1 second of arc) from the position of the SIGNIFICANT_POINT used as the end of the SEGMENT.
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_LEN If VAL_LEN is specified, then UOM_DIST is mandatory
[ Technical rule  -  Source:   AIXM ]
SERVICE
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV is specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV is specified
[ Consistency rule  -  Source:   AIXM ]
SERVICE_AT_AD_HP
SERVICE_IN_AIRSPACE
SERVICE_ON_HOLDING_PROC
  also - SERVICECODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'
[ Consistency rule  -  Source:   AIXM ]
SERVICE_ON_IAP
  also - SERVICECODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'
[ Consistency rule  -  Source:   AIXM ]
SERVICE_ON_RTE_SEG
  also - SERVICECODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'
[ Consistency rule  -  Source:   AIXM ]
SERVICE_ON_SID
  also - SERVICECODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'
[ Consistency rule  -  Source:   AIXM ]
SERVICE_ON_STAR
  also - SERVICECODE_TYPE of the related SERVICE must have one of the values: 'ADVS', 'EFAS', 'FIS', 'FISA', 'RADAR', 'ATS', 'ATC', 'ATFM', 'ALRS', 'CTAF', 'VDF', 'UDF', 'DVDF'
[ Consistency rule  -  Source:   AIXM ]
SID
  composed of - PROCEDURE_LEGThe value of NO_SEQ of all PROCEDURE_LEG that are related to the same SID must be in a sequence, either ascending or descending (at one moment in time). This inherently implies uniqueness
[ Technical rule  -  Source:   AIXM ]
SID_USAGE
SIGNIFICANT_POINT
SIGNIFICANT_POINT_IN_AS
SPECIAL_DATE
  associated with - ORG_AUTHThe related Organisation/Authority must be of type 'State' (CODE_TYPE='S')
[ Consistency rule  -  Source:   AIXM ]
SPEC_NAV_STATION
 CODE_TYPE_SER The value of the CODE_TYPE_SER may be 'M' only if CODE_TYPE of the related SPEC_NAV_SYS is 'DECCA', 'LORANA', 'LORANC' or 'LORAND'
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE_SER The value of the CODE_TYPE_SER may be 'S' only if CODE_TYPE of the related SPEC_NAV_SYS is 'LORANA', LORANC' or 'LORAND'
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE_SER The value of the CODE_TYPE_SER may be 'RS', 'GS' or 'PS' only if CODE_TYPE of the related SPEC_NAV_SYS is 'DECCA'
[ Consistency rule  -  Source:   AIXM ]
 VAL_FREQ If VAL_FREQ is specified, then UOM_FREQ is mandatory
[ Technical rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
SPEC_NAV_SYS
STAR
  composed of - PROCEDURE_LEGThe value of NO_SEQ of all PROCEDURE_LEG that are related to the same STAR must be in a sequence, either ascending or descending (at one moment in time). This inherently implies uniqueness
[ Technical rule  -  Source:   AIXM ]
STAR_USAGE
SURFACE_CHARACTERISTICS
 VAL_PCN_CLASS The value should be lower than 200.
[ Data plausibility rule  -  Source:   ICAO Annex 14 ]
 VAL_PCN_CLASS If VAL_PCN_CLASS is specified, then CODE_PCN_PAVEMENT_TYPE, CODE_PCN_PAVEMENT_SUBGRADE and CODE_PCN_EVAL_METHOD must be specified.
[ Standard  -  Source:   ICAO Annex 14, item 2.6 ]
 VAL_PCN_CLASS If VAL_PCN_CLASS is specified, then CODE_PCN_MAX_TIRE_PRESSURE or VAL_PCN_MAX_TIRE_PRESSURE must be specified.
[ Standard  -  Source:   ICAO Annex 14 ]
 VAL_PCN_MAX_TIRE_PRESSURE The value should be lower than 2.00
[ Data plausibility rule  -  Source:   ICAO Annex 14 ]
 VAL_LCN_CLASS The value should be lower than 200.
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_SIWL_WEIGHT If VAL_SIWL_WEIGHT is specified, then UOM_SIWL_WEIGHT is mandatory.
[ Technical rule  -  Source:   AIXM ]
 VAL_SIWL_WEIGHT If VAL_SIWL_WEIGHT is specified, then VAL_SIWL_TIRE_PRESSURE must be specified.
[ Consistency rule  -  Source:   AIXM ]
 VAL_SIWL_TIRE_PRESSURE If VAL_SIWL_TIRE_PRESSURE is specified then UOM_SIWL_TIRE_PRESSURE is mandatory.
[ Technical rule  -  Source:   AIXM ]
 VAL_AUW_WEIGHT If VAL_AUW_WEIGHT is specified, then UOM_AUW_WEIGHT is mandatory.
[ Technical rule  -  Source:   AIXM ]
SURFACE_LGT_GROUP
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 NO_LEN If NO_LEN is greater than 1, then VAL_LEN_SPACING is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_LEN_SPACING If VAL_LEN_SPACING is specified, then UOM_DIST is mandatory
[ Technical rule  -  Source:   AIXM ]
 NO_WID If NO_WID is greater than 1, then VAL_WID_SPACING is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_WID_SPACING If VAL_WID_SPACING is specified, then UOM_DIST is mandatory
[ Technical rule  -  Source:   AIXM ]
SURFACE_LGT_SYS
SWY
 VAL_LEN If VAL_LEN is specified, then UOM_DIM is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_WID This value must be equal with the value of the VAL_WID of the related RWY (throught RWY_DIRECTION)
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_WID If VAL_WID is specified, then UOM_DIM is mandatory
[ Technical rule  -  Source:   AIXM ]
 [CODE_COMPOSITION] If CODE_COMPOSITION is 'WATER', then CODE_COND_SFC, CODE_STRENGTH and TXT_DESCR_STRENGTH may not be specified
[ Consistency rule  -  Source:   AIXM ]
 [CODE_STRENGTH] If CODE_STRENGTH has the value 'PCN', then the value of TXT_DESCR_STRENGTH shall conform to the rules for the PCN-ACN method, as specified in ICAO Annex 14, item 2.6.
Examples:
- '80/R/B/W/T'
- '40/ F/ B /0.80 MPa /T'
- '50/F/A/Y/U Note: - Composite construction'
- '50/F/A/Y/U Note: - The reported PCN is subject to a B747-400 all-up mass limitation of 390 000 kg.'
If no method is indicated in the 'Surface strength method' field, then there are no restrictions with regard to the content of this field. For example: 'LCN 72, h= 56'
[ Standard  -  Source:   ICAO Annex 14, item 2.6 ]
TACAN
 CODE_ID CODE_ID shall not be duplicated within 600 NM of the location of the TACAN (see Annex 11, Appendix 2, paragraph 2.2.2)
[ Standard  -  Source:   Annex 11, Appendix 2, paragraph 2.2.2 ]
 VAL_MAG_VAR If VAL_MAG_VAR is specified, then DATE_MAG_VAR is mandatory
[ Consistency rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
  co-located with - VORThe value of the CODE_CHANNEL must be paired zith the VAL_FREQ of the related VOR; the channel-frequency pairing table is identical to the one for DME-VOR, as contained in Table A, ICAO Annex 10, Vol.1.
[ Standard  -  Source:   FAA (NTIA Manual of Regulations and Procedures for Federal Radio Frequency Manegement - May 2003 Edition, January 2005 Revisions, 4.3.5) ]
TACAN_USAGE_LIMIT
 CODE_TYPE If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory
[ Consistency rule  -  Source:   AIXM ]
TFC_FLOW_RESTR
 CODE_TYPE If CODE_TYPE='M', than the relationship 'regulating the use of TFC_FLOW_RTE' is mandatory
[ Consistency rule  -  Source:   AIXM ]
TFC_FLOW_RTE
TFC_FLOW_RTE_ELEMENT
 VAL_SPEED If VAL_SPEED is specified, then UOM_SPEED, CODE_SPEED_REF and CODE_SPEED_CRITERIA are mandatory.
[ Technical rule  -  Source:   AIXM ]
TFC_FLOW_RTE_ELEMENT_LVL
 VAL_DIST_VER_LOWER When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), VAL_DIST_VER_LOWER must be between VAL_DIST_VER_LOWER and VAL_DIST_VER_UPPER of the related RTE_SEG
[ Data plausibility rule  -  Source:   AIXM ]
 UOM_DIST_VER_LOWER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_LOWER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), the value of VAL_DIST_VER_UPPER must be between VAL_DIST_VER_LOWER and VAL_DIST_VER_UPPER of the related RTE_SEG
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_DIST_VER_UPPER When expressed using the same unit of measurement (UOM_DIST_VER_*) and the same vertical reference (CODE_DIST_VER_*), the value of VAL_DIST_VER_UPPER must be higher than the value of VAL_DIST_VER_LOWER
[ Data plausibility rule  -  Source:   AIXM ]
 UOM_DIST_VER_UPPER If the unit of measurement has the value 'FL' or 'SM', then the attribute CODE_DIST_VER_UPPER must have the value 'STD' (standard pressure).
[ Technical rule  -  Source:   AIXM ]
TIMESHEET
   At least one of the two attributes TIME_WEF or CODE_EVENT_WEF must be specified
[ Technical rule  -  Source:   AIXM ]
   If both TIME_WEF and CODE_EVENT_WEF are specified, then CODE_COMB_WEF is mandatory as it indicates which of the two sets takes precedence, i.e. which is the latest and which is the earliest
[ Consistency rule  -  Source:   AIXM ]
   TIME_REL_EVENT_WEF may be specified only if CODE_EVENT_WEF was specified
[ Consistency rule  -  Source:   AIXM ]
   At least one of the two attributes TIME_TIL or CODE_EVENT_TIL must be specified
[ Technical rule  -  Source:   AIXM ]
   If both TIME_TIL and CODE_EVENT_TIL are specified, then CODE_COMB_TIL is mandatory as it indicates which of the two sets takes precedence, i.e. which is the latest and which is the earliest
[ Consistency rule  -  Source:   AIXM ]
   TIME_REL_EVENT_TIL may be specified only if CODE_EVENT_TIL was specified
[ Consistency rule  -  Source:   AIXM ]
 CODE_TIME_REF If CODE_TIME_REF = 'UTCW', then the attributes DATE_VALID_WEF and DATE_VALID_TILL cannot take the values 'SDLST' or 'EDLST'.
[ Consistency rule  -  Source:   AIXM ]
 CODE_DAY_TIL The allowable values for the CODE_DAY and CODE_DAY_TIL belong to 4 distinct sets:
- {MON, TUE, WED, THU, FRI, SAT or SUN},
- {PWD, WD, AWD},
- {PLH, LH, ALH},
-{ANY}.
CODE_DAY_TIL must either be NULL or have a value in the same set as the CODE_DAY. If CODE_DAY='ANY', then CODE_DAY_TIL must be NULL
[ Consistency rule  -  Source:   AIXM ]
TIMETABLE
 CODE_WORK_HR  If the value of this attribute is 'TIMSH', then the relationship between TIMETABLE and TIMESHEET is mandatory
[ Technical rule  -  Source:   AIXM ]
TLOF
   The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 20 KM) to that of the ARP of the related AD_HP
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_LEN If specified, VAL_LEN must correspond (within 5 metres) to the length calculated using the coordinates of the related TLOF_SHAPE_POINTs
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_LEN If VAL_LEN is specified, then UOM_DIM is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_WID If specified, VAL_WID must correspond (within 5 metres) to the width calculated using the coordinates of the related TLOF_SHAPE_POINTs
[ Data plausibility rule  -  Source:   AIXM ]
 VAL_WID If VAL_WID is specified, then UOM_DIM is mandatory
[ Technical rule  -  Source:   AIXM ]
 [CODE_STRENGTH] If CODE_STRENGTH has the value 'PCN', then the value of TXT_DESCR_STRENGTH shall conform to the rules for the PCN-ACN method, as specified in ICAO Annex 14, item 2.6.
Examples:
- '80/R/B/W/T'
- '40/ F/ B /0.80 MPa /T'
- '50/F/A/Y/U Note: - Composite construction'
- '50/F/A/Y/U Note: - The reported PCN is subject to a B747-400 all-up mass limitation of 390 000 kg.'
If no method is indicated in the 'Surface strength method' field, then there are no restrictions with regard to the content of this field. For example: 'LCN 72, h= 56'
[ Standard  -  Source:   ICAO Annex 14, item 2.6 ]
  situated on - FATOThe related FATO should be related to the same AD_HP as the current TLOF.
[ Technical rule  -  Source:   AIXM ]
TLOF_LGT_SYS
... see as well the rules of the super-type entity SURFACE_LGT_SYS
TLOF_SAFE_AREA
... see as well the rules of the super-type entity LANDING_PROTECTION_AREA
TWY
 VAL_WID If VAL_WID is specified, then UOM_WID is mandatory
[ Technical rule  -  Source:   AIXM ]
 [CODE_COMPOSITION] If CODE_COMPOSITION is 'WATER', then CODE_COND_SFC, CODE_STRENGTH and TXT_DESCR_STRENGTH may not be specified
[ Consistency rule  -  Source:   AIXM ]
 [CODE_STRENGTH] If CODE_STRENGTH has the value 'PCN', then the value of TXT_DESCR_STRENGTH shall conform to the rules for the PCN-ACN method, as specified in ICAO Annex 14, item 2.6.
Examples:
- '80/R/B/W/T'
- '40/ F/ B /0.80 MPa /T'
- '50/F/A/Y/U Note: - Composite construction'
- '50/F/A/Y/U Note: - The reported PCN is subject to a B747-400 all-up mass limitation of 390 000 kg.'
If no method is indicated in the 'Surface strength method' field, then there are no restrictions with regard to the content of this field. For example: 'LCN 72, h= 56'
[ Standard  -  Source:   ICAO Annex 14, item 2.6 ]
TWY_CLINE_POINT
   The position given by GEO_LAT, GEO_LONG must be plausibly close (less than 20 KM) to that of the ARP of the related AD_HP
[ Data plausibility rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
TWY_HOLDING_POSITION
TWY_INTERSECTION
   A taxiway may not intersect itself
[ Consistency rule  -  Source:   AIXM ]
   A taxiway may not intersect twice the same taxiway, runway or FATO
[ Consistency rule  -  Source:   AIXM ]
TWY_LGT_SYS
... see as well the rules of the super-type entity SURFACE_LGT_SYS
UNIT
   For every UNIT there must be at least one postal address and one telephone number defined
[ Minimal data rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
  located at - AD_HPThe position given by GEO_LAT, GEO_LONG must be plausibly close (less than 20 KM) to that of the ARP of the related AD_HP
[ Data plausibility rule  -  Source:   AIXM ]
UNIT_ASSOC
   If a unit having CODE_TYPE='RSC' ('rescue sub-centre') is part of a subordinate association (CODE_TYPE of UNIT_ASSOC is 'SUB') with a UNIT with CODE_TYPE='RCC' ('rescue co-ordination centre') or 'SAR' ('search and rescue centre'), it takes always the role of the child
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE='CL' ('co-located'), than the geographical position of the two units, if specified using the GEO_LAT and GEO_LONG attributes, have to be plausibly close (less than 5 KM)
[ Data plausibility rule  -  Source:   AIXM ]
VOR
 CODE_ID CODE_ID shall not be duplicated within 600 NM of the location of the VOR (see Annex 11, Appendix 2, paragraph 2.2.2)
[ Standard  -  Source:   ICAO Annex 11, Appendix 2, paragraph 2.2.2 ]
 VAL_FREQ The value of the VAL_FREQ must be in the interval 108.000 to 117.975 MHz
[ Data plausibility rule  -  Source:   ICAO Annex 10, Vol. 1, section 3.3.2.1 ]
 VAL_FREQ The value of the VAL_FREQ must be multiple of 50 kHz (e.g. 117.950 is a correct value while 117.975 is not)
(see ICAO Annex 10, Vol. 1, section 3.3.2.1)
[ Data plausibility rule  -  Source:   ICAO Annex 10, Vol. 1, section 3.3.2.1 ]
 VAL_MAG_VAR If VAL_MAG_VAR is specified, then DATE_MAG_VAR is mandatory
[ Consistency rule  -  Source:   AIXM ]
 CODE_DATUM All geographical coordinates should be expressed in the WGS 84 system
[ Standard  -  Source:   ICAO Annex 15, item 3.7.1.1 ]
 VAL_GEO_ACCURACY If VAL_GEO_ACCURACY is specified, then UOM_GEO_ACCURACY is mandatory
[ Consistency rule  -  Source:   AIXM ]
 VAL_ELEV If VAL_ELEV is specified, then UOM_DIST_VER is mandatory
[ Technical rule  -  Source:   AIXM ]
 VAL_ELEV_ACCURACY VAL_ELEV_ACCURACY may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
 VAL_GEOID_UNDULATION VAL_GEOID_UNDULATION may be specified only if VAL_ELEV has been specified
[ Consistency rule  -  Source:   AIXM ]
VOR_USAGE_LIMIT
 CODE_TYPE If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 CODE_TYPE If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory
[ Consistency rule  -  Source:   AIXM ]
[AIRSPACE_ASSOC]
   An AIRSPACE that appears as child in an AIRSPACE_ASSOC with CODE_TYPE='BOM', cannot appear as child in an another AIRSPACE_ASSOC with CODE_TYPE='ABOVE-BELOW' (i.e., one AIRSPACE cannot be in the same time the result of a Bill Of Material aggregation and also being indicated as using the same horizontal border as another airspace)
[ Consistency rule  -  Source:   AIXM ]
   In any set of AIRSPACE_ASSOCIATION occurences with CODE_TYPE = 'BOM' and having the same child AIRSPACE, there must exist one and only one occurence with CODE_OPR = 'BASE'
[ Consistency rule  -  Source:   AIXM ]
   AIRSPACE with CODE_TYPE='FIR' cannot appear as child in an AIRSPACE_ASSOCIATION of type 'BOM' or 'ABOVE-BELOW'
[ Consistency rule  -  Source:   AIXM ]
 [CODE_TYPE] If CODE_TYPE = 'BOM', then CODE_OPR and NO_SEQ_OPR are mandatory. Otherwise, they cannot be specified
[ Consistency rule  -  Source:   AIXM ]
 [CODE_OPR] If CODE_OPR = 'BASE', then NO_SEQ_OPR must be '1' (first)
[ EAD specific rule  -  Source:   AIXM ]
[DME_LIMITATION]
 [CODE_TYPE] If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 [CODE_TYPE] If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory
[ Consistency rule  -  Source:   AIXM ]
 [VAL_DIST_OUTER] VAL_DIST_OUTER must be greater than VAL_DIST_INNER
[ Data plausibility rule  -  Source:   AIXM ]
 [VAL_DIST_VER_UPPER] If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 [VAL_ANGLE_SCALLOP] VAL_ANGLE_SCALLOP may be specified only if CODE_TYPE is 'SCL' or 'CVR'
[ Consistency rule  -  Source:   AIXM ]
[NDB_LIMITATION]
 [CODE_TYPE] If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 [CODE_TYPE] If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory
[ Consistency rule  -  Source:   AIXM ]
 [VAL_DIST_OUTER] VAL_DIST_OUTER must be greater than VAL_DIST_INNER
[ Data plausibility rule  -  Source:   AIXM ]
 [VAL_DIST_VER_UPPER] If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 [VAL_ANGLE_SCALLOP] VAL_ANGLE_SCALLOP may be specified only if CODE_TYPE is 'SCL' or 'CVR'
[ Consistency rule  -  Source:   AIXM ]
[TACAN_LIMITATION]
 [CODE_COMPONENT] CODE_COMPONENT is mandatory if this limitation is related to a TACAN (relation 'limiting TACAN')
[ Consistency rule  -  Source:   AIXM ]
 [CODE_COMPONENT] CODE_COMPONENT is empty if this limitation is not related to a TACAN (relation 'limiting TACAN')
[ Consistency rule  -  Source:   AIXM ]
 [CODE_TYPE] If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 [CODE_TYPE] If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory
[ Consistency rule  -  Source:   AIXM ]
 [VAL_DIST_OUTER] VAL_DIST_OUTER must be greater than VAL_DIST_INNER
[ Data plausibility rule  -  Source:   AIXM ]
 [VAL_DIST_VER_UPPER] If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 [VAL_ANGLE_SCALLOP] VAL_ANGLE_SCALLOP may be specified only if CODE_TYPE is 'SCL' or 'CVR'
[ Consistency rule  -  Source:   AIXM ]
[VOR_LIMITATION]
 [CODE_TYPE] If CODE_TYPE='CVR' ('coverage'), then VAL_DIST_OUTER is mandatory
[ Consistency rule  -  Source:   AIXM ]
 [CODE_TYPE] If CODE_TYPE='SCL' ('scalloping'), then VAL_ANGLE_SCALLOP is mandatory
[ Consistency rule  -  Source:   AIXM ]
 [VAL_DIST_OUTER] VAL_DIST_OUTER must be greater than VAL_DIST_INNER
[ Data plausibility rule  -  Source:   AIXM ]
 [VAL_DIST_VER_UPPER] If VAL_DIST_VER_UPPER is specified, then UOM_DIST_VER_UPPER and CODE_DIST_VER_UPPER are mandatory
[ Technical rule  -  Source:   AIXM ]
 [VAL_ANGLE_SCALLOP] VAL_ANGLE_SCALLOP may be specified only if CODE_TYPE is 'SCL' or 'CVR'
[ Consistency rule  -  Source:   AIXM ]