UID Profile: EAD Profile: eEAD_Demo Profile: Event_FAA Profile: ICAO_AIP_DS Source Reference Rule textual description Rule tagged description Comments Diagnostics AIXM Class AIXM Attributes AIXM Associations Timeslice Applicability Category Name
AIXM-5.1_RULE-DA04A Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a Unit[1] has name equal-to Unit[2]. name <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Unit[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> name </noun_concept><keyword> equal-to </keyword><noun_concept> Unit[2]. name </noun_concept> There cannot exists two different Unit that have identical values for name Found two different Unit that have identical values for name. Backwards mapping to AIXM 4.5 is impossible. Unit name set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for Unit - attribute
AIXM-5.1_RULE-DA04B Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a AirportHeliport[1] has designator equal-to AirportHeliport[2].designator <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHeliport[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> AirportHeliport[2].designator </noun_concept> There cannot exists two different AirportHeliport that have identical values for designator Found two different AirportHeliport that have identical values for designator. Backwards mapping to AIXM 4.5 is impossible. AirportHeliport designator set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for AirportHeliport - attribute
AIXM-5.1_RULE-DA04C Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a GeoBorder[1] has name equal-to GeoBorder[2]. name <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> GeoBorder[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> name </noun_concept><keyword> equal-to </keyword><noun_concept> GeoBorder[2]. name </noun_concept> There cannot exists two different GeoBorder that have identical values for name Found two different GeoBorder that have identical values for name. Backwards mapping to AIXM 4.5 is impossible. GeoBorder name set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for GeoBorder - attribute
AIXM-5.1_RULE-D8CC1 AIXM Model Each AerialRefuellingAnchor with assigned speedLimit shall have assigned speedLimit.uom value <keyword> Each </keyword><noun_concept> AerialRefuellingAnchor </noun_concept><keyword> with assigned </keyword><noun_concept> speedLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> speedLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AerialRefuellingAnchor with assigned speedLimit value missing unit of measurement AerialRefuellingAnchor speedLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CC2 AIXM Model Each AerialRefuellingAnchor with assigned legSeparation shall have assigned legSeparation.uom value <keyword> Each </keyword><noun_concept> AerialRefuellingAnchor </noun_concept><keyword> with assigned </keyword><noun_concept> legSeparation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> legSeparation.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AerialRefuellingAnchor with assigned legSeparation value missing unit of measurement AerialRefuellingAnchor legSeparation All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CC3 AIXM Model Each AerialRefuellingAnchor with assigned legLength shall have assigned legLength.uom value <keyword> Each </keyword><noun_concept> AerialRefuellingAnchor </noun_concept><keyword> with assigned </keyword><noun_concept> legLength </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> legLength.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AerialRefuellingAnchor with assigned legLength value missing unit of measurement AerialRefuellingAnchor legLength All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CC4 AIXM Model Each AerialRefuellingAnchor with assigned refuellingBaseLevel shall have assigned refuellingBaseLevel.uom value <keyword> Each </keyword><noun_concept> AerialRefuellingAnchor </noun_concept><keyword> with assigned </keyword><noun_concept> refuellingBaseLevel </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> refuellingBaseLevel.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AerialRefuellingAnchor with assigned refuellingBaseLevel value missing unit of measurement AerialRefuellingAnchor refuellingBaseLevel All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CEF AIXM Model Each DirectFlightClass with assigned exceedLength shall have assigned exceedLength.uom value <keyword> Each </keyword><noun_concept> DirectFlightClass </noun_concept><keyword> with assigned </keyword><noun_concept> exceedLength </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> exceedLength.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found DirectFlightClass with assigned exceedLength value missing unit of measurement DirectFlightClass exceedLength All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D04 AIXM Model Each FlightRestrictionLevel with assigned upperLevel shall have assigned upperLevel.uom value <keyword> Each </keyword><noun_concept> FlightRestrictionLevel </noun_concept><keyword> with assigned </keyword><noun_concept> upperLevel </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLevel.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found FlightRestrictionLevel with assigned upperLevel value missing unit of measurement FlightRestrictionLevel upperLevel All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D05 AIXM Model Each FlightRestrictionLevel with assigned lowerLevel shall have assigned lowerLevel.uom value <keyword> Each </keyword><noun_concept> FlightRestrictionLevel </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLevel </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLevel.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found FlightRestrictionLevel with assigned lowerLevel value missing unit of measurement FlightRestrictionLevel lowerLevel All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D06 AIXM Model Each FlightRoutingElement with assigned speed shall have assigned speed.uom value <keyword> Each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> speed </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> speed.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found FlightRoutingElement with assigned speed value missing unit of measurement FlightRoutingElement speed All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D19 AIXM Model Each Meteorology with assigned visibility shall have assigned visibility.uom value <keyword> Each </keyword><noun_concept> Meteorology </noun_concept><keyword> with assigned </keyword><noun_concept> visibility </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> visibility.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Meteorology with assigned visibility value missing unit of measurement Meteorology visibility All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D1A AIXM Model Each Meteorology with assigned runwayVisualRange shall have assigned runwayVisualRange.uom value <keyword> Each </keyword><noun_concept> Meteorology </noun_concept><keyword> with assigned </keyword><noun_concept> runwayVisualRange </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> runwayVisualRange.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Meteorology with assigned runwayVisualRange value missing unit of measurement Meteorology runwayVisualRange All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D30 AIXM Model Each PilotControlledLighting with assigned duration shall have assigned duration.uom value <keyword> Each </keyword><noun_concept> PilotControlledLighting </noun_concept><keyword> with assigned </keyword><noun_concept> duration </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> duration.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found PilotControlledLighting with assigned duration value missing unit of measurement PilotControlledLighting duration All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D31 AIXM Model Each PilotControlledLighting with assigned radioFrequency shall have assigned radioFrequency.uom value <keyword> Each </keyword><noun_concept> PilotControlledLighting </noun_concept><keyword> with assigned </keyword><noun_concept> radioFrequency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> radioFrequency.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found PilotControlledLighting with assigned radioFrequency value missing unit of measurement PilotControlledLighting radioFrequency All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D39 AIXM Model Each Ridge with assigned distance shall have assigned distance.uom value <keyword> Each </keyword><noun_concept> Ridge </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Ridge with assigned distance value missing unit of measurement Ridge distance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D3A AIXM Model Each Ridge with assigned depth shall have assigned depth.uom value <keyword> Each </keyword><noun_concept> Ridge </noun_concept><keyword> with assigned </keyword><noun_concept> depth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> depth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Ridge with assigned depth value missing unit of measurement Ridge depth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D4E AIXM Model Each RunwayContamination with assigned clearedLength shall have assigned clearedLength.uom value <keyword> Each </keyword><noun_concept> RunwayContamination </noun_concept><keyword> with assigned </keyword><noun_concept> clearedLength </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> clearedLength.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayContamination with assigned clearedLength value missing unit of measurement RunwayContamination clearedLength All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D4F AIXM Model Each RunwayContamination with assigned clearedWidth shall have assigned clearedWidth.uom value <keyword> Each </keyword><noun_concept> RunwayContamination </noun_concept><keyword> with assigned </keyword><noun_concept> clearedWidth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> clearedWidth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayContamination with assigned clearedWidth value missing unit of measurement RunwayContamination clearedWidth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D50 AIXM Model Each RunwayContamination with assigned furtherClearanceLength shall have assigned furtherClearanceLength.uom value <keyword> Each </keyword><noun_concept> RunwayContamination </noun_concept><keyword> with assigned </keyword><noun_concept> furtherClearanceLength </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> furtherClearanceLength.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayContamination with assigned furtherClearanceLength value missing unit of measurement RunwayContamination furtherClearanceLength All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D51 AIXM Model Each RunwayContamination with assigned furtherClearanceWidth shall have assigned furtherClearanceWidth.uom value <keyword> Each </keyword><noun_concept> RunwayContamination </noun_concept><keyword> with assigned </keyword><noun_concept> furtherClearanceWidth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> furtherClearanceWidth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayContamination with assigned furtherClearanceWidth value missing unit of measurement RunwayContamination furtherClearanceWidth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D52 AIXM Model Each RunwayContamination with assigned clearedLengthBegin shall have assigned clearedLengthBegin.uom value <keyword> Each </keyword><noun_concept> RunwayContamination </noun_concept><keyword> with assigned </keyword><noun_concept> clearedLengthBegin </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> clearedLengthBegin.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayContamination with assigned clearedLengthBegin value missing unit of measurement RunwayContamination clearedLengthBegin All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D5A Error AIXM Model Each SDF with assigned frequency shall have assigned frequency.uom value <keyword> Each </keyword><noun_concept> SDF </noun_concept><keyword> with assigned </keyword><noun_concept> frequency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SDF with assigned frequency value missing unit of measurement SDF frequency All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D6E AIXM Model Each TaxiwayContamination with assigned clearedWidth shall have assigned clearedWidth.uom value <keyword> Each </keyword><noun_concept> TaxiwayContamination </noun_concept><keyword> with assigned </keyword><noun_concept> clearedWidth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> clearedWidth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found TaxiwayContamination with assigned clearedWidth value missing unit of measurement TaxiwayContamination clearedWidth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D78 AIXM Model Each UnplannedHolding with assigned authorizedAltitude shall have assigned authorizedAltitude.uom value <keyword> Each </keyword><noun_concept> UnplannedHolding </noun_concept><keyword> with assigned </keyword><noun_concept> authorizedAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> authorizedAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found UnplannedHolding with assigned authorizedAltitude value missing unit of measurement UnplannedHolding authorizedAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-1A4A79 Warning Warning ICAO Annex 11 Each AirspaceLayer with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> AirspaceLayer </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found AirspaceLayer with lowerLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement AirspaceLayer lowerLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A7B Warning Warning ICAO Annex 11 Each AirspaceLayer with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> AirspaceLayer </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found AirspaceLayer with upperLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement AirspaceLayer upperLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A7C Error ICAO Annex 11 Each AirspaceVolume with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found AirspaceVolume with upperLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement AirspaceVolume upperLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A7D Error ICAO Annex 11 Each AirspaceVolume with maximumLimit.uom equal-to ('FL', 'SM') shall have maximumLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> maximumLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> maximumLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found AirspaceVolume with maximumLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement AirspaceVolume maximumLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A7E Error ICAO Annex 11 Each AirspaceVolume with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found AirspaceVolume with lowerLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement AirspaceVolume lowerLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A7F Error ICAO Annex 11 Each AirspaceVolume with minimumLimit.uom equal-to ('FL', 'SM') shall have minimumLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> minimumLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> minimumLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found AirspaceVolume with minimumLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement AirspaceVolume minimumLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A80 Warning ICAO Annex 11 Each ApproachAltitudeTable with altitude.uom equal-to ('FL', 'SM') shall have altitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> ApproachAltitudeTable </noun_concept><keyword> with </keyword><noun_concept> altitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found ApproachAltitudeTable with altitude value that does not correspond to 'FL' (or 'SM') as unit of measurement ApproachAltitudeTable altitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A81 Warning ICAO Annex 11 Each CircleSector with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found CircleSector with upperLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement CircleSector upperLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A82 Warning ICAO Annex 11 Each CircleSector with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found CircleSector with lowerLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement CircleSector lowerLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A83 Warning ICAO Annex 11 Each DepartureArrivalCondition with minimumCrossingAtEnd.uom equal-to ('FL', 'SM') shall have minimumCrossingAtEnd value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><keyword> with </keyword><noun_concept> minimumCrossingAtEnd.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> minimumCrossingAtEnd </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found DepartureArrivalCondition with minimumCrossingAtEnd value that does not correspond to 'FL' (or 'SM') as unit of measurement DepartureArrivalCondition minimumCrossingAtEnd All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A84 Warning ICAO Annex 11 Each DepartureArrivalCondition with maximumCrossingAtEnd.uom equal-to ('FL', 'SM') shall have maximumCrossingAtEnd value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><keyword> with </keyword><noun_concept> maximumCrossingAtEnd.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> maximumCrossingAtEnd </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found DepartureArrivalCondition with maximumCrossingAtEnd value that does not correspond to 'FL' (or 'SM') as unit of measurement DepartureArrivalCondition maximumCrossingAtEnd All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A89 Warning ICAO Annex 11 Each HoldingAssessment with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found HoldingAssessment with upperLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement HoldingAssessment upperLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A8A Warning ICAO Annex 11 Each HoldingAssessment with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found HoldingAssessment with lowerLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement HoldingAssessment lowerLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A8B Warning ICAO Annex 11 Each HoldingUse with instructedAltitude.uom equal-to ('FL', 'SM') shall have instructedAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> HoldingUse </noun_concept><keyword> with </keyword><noun_concept> instructedAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> instructedAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found HoldingUse with instructedAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement HoldingUse instructedAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A8C Warning ICAO Annex 11 Each Minima with altitude.uom equal-to ('FL', 'SM') shall have altitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> Minima </noun_concept><keyword> with </keyword><noun_concept> altitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found Minima with altitude value that does not correspond to 'FL' (or 'SM') as unit of measurement Minima altitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A8F Error ICAO Annex 11 Each RouteSegment with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found RouteSegment with upperLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement RouteSegment upperLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A90 Error ICAO Annex 11 Each RouteSegment with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found RouteSegment with lowerLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement RouteSegment lowerLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A91 Warning ICAO Annex 11 Each RouteSegment with minimumCrossingAtEnd.uom equal-to ('FL', 'SM') shall have minimumCrossingAtEnd value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with </keyword><noun_concept> minimumCrossingAtEnd.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> minimumCrossingAtEnd </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found RouteSegment with minimumCrossingAtEnd value that does not correspond to 'FL' (or 'SM') as unit of measurement RouteSegment minimumCrossingAtEnd All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A92 Warning ICAO Annex 11 Each RouteSegment with maximumCrossingAtEnd.uom equal-to ('FL', 'SM') shall have maximumCrossingAtEnd value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with </keyword><noun_concept> maximumCrossingAtEnd.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> maximumCrossingAtEnd </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found RouteSegment with maximumCrossingAtEnd value that does not correspond to 'FL' (or 'SM') as unit of measurement RouteSegment maximumCrossingAtEnd All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A97 Warning ICAO Annex 11 Each ArrivalFeederLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found ArrivalFeederLeg with upperLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement ArrivalFeederLeg upperLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A98 Warning ICAO Annex 11 Each ArrivalFeederLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found ArrivalFeederLeg with lowerLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement ArrivalFeederLeg lowerLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A99 Warning ICAO Annex 11 Each ArrivalFeederLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideATC value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideATC </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found ArrivalFeederLeg with altitudeOverrideATC value that does not correspond to 'FL' (or 'SM') as unit of measurement ArrivalFeederLeg altitudeOverrideATC All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A9A Warning ICAO Annex 11 Each FinalLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found FinalLeg with upperLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement FinalLeg upperLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A9B Warning ICAO Annex 11 Each FinalLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found FinalLeg with lowerLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement FinalLeg lowerLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A9C Warning ICAO Annex 11 Each FinalLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideATC value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideATC </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found FinalLeg with altitudeOverrideATC value that does not correspond to 'FL' (or 'SM') as unit of measurement FinalLeg altitudeOverrideATC All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A9D Warning ICAO Annex 11 Each InitialLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found InitialLeg with upperLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement InitialLeg upperLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A9E Warning ICAO Annex 11 Each InitialLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found InitialLeg with lowerLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement InitialLeg lowerLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4A9F Warning ICAO Annex 11 Each InitialLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideATC value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideATC </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found InitialLeg with altitudeOverrideATC value that does not correspond to 'FL' (or 'SM') as unit of measurement InitialLeg altitudeOverrideATC All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA0 Warning ICAO Annex 11 Each IntermediateLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found IntermediateLeg with upperLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement IntermediateLeg upperLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA1 Warning ICAO Annex 11 Each IntermediateLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found IntermediateLeg with lowerLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement IntermediateLeg lowerLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA2 Warning ICAO Annex 11 Each IntermediateLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideATC value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideATC </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found IntermediateLeg with altitudeOverrideATC value that does not correspond to 'FL' (or 'SM') as unit of measurement IntermediateLeg altitudeOverrideATC All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA3 Warning ICAO Annex 11 Each MissedApproachLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found MissedApproachLeg with upperLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement MissedApproachLeg upperLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA4 Warning ICAO Annex 11 Each MissedApproachLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found MissedApproachLeg with lowerLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement MissedApproachLeg lowerLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA5 Warning ICAO Annex 11 Each MissedApproachLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideATC value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideATC </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found MissedApproachLeg with altitudeOverrideATC value that does not correspond to 'FL' (or 'SM') as unit of measurement MissedApproachLeg altitudeOverrideATC All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA6 Warning ICAO Annex 11 Each ArrivalLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found ArrivalLeg with upperLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement ArrivalLeg upperLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA7 Warning ICAO Annex 11 Each ArrivalLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found ArrivalLeg with lowerLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement ArrivalLeg lowerLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA8 Warning ICAO Annex 11 Each ArrivalLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideATC value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideATC </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found ArrivalLeg with altitudeOverrideATC value that does not correspond to 'FL' (or 'SM') as unit of measurement ArrivalLeg altitudeOverrideATC All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AA9 Warning ICAO Annex 11 Each DepartureLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found DepartureLeg with upperLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement DepartureLeg upperLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AAA Warning ICAO Annex 11 Each DepartureLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found DepartureLeg with lowerLimitAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement DepartureLeg lowerLimitAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AAB Warning ICAO Annex 11 Each DepartureLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideATC value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideATC </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found DepartureLeg with altitudeOverrideATC value that does not correspond to 'FL' (or 'SM') as unit of measurement DepartureLeg altitudeOverrideATC All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AAC Warning ICAO Annex 11 Each CheckpointINS with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> CheckpointINS </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found CheckpointINS with upperLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement CheckpointINS upperLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AAD Warning ICAO Annex 11 Each CheckpointINS with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> CheckpointINS </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found CheckpointINS with lowerLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement CheckpointINS lowerLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AAE Warning ICAO Annex 11 Each CheckpointVOR with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> CheckpointVOR </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found CheckpointVOR with upperLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement CheckpointVOR upperLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4AAF Warning ICAO Annex 11 Each CheckpointVOR with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimit value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> CheckpointVOR </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimit </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have 1, 2 or 3 digits Found CheckpointVOR with lowerLimit value that does not correspond to 'FL' (or 'SM') as unit of measurement CheckpointVOR lowerLimit All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A4E61 Error Error AIXM 4.5 Business Rules Each AirspaceVolume with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). AirspaceVolume lowerLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E62 Error AIXM 4.5 Business Rules Each RouteSegment with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). RouteSegment lowerLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E64 Error AIXM 4.5 Business Rules Each AirspaceLayer with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> AirspaceLayer </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). AirspaceLayer upperLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E65 Warning AIXM 4.5 Business Rules Each Minima with altitude.uom equal-to ('FL', 'SM') shall have altitudeReference equal-to 'STD' <keyword> Each </keyword><noun_concept> Minima </noun_concept><keyword> with </keyword><noun_concept> altitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). Minima altitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E67 Warning AIXM 4.5 Business Rules Each HoldingUse with instructedAltitude.uom equal-to ('FL', 'SM') shall have instructionAltitudeReference equal-to 'STD' <keyword> Each </keyword><noun_concept> HoldingUse </noun_concept><keyword> with </keyword><noun_concept> instructedAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> instructionAltitudeReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). HoldingUse instructedAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E68 Error AIXM 4.5 Business Rules Each RouteSegment with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). RouteSegment upperLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E6A Warning AIXM 4.5 Business Rules Each DepartureArrivalCondition with maximumCrossingAtEnd.uom equal-to ('FL', 'SM') shall have maximumCrossingAtEndReference equal-to 'STD' <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><keyword> with </keyword><noun_concept> maximumCrossingAtEnd.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> maximumCrossingAtEndReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). DepartureArrivalCondition maximumCrossingAtEnd EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E6B Error AIXM 4.5 Business Rules Each RouteSegment with minimumCrossingAtEnd.uom equal-to ('FL', 'SM') shall have minimumCrossingAtEndReference equal-to 'STD' <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with </keyword><noun_concept> minimumCrossingAtEnd.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> minimumCrossingAtEndReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). RouteSegment minimumCrossingAtEnd EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E6C Warning AIXM 4.5 Business Rules Each HoldingAssessment with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). HoldingAssessment upperLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E6D Warning AIXM 4.5 Business Rules Each CircleSector with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). CircleSector lowerLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E6F Error AIXM 4.5 Business Rules Each RouteSegment with maximumCrossingAtEnd.uom equal-to ('FL', 'SM') shall have maximumCrossingAtEndReference equal-to 'STD' <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with </keyword><noun_concept> maximumCrossingAtEnd.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> maximumCrossingAtEndReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). RouteSegment maximumCrossingAtEnd EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E72 Warning AIXM 4.5 Business Rules Each HoldingAssessment with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). HoldingAssessment lowerLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E73 Error AIXM 4.5 Business Rules Each AirspaceVolume with minimumLimit.uom equal-to ('FL', 'SM') shall have minimumLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> minimumLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> minimumLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). AirspaceVolume minimumLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E75 Warning AIXM 4.5 Business Rules Each ApproachAltitudeTable with altitude.uom equal-to ('FL', 'SM') shall have altitudeReference equal-to 'STD' <keyword> Each </keyword><noun_concept> ApproachAltitudeTable </noun_concept><keyword> with </keyword><noun_concept> altitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). ApproachAltitudeTable altitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E76 Error AIXM 4.5 Business Rules Each AirspaceVolume with maximumLimit.uom equal-to ('FL', 'SM') shall have maximumLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> maximumLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> maximumLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). AirspaceVolume maximumLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E77 Warning AIXM 4.5 Business Rules Each CircleSector with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). CircleSector upperLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E79 Warning AIXM 4.5 Business Rules Each DepartureArrivalCondition with minimumCrossingAtEnd.uom equal-to ('FL', 'SM') shall have minimumCrossingAtEndReference equal-to 'STD' <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><keyword> with </keyword><noun_concept> minimumCrossingAtEnd.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> minimumCrossingAtEndReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). DepartureArrivalCondition minimumCrossingAtEnd EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E7A Error Error AIXM 4.5 Business Rules Each AirspaceVolume with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). AirspaceVolume upperLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E7B Warning AIXM 4.5 Business Rules Each AirspaceLayer with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> AirspaceLayer </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). AirspaceLayer lowerLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E7C Warning AIXM 4.5 Business Rules Each ArrivalFeederLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). ArrivalFeederLeg upperLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E7D Warning AIXM 4.5 Business Rules Each ArrivalFeederLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). ArrivalFeederLeg lowerLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E7E Warning AIXM 4.5 Business Rules Each ArrivalFeederLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideReference equal-to 'STD' <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). ArrivalFeederLeg altitudeOverrideATC EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E7F Warning AIXM 4.5 Business Rules Each FinalLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). FinalLeg upperLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E80 Warning AIXM 4.5 Business Rules Each FinalLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). FinalLeg lowerLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E81 Warning AIXM 4.5 Business Rules Each FinalLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideReference equal-to 'STD' <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). FinalLeg altitudeOverrideATC EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E82 Warning AIXM 4.5 Business Rules Each InitialLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). InitialLeg upperLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E83 Warning AIXM 4.5 Business Rules Each InitialLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). InitialLeg lowerLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E84 Warning AIXM 4.5 Business Rules Each InitialLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideReference equal-to 'STD' <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). InitialLeg altitudeOverrideATC EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E85 Warning AIXM 4.5 Business Rules Each IntermediateLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). IntermediateLeg upperLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E86 Warning AIXM 4.5 Business Rules Each IntermediateLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). IntermediateLeg lowerLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E87 Warning AIXM 4.5 Business Rules Each IntermediateLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideReference equal-to 'STD' <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). IntermediateLeg altitudeOverrideATC EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E88 Warning AIXM 4.5 Business Rules Each MissedApproachLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). MissedApproachLeg upperLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E89 Warning AIXM 4.5 Business Rules Each MissedApproachLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). MissedApproachLeg lowerLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E8A Warning AIXM 4.5 Business Rules Each MissedApproachLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideReference equal-to 'STD' <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). MissedApproachLeg altitudeOverrideATC EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E8B Warning AIXM 4.5 Business Rules Each ArrivalLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). ArrivalLeg upperLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E8C Warning AIXM 4.5 Business Rules Each ArrivalLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). ArrivalLeg lowerLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E8D Warning AIXM 4.5 Business Rules Each ArrivalLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideReference equal-to 'STD' <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). ArrivalLeg altitudeOverrideATC EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E8E Warning AIXM 4.5 Business Rules Each DepartureLeg with upperLimitAltitude.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). DepartureLeg upperLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E8F Warning AIXM 4.5 Business Rules Each DepartureLeg with lowerLimitAltitude.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). DepartureLeg lowerLimitAltitude EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E90 Warning AIXM 4.5 Business Rules Each DepartureLeg with altitudeOverrideATC.uom equal-to ('FL', 'SM') shall have altitudeOverrideReference equal-to 'STD' <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> altitudeOverrideReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). DepartureLeg altitudeOverrideATC EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E91 Warning AIXM 4.5 Business Rules Each CheckpointINS with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> CheckpointINS </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). CheckpointINS upperLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E92 Warning AIXM 4.5 Business Rules Each CheckpointINS with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> CheckpointINS </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). CheckpointINS lowerLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E93 Warning AIXM 4.5 Business Rules Each CheckpointVOR with upperLimit.uom equal-to ('FL', 'SM') shall have upperLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> CheckpointVOR </noun_concept><keyword> with </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). CheckpointVOR upperLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A4E94 Warning AIXM 4.5 Business Rules Each CheckpointVOR with lowerLimit.uom equal-to ('FL', 'SM') shall have lowerLimitReference equal-to 'STD' <keyword> Each </keyword><noun_concept> CheckpointVOR </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLimitReference </noun_concept><keyword> equal-to </keyword><name> 'STD' </name> If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). If the unit of measurement has the value 'FL' or 'SM', then the corresponding altitude reference shall have the value 'STD' (standard pressure). CheckpointVOR lowerLimit EXCL_DELTA;NO_REF Data consistency rule Standard pressure as reference for FL or SM (EAD profile)
AIXM-5.1_RULE-1A3EC1 Error Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Curve shall not have descendant ArcStringByBulge <keyword> Each </keyword><noun_concept> Curve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> ArcStringByBulge </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Curve with ArcStringByBulge descendant Curve ArcStringByBulge N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EC2 Error Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Curve shall not have descendant ArcByBulge <keyword> Each </keyword><noun_concept> Curve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> ArcByBulge </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Curve with ArcByBulge descendant Curve ArcByBulge N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EC3 Error Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Curve shall not have descendant ArcString <keyword> Each </keyword><noun_concept> Curve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> ArcString </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Curve with ArcString descendant Curve ArcString N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EC4 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Curve shall not have descendant BSplineCurve <keyword> Each </keyword><noun_concept> Curve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> BSplineCurve </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Curve with BSplineCurve descendant Curve BSplineCurve N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EC5 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Curve shall not have descendant Bezier <keyword> Each </keyword><noun_concept> Curve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Bezier </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Curve with Bezier descendant Curve Bezier N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EC6 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Curve shall not have descendant CubicSpline <keyword> Each </keyword><noun_concept> Curve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> CubicSpline </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Curve with CubicSpline descendant Curve CubicSpline N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EC7 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Curve shall not have descendant Clothoid <keyword> Each </keyword><noun_concept> Curve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Clothoid </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Curve with Clothoid descendant Curve Clothoid N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EC8 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Curve shall not have descendant OffsetCurve <keyword> Each </keyword><noun_concept> Curve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> OffsetCurve </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Curve with OffsetCurve descendant Curve OffsetCurve N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EC9 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedCurve shall not have descendant ArcStringByBulge <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> ArcStringByBulge </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedCurve with ArcStringByBulge descendant ElevatedCurve ArcStringByBulge N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ECA Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedCurve shall not have descendant ArcByBulge <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> ArcByBulge </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedCurve with ArcByBulge descendant ElevatedCurve ArcByBulge N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ECB Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedCurve shall not have descendant ArcString <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> ArcString </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedCurve with ArcString descendant ElevatedCurve ArcString N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ECC Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedCurve shall not have descendant BSplineCurve <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> BSplineCurve </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedCurve with BSplineCurve descendant ElevatedCurve BSplineCurve N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ECD Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedCurve shall not have descendant Bezier <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Bezier </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedCurve with Bezier descendant ElevatedCurve Bezier N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ECE Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedCurve shall not have descendant CubicSpline <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> CubicSpline </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedCurve with CubicSpline descendant ElevatedCurve CubicSpline N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ECF Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedCurve shall not have descendant Clothoid <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Clothoid </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedCurve with Clothoid descendant ElevatedCurve Clothoid N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED0 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedCurve shall not have descendant OffsetCurve <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> OffsetCurve </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedCurve with OffsetCurve descendant ElevatedCurve OffsetCurve N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED1 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Surface shall not have descendant Rectangle <keyword> Each </keyword><noun_concept> Surface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Rectangle </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Surface with Rectangle descendant Surface Rectangle N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED2 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Surface shall not have descendant Triangle <keyword> Each </keyword><noun_concept> Surface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Triangle </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Surface with Triangle descendant Surface Triangle N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED3 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Surface shall not have descendant Cone <keyword> Each </keyword><noun_concept> Surface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Cone </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Surface with Cone descendant Surface Cone N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED4 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Surface shall not have descendant Cylinder <keyword> Each </keyword><noun_concept> Surface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Cylinder </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Surface with Cylinder descendant Surface Cylinder N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED5 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Surface shall not have descendant Sphere <keyword> Each </keyword><noun_concept> Surface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Sphere </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Surface with Sphere descendant Surface Sphere N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED6 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each Surface shall not have descendant LinearRing <keyword> Each </keyword><noun_concept> Surface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> LinearRing </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found Surface with LinearRing descendant Surface LinearRing N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED7 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedSurface shall not have descendant Rectangle <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Rectangle </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedSurface with Rectangle descendant ElevatedSurface Rectangle N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED8 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedSurface shall not have descendant Triangle <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Triangle </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedSurface with Triangle descendant ElevatedSurface Triangle N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3ED9 Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedSurface shall not have descendant Cone <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Cone </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedSurface with Cone descendant ElevatedSurface Cone N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EDA Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedSurface shall not have descendant Cylinder <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Cylinder </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedSurface with Cylinder descendant ElevatedSurface Cylinder N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EDB Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedSurface shall not have descendant Sphere <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> Sphere </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedSurface with Sphere descendant ElevatedSurface Sphere N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3EDC Error AIXM GML Profile https://portal.opengeospatial.org/files/?artifact_id=47859 Each ElevatedSurface shall not have descendant LinearRing <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> shall not </keyword><verb_concept> have descendant </verb_concept><noun_concept> LinearRing </noun_concept> GML elements that are not included in the GML Aviation profile (https://portal.opengeospatial.org/files/?artifact_id=47859) shall not be used in AIXM. GML Profile error: found ElevatedSurface with LinearRing descendant ElevatedSurface LinearRing N/A Recommended practice (ICAO, industry, etc.) GML Profile - not allowed geometry for Point, Curve, Surface
AIXM-5.1_RULE-1A3309 Warning AIXM 4.5 Each AirportHeliportAvailability shall have assigned usage value <keyword> Each </keyword><noun_concept> AirportHeliportAvailability </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> usage </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliportAvailability without usage value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliportAvailability usage N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A330A Warning AIXM 4.5 Each SpecialNavigationStation shall have assigned systemChain value <keyword> Each </keyword><noun_concept> SpecialNavigationStation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> systemChain </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialNavigationStation without systemChain value. Backwards mapping to AIXM 4.5 will not be possible. SpecialNavigationStation systemChain N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A330B Warning AIXM 4.5 Each StandardInstrumentDeparture shall have assigned airportHeliport value <keyword> Each </keyword><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found StandardInstrumentDeparture without airportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. StandardInstrumentDeparture airportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A330D Warning AIXM 4.5 Each AircraftStand shall have assigned apronLocation value <keyword> Each </keyword><noun_concept> AircraftStand </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> apronLocation </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AircraftStand without apronLocation value. Backwards mapping to AIXM 4.5 will not be possible. AircraftStand apronLocation N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3310 Warning AIXM 4.5 Each UsageCondition shall have assigned selection value <keyword> Each </keyword><noun_concept> UsageCondition </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> selection </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found UsageCondition without selection value. Backwards mapping to AIXM 4.5 will not be possible. UsageCondition selection N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3313 Warning AIXM 4.5 Each StandardInstrumentArrival shall have assigned availability value <keyword> Each </keyword><noun_concept> StandardInstrumentArrival </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> availability </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found StandardInstrumentArrival without availability value. Backwards mapping to AIXM 4.5 will not be possible. StandardInstrumentArrival availability N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3315 Warning AIXM 4.5 Each ApronLightSystem shall have assigned lightedApron value <keyword> Each </keyword><noun_concept> ApronLightSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lightedApron </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found ApronLightSystem without lightedApron value. Backwards mapping to AIXM 4.5 will not be possible. ApronLightSystem lightedApron N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3319 Warning AIXM 4.5 Each UsageCondition shall have assigned type value <keyword> Each </keyword><noun_concept> UsageCondition </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found UsageCondition without type value. Backwards mapping to AIXM 4.5 will not be possible. UsageCondition type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A331B Warning AIXM 4.5 Each PassengerService shall have assigned airportHeliport value <keyword> Each </keyword><noun_concept> PassengerService </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found PassengerService without airportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. PassengerService airportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A331C Warning AIXM 4.5 Each Azimuth shall have assigned designator value <keyword> Each </keyword><noun_concept> Azimuth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Azimuth without designator value. Backwards mapping to AIXM 4.5 will not be possible. Azimuth designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3320 Warning AIXM 4.5 Each AircraftStand shall have assigned designator value <keyword> Each </keyword><noun_concept> AircraftStand </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AircraftStand without designator value. Backwards mapping to AIXM 4.5 will not be possible. AircraftStand designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3323 Warning AIXM 4.5 Each Apron shall have assigned name value <keyword> Each </keyword><noun_concept> Apron </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> name </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Apron without name value. Backwards mapping to AIXM 4.5 will not be possible. Apron name N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3325 Warning AIXM 4.5 Each Timesheet shall have assigned startDate value <keyword> Each </keyword><noun_concept> Timesheet </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> startDate </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Timesheet without startDate value. Backwards mapping to AIXM 4.5 will not be possible. Timesheet startDate N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A332D Warning AIXM 4.5 Each Azimuth shall have assigned channel value <keyword> Each </keyword><noun_concept> Azimuth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> channel </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Azimuth without channel value. Backwards mapping to AIXM 4.5 will not be possible. Azimuth channel N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A332E Warning AIXM 4.5 Each FireFightingService shall have assigned airportHeliport value <keyword> Each </keyword><noun_concept> FireFightingService </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found FireFightingService without airportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. FireFightingService airportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A332F Warning AIXM 4.5 Each StandardLevelColumn shall have assigned levelTable value <keyword> Each </keyword><noun_concept> StandardLevelColumn </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> levelTable </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found StandardLevelColumn without levelTable value. Backwards mapping to AIXM 4.5 will not be possible. StandardLevelColumn levelTable N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3332 Warning AIXM 4.5 Each Azimuth shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> Azimuth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Azimuth without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. Azimuth location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3334 Warning AIXM 4.5 Each Glidepath shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> Glidepath </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Glidepath without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. Glidepath location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3335 Warning AIXM 4.5 Each SpecialNavigationStation shall have assigned type value <keyword> Each </keyword><noun_concept> SpecialNavigationStation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialNavigationStation without type value. Backwards mapping to AIXM 4.5 will not be possible. SpecialNavigationStation type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3337 Warning AIXM 4.5 Each RunwayCentrelinePoint shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RunwayCentrelinePoint without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. RunwayCentrelinePoint location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3338 Warning AIXM 4.5 Each RunwayCentrelinePoint shall have assigned onRunway value <keyword> Each </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> onRunway </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RunwayCentrelinePoint without onRunway value. Backwards mapping to AIXM 4.5 will not be possible. RunwayCentrelinePoint onRunway N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3339 Warning AIXM 4.5 Each Glidepath shall have assigned frequency value <keyword> Each </keyword><noun_concept> Glidepath </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Glidepath without frequency value. Backwards mapping to AIXM 4.5 will not be possible. Glidepath frequency N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A333A Warning AIXM 4.5 Each Localizer shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> Localizer </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Localizer without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. Localizer location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A333D Warning AIXM 4.5 Each ApproachLightingSystem shall have assigned type value <keyword> Each </keyword><noun_concept> ApproachLightingSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found ApproachLightingSystem without type value. Backwards mapping to AIXM 4.5 will not be possible. ApproachLightingSystem type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A333F Warning AIXM 4.5 Each AircraftStand shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> AircraftStand </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AircraftStand without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. AircraftStand location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3341 Warning AIXM 4.5 Each RunwayProtectArea shall have assigned surfaceProperties value <keyword> Each </keyword><noun_concept> RunwayProtectArea </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> surfaceProperties </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RunwayProtectArea without surfaceProperties value. Backwards mapping to AIXM 4.5 will not be possible. RunwayProtectArea surfaceProperties N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3342 Warning AIXM 4.5 Each DistanceIndication shall have assigned distance value <keyword> Each </keyword><noun_concept> DistanceIndication </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distance </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DistanceIndication without distance value. Backwards mapping to AIXM 4.5 will not be possible. DistanceIndication distance N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3343 Warning AIXM 4.5 Each StandardLevelColumn shall have assigned level value <keyword> Each </keyword><noun_concept> StandardLevelColumn </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> level </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found StandardLevelColumn without level value. Backwards mapping to AIXM 4.5 will not be possible. StandardLevelColumn level N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3344 Warning AIXM 4.5 Each Elevation shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> Elevation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Elevation without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. Elevation location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3345 Warning AIXM 4.5 Each SpecialNavigationSystem shall have assigned designator value <keyword> Each </keyword><noun_concept> SpecialNavigationSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialNavigationSystem without designator value. Backwards mapping to AIXM 4.5 will not be possible. SpecialNavigationSystem designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3346 Warning AIXM 4.5 Each Apron shall have assigned surfaceProperties value <keyword> Each </keyword><noun_concept> Apron </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> surfaceProperties </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Apron without surfaceProperties value. Backwards mapping to AIXM 4.5 will not be possible. Apron surfaceProperties N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A334C Warning AIXM 4.5 Each UnitDependency shall have assigned type value <keyword> Each </keyword><noun_concept> UnitDependency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found UnitDependency without type value. Backwards mapping to AIXM 4.5 will not be possible. UnitDependency type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A334D Warning AIXM 4.5 Each TouchDownLiftOff shall have assigned associatedAirportHeliport value <keyword> Each </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TouchDownLiftOff without associatedAirportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. TouchDownLiftOff associatedAirportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A334E Warning AIXM 4.5 Each AirportSuppliesService shall have assigned airportHeliport value <keyword> Each </keyword><noun_concept> AirportSuppliesService </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportSuppliesService without airportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. AirportSuppliesService airportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A334F Warning AIXM 4.5 Each TouchDownLiftOffLightSystem shall have assigned position value <keyword> Each </keyword><noun_concept> TouchDownLiftOffLightSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> position </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TouchDownLiftOffLightSystem without position value. Backwards mapping to AIXM 4.5 will not be possible. TouchDownLiftOffLightSystem position N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3352 Warning AIXM 4.5 Each VerticalStructure shall have assigned lighted value <keyword> Each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lighted </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found VerticalStructure without lighted value. Backwards mapping to AIXM 4.5 will not be possible. VerticalStructure lighted N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3353 Warning AIXM 4.5 Each Oxygen shall have assigned type value <keyword> Each </keyword><noun_concept> Oxygen </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Oxygen without type value. Backwards mapping to AIXM 4.5 will not be possible. Oxygen type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3354 Warning AIXM 4.5 Each RunwayProtectArea shall have assigned type value <keyword> Each </keyword><noun_concept> RunwayProtectArea </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RunwayProtectArea without type value. Backwards mapping to AIXM 4.5 will not be possible. RunwayProtectArea type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3357 Warning AIXM 4.5 Each Taxiway shall have assigned associatedAirportHeliport value <keyword> Each </keyword><noun_concept> Taxiway </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Taxiway without associatedAirportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. Taxiway associatedAirportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3359 Warning AIXM 4.5 Each InstrumentApproachProcedure shall have assigned airportHeliport value <keyword> Each </keyword><noun_concept> InstrumentApproachProcedure </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found InstrumentApproachProcedure without airportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. InstrumentApproachProcedure airportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A335F Warning AIXM 4.5 Each RouteAvailability shall have assigned status value <keyword> Each </keyword><noun_concept> RouteAvailability </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> status </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RouteAvailability without status value. Backwards mapping to AIXM 4.5 will not be possible. RouteAvailability status N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3361 Warning AIXM 4.5 Each TouchDownLiftOffLightSystem shall have assigned lightedTouchDownLiftOff value <keyword> Each </keyword><noun_concept> TouchDownLiftOffLightSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lightedTouchDownLiftOff </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TouchDownLiftOffLightSystem without lightedTouchDownLiftOff value. Backwards mapping to AIXM 4.5 will not be possible. TouchDownLiftOffLightSystem lightedTouchDownLiftOff N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3362 Warning AIXM 4.5 Each ProcedureAvailability shall have assigned status value <keyword> Each </keyword><noun_concept> ProcedureAvailability </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> status </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found ProcedureAvailability without status value. Backwards mapping to AIXM 4.5 will not be possible. ProcedureAvailability status N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3369 Warning AIXM 4.5 Each TouchDownLiftOff shall have assigned designator value <keyword> Each </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TouchDownLiftOff without designator value. Backwards mapping to AIXM 4.5 will not be possible. TouchDownLiftOff designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A336A Warning AIXM 4.5 Each RunwayDirectionLightSystem shall have assigned associatedRunwayDirection value <keyword> Each </keyword><noun_concept> RunwayDirectionLightSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> associatedRunwayDirection </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RunwayDirectionLightSystem without associatedRunwayDirection value. Backwards mapping to AIXM 4.5 will not be possible. RunwayDirectionLightSystem associatedRunwayDirection N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A336D Warning AIXM 4.5 Each AirportHeliportCollocation shall have assigned dependentAirport value <keyword> Each </keyword><noun_concept> AirportHeliportCollocation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> dependentAirport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliportCollocation without dependentAirport value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliportCollocation dependentAirport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A336F Warning AIXM 4.5 Each Service shall have assigned serviceProvider value <keyword> Each </keyword><noun_concept> Service </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Service without serviceProvider value. Backwards mapping to AIXM 4.5 will not be possible. Service serviceProvider N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3370 Warning AIXM 4.5 Each Oil shall have assigned category value <keyword> Each </keyword><noun_concept> Oil </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> category </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Oil without category value. Backwards mapping to AIXM 4.5 will not be possible. Oil category N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3372 Warning Warning AIXM 4.5 Each AeronauticalGroundLight shall have assigned type value <keyword> Each </keyword><noun_concept> AeronauticalGroundLight </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AeronauticalGroundLight without type value. Backwards mapping to AIXM 4.5 will not be possible. AeronauticalGroundLight type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3373 Warning AIXM 4.5 Each Azimuth shall have assigned type value <keyword> Each </keyword><noun_concept> Azimuth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Azimuth without type value. Backwards mapping to AIXM 4.5 will not be possible. Azimuth type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3374 Warning AIXM 4.5 Each Localizer shall have assigned frequency value <keyword> Each </keyword><noun_concept> Localizer </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Localizer without frequency value. Backwards mapping to AIXM 4.5 will not be possible. Localizer frequency N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3376 Warning AIXM 4.5 Each RadioCommunicationChannel shall have assigned frequencyTransmission value <keyword> Each </keyword><noun_concept> RadioCommunicationChannel </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequencyTransmission </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RadioCommunicationChannel without frequencyTransmission value. Backwards mapping to AIXM 4.5 will not be possible. RadioCommunicationChannel frequencyTransmission N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3378 Warning AIXM 4.5 Each SpecialNavigationStation shall have assigned position.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> SpecialNavigationStation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> position.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialNavigationStation without position.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. SpecialNavigationStation position.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3379 Warning AIXM 4.5 Each AirportHeliportCollocation shall have assigned type value <keyword> Each </keyword><noun_concept> AirportHeliportCollocation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliportCollocation without type value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliportCollocation type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A337B Warning AIXM 4.5 Each SpecialDate shall have assigned type value <keyword> Each </keyword><noun_concept> SpecialDate </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialDate without type value. Backwards mapping to AIXM 4.5 will not be possible. SpecialDate type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A337C Warning AIXM 4.5 Each RunwayDirectionLightSystem shall have assigned position value <keyword> Each </keyword><noun_concept> RunwayDirectionLightSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> position </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RunwayDirectionLightSystem without position value. Backwards mapping to AIXM 4.5 will not be possible. RunwayDirectionLightSystem position N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3380 Warning AIXM 4.5 Each HoldingPattern shall have assigned type value <keyword> Each </keyword><noun_concept> HoldingPattern </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found HoldingPattern without type value. Backwards mapping to AIXM 4.5 will not be possible. HoldingPattern type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3381 Warning AIXM 4.5 Each StandardInstrumentDeparture shall have assigned availability.ProcedureAvailability value <keyword> Each </keyword><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> availability.ProcedureAvailability </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found StandardInstrumentDeparture without availability.ProcedureAvailability value. Backwards mapping to AIXM 4.5 will not be possible. StandardInstrumentDeparture availability.ProcedureAvailability N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3383 Warning AIXM 4.5 Each Taxiway shall have assigned designator value <keyword> Each </keyword><noun_concept> Taxiway </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Taxiway without designator value. Backwards mapping to AIXM 4.5 will not be possible. Taxiway designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3385 Warning AIXM 4.5 Each StandardLevel shall have assigned verticalDistance value <keyword> Each </keyword><noun_concept> StandardLevel </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalDistance </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found StandardLevel without verticalDistance value. Backwards mapping to AIXM 4.5 will not be possible. StandardLevel verticalDistance N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3386 Warning AIXM 4.5 Each StandardInstrumentArrival shall have assigned airportHeliport value <keyword> Each </keyword><noun_concept> StandardInstrumentArrival </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found StandardInstrumentArrival without airportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. StandardInstrumentArrival airportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3388 Warning AIXM 4.5 Each OrganisationAuthorityAssociation shall have assigned type value <keyword> Each </keyword><noun_concept> OrganisationAuthorityAssociation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found OrganisationAuthorityAssociation without type value. Backwards mapping to AIXM 4.5 will not be possible. OrganisationAuthorityAssociation type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A338B Warning AIXM 4.5 Each TouchDownLiftOff shall have assigned aimingPoint.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> aimingPoint.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TouchDownLiftOff without aimingPoint.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. TouchDownLiftOff aimingPoint.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A338C Warning AIXM 4.5 Each AircraftGroundService shall have assigned airportHeliport value <keyword> Each </keyword><noun_concept> AircraftGroundService </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AircraftGroundService without airportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. AircraftGroundService airportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A338E Warning AIXM 4.5 Each Taxiway shall have assigned type value <keyword> Each </keyword><noun_concept> Taxiway </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Taxiway without type value. Backwards mapping to AIXM 4.5 will not be possible. Taxiway type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3390 Warning AIXM 4.5 Each RunwayProtectArea shall have assigned protectedRunwayDirection value <keyword> Each </keyword><noun_concept> RunwayProtectArea </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> protectedRunwayDirection </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RunwayProtectArea without protectedRunwayDirection value. Backwards mapping to AIXM 4.5 will not be possible. RunwayProtectArea protectedRunwayDirection N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3394 Warning AIXM 4.5 Each AirportHeliportCollocation shall have assigned hostAirport value <keyword> Each </keyword><noun_concept> AirportHeliportCollocation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> hostAirport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliportCollocation without hostAirport value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliportCollocation hostAirport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3397 Warning AIXM 4.5 Each Timesheet shall have assigned day value <keyword> Each </keyword><noun_concept> Timesheet </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> day </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Timesheet without day value. Backwards mapping to AIXM 4.5 will not be possible. Timesheet day N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3399 Warning AIXM 4.5 Each Timesheet shall have assigned timeReference value <keyword> Each </keyword><noun_concept> Timesheet </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> timeReference </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Timesheet without timeReference value. Backwards mapping to AIXM 4.5 will not be possible. Timesheet timeReference N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A339A Warning AIXM 4.5 Each TouchDownLiftOffSafeArea shall have assigned protectedTouchDownLiftOff value <keyword> Each </keyword><noun_concept> TouchDownLiftOffSafeArea </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> protectedTouchDownLiftOff </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TouchDownLiftOffSafeArea without protectedTouchDownLiftOff value. Backwards mapping to AIXM 4.5 will not be possible. TouchDownLiftOffSafeArea protectedTouchDownLiftOff N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A339B Warning Warning AIXM 4.5 Each AeronauticalGroundLight shall have assigned name value <keyword> Each </keyword><noun_concept> AeronauticalGroundLight </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> name </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AeronauticalGroundLight without name value. Backwards mapping to AIXM 4.5 will not be possible. AeronauticalGroundLight name N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A339D Warning AIXM 4.5 Each RouteAvailability shall have assigned direction value <keyword> Each </keyword><noun_concept> RouteAvailability </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> direction </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RouteAvailability without direction value. Backwards mapping to AIXM 4.5 will not be possible. RouteAvailability direction N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A339F Warning AIXM 4.5 Each Fuel shall have assigned category value <keyword> Each </keyword><noun_concept> Fuel </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> category </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Fuel without category value. Backwards mapping to AIXM 4.5 will not be possible. Fuel category N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33A4 Warning AIXM 4.5 Each SpecialNavigationStation shall have assigned name value <keyword> Each </keyword><noun_concept> SpecialNavigationStation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> name </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialNavigationStation without name value. Backwards mapping to AIXM 4.5 will not be possible. SpecialNavigationStation name N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33A8 Warning AIXM 4.5 Each ObstacleArea shall have assigned reference value <keyword> Each </keyword><noun_concept> ObstacleArea </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> reference </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found ObstacleArea without reference value. Backwards mapping to AIXM 4.5 will not be possible. ObstacleArea reference N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33AD Warning AIXM 4.5 Each TaxiwayLightSystem shall have assigned position value <keyword> Each </keyword><noun_concept> TaxiwayLightSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> position </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TaxiwayLightSystem without position value. Backwards mapping to AIXM 4.5 will not be possible. TaxiwayLightSystem position N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33AE Warning AIXM 4.5 Each ObstacleArea shall have assigned obstacle value <keyword> Each </keyword><noun_concept> ObstacleArea </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> obstacle </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found ObstacleArea without obstacle value. Backwards mapping to AIXM 4.5 will not be possible. ObstacleArea obstacle N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33B3 Warning AIXM 4.5 Each SpecialDate shall have assigned dateDay value <keyword> Each </keyword><noun_concept> SpecialDate </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> dateDay </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialDate without dateDay value. Backwards mapping to AIXM 4.5 will not be possible. SpecialDate dateDay N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33B6 Warning Warning AIXM 4.5 Each AeronauticalGroundLight shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> AeronauticalGroundLight </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AeronauticalGroundLight without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. AeronauticalGroundLight location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33B8 Warning AIXM 4.5 Each TaxiwayLightSystem shall have assigned lightedTaxiway value <keyword> Each </keyword><noun_concept> TaxiwayLightSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lightedTaxiway </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TaxiwayLightSystem without lightedTaxiway value. Backwards mapping to AIXM 4.5 will not be possible. TaxiwayLightSystem lightedTaxiway N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33B9 Warning AIXM 4.5 Each AngleIndication shall have assigned angle value <keyword> Each </keyword><noun_concept> AngleIndication </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> angle </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AngleIndication without angle value. Backwards mapping to AIXM 4.5 will not be possible. AngleIndication angle N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33BB Warning AIXM 4.5 Each SpecialDate shall have assigned authority.OrganisationAuthority value <keyword> Each </keyword><noun_concept> SpecialDate </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> authority.OrganisationAuthority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialDate without authority.OrganisationAuthority value. Backwards mapping to AIXM 4.5 will not be possible. SpecialDate authority.OrganisationAuthority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33BC Warning AIXM 4.5 Each VerticalStructure shall have assigned group value <keyword> Each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> group </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found VerticalStructure without group value. Backwards mapping to AIXM 4.5 will not be possible. VerticalStructure group N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33C2 Warning AIXM 4.5 Each Apron shall have assigned associatedAirportHeliport value <keyword> Each </keyword><noun_concept> Apron </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Apron without associatedAirportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. Apron associatedAirportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33C3 Warning AIXM 4.5 Each RadioFrequencyArea shall have assigned type value <keyword> Each </keyword><noun_concept> RadioFrequencyArea </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RadioFrequencyArea without type value. Backwards mapping to AIXM 4.5 will not be possible. RadioFrequencyArea type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33C7 Warning AIXM 4.5 Each HoldingPattern shall have assigned holdingPoint value <keyword> Each </keyword><noun_concept> HoldingPattern </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> holdingPoint </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found HoldingPattern without holdingPoint value. Backwards mapping to AIXM 4.5 will not be possible. HoldingPattern holdingPoint N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33C9 Warning AIXM 4.5 Each SpecialNavigationSystem shall have assigned responsibleOrganisation value <keyword> Each </keyword><noun_concept> SpecialNavigationSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> responsibleOrganisation </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialNavigationSystem without responsibleOrganisation value. Backwards mapping to AIXM 4.5 will not be possible. SpecialNavigationSystem responsibleOrganisation N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33CA Warning AIXM 4.5 Each CallsignDetail shall have assigned callSign value <keyword> Each </keyword><noun_concept> CallsignDetail </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> callSign </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found CallsignDetail without callSign value. Backwards mapping to AIXM 4.5 will not be possible. CallsignDetail callSign N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33CC Warning AIXM 4.5 Each ApproachLightingSystem shall have assigned servedRunwayDirection value <keyword> Each </keyword><noun_concept> ApproachLightingSystem </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> servedRunwayDirection </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found ApproachLightingSystem without servedRunwayDirection value. Backwards mapping to AIXM 4.5 will not be possible. ApproachLightingSystem servedRunwayDirection N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33CD Warning AIXM 4.5 Each Localizer shall have assigned designator value <keyword> Each </keyword><noun_concept> Localizer </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Localizer without designator value. Backwards mapping to AIXM 4.5 will not be possible. Localizer designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33CE Warning AIXM 4.5 Each AircraftStand shall have assigned type value <keyword> Each </keyword><noun_concept> AircraftStand </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AircraftStand without type value. Backwards mapping to AIXM 4.5 will not be possible. AircraftStand type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33CF Warning AIXM 4.5 Each Timesheet shall have assigned endDate value <keyword> Each </keyword><noun_concept> Timesheet </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> endDate </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Timesheet without endDate value. Backwards mapping to AIXM 4.5 will not be possible. Timesheet endDate N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33D0 Warning AIXM 4.5 Each RadioFrequencyArea shall have assigned signalType value <keyword> Each </keyword><noun_concept> RadioFrequencyArea </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> signalType </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RadioFrequencyArea without signalType value. Backwards mapping to AIXM 4.5 will not be possible. RadioFrequencyArea signalType N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33D2 Warning AIXM 4.5 Each VerticalStructure shall have assigned type value <keyword> Each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found VerticalStructure without type value. Backwards mapping to AIXM 4.5 will not be possible. VerticalStructure type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33D3 Warning AIXM 4.5 Each CallsignDetail shall have assigned language value <keyword> Each </keyword><noun_concept> CallsignDetail </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> language </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found CallsignDetail without language value. Backwards mapping to AIXM 4.5 will not be possible. CallsignDetail language N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33D6 Warning AIXM 4.5 Each SpecialNavigationStation shall have assigned responsibleOrganisation value <keyword> Each </keyword><noun_concept> SpecialNavigationStation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> responsibleOrganisation </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SpecialNavigationStation without responsibleOrganisation value. Backwards mapping to AIXM 4.5 will not be possible. SpecialNavigationStation responsibleOrganisation N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33DC Warning AIXM 4.5 Each AirportClearanceService shall have assigned airportHeliport value <keyword> Each </keyword><noun_concept> AirportClearanceService </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportClearanceService without airportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. AirportClearanceService airportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33DD Warning AIXM 4.5 Each Timesheet shall have assigned daylightSavingAdjust value <keyword> Each </keyword><noun_concept> Timesheet </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> daylightSavingAdjust </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Timesheet without daylightSavingAdjust value. Backwards mapping to AIXM 4.5 will not be possible. Timesheet daylightSavingAdjust N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33DE Warning AIXM 4.5 Each HoldingUse shall have assigned theHoldingPattern value <keyword> Each </keyword><noun_concept> HoldingUse </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theHoldingPattern </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found HoldingUse without theHoldingPattern value. Backwards mapping to AIXM 4.5 will not be possible. HoldingUse theHoldingPattern N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E5 Warning AIXM 4.5 Each ProcedureTransitionLeg shall have assigned theSegmentLeg value <keyword> Each </keyword><noun_concept> ProcedureTransitionLeg </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theSegmentLeg </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found ProcedureTransitionLeg without theSegmentLeg value. Backwards mapping to AIXM 4.5 will not be possible. ProcedureTransitionLeg theSegmentLeg N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E6 Warning AIXM 4.5 Each RadarComponent shall have assigned theRadarEquipment value <keyword> Each </keyword><noun_concept> RadarComponent </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theRadarEquipment </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RadarComponent without theRadarEquipment value. Backwards mapping to AIXM 4.5 will not be possible. RadarComponent theRadarEquipment N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E7 Warning AIXM 4.5 Each AngleUse shall have assigned theAngleIndication value <keyword> Each </keyword><noun_concept> AngleUse </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theAngleIndication </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AngleUse without theAngleIndication value. Backwards mapping to AIXM 4.5 will not be possible. AngleUse theAngleIndication N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E8 Warning AIXM 4.5 Each SurveillanceGroundStation shall have assigned theUnit value <keyword> Each </keyword><noun_concept> SurveillanceGroundStation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theUnit </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found SurveillanceGroundStation without theUnit value. Backwards mapping to AIXM 4.5 will not be possible. SurveillanceGroundStation theUnit N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E9 Warning AIXM 4.5 Each AuthorityForSpecialNavigationStation shall have assigned theOrganisationAuthority value <keyword> Each </keyword><noun_concept> AuthorityForSpecialNavigationStation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theOrganisationAuthority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AuthorityForSpecialNavigationStation without theOrganisationAuthority value. Backwards mapping to AIXM 4.5 will not be possible. AuthorityForSpecialNavigationStation theOrganisationAuthority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33EA Warning AIXM 4.5 Each NavaidEquipmentDistance shall have assigned theNavaidEquipment value <keyword> Each </keyword><noun_concept> NavaidEquipmentDistance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theNavaidEquipment </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found NavaidEquipmentDistance without theNavaidEquipment value. Backwards mapping to AIXM 4.5 will not be possible. NavaidEquipmentDistance theNavaidEquipment N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33ED Warning AIXM 4.5 Each InstrumentApproachProcedure shall have assigned approachType value <keyword> Each </keyword><noun_concept> InstrumentApproachProcedure </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> approachType </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found InstrumentApproachProcedure without approachType value. Backwards mapping to AIXM 4.5 will not be possible. InstrumentApproachProcedure approachType N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33EE Warning AIXM 4.5 Each InstrumentApproachProcedure shall have assigned name value <keyword> Each </keyword><noun_concept> InstrumentApproachProcedure </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> name </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found InstrumentApproachProcedure without name value. Backwards mapping to AIXM 4.5 will not be possible. InstrumentApproachProcedure name N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-D4A59 Error Error Each AirportHeliport with assigned fieldElevationAccuracy value and with assigned ARP.ElevatedPoint.geoidUndulation value shall have fieldElevationAccuracy.uom equal-to ARP.ElevatedPoint.geoidUndulation.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> fieldElevationAccuracy </noun_concept><keyword> value and with assigned </keyword><noun_concept> ARP.ElevatedPoint.geoidUndulation </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> fieldElevationAccuracy.uom </noun_concept><keyword> equal-to </keyword><noun_concept> ARP.ElevatedPoint.geoidUndulation.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport ARP.ElevatedPoint.geoidUndulation fieldElevationAccuracy Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A5A Error Each ElevatedPoint with assigned geoidUndulation value and with assigned verticalAccuracy value shall have geoidUndulation.uom equal-to verticalAccuracy.uom <keyword> Each </keyword><noun_concept> ElevatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> geoidUndulation </noun_concept><keyword> value and with assigned </keyword><noun_concept> verticalAccuracy </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> geoidUndulation.uom </noun_concept><keyword> equal-to </keyword><noun_concept> verticalAccuracy.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. ElevatedPoint verticalAccuracy geoidUndulation Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A5B Error Each ElevatedPoint with assigned verticalAccuracy value and with assigned elevation value shall have verticalAccuracy.uom equal-to elevation.uom <keyword> Each </keyword><noun_concept> ElevatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> verticalAccuracy </noun_concept><keyword> value and with assigned </keyword><noun_concept> elevation </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><noun_concept> elevation.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. ElevatedPoint elevation verticalAccuracy Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A5E Error Each AirportHeliport with assigned ARP.ElevatedPoint.verticalAccuracy value and with assigned ARP.ElevatedPoint.geoidUndulation value shall have ARP.ElevatedPoint.verticalAccuracy.uom equal-to ARP.ElevatedPoint.geoidUndulation.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> ARP.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value and with assigned </keyword><noun_concept> ARP.ElevatedPoint.geoidUndulation </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> ARP.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><noun_concept> ARP.ElevatedPoint.geoidUndulation.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport ARP.ElevatedPoint.geoidUndulation ARP.ElevatedPoint.verticalAccuracy Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A5F Error Each AirportHeliport with assigned ARP.ElevatedPoint.geoidUndulation value and with assigned fieldElevation value shall have ARP.ElevatedPoint.geoidUndulation.uom equal-to fieldElevation.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> ARP.ElevatedPoint.geoidUndulation </noun_concept><keyword> value and with assigned </keyword><noun_concept> fieldElevation </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> ARP.ElevatedPoint.geoidUndulation.uom </noun_concept><keyword> equal-to </keyword><noun_concept> fieldElevation.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport fieldElevation ARP.ElevatedPoint.geoidUndulation Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A60 Error Each AirportHeliport with assigned ARP.ElevatedPoint.elevation value and with assigned ARP.ElevatedPoint.verticalAccuracy value shall have ARP.ElevatedPoint.elevation.uom equal-to ARP.ElevatedPoint.verticalAccuracy.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> ARP.ElevatedPoint.elevation </noun_concept><keyword> value and with assigned </keyword><noun_concept> ARP.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> ARP.ElevatedPoint.elevation.uom </noun_concept><keyword> equal-to </keyword><noun_concept> ARP.ElevatedPoint.verticalAccuracy.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport ARP.ElevatedPoint.verticalAccuracy ARP.ElevatedPoint.elevation Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A66 Error Each AirportHeliport with assigned fieldElevationAccuracy value and with assigned ARP.ElevatedPoint.elevation value shall have fieldElevationAccuracy.uom equal-to ARP.ElevatedPoint.elevation.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> fieldElevationAccuracy </noun_concept><keyword> value and with assigned </keyword><noun_concept> ARP.ElevatedPoint.elevation </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> fieldElevationAccuracy.uom </noun_concept><keyword> equal-to </keyword><noun_concept> ARP.ElevatedPoint.elevation.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport ARP.ElevatedPoint.elevation fieldElevationAccuracy Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A67 Error Each ElevatedPoint with assigned elevation value and with assigned geoidUndulation value shall have elevation.uom equal-to geoidUndulation.uom <keyword> Each </keyword><noun_concept> ElevatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> elevation </noun_concept><keyword> value and with assigned </keyword><noun_concept> geoidUndulation </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> elevation.uom </noun_concept><keyword> equal-to </keyword><noun_concept> geoidUndulation.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. ElevatedPoint geoidUndulation elevation Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A69 Error Each AirportHeliport with assigned fieldElevation value and with assigned fieldElevationAccuracy value shall have fieldElevation.uom equal-to fieldElevationAccuracy.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> fieldElevation </noun_concept><keyword> value and with assigned </keyword><noun_concept> fieldElevationAccuracy </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> fieldElevation.uom </noun_concept><keyword> equal-to </keyword><noun_concept> fieldElevationAccuracy.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport fieldElevationAccuracy fieldElevation Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A6D Error Each AirportHeliport with assigned fieldElevation value and with assigned ARP.ElevatedPoint.elevation value shall have fieldElevation.uom equal-to ARP.ElevatedPoint.elevation.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> fieldElevation </noun_concept><keyword> value and with assigned </keyword><noun_concept> ARP.ElevatedPoint.elevation </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> fieldElevation.uom </noun_concept><keyword> equal-to </keyword><noun_concept> ARP.ElevatedPoint.elevation.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport ARP.ElevatedPoint.elevation fieldElevation Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A6F Error Each AirportHeliport with assigned ARP.ElevatedPoint.elevation value and with assigned ARP.ElevatedPoint.geoidUndulation value shall have ARP.ElevatedPoint.elevation.uom equal-to ARP.ElevatedPoint.geoidUndulation.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> ARP.ElevatedPoint.elevation </noun_concept><keyword> value and with assigned </keyword><noun_concept> ARP.ElevatedPoint.geoidUndulation </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> ARP.ElevatedPoint.elevation.uom </noun_concept><keyword> equal-to </keyword><noun_concept> ARP.ElevatedPoint.geoidUndulation.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport ARP.ElevatedPoint.geoidUndulation ARP.ElevatedPoint.elevation Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A70 Error Each AirportHeliport with assigned fieldElevationAccuracy value and with assigned ARP.ElevatedPoint.verticalAccuracy value shall have fieldElevationAccuracy.uom equal-to ARP.ElevatedPoint.verticalAccuracy.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> fieldElevationAccuracy </noun_concept><keyword> value and with assigned </keyword><noun_concept> ARP.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> fieldElevationAccuracy.uom </noun_concept><keyword> equal-to </keyword><noun_concept> ARP.ElevatedPoint.verticalAccuracy.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport ARP.ElevatedPoint.verticalAccuracy fieldElevationAccuracy Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A71 Error Error Each RouteSegment with assigned widthLeft value and with assigned widthRight value shall have widthLeft.uom equal-to widthRight.uom <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> widthLeft </noun_concept><keyword> value and with assigned </keyword><noun_concept> widthRight </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> widthLeft.uom </noun_concept><keyword> equal-to </keyword><noun_concept> widthRight.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. RouteSegment widthRight widthLeft Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A72 Error Each RunwayDirection with assigned elevationTDZ value and with assigned elevationTDZAccuracy value shall have elevationTDZ.uom equal-to elevationTDZAccuracy.uom <keyword> Each </keyword><noun_concept> RunwayDirection </noun_concept><keyword> with assigned </keyword><noun_concept> elevationTDZ </noun_concept><keyword> value and with assigned </keyword><noun_concept> elevationTDZAccuracy </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> elevationTDZ.uom </noun_concept><keyword> equal-to </keyword><noun_concept> elevationTDZAccuracy.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. RunwayDirection elevationTDZAccuracy elevationTDZ Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D4A73 Error Each AirportHeliport with assigned fieldElevation value and with assigned ARP.ElevatedPoint.verticalAccuracy value shall have fieldElevation.uom equal-to ARP.ElevatedPoint.verticalAccuracy.uom <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> fieldElevation </noun_concept><keyword> value and with assigned </keyword><noun_concept> ARP.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> fieldElevation.uom </noun_concept><keyword> equal-to </keyword><noun_concept> ARP.ElevatedPoint.verticalAccuracy.uom </noun_concept> Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. Certain dimension value properties, if specified, must use same unit of measurement. This is both for logical reasons (for example, it does not make sense to use FT for elevation and M for elevation accuracy) and for ensuring AIXM 4.5 backwards mapping. AirportHeliport ARP.ElevatedPoint.verticalAccuracy fieldElevation Data consistency rule Unit of measurement must be the same
AIXM-5.1_RULE-D8CC5 Error AIXM Model Each AircraftCharacteristic with assigned wingSpan shall have assigned wingSpan.uom value <keyword> Each </keyword><noun_concept> AircraftCharacteristic </noun_concept><keyword> with assigned </keyword><noun_concept> wingSpan </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> wingSpan.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AircraftCharacteristic with assigned wingSpan value missing unit of measurement AircraftCharacteristic wingSpan All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CC6 Error AIXM Model Each AircraftCharacteristic with assigned weight shall have assigned weight.uom value <keyword> Each </keyword><noun_concept> AircraftCharacteristic </noun_concept><keyword> with assigned </keyword><noun_concept> weight </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> weight.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AircraftCharacteristic with assigned weight value missing unit of measurement AircraftCharacteristic weight All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CC7 Error AIXM Model Each AircraftCharacteristic with assigned speed shall have assigned speed.uom value <keyword> Each </keyword><noun_concept> AircraftCharacteristic </noun_concept><keyword> with assigned </keyword><noun_concept> speed </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> speed.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AircraftCharacteristic with assigned speed value missing unit of measurement AircraftCharacteristic speed All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CC8 Error Error AIXM Model Each AirportHeliport with assigned fieldElevation shall have assigned fieldElevation.uom value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> fieldElevation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> fieldElevation.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirportHeliport with assigned fieldElevation value missing unit of measurement AirportHeliport fieldElevation All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CC9 Error Error AIXM Model Each AirportHeliport with assigned fieldElevationAccuracy shall have assigned fieldElevationAccuracy.uom value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> fieldElevationAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> fieldElevationAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirportHeliport with assigned fieldElevationAccuracy value missing unit of measurement AirportHeliport fieldElevationAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CCA Error AIXM Model Each AirportHeliport with assigned referenceTemperature shall have assigned referenceTemperature.uom value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> referenceTemperature </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> referenceTemperature.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirportHeliport with assigned referenceTemperature value missing unit of measurement AirportHeliport referenceTemperature All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CCB Error AIXM Model Each AirportHeliport with assigned transitionAltitude shall have assigned transitionAltitude.uom value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> transitionAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> transitionAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirportHeliport with assigned transitionAltitude value missing unit of measurement AirportHeliport transitionAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CCC Error AIXM Model Each AirportHeliport with assigned transitionLevel shall have assigned transitionLevel.uom value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> transitionLevel </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> transitionLevel.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirportHeliport with assigned transitionLevel value missing unit of measurement AirportHeliport transitionLevel All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CCD Error AIXM Model Each AirportHeliport with assigned lowestTemperature shall have assigned lowestTemperature.uom value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> lowestTemperature </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowestTemperature.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirportHeliport with assigned lowestTemperature value missing unit of measurement AirportHeliport lowestTemperature All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CCE Error AIXM Model Each AirportHeliportProtectionArea with assigned width shall have assigned width.uom value <keyword> Each </keyword><noun_concept> AirportHeliportProtectionArea </noun_concept><keyword> with assigned </keyword><noun_concept> width </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirportHeliportProtectionArea with assigned width value missing unit of measurement AirportHeliportProtectionArea width All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CCF Error AIXM Model Each AirportHeliportProtectionArea with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> AirportHeliportProtectionArea </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirportHeliportProtectionArea with assigned length value missing unit of measurement AirportHeliportProtectionArea length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD0 Error AIXM Model Each Airspace with assigned upperLowerSeparation shall have assigned upperLowerSeparation.uom value <keyword> Each </keyword><noun_concept> Airspace </noun_concept><keyword> with assigned </keyword><noun_concept> upperLowerSeparation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLowerSeparation.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Airspace with assigned upperLowerSeparation value missing unit of measurement Airspace upperLowerSeparation All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD1 Error AIXM Model Each AirspaceLayer with assigned upperLimit shall have assigned upperLimit.uom value <keyword> Each </keyword><noun_concept> AirspaceLayer </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirspaceLayer with assigned upperLimit value missing unit of measurement AirspaceLayer upperLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD2 Error AIXM Model Each AirspaceLayer with assigned lowerLimit shall have assigned lowerLimit.uom value <keyword> Each </keyword><noun_concept> AirspaceLayer </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirspaceLayer with assigned lowerLimit value missing unit of measurement AirspaceLayer lowerLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD3 Error Error AIXM Model Each AirspaceVolume with assigned upperLimit shall have assigned upperLimit.uom value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirspaceVolume with assigned upperLimit value missing unit of measurement AirspaceVolume upperLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD4 Error AIXM Model Each AirspaceVolume with assigned maximumLimit shall have assigned maximumLimit.uom value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> maximumLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> maximumLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirspaceVolume with assigned maximumLimit value missing unit of measurement AirspaceVolume maximumLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD5 Error Error AIXM Model Each AirspaceVolume with assigned lowerLimit shall have assigned lowerLimit.uom value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirspaceVolume with assigned lowerLimit value missing unit of measurement AirspaceVolume lowerLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD6 Error AIXM Model Each AirspaceVolume with assigned minimumLimit shall have assigned minimumLimit.uom value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> minimumLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirspaceVolume with assigned minimumLimit value missing unit of measurement AirspaceVolume minimumLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD7 Error AIXM Model Each AirspaceVolume with assigned width shall have assigned width.uom value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> width </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AirspaceVolume with assigned width value missing unit of measurement AirspaceVolume width All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD8 Error AIXM Model Each AltitudeAdjustment with assigned altitudeAdjustment shall have assigned altitudeAdjustment.uom value <keyword> Each </keyword><noun_concept> AltitudeAdjustment </noun_concept><keyword> with assigned </keyword><noun_concept> altitudeAdjustment </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeAdjustment.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AltitudeAdjustment with assigned altitudeAdjustment value missing unit of measurement AltitudeAdjustment altitudeAdjustment All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CD9 Error AIXM Model Each AngleIndication with assigned minimumReceptionAltitude shall have assigned minimumReceptionAltitude.uom value <keyword> Each </keyword><noun_concept> AngleIndication </noun_concept><keyword> with assigned </keyword><noun_concept> minimumReceptionAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumReceptionAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found AngleIndication with assigned minimumReceptionAltitude value missing unit of measurement AngleIndication minimumReceptionAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CDA Error AIXM Model Each ApproachAltitudeTable with assigned altitude shall have assigned altitude.uom value <keyword> Each </keyword><noun_concept> ApproachAltitudeTable </noun_concept><keyword> with assigned </keyword><noun_concept> altitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ApproachAltitudeTable with assigned altitude value missing unit of measurement ApproachAltitudeTable altitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CDB Error AIXM Model Each ApproachDistanceTable with assigned valueHAT shall have assigned valueHAT.uom value <keyword> Each </keyword><noun_concept> ApproachDistanceTable </noun_concept><keyword> with assigned </keyword><noun_concept> valueHAT </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> valueHAT.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ApproachDistanceTable with assigned valueHAT value missing unit of measurement ApproachDistanceTable valueHAT All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CDC Error AIXM Model Each ApproachDistanceTable with assigned distance shall have assigned distance.uom value <keyword> Each </keyword><noun_concept> ApproachDistanceTable </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ApproachDistanceTable with assigned distance value missing unit of measurement ApproachDistanceTable distance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CDD Error AIXM Model Each ApproachLightingSystem with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> ApproachLightingSystem </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ApproachLightingSystem with assigned length value missing unit of measurement ApproachLightingSystem length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CDE Error AIXM Model Each ApproachTimingTable with assigned time shall have assigned time.uom value <keyword> Each </keyword><noun_concept> ApproachTimingTable </noun_concept><keyword> with assigned </keyword><noun_concept> time </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> time.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ApproachTimingTable with assigned time value missing unit of measurement ApproachTimingTable time All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CDF Error AIXM Model Each ApproachTimingTable with assigned speed shall have assigned speed.uom value <keyword> Each </keyword><noun_concept> ApproachTimingTable </noun_concept><keyword> with assigned </keyword><noun_concept> speed </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> speed.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ApproachTimingTable with assigned speed value missing unit of measurement ApproachTimingTable speed All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE0 Error AIXM Model Each ApronElement with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> ApronElement </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ApronElement with assigned length value missing unit of measurement ApronElement length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE1 Error AIXM Model Each ApronElement with assigned width shall have assigned width.uom value <keyword> Each </keyword><noun_concept> ApronElement </noun_concept><keyword> with assigned </keyword><noun_concept> width </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ApronElement with assigned width value missing unit of measurement ApronElement width All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE2 Error AIXM Model Each ArrestingGear with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> ArrestingGear </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ArrestingGear with assigned length value missing unit of measurement ArrestingGear length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE3 Error AIXM Model Each ArrestingGear with assigned width shall have assigned width.uom value <keyword> Each </keyword><noun_concept> ArrestingGear </noun_concept><keyword> with assigned </keyword><noun_concept> width </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ArrestingGear with assigned width value missing unit of measurement ArrestingGear width All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE4 Error AIXM Model Each ArrestingGear with assigned location shall have assigned location.uom value <keyword> Each </keyword><noun_concept> ArrestingGear </noun_concept><keyword> with assigned </keyword><noun_concept> location </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ArrestingGear with assigned location value missing unit of measurement ArrestingGear location All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE5 Error AIXM Model Each ChangeOverPoint with assigned distance shall have assigned distance.uom value <keyword> Each </keyword><noun_concept> ChangeOverPoint </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ChangeOverPoint with assigned distance value missing unit of measurement ChangeOverPoint distance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE6 Error AIXM Model Each CircleSector with assigned innerDistance shall have assigned innerDistance.uom value <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with assigned </keyword><noun_concept> innerDistance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> innerDistance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found CircleSector with assigned innerDistance value missing unit of measurement CircleSector innerDistance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE7 Error AIXM Model Each CircleSector with assigned outerDistance shall have assigned outerDistance.uom value <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with assigned </keyword><noun_concept> outerDistance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> outerDistance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found CircleSector with assigned outerDistance value missing unit of measurement CircleSector outerDistance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE8 Error AIXM Model Each CircleSector with assigned upperLimit shall have assigned upperLimit.uom value <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found CircleSector with assigned upperLimit value missing unit of measurement CircleSector upperLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CE9 Error AIXM Model Each CircleSector with assigned lowerLimit shall have assigned lowerLimit.uom value <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found CircleSector with assigned lowerLimit value missing unit of measurement CircleSector lowerLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CEA Error AIXM Model Each Curve with assigned horizontalAccuracy shall have assigned horizontalAccuracy.uom value <keyword> Each </keyword><noun_concept> Curve </noun_concept><keyword> with assigned </keyword><noun_concept> horizontalAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> horizontalAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Curve with assigned horizontalAccuracy value missing unit of measurement Curve horizontalAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CEB Error AIXM Model Each DepartureArrivalCondition with assigned minimumEnrouteAltitude shall have assigned minimumEnrouteAltitude.uom value <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><keyword> with assigned </keyword><noun_concept> minimumEnrouteAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumEnrouteAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found DepartureArrivalCondition with assigned minimumEnrouteAltitude value missing unit of measurement DepartureArrivalCondition minimumEnrouteAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CEC Error AIXM Model Each DepartureArrivalCondition with assigned minimumCrossingAtEnd shall have assigned minimumCrossingAtEnd.uom value <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><keyword> with assigned </keyword><noun_concept> minimumCrossingAtEnd </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumCrossingAtEnd.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found DepartureArrivalCondition with assigned minimumCrossingAtEnd value missing unit of measurement DepartureArrivalCondition minimumCrossingAtEnd All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CED Error AIXM Model Each DepartureArrivalCondition with assigned maximumCrossingAtEnd shall have assigned maximumCrossingAtEnd.uom value <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><keyword> with assigned </keyword><noun_concept> maximumCrossingAtEnd </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> maximumCrossingAtEnd.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found DepartureArrivalCondition with assigned maximumCrossingAtEnd value missing unit of measurement DepartureArrivalCondition maximumCrossingAtEnd All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CEE Error AIXM Model Each DepartureLeg with assigned minimumObstacleClearanceAltitude shall have assigned minimumObstacleClearanceAltitude.uom value <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with assigned </keyword><noun_concept> minimumObstacleClearanceAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumObstacleClearanceAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found DepartureLeg with assigned minimumObstacleClearanceAltitude value missing unit of measurement DepartureLeg minimumObstacleClearanceAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF0 Error AIXM Model Each DistanceIndication with assigned distance shall have assigned distance.uom value <keyword> Each </keyword><noun_concept> DistanceIndication </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found DistanceIndication with assigned distance value missing unit of measurement DistanceIndication distance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF1 Error AIXM Model Each DistanceIndication with assigned minimumReceptionAltitude shall have assigned minimumReceptionAltitude.uom value <keyword> Each </keyword><noun_concept> DistanceIndication </noun_concept><keyword> with assigned </keyword><noun_concept> minimumReceptionAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumReceptionAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found DistanceIndication with assigned minimumReceptionAltitude value missing unit of measurement DistanceIndication minimumReceptionAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF2 Error AIXM Model Each DME with assigned ghostFrequency shall have assigned ghostFrequency.uom value <keyword> Each </keyword><noun_concept> DME </noun_concept><keyword> with assigned </keyword><noun_concept> ghostFrequency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> ghostFrequency.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found DME with assigned ghostFrequency value missing unit of measurement DME ghostFrequency All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF3 Error AIXM Model Each DME with assigned displace shall have assigned displace.uom value <keyword> Each </keyword><noun_concept> DME </noun_concept><keyword> with assigned </keyword><noun_concept> displace </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> displace.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found DME with assigned displace value missing unit of measurement DME displace All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF4 Error AIXM Model Each ElevatedCurve with assigned elevation shall have assigned elevation.uom value <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> with assigned </keyword><noun_concept> elevation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> elevation.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ElevatedCurve with assigned elevation value missing unit of measurement ElevatedCurve elevation All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF5 Error AIXM Model Each ElevatedCurve with assigned geoidUndulation shall have assigned geoidUndulation.uom value <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> with assigned </keyword><noun_concept> geoidUndulation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> geoidUndulation.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ElevatedCurve with assigned geoidUndulation value missing unit of measurement ElevatedCurve geoidUndulation All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF6 Error AIXM Model Each ElevatedCurve with assigned verticalAccuracy shall have assigned verticalAccuracy.uom value <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> with assigned </keyword><noun_concept> verticalAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ElevatedCurve with assigned verticalAccuracy value missing unit of measurement ElevatedCurve verticalAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF7 Error AIXM Model Each ElevatedPoint with assigned elevation shall have assigned elevation.uom value <keyword> Each </keyword><noun_concept> ElevatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> elevation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> elevation.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ElevatedPoint with assigned elevation value missing unit of measurement ElevatedPoint elevation All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF8 Error AIXM Model Each ElevatedPoint with assigned geoidUndulation shall have assigned geoidUndulation.uom value <keyword> Each </keyword><noun_concept> ElevatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> geoidUndulation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> geoidUndulation.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ElevatedPoint with assigned geoidUndulation value missing unit of measurement ElevatedPoint geoidUndulation All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CF9 Error AIXM Model Each ElevatedPoint with assigned verticalAccuracy shall have assigned verticalAccuracy.uom value <keyword> Each </keyword><noun_concept> ElevatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> verticalAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ElevatedPoint with assigned verticalAccuracy value missing unit of measurement ElevatedPoint verticalAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CFA Error AIXM Model Each ElevatedSurface with assigned elevation shall have assigned elevation.uom value <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> with assigned </keyword><noun_concept> elevation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> elevation.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ElevatedSurface with assigned elevation value missing unit of measurement ElevatedSurface elevation All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CFB Error AIXM Model Each ElevatedSurface with assigned geoidUndulation shall have assigned geoidUndulation.uom value <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> with assigned </keyword><noun_concept> geoidUndulation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> geoidUndulation.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ElevatedSurface with assigned geoidUndulation value missing unit of measurement ElevatedSurface geoidUndulation All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CFC Error AIXM Model Each ElevatedSurface with assigned verticalAccuracy shall have assigned verticalAccuracy.uom value <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> with assigned </keyword><noun_concept> verticalAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ElevatedSurface with assigned verticalAccuracy value missing unit of measurement ElevatedSurface verticalAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CFD Error AIXM Model Each EnRouteSegmentPoint with assigned turnRadius shall have assigned turnRadius.uom value <keyword> Each </keyword><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> turnRadius </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> turnRadius.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found EnRouteSegmentPoint with assigned turnRadius value missing unit of measurement EnRouteSegmentPoint turnRadius All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CFE Error AIXM Model Each EquipmentUnavailableAdjustmentColumn with assigned visibilityAdjustment shall have assigned visibilityAdjustment.uom value <keyword> Each </keyword><noun_concept> EquipmentUnavailableAdjustmentColumn </noun_concept><keyword> with assigned </keyword><noun_concept> visibilityAdjustment </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> visibilityAdjustment.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found EquipmentUnavailableAdjustmentColumn with assigned visibilityAdjustment value missing unit of measurement EquipmentUnavailableAdjustmentColumn visibilityAdjustment All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8CFF Error AIXM Model Each FASDataBlock with assigned thresholdCourseWidth shall have assigned thresholdCourseWidth.uom value <keyword> Each </keyword><noun_concept> FASDataBlock </noun_concept><keyword> with assigned </keyword><noun_concept> thresholdCourseWidth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> thresholdCourseWidth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found FASDataBlock with assigned thresholdCourseWidth value missing unit of measurement FASDataBlock thresholdCourseWidth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D00 Error AIXM Model Each FASDataBlock with assigned lengthOffset shall have assigned lengthOffset.uom value <keyword> Each </keyword><noun_concept> FASDataBlock </noun_concept><keyword> with assigned </keyword><noun_concept> lengthOffset </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lengthOffset.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found FASDataBlock with assigned lengthOffset value missing unit of measurement FASDataBlock lengthOffset All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D01 Error AIXM Model Each FinalLeg with assigned minimumBaroVnavTemperature shall have assigned minimumBaroVnavTemperature.uom value <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> minimumBaroVnavTemperature </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumBaroVnavTemperature.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found FinalLeg with assigned minimumBaroVnavTemperature value missing unit of measurement FinalLeg minimumBaroVnavTemperature All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D02 Error AIXM Model Each FinalLeg with assigned courseCentrelineDistance shall have assigned courseCentrelineDistance.uom value <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> courseCentrelineDistance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> courseCentrelineDistance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found FinalLeg with assigned courseCentrelineDistance value missing unit of measurement FinalLeg courseCentrelineDistance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D03 Error AIXM Model Each FinalLeg with assigned courseOffsetDistance shall have assigned courseOffsetDistance.uom value <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> courseOffsetDistance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> courseOffsetDistance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found FinalLeg with assigned courseOffsetDistance value missing unit of measurement FinalLeg courseOffsetDistance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D07 Error AIXM Model Each Glidepath with assigned frequency shall have assigned frequency.uom value <keyword> Each </keyword><noun_concept> Glidepath </noun_concept><keyword> with assigned </keyword><noun_concept> frequency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Glidepath with assigned frequency value missing unit of measurement Glidepath frequency All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D08 Error AIXM Model Each Glidepath with assigned rdh shall have assigned rdh.uom value <keyword> Each </keyword><noun_concept> Glidepath </noun_concept><keyword> with assigned </keyword><noun_concept> rdh </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> rdh.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Glidepath with assigned rdh value missing unit of measurement Glidepath rdh All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D09 Error AIXM Model Each Glidepath with assigned rdhAccuracy shall have assigned rdhAccuracy.uom value <keyword> Each </keyword><noun_concept> Glidepath </noun_concept><keyword> with assigned </keyword><noun_concept> rdhAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> rdhAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Glidepath with assigned rdhAccuracy value missing unit of measurement Glidepath rdhAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D0A Error AIXM Model Each GuidanceLine with assigned maxSpeed shall have assigned maxSpeed.uom value <keyword> Each </keyword><noun_concept> GuidanceLine </noun_concept><keyword> with assigned </keyword><noun_concept> maxSpeed </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> maxSpeed.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found GuidanceLine with assigned maxSpeed value missing unit of measurement GuidanceLine maxSpeed All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D0B Error AIXM Model Each HoldingAssessment with assigned upperLimit shall have assigned upperLimit.uom value <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingAssessment with assigned upperLimit value missing unit of measurement HoldingAssessment upperLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D0C Error AIXM Model Each HoldingAssessment with assigned lowerLimit shall have assigned lowerLimit.uom value <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingAssessment with assigned lowerLimit value missing unit of measurement HoldingAssessment lowerLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D0D Error AIXM Model Each HoldingAssessment with assigned speedLimit shall have assigned speedLimit.uom value <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with assigned </keyword><noun_concept> speedLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> speedLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingAssessment with assigned speedLimit value missing unit of measurement HoldingAssessment speedLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D0E Error AIXM Model Each HoldingAssessment with assigned legLengthToward shall have assigned legLengthToward.uom value <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with assigned </keyword><noun_concept> legLengthToward </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> legLengthToward.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingAssessment with assigned legLengthToward value missing unit of measurement HoldingAssessment legLengthToward All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D0F Error AIXM Model Each HoldingAssessment with assigned legLengthAway shall have assigned legLengthAway.uom value <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with assigned </keyword><noun_concept> legLengthAway </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> legLengthAway.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingAssessment with assigned legLengthAway value missing unit of measurement HoldingAssessment legLengthAway All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D10 Error AIXM Model Each HoldingPattern with assigned upperLimit shall have assigned upperLimit.uom value <keyword> Each </keyword><noun_concept> HoldingPattern </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingPattern with assigned upperLimit value missing unit of measurement HoldingPattern upperLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D11 Error AIXM Model Each HoldingPattern with assigned lowerLimit shall have assigned lowerLimit.uom value <keyword> Each </keyword><noun_concept> HoldingPattern </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingPattern with assigned lowerLimit value missing unit of measurement HoldingPattern lowerLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D12 Error AIXM Model Each HoldingPattern with assigned speedLimit shall have assigned speedLimit.uom value <keyword> Each </keyword><noun_concept> HoldingPattern </noun_concept><keyword> with assigned </keyword><noun_concept> speedLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> speedLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingPattern with assigned speedLimit value missing unit of measurement HoldingPattern speedLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D13 Error AIXM Model Each HoldingPatternDistance with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> HoldingPatternDistance </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingPatternDistance with assigned length value missing unit of measurement HoldingPatternDistance length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D14 Error AIXM Model Each HoldingPatternDuration with assigned duration shall have assigned duration.uom value <keyword> Each </keyword><noun_concept> HoldingPatternDuration </noun_concept><keyword> with assigned </keyword><noun_concept> duration </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> duration.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingPatternDuration with assigned duration value missing unit of measurement HoldingPatternDuration duration All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D15 Error AIXM Model Each HoldingUse with assigned instructedAltitude shall have assigned instructedAltitude.uom value <keyword> Each </keyword><noun_concept> HoldingUse </noun_concept><keyword> with assigned </keyword><noun_concept> instructedAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> instructedAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found HoldingUse with assigned instructedAltitude value missing unit of measurement HoldingUse instructedAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D16 Error AIXM Model Each LightElement with assigned intensity shall have assigned intensity.uom value <keyword> Each </keyword><noun_concept> LightElement </noun_concept><keyword> with assigned </keyword><noun_concept> intensity </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> intensity.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found LightElement with assigned intensity value missing unit of measurement LightElement intensity All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D17 Error AIXM Model Each Localizer with assigned frequency shall have assigned frequency.uom value <keyword> Each </keyword><noun_concept> Localizer </noun_concept><keyword> with assigned </keyword><noun_concept> frequency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Localizer with assigned frequency value missing unit of measurement Localizer frequency All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D18 Error AIXM Model Each MarkerBeacon with assigned frequency shall have assigned frequency.uom value <keyword> Each </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> with assigned </keyword><noun_concept> frequency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found MarkerBeacon with assigned frequency value missing unit of measurement MarkerBeacon frequency All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D1B Error AIXM Model Each Minima with assigned altitude shall have assigned altitude.uom value <keyword> Each </keyword><noun_concept> Minima </noun_concept><keyword> with assigned </keyword><noun_concept> altitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Minima with assigned altitude value missing unit of measurement Minima altitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D1C Error AIXM Model Each Minima with assigned height shall have assigned height.uom value <keyword> Each </keyword><noun_concept> Minima </noun_concept><keyword> with assigned </keyword><noun_concept> height </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> height.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Minima with assigned height value missing unit of measurement Minima height All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D1D Error AIXM Model Each Minima with assigned militaryHeight shall have assigned militaryHeight.uom value <keyword> Each </keyword><noun_concept> Minima </noun_concept><keyword> with assigned </keyword><noun_concept> militaryHeight </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> militaryHeight.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Minima with assigned militaryHeight value missing unit of measurement Minima militaryHeight All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D1E Error AIXM Model Each Minima with assigned radioHeight shall have assigned radioHeight.uom value <keyword> Each </keyword><noun_concept> Minima </noun_concept><keyword> with assigned </keyword><noun_concept> radioHeight </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> radioHeight.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Minima with assigned radioHeight value missing unit of measurement Minima radioHeight All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D1F Error AIXM Model Each Minima with assigned visibility shall have assigned visibility.uom value <keyword> Each </keyword><noun_concept> Minima </noun_concept><keyword> with assigned </keyword><noun_concept> visibility </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> visibility.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Minima with assigned visibility value missing unit of measurement Minima visibility All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D20 Error AIXM Model Each Minima with assigned militaryVisibility shall have assigned militaryVisibility.uom value <keyword> Each </keyword><noun_concept> Minima </noun_concept><keyword> with assigned </keyword><noun_concept> militaryVisibility </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> militaryVisibility.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Minima with assigned militaryVisibility value missing unit of measurement Minima militaryVisibility All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D21 Error AIXM Model Each MissedApproachGroup with assigned alternateClimbAltitude shall have assigned alternateClimbAltitude.uom value <keyword> Each </keyword><noun_concept> MissedApproachGroup </noun_concept><keyword> with assigned </keyword><noun_concept> alternateClimbAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> alternateClimbAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found MissedApproachGroup with assigned alternateClimbAltitude value missing unit of measurement MissedApproachGroup alternateClimbAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D22 Error AIXM Model Each MissedApproachLeg with assigned heightMAPT shall have assigned heightMAPT.uom value <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with assigned </keyword><noun_concept> heightMAPT </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> heightMAPT.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found MissedApproachLeg with assigned heightMAPT value missing unit of measurement MissedApproachLeg heightMAPT All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D23 Error AIXM Model Each NavaidEquipmentDistance with assigned distance shall have assigned distance.uom value <keyword> Each </keyword><noun_concept> NavaidEquipmentDistance </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found NavaidEquipmentDistance with assigned distance value missing unit of measurement NavaidEquipmentDistance distance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D24 Error AIXM Model Each NavaidEquipmentDistance with assigned distanceAccuracy shall have assigned distanceAccuracy.uom value <keyword> Each </keyword><noun_concept> NavaidEquipmentDistance </noun_concept><keyword> with assigned </keyword><noun_concept> distanceAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distanceAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found NavaidEquipmentDistance with assigned distanceAccuracy value missing unit of measurement NavaidEquipmentDistance distanceAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D25 Error AIXM Model Each NavigationArea with assigned minimumCeiling shall have assigned minimumCeiling.uom value <keyword> Each </keyword><noun_concept> NavigationArea </noun_concept><keyword> with assigned </keyword><noun_concept> minimumCeiling </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumCeiling.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found NavigationArea with assigned minimumCeiling value missing unit of measurement NavigationArea minimumCeiling All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D26 Error AIXM Model Each NavigationArea with assigned minimumVisibility shall have assigned minimumVisibility.uom value <keyword> Each </keyword><noun_concept> NavigationArea </noun_concept><keyword> with assigned </keyword><noun_concept> minimumVisibility </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumVisibility.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found NavigationArea with assigned minimumVisibility value missing unit of measurement NavigationArea minimumVisibility All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D27 Error AIXM Model Each NavigationSystemCheckpoint with assigned upperLimit shall have assigned upperLimit.uom value <keyword> Each </keyword><noun_concept> NavigationSystemCheckpoint </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found NavigationSystemCheckpoint with assigned upperLimit value missing unit of measurement NavigationSystemCheckpoint upperLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D28 Error AIXM Model Each NavigationSystemCheckpoint with assigned lowerLimit shall have assigned lowerLimit.uom value <keyword> Each </keyword><noun_concept> NavigationSystemCheckpoint </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found NavigationSystemCheckpoint with assigned lowerLimit value missing unit of measurement NavigationSystemCheckpoint lowerLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D29 Error AIXM Model Each NavigationSystemCheckpoint with assigned distance shall have assigned distance.uom value <keyword> Each </keyword><noun_concept> NavigationSystemCheckpoint </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found NavigationSystemCheckpoint with assigned distance value missing unit of measurement NavigationSystemCheckpoint distance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D2A Error AIXM Model Each NDB with assigned frequency shall have assigned frequency.uom value <keyword> Each </keyword><noun_concept> NDB </noun_concept><keyword> with assigned </keyword><noun_concept> frequency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found NDB with assigned frequency value missing unit of measurement NDB frequency All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D2B Error AIXM Model Each ObstacleAssessmentArea with assigned assessedAltitude shall have assigned assessedAltitude.uom value <keyword> Each </keyword><noun_concept> ObstacleAssessmentArea </noun_concept><keyword> with assigned </keyword><noun_concept> assessedAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> assessedAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ObstacleAssessmentArea with assigned assessedAltitude value missing unit of measurement ObstacleAssessmentArea assessedAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D2C Error AIXM Model Each ObstacleAssessmentArea with assigned slopeLowerAltitude shall have assigned slopeLowerAltitude.uom value <keyword> Each </keyword><noun_concept> ObstacleAssessmentArea </noun_concept><keyword> with assigned </keyword><noun_concept> slopeLowerAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> slopeLowerAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ObstacleAssessmentArea with assigned slopeLowerAltitude value missing unit of measurement ObstacleAssessmentArea slopeLowerAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D2D Error AIXM Model Each ObstaclePlacement with assigned obstacleDistance shall have assigned obstacleDistance.uom value <keyword> Each </keyword><noun_concept> ObstaclePlacement </noun_concept><keyword> with assigned </keyword><noun_concept> obstacleDistance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> obstacleDistance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found ObstaclePlacement with assigned obstacleDistance value missing unit of measurement ObstaclePlacement obstacleDistance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D2E Error AIXM Model Each Obstruction with assigned requiredClearance shall have assigned requiredClearance.uom value <keyword> Each </keyword><noun_concept> Obstruction </noun_concept><keyword> with assigned </keyword><noun_concept> requiredClearance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> requiredClearance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Obstruction with assigned requiredClearance value missing unit of measurement Obstruction requiredClearance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D2F Error AIXM Model Each Obstruction with assigned minimumAltitude shall have assigned minimumAltitude.uom value <keyword> Each </keyword><noun_concept> Obstruction </noun_concept><keyword> with assigned </keyword><noun_concept> minimumAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Obstruction with assigned minimumAltitude value missing unit of measurement Obstruction minimumAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D32 Error AIXM Model Each Point with assigned horizontalAccuracy shall have assigned horizontalAccuracy.uom value <keyword> Each </keyword><noun_concept> Point </noun_concept><keyword> with assigned </keyword><noun_concept> horizontalAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> horizontalAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Point with assigned horizontalAccuracy value missing unit of measurement Point horizontalAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D33 Error AIXM Model Each PointReference with assigned priorFixTolerance shall have assigned priorFixTolerance.uom value <keyword> Each </keyword><noun_concept> PointReference </noun_concept><keyword> with assigned </keyword><noun_concept> priorFixTolerance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> priorFixTolerance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found PointReference with assigned priorFixTolerance value missing unit of measurement PointReference priorFixTolerance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D34 Error AIXM Model Each PointReference with assigned postFixTolerance shall have assigned postFixTolerance.uom value <keyword> Each </keyword><noun_concept> PointReference </noun_concept><keyword> with assigned </keyword><noun_concept> postFixTolerance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> postFixTolerance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found PointReference with assigned postFixTolerance value missing unit of measurement PointReference postFixTolerance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D35 Error AIXM Model Each RadarEquipment with assigned range shall have assigned range.uom value <keyword> Each </keyword><noun_concept> RadarEquipment </noun_concept><keyword> with assigned </keyword><noun_concept> range </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> range.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RadarEquipment with assigned range value missing unit of measurement RadarEquipment range All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D36 Error AIXM Model Each RadarEquipment with assigned rangeAccuracy shall have assigned rangeAccuracy.uom value <keyword> Each </keyword><noun_concept> RadarEquipment </noun_concept><keyword> with assigned </keyword><noun_concept> rangeAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> rangeAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RadarEquipment with assigned rangeAccuracy value missing unit of measurement RadarEquipment rangeAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D37 Error AIXM Model Each RadioCommunicationChannel with assigned frequencyTransmission shall have assigned frequencyTransmission.uom value <keyword> Each </keyword><noun_concept> RadioCommunicationChannel </noun_concept><keyword> with assigned </keyword><noun_concept> frequencyTransmission </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequencyTransmission.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RadioCommunicationChannel with assigned frequencyTransmission value missing unit of measurement RadioCommunicationChannel frequencyTransmission All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D38 Error AIXM Model Each RadioCommunicationChannel with assigned frequencyReception shall have assigned frequencyReception.uom value <keyword> Each </keyword><noun_concept> RadioCommunicationChannel </noun_concept><keyword> with assigned </keyword><noun_concept> frequencyReception </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequencyReception.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RadioCommunicationChannel with assigned frequencyReception value missing unit of measurement RadioCommunicationChannel frequencyReception All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D3B Error AIXM Model Each RouteSegment with assigned upperLimit shall have assigned upperLimit.uom value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RouteSegment with assigned upperLimit value missing unit of measurement RouteSegment upperLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D3C Error AIXM Model Each RouteSegment with assigned lowerLimit shall have assigned lowerLimit.uom value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RouteSegment with assigned lowerLimit value missing unit of measurement RouteSegment lowerLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D3D Error AIXM Model Each RouteSegment with assigned minimumObstacleClearanceAltitude shall have assigned minimumObstacleClearanceAltitude.uom value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> minimumObstacleClearanceAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumObstacleClearanceAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RouteSegment with assigned minimumObstacleClearanceAltitude value missing unit of measurement RouteSegment minimumObstacleClearanceAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D3E Error AIXM Model Each RouteSegment with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RouteSegment with assigned length value missing unit of measurement RouteSegment length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D3F Error AIXM Model Each RouteSegment with assigned widthLeft shall have assigned widthLeft.uom value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> widthLeft </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> widthLeft.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RouteSegment with assigned widthLeft value missing unit of measurement RouteSegment widthLeft All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D40 Error AIXM Model Each RouteSegment with assigned widthRight shall have assigned widthRight.uom value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> widthRight </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> widthRight.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RouteSegment with assigned widthRight value missing unit of measurement RouteSegment widthRight All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D41 Error AIXM Model Each RouteSegment with assigned minimumEnrouteAltitude shall have assigned minimumEnrouteAltitude.uom value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> minimumEnrouteAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumEnrouteAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RouteSegment with assigned minimumEnrouteAltitude value missing unit of measurement RouteSegment minimumEnrouteAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D42 Error AIXM Model Each RouteSegment with assigned minimumCrossingAtEnd shall have assigned minimumCrossingAtEnd.uom value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> minimumCrossingAtEnd </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumCrossingAtEnd.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RouteSegment with assigned minimumCrossingAtEnd value missing unit of measurement RouteSegment minimumCrossingAtEnd All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D43 Error AIXM Model Each RouteSegment with assigned maximumCrossingAtEnd shall have assigned maximumCrossingAtEnd.uom value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> maximumCrossingAtEnd </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> maximumCrossingAtEnd.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RouteSegment with assigned maximumCrossingAtEnd value missing unit of measurement RouteSegment maximumCrossingAtEnd All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D44 Error AIXM Model Each Runway with assigned nominalLength shall have assigned nominalLength.uom value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> nominalLength </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> nominalLength.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Runway with assigned nominalLength value missing unit of measurement Runway nominalLength All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D45 Error AIXM Model Each Runway with assigned lengthAccuracy shall have assigned lengthAccuracy.uom value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> lengthAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lengthAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Runway with assigned lengthAccuracy value missing unit of measurement Runway lengthAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D46 Error AIXM Model Each Runway with assigned nominalWidth shall have assigned nominalWidth.uom value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> nominalWidth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> nominalWidth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Runway with assigned nominalWidth value missing unit of measurement Runway nominalWidth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D47 Error AIXM Model Each Runway with assigned widthAccuracy shall have assigned widthAccuracy.uom value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> widthAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> widthAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Runway with assigned widthAccuracy value missing unit of measurement Runway widthAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D48 Error AIXM Model Each Runway with assigned widthShoulder shall have assigned widthShoulder.uom value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> widthShoulder </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> widthShoulder.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Runway with assigned widthShoulder value missing unit of measurement Runway widthShoulder All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D49 Error AIXM Model Each Runway with assigned lengthStrip shall have assigned lengthStrip.uom value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> lengthStrip </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lengthStrip.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Runway with assigned lengthStrip value missing unit of measurement Runway lengthStrip All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D4A Error AIXM Model Each Runway with assigned widthStrip shall have assigned widthStrip.uom value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> widthStrip </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> widthStrip.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Runway with assigned widthStrip value missing unit of measurement Runway widthStrip All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D4B Error AIXM Model Each Runway with assigned lengthOffset shall have assigned lengthOffset.uom value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> lengthOffset </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lengthOffset.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Runway with assigned lengthOffset value missing unit of measurement Runway lengthOffset All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D4C Error AIXM Model Each Runway with assigned widthOffset shall have assigned widthOffset.uom value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> widthOffset </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> widthOffset.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Runway with assigned widthOffset value missing unit of measurement Runway widthOffset All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D4D Error AIXM Model Each RunwayBlastPad with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> RunwayBlastPad </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayBlastPad with assigned length value missing unit of measurement RunwayBlastPad length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D53 Error AIXM Model Each RunwayDeclaredDistanceValue with assigned distance shall have assigned distance.uom value <keyword> Each </keyword><noun_concept> RunwayDeclaredDistanceValue </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayDeclaredDistanceValue with assigned distance value missing unit of measurement RunwayDeclaredDistanceValue distance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D54 Error AIXM Model Each RunwayDeclaredDistanceValue with assigned distanceAccuracy shall have assigned distanceAccuracy.uom value <keyword> Each </keyword><noun_concept> RunwayDeclaredDistanceValue </noun_concept><keyword> with assigned </keyword><noun_concept> distanceAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> distanceAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayDeclaredDistanceValue with assigned distanceAccuracy value missing unit of measurement RunwayDeclaredDistanceValue distanceAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D55 Error AIXM Model Each RunwayDirection with assigned elevationTDZ shall have assigned elevationTDZ.uom value <keyword> Each </keyword><noun_concept> RunwayDirection </noun_concept><keyword> with assigned </keyword><noun_concept> elevationTDZ </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> elevationTDZ.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayDirection with assigned elevationTDZ value missing unit of measurement RunwayDirection elevationTDZ All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D56 Error AIXM Model Each RunwayDirection with assigned elevationTDZAccuracy shall have assigned elevationTDZAccuracy.uom value <keyword> Each </keyword><noun_concept> RunwayDirection </noun_concept><keyword> with assigned </keyword><noun_concept> elevationTDZAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> elevationTDZAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayDirection with assigned elevationTDZAccuracy value missing unit of measurement RunwayDirection elevationTDZAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D57 Error AIXM Model Each RunwayElement with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> RunwayElement </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayElement with assigned length value missing unit of measurement RunwayElement length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D58 Error AIXM Model Each RunwayElement with assigned width shall have assigned width.uom value <keyword> Each </keyword><noun_concept> RunwayElement </noun_concept><keyword> with assigned </keyword><noun_concept> width </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found RunwayElement with assigned width value missing unit of measurement RunwayElement width All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D59 Error AIXM Model Each SafeAltitudeAreaSector with assigned bufferWidth shall have assigned bufferWidth.uom value <keyword> Each </keyword><noun_concept> SafeAltitudeAreaSector </noun_concept><keyword> with assigned </keyword><noun_concept> bufferWidth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> bufferWidth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SafeAltitudeAreaSector with assigned bufferWidth value missing unit of measurement SafeAltitudeAreaSector bufferWidth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D5B Error AIXM Model Each SectorDesign with assigned terminationAltitude shall have assigned terminationAltitude.uom value <keyword> Each </keyword><noun_concept> SectorDesign </noun_concept><keyword> with assigned </keyword><noun_concept> terminationAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> terminationAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SectorDesign with assigned terminationAltitude value missing unit of measurement SectorDesign terminationAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D5C Error AIXM Model Each SegmentLeg with assigned speedLimit shall have assigned speedLimit.uom value <keyword> Each </keyword><noun_concept> SegmentLeg </noun_concept><keyword> with assigned </keyword><noun_concept> speedLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> speedLimit.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SegmentLeg with assigned speedLimit value missing unit of measurement SegmentLeg speedLimit All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D5D Error AIXM Model Each SegmentLeg with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> SegmentLeg </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SegmentLeg with assigned length value missing unit of measurement SegmentLeg length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D5E Error AIXM Model Each SegmentLeg with assigned duration shall have assigned duration.uom value <keyword> Each </keyword><noun_concept> SegmentLeg </noun_concept><keyword> with assigned </keyword><noun_concept> duration </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> duration.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SegmentLeg with assigned duration value missing unit of measurement SegmentLeg duration All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D5F Error AIXM Model Each SegmentLeg with assigned upperLimitAltitude shall have assigned upperLimitAltitude.uom value <keyword> Each </keyword><noun_concept> SegmentLeg </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimitAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SegmentLeg with assigned upperLimitAltitude value missing unit of measurement SegmentLeg upperLimitAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D60 Error AIXM Model Each SegmentLeg with assigned lowerLimitAltitude shall have assigned lowerLimitAltitude.uom value <keyword> Each </keyword><noun_concept> SegmentLeg </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimitAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SegmentLeg with assigned lowerLimitAltitude value missing unit of measurement SegmentLeg lowerLimitAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D61 Error AIXM Model Each SegmentLeg with assigned altitudeOverrideATC shall have assigned altitudeOverrideATC.uom value <keyword> Each </keyword><noun_concept> SegmentLeg </noun_concept><keyword> with assigned </keyword><noun_concept> altitudeOverrideATC </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeOverrideATC.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SegmentLeg with assigned altitudeOverrideATC value missing unit of measurement SegmentLeg altitudeOverrideATC All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D62 Error AIXM Model Each SpecialNavigationStation with assigned frequency shall have assigned frequency.uom value <keyword> Each </keyword><noun_concept> SpecialNavigationStation </noun_concept><keyword> with assigned </keyword><noun_concept> frequency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SpecialNavigationStation with assigned frequency value missing unit of measurement SpecialNavigationStation frequency All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D63 Error AIXM Model Each StandardLevel with assigned verticalDistance shall have assigned verticalDistance.uom value <keyword> Each </keyword><noun_concept> StandardLevel </noun_concept><keyword> with assigned </keyword><noun_concept> verticalDistance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalDistance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found StandardLevel with assigned verticalDistance value missing unit of measurement StandardLevel verticalDistance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D64 Error AIXM Model Each Surface with assigned horizontalAccuracy shall have assigned horizontalAccuracy.uom value <keyword> Each </keyword><noun_concept> Surface </noun_concept><keyword> with assigned </keyword><noun_concept> horizontalAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> horizontalAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Surface with assigned horizontalAccuracy value missing unit of measurement Surface horizontalAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D65 Error AIXM Model Each SurfaceCharacteristics with assigned weightSIWL shall have assigned weightSIWL.uom value <keyword> Each </keyword><noun_concept> SurfaceCharacteristics </noun_concept><keyword> with assigned </keyword><noun_concept> weightSIWL </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> weightSIWL.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SurfaceCharacteristics with assigned weightSIWL value missing unit of measurement SurfaceCharacteristics weightSIWL All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D66 Error AIXM Model Each SurfaceCharacteristics with assigned tyrePressureSIWL shall have assigned tyrePressureSIWL.uom value <keyword> Each </keyword><noun_concept> SurfaceCharacteristics </noun_concept><keyword> with assigned </keyword><noun_concept> tyrePressureSIWL </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> tyrePressureSIWL.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SurfaceCharacteristics with assigned tyrePressureSIWL value missing unit of measurement SurfaceCharacteristics tyrePressureSIWL All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D67 Error AIXM Model Each SurfaceCharacteristics with assigned weightAUW shall have assigned weightAUW.uom value <keyword> Each </keyword><noun_concept> SurfaceCharacteristics </noun_concept><keyword> with assigned </keyword><noun_concept> weightAUW </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> weightAUW.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SurfaceCharacteristics with assigned weightAUW value missing unit of measurement SurfaceCharacteristics weightAUW All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D68 Error AIXM Model Each SurfaceContamination with assigned depth shall have assigned depth.uom value <keyword> Each </keyword><noun_concept> SurfaceContamination </noun_concept><keyword> with assigned </keyword><noun_concept> depth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> depth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SurfaceContamination with assigned depth value missing unit of measurement SurfaceContamination depth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D6B Error AIXM Model Each Taxiway with assigned width shall have assigned width.uom value <keyword> Each </keyword><noun_concept> Taxiway </noun_concept><keyword> with assigned </keyword><noun_concept> width </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Taxiway with assigned width value missing unit of measurement Taxiway width All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D6C Error AIXM Model Each Taxiway with assigned widthShoulder shall have assigned widthShoulder.uom value <keyword> Each </keyword><noun_concept> Taxiway </noun_concept><keyword> with assigned </keyword><noun_concept> widthShoulder </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> widthShoulder.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Taxiway with assigned widthShoulder value missing unit of measurement Taxiway widthShoulder All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D6D Error AIXM Model Each Taxiway with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> Taxiway </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Taxiway with assigned length value missing unit of measurement Taxiway length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D6F Error AIXM Model Each TaxiwayElement with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> TaxiwayElement </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found TaxiwayElement with assigned length value missing unit of measurement TaxiwayElement length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D70 Error AIXM Model Each TaxiwayElement with assigned width shall have assigned width.uom value <keyword> Each </keyword><noun_concept> TaxiwayElement </noun_concept><keyword> with assigned </keyword><noun_concept> width </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found TaxiwayElement with assigned width value missing unit of measurement TaxiwayElement width All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D71 Error AIXM Model Each TerminalArrivalArea with assigned outerBufferWidth shall have assigned outerBufferWidth.uom value <keyword> Each </keyword><noun_concept> TerminalArrivalArea </noun_concept><keyword> with assigned </keyword><noun_concept> outerBufferWidth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> outerBufferWidth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found TerminalArrivalArea with assigned outerBufferWidth value missing unit of measurement TerminalArrivalArea outerBufferWidth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D72 Error AIXM Model Each TerminalArrivalArea with assigned lateralBufferWidth shall have assigned lateralBufferWidth.uom value <keyword> Each </keyword><noun_concept> TerminalArrivalArea </noun_concept><keyword> with assigned </keyword><noun_concept> lateralBufferWidth </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lateralBufferWidth.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found TerminalArrivalArea with assigned lateralBufferWidth value missing unit of measurement TerminalArrivalArea lateralBufferWidth All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D73 Error AIXM Model Each TerminalSegmentPoint with assigned leadDME shall have assigned leadDME.uom value <keyword> Each </keyword><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> leadDME </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> leadDME.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found TerminalSegmentPoint with assigned leadDME value missing unit of measurement TerminalSegmentPoint leadDME All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D74 Error AIXM Model Each Timesheet with assigned startTimeRelativeEvent shall have assigned startTimeRelativeEvent.uom value <keyword> Each </keyword><noun_concept> Timesheet </noun_concept><keyword> with assigned </keyword><noun_concept> startTimeRelativeEvent </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> startTimeRelativeEvent.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Timesheet with assigned startTimeRelativeEvent value missing unit of measurement Timesheet startTimeRelativeEvent All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D75 Error AIXM Model Each Timesheet with assigned endTimeRelativeEvent shall have assigned endTimeRelativeEvent.uom value <keyword> Each </keyword><noun_concept> Timesheet </noun_concept><keyword> with assigned </keyword><noun_concept> endTimeRelativeEvent </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> endTimeRelativeEvent.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found Timesheet with assigned endTimeRelativeEvent value missing unit of measurement Timesheet endTimeRelativeEvent All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D76 Error AIXM Model Each TouchDownLiftOff with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found TouchDownLiftOff with assigned length value missing unit of measurement TouchDownLiftOff length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D77 Error AIXM Model Each TouchDownLiftOff with assigned width shall have assigned width.uom value <keyword> Each </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with assigned </keyword><noun_concept> width </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found TouchDownLiftOff with assigned width value missing unit of measurement TouchDownLiftOff width All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D79 Error AIXM Model Each UsageCondition with assigned priorPermission shall have assigned priorPermission.uom value <keyword> Each </keyword><noun_concept> UsageCondition </noun_concept><keyword> with assigned </keyword><noun_concept> priorPermission </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> priorPermission.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found UsageCondition with assigned priorPermission value missing unit of measurement UsageCondition priorPermission All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D7A Error AIXM Model Each VerticalStructure with assigned length shall have assigned length.uom value <keyword> Each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> length </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found VerticalStructure with assigned length value missing unit of measurement VerticalStructure length All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D7B Error AIXM Model Each VerticalStructure with assigned width shall have assigned width.uom value <keyword> Each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> width </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found VerticalStructure with assigned width value missing unit of measurement VerticalStructure width All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D7C Error AIXM Model Each VerticalStructure with assigned radius shall have assigned radius.uom value <keyword> Each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> radius </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> radius.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found VerticalStructure with assigned radius value missing unit of measurement VerticalStructure radius All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D7D Error AIXM Model Each VerticalStructurePart with assigned verticalExtent shall have assigned verticalExtent.uom value <keyword> Each </keyword><noun_concept> VerticalStructurePart </noun_concept><keyword> with assigned </keyword><noun_concept> verticalExtent </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalExtent.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found VerticalStructurePart with assigned verticalExtent value missing unit of measurement VerticalStructurePart verticalExtent All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D7E Error AIXM Model Each VerticalStructurePart with assigned verticalExtentAccuracy shall have assigned verticalExtentAccuracy.uom value <keyword> Each </keyword><noun_concept> VerticalStructurePart </noun_concept><keyword> with assigned </keyword><noun_concept> verticalExtentAccuracy </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalExtentAccuracy.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found VerticalStructurePart with assigned verticalExtentAccuracy value missing unit of measurement VerticalStructurePart verticalExtentAccuracy All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D7F Error AIXM Model Each VisualGlideSlopeIndicator with assigned minimumEyeHeightOverThreshold shall have assigned minimumEyeHeightOverThreshold.uom value <keyword> Each </keyword><noun_concept> VisualGlideSlopeIndicator </noun_concept><keyword> with assigned </keyword><noun_concept> minimumEyeHeightOverThreshold </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumEyeHeightOverThreshold.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found VisualGlideSlopeIndicator with assigned minimumEyeHeightOverThreshold value missing unit of measurement VisualGlideSlopeIndicator minimumEyeHeightOverThreshold All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D80 Error AIXM Model Each VOR with assigned frequency shall have assigned frequency.uom value <keyword> Each </keyword><noun_concept> VOR </noun_concept><keyword> with assigned </keyword><noun_concept> frequency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found VOR with assigned frequency value missing unit of measurement VOR frequency All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D81 Error AIXM Model Each SecondarySurveillanceRadar with assigned verticalCoverageDistance shall have assigned verticalCoverageDistance.uom value <keyword> Each </keyword><noun_concept> SecondarySurveillanceRadar </noun_concept><keyword> with assigned </keyword><noun_concept> verticalCoverageDistance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalCoverageDistance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SecondarySurveillanceRadar with assigned verticalCoverageDistance value missing unit of measurement SecondarySurveillanceRadar verticalCoverageDistance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D82 Error AIXM Model Each SecondarySurveillanceRadar with assigned verticalCoverageAltitude shall have assigned verticalCoverageAltitude.uom value <keyword> Each </keyword><noun_concept> SecondarySurveillanceRadar </noun_concept><keyword> with assigned </keyword><noun_concept> verticalCoverageAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalCoverageAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found SecondarySurveillanceRadar with assigned verticalCoverageAltitude value missing unit of measurement SecondarySurveillanceRadar verticalCoverageAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D83 Error AIXM Model Each PrimarySurveillanceRadar with assigned verticalCoverageAltitude shall have assigned verticalCoverageAltitude.uom value <keyword> Each </keyword><noun_concept> PrimarySurveillanceRadar </noun_concept><keyword> with assigned </keyword><noun_concept> verticalCoverageAltitude </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalCoverageAltitude.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found PrimarySurveillanceRadar with assigned verticalCoverageAltitude value missing unit of measurement PrimarySurveillanceRadar verticalCoverageAltitude All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-D8D84 Error AIXM Model Each PrimarySurveillanceRadar with assigned verticalCoverageDistance shall have assigned verticalCoverageDistance.uom value <keyword> Each </keyword><noun_concept> PrimarySurveillanceRadar </noun_concept><keyword> with assigned </keyword><noun_concept> verticalCoverageDistance </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> verticalCoverageDistance.uom </noun_concept><keyword> value </keyword> The Unit of measurement shall be specified if a value is specified for a property with uom attribute. Found PrimarySurveillanceRadar with assigned verticalCoverageDistance value missing unit of measurement PrimarySurveillanceRadar verticalCoverageDistance All Coding rule Mandatory unit of measurement
AIXM-5.1_RULE-1028BA Error AIXM Model It is obligatory that each Service specialisation TrafficSeparationService specialisation AirTrafficControlService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TrafficSeparationService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. AirTrafficControlService serviceProvider ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028BB Error AIXM Model It is obligatory that each Service specialisation TrafficSeparationService specialisation GroundTrafficControlService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TrafficSeparationService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> GroundTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. GroundTrafficControlService serviceProvider ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028BC Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation PassengerService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> PassengerService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. PassengerService serviceProvider ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028BD Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation AircraftGroundService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AircraftGroundService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. AircraftGroundService serviceProvider ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028BE Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation FireFightingService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> FireFightingService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. FireFightingService serviceProvider ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028BF Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation AirportSuppliesService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportSuppliesService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. AirportSuppliesService serviceProvider ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028C0 Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation AirportClearanceService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportClearanceService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. AirportClearanceService serviceProvider ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028C2 Error AIXM Model It is obligatory that each Service specialisation TrafficSeparationService specialisation GroundTrafficControlService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TrafficSeparationService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> GroundTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. GroundTrafficControlService radioCommunication ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028C3 Error AIXM Model It is obligatory that each Service specialisation TrafficSeparationService specialisation AirTrafficControlService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TrafficSeparationService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. AirTrafficControlService radioCommunication ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028C4 Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation PassengerService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> PassengerService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. PassengerService radioCommunication ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028C5 Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation AircraftGroundService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AircraftGroundService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. AircraftGroundService radioCommunication ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028C6 Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation FireFightingService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> FireFightingService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. FireFightingService radioCommunication ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028C7 Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation AirportSuppliesService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportSuppliesService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. AirportSuppliesService radioCommunication ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028C8 Error AIXM Model It is obligatory that each Service specialisation AirportGroundService specialisation AirportClearanceService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportClearanceService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. AirportClearanceService radioCommunication ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028D7 Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation ArrivalFeederLeg with assigned holding.HoldingUse.theHoldingPattern value has holding.HoldingUse.theHoldingPattern value resolved-into exactly one establishes HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with assigned </keyword><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> establishes </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. ArrivalFeederLeg holding.HoldingUse.theHoldingPattern ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028D8 Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation InitialLeg with assigned holding.HoldingUse.theHoldingPattern value has holding.HoldingUse.theHoldingPattern value resolved-into exactly one establishes HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InitialLeg </noun_concept><keyword> with assigned </keyword><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> establishes </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. InitialLeg holding.HoldingUse.theHoldingPattern ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028D9 Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation IntermediateLeg with assigned holding.HoldingUse.theHoldingPattern value has holding.HoldingUse.theHoldingPattern value resolved-into exactly one establishes HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> IntermediateLeg </noun_concept><keyword> with assigned </keyword><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> establishes </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. IntermediateLeg holding.HoldingUse.theHoldingPattern ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028DA Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation FinalLeg with assigned holding.HoldingUse.theHoldingPattern value has holding.HoldingUse.theHoldingPattern value resolved-into exactly one establishes HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> establishes </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. FinalLeg holding.HoldingUse.theHoldingPattern ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028DB Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation MissedApproachLeg with assigned holding.HoldingUse.theHoldingPattern value has holding.HoldingUse.theHoldingPattern value resolved-into exactly one establishes HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MissedApproachLeg </noun_concept><keyword> with assigned </keyword><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> holding.HoldingUse.theHoldingPattern </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> establishes </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. MissedApproachLeg holding.HoldingUse.theHoldingPattern ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028DC Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation ArrivalFeederLeg with assigned angle value has angle value resolved-into exactly one isLimitedBy AngleIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with assigned </keyword><noun_concept> angle </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> angle </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> AngleIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. ArrivalFeederLeg angle ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028DD Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation InitialLeg with assigned angle value has angle value resolved-into exactly one isLimitedBy AngleIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InitialLeg </noun_concept><keyword> with assigned </keyword><noun_concept> angle </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> angle </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> AngleIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. InitialLeg angle ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028DE Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation IntermediateLeg with assigned angle value has angle value resolved-into exactly one isLimitedBy AngleIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> IntermediateLeg </noun_concept><keyword> with assigned </keyword><noun_concept> angle </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> angle </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> AngleIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. IntermediateLeg angle ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028DF Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation FinalLeg with assigned angle value has angle value resolved-into exactly one isLimitedBy AngleIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> angle </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> angle </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> AngleIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. FinalLeg angle ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028E0 Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation MissedApproachLeg with assigned angle value has angle value resolved-into exactly one isLimitedBy AngleIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MissedApproachLeg </noun_concept><keyword> with assigned </keyword><noun_concept> angle </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> angle </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> AngleIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. MissedApproachLeg angle ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028E1 Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation ArrivalFeederLeg with assigned distance value has distance value resolved-into exactly one isLimitedBy DistanceIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> distance </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> DistanceIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. ArrivalFeederLeg distance ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028E2 Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation InitialLeg with assigned distance value has distance value resolved-into exactly one isLimitedBy DistanceIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InitialLeg </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> distance </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> DistanceIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. InitialLeg distance ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028E3 Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation IntermediateLeg with assigned distance value has distance value resolved-into exactly one isLimitedBy DistanceIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> IntermediateLeg </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> distance </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> DistanceIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. IntermediateLeg distance ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028E4 Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation FinalLeg with assigned distance value has distance value resolved-into exactly one isLimitedBy DistanceIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> distance </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> DistanceIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. FinalLeg distance ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1028E5 Error AIXM Model It is obligatory that each SegmentLeg specialisation ApproachLeg specialisation MissedApproachLeg with assigned distance value has distance value resolved-into exactly one isLimitedBy DistanceIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MissedApproachLeg </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> distance </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> DistanceIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. MissedApproachLeg distance ANY;WITH_REF Minimal data rule Referential integrity - second level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5249 Error AIXM Model It is obligatory that each Service specialisation InformationService with assigned navaidBroadcast value has navaidBroadcast value resolved-into exactly one broadcastsOn VOR <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InformationService </noun_concept><keyword> with assigned </keyword><noun_concept> navaidBroadcast </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> navaidBroadcast </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> broadcastsOn </verb_concept><noun_concept> VOR </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. InformationService navaidBroadcast set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A524A Error AIXM Model It is obligatory that each Service specialisation InformationService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InformationService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. InformationService serviceProvider set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A524B Error AIXM Model It is obligatory that each Service specialisation AirTrafficManagementService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirTrafficManagementService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AirTrafficManagementService serviceProvider set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A524C Error AIXM Model It is obligatory that each Service specialisation SearchRescueService with assigned serviceProvider value has serviceProvider value resolved-into exactly one isProvidedBy Unit <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SearchRescueService </noun_concept><keyword> with assigned </keyword><noun_concept> serviceProvider </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> serviceProvider </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedBy </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. SearchRescueService serviceProvider set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A524D Error AIXM Model It is obligatory that each Service specialisation InformationService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InformationService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. InformationService radioCommunication set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A524E Error AIXM Model It is obligatory that each Service specialisation AirTrafficManagementService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirTrafficManagementService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AirTrafficManagementService radioCommunication set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A524F Error AIXM Model It is obligatory that each Service specialisation SearchRescueService with assigned radioCommunication value has radioCommunication value resolved-into exactly one uses RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SearchRescueService </noun_concept><keyword> with assigned </keyword><noun_concept> radioCommunication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radioCommunication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. SearchRescueService radioCommunication set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5250 Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentDeparture with assigned airportHeliport value has airportHeliport value resolved-into exactly one services AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> services </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentDeparture airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5251 Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentArrival with assigned airportHeliport value has airportHeliport value resolved-into exactly one services AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentArrival </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> services </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentArrival airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5252 Error AIXM Model It is obligatory that each Procedure specialisation InstrumentApproachProcedure with assigned airportHeliport value has airportHeliport value resolved-into exactly one services AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> services </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. InstrumentApproachProcedure airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5253 Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentDeparture with assigned safeAltitude value has safeAltitude value resolved-into exactly one isProtectedBy SafeAltitudeArea <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> with assigned </keyword><noun_concept> safeAltitude </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> safeAltitude </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProtectedBy </verb_concept><noun_concept> SafeAltitudeArea </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentDeparture safeAltitude set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5254 Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentArrival with assigned safeAltitude value has safeAltitude value resolved-into exactly one isProtectedBy SafeAltitudeArea <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentArrival </noun_concept><keyword> with assigned </keyword><noun_concept> safeAltitude </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> safeAltitude </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProtectedBy </verb_concept><noun_concept> SafeAltitudeArea </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentArrival safeAltitude set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5255 Error AIXM Model It is obligatory that each Procedure specialisation InstrumentApproachProcedure with assigned safeAltitude value has safeAltitude value resolved-into exactly one isProtectedBy SafeAltitudeArea <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept><keyword> with assigned </keyword><noun_concept> safeAltitude </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> safeAltitude </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProtectedBy </verb_concept><noun_concept> SafeAltitudeArea </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. InstrumentApproachProcedure safeAltitude set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5256 Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentDeparture with assigned guidanceFacility.GuidanceService.navaid value has guidanceFacility.GuidanceService.navaid value resolved-into exactly one uses Navaid <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> with assigned </keyword><noun_concept> guidanceFacility.GuidanceService.navaid </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> guidanceFacility.GuidanceService.navaid </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentDeparture guidanceFacility.GuidanceService.navaid set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5257 Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentDeparture with assigned guidanceFacility.GuidanceService.specialNavigationSystem value has guidanceFacility.GuidanceService.specialNavigationSystem value resolved-into exactly one uses SpecialNavigationSystem <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> with assigned </keyword><noun_concept> guidanceFacility.GuidanceService.specialNavigationSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> guidanceFacility.GuidanceService.specialNavigationSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> SpecialNavigationSystem </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentDeparture guidanceFacility.GuidanceService.specialNavigationSystem set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5259 Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentArrival with assigned guidanceFacility.GuidanceService.navaid value has guidanceFacility.GuidanceService.navaid value resolved-into exactly one uses Navaid <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentArrival </noun_concept><keyword> with assigned </keyword><noun_concept> guidanceFacility.GuidanceService.navaid </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> guidanceFacility.GuidanceService.navaid </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentArrival guidanceFacility.GuidanceService.navaid set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A525A Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentArrival with assigned guidanceFacility.GuidanceService.specialNavigationSystem value has guidanceFacility.GuidanceService.specialNavigationSystem value resolved-into exactly one uses SpecialNavigationSystem <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentArrival </noun_concept><keyword> with assigned </keyword><noun_concept> guidanceFacility.GuidanceService.specialNavigationSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> guidanceFacility.GuidanceService.specialNavigationSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> SpecialNavigationSystem </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentArrival guidanceFacility.GuidanceService.specialNavigationSystem set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A525C Error AIXM Model It is obligatory that each Procedure specialisation InstrumentApproachProcedure with assigned guidanceFacility.GuidanceService.navaid value has guidanceFacility.GuidanceService.navaid value resolved-into exactly one uses Navaid <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept><keyword> with assigned </keyword><noun_concept> guidanceFacility.GuidanceService.navaid </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> guidanceFacility.GuidanceService.navaid </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. InstrumentApproachProcedure guidanceFacility.GuidanceService.navaid set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A525D Error AIXM Model It is obligatory that each Procedure specialisation InstrumentApproachProcedure with assigned guidanceFacility.GuidanceService.specialNavigationSystem value has guidanceFacility.GuidanceService.specialNavigationSystem value resolved-into exactly one uses SpecialNavigationSystem <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept><keyword> with assigned </keyword><noun_concept> guidanceFacility.GuidanceService.specialNavigationSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> guidanceFacility.GuidanceService.specialNavigationSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> SpecialNavigationSystem </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. InstrumentApproachProcedure guidanceFacility.GuidanceService.specialNavigationSystem set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A525F Error AIXM Model It is obligatory that each SegmentLeg specialisation DepartureLeg with assigned holding.HoldingUse.theHolding value has holding.HoldingUse.theHolding value resolved-into exactly one establishes HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DepartureLeg </noun_concept><keyword> with assigned </keyword><noun_concept> holding.HoldingUse.theHolding </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> holding.HoldingUse.theHolding </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> establishes </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. DepartureLeg holding.HoldingUse.theHolding set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5260 Error AIXM Model It is obligatory that each SegmentLeg specialisation ArrivalLeg with assigned holding.HoldingUse.theHolding value has holding.HoldingUse.theHolding value resolved-into exactly one establishes HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> holding.HoldingUse.theHolding </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> holding.HoldingUse.theHolding </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> establishes </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ArrivalLeg holding.HoldingUse.theHolding set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5261 Error AIXM Model It is obligatory that each SegmentLeg specialisation DepartureLeg with assigned angle value has angle value resolved-into exactly one isLimitedBy AngleIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DepartureLeg </noun_concept><keyword> with assigned </keyword><noun_concept> angle </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> angle </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> AngleIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. DepartureLeg angle set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5262 Error AIXM Model It is obligatory that each SegmentLeg specialisation ArrivalLeg with assigned angle value has angle value resolved-into exactly one isLimitedBy AngleIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> angle </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> angle </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> AngleIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ArrivalLeg angle set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5263 Error AIXM Model It is obligatory that each SegmentLeg specialisation DepartureLeg with assigned distance value has distance value resolved-into exactly one isLimitedBy DistanceIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DepartureLeg </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> distance </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> DistanceIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. DepartureLeg distance set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5264 Error AIXM Model It is obligatory that each SegmentLeg specialisation ArrivalLeg with assigned distance value has distance value resolved-into exactly one isLimitedBy DistanceIndication <keyword> It is obligatory that each </keyword><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> distance </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> distance </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLimitedBy </verb_concept><noun_concept> DistanceIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ArrivalLeg distance set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5265 Error AIXM Model It is obligatory that each NavaidEquipment specialisation Localizer with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. Localizer authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5266 Error AIXM Model It is obligatory that each NavaidEquipment specialisation Glidepath with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. Glidepath authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5267 Error AIXM Model It is obligatory that each NavaidEquipment specialisation VOR with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. VOR authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5268 Error AIXM Model It is obligatory that each NavaidEquipment specialisation TACAN with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. TACAN authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5269 Error AIXM Model It is obligatory that each NavaidEquipment specialisation DME with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. DME authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A526A Error AIXM Model It is obligatory that each NavaidEquipment specialisation NDB with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. NDB authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A526B Error AIXM Model It is obligatory that each NavaidEquipment specialisation MarkerBeacon with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. MarkerBeacon authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A526D Error AIXM Model It is obligatory that each NavaidEquipment specialisation Elevation with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. Elevation authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A526F Error AIXM Model It is obligatory that each NavaidEquipment specialisation Azimuth with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. Azimuth authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5270 Error AIXM Model It is obligatory that each NavigationSystemCheckpoint specialisation CheckpointVOR with assigned airportHeliport value has airportHeliport value resolved-into exactly one establishedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> NavigationSystemCheckpoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> CheckpointVOR </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> establishedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. CheckpointVOR airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5271 Error AIXM Model It is obligatory that each NavigationSystemCheckpoint specialisation CheckpointINS with assigned airportHeliport value has airportHeliport value resolved-into exactly one establishedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> NavigationSystemCheckpoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> CheckpointINS </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> establishedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. CheckpointINS airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5285 Error Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation AirportHeliportAvailability with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportHeliportAvailability </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AirportHeliportAvailability specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5286 Error Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation AirportHeliportResponsibilityOrganisation with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportHeliportResponsibilityOrganisation </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AirportHeliportResponsibilityOrganisation specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5287 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation AirspaceActivation with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirspaceActivation </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AirspaceActivation specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5288 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation AirspaceLayerClass with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirspaceLayerClass </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AirspaceLayerClass specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A528A Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation ApronAreaAvailability with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApronAreaAvailability </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ApronAreaAvailability specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A528B Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation CirclingRestriction with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> CirclingRestriction </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. CirclingRestriction specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A528C Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation ConditionCombination with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ConditionCombination </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ConditionCombination specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A528E Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation GroundLightingAvailability with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> GroundLightingAvailability </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. GroundLightingAvailability specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A528F Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation LightElementStatus with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> LightElementStatus </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. LightElementStatus specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5290 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation ManoeuvringAreaAvailability with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ManoeuvringAreaAvailability </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ManoeuvringAreaAvailability specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5291 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation NavaidEquipmentMonitoring with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NavaidEquipmentMonitoring </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. NavaidEquipmentMonitoring specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5292 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation NavaidOperationalStatus with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NavaidOperationalStatus </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. NavaidOperationalStatus specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5293 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation OnlineContact with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> OnlineContact </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. OnlineContact specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5294 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation PostalAddress with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> PostalAddress </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. PostalAddress specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5295 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation ProcedureAvailability with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ProcedureAvailability </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ProcedureAvailability specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5296 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation RadioCommunicationOperationalStatus with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> RadioCommunicationOperationalStatus </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. RadioCommunicationOperationalStatus specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5297 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation RouteAvailability with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> RouteAvailability </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. RouteAvailability specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5298 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation RunwayDeclaredDistanceValue with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> RunwayDeclaredDistanceValue </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. RunwayDeclaredDistanceValue specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A5299 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation ServiceOperationalStatus with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ServiceOperationalStatus </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ServiceOperationalStatus specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A529A Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation SpecialNavigationStationStatus with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SpecialNavigationStationStatus </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. SpecialNavigationStationStatus specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A529B Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation TelephoneContact with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TelephoneContact </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. TelephoneContact specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A529E Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation VerticalStructurePart with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VerticalStructurePart </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. VerticalStructurePart specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A0 Error AIXM Model It is obligatory that each SegmentPoint specialisation TerminalSegmentPoint with assigned extendedServiceVolume value has extendedServiceVolume value resolved-into exactly one isApprovedUsing RadioFrequencyArea <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> extendedServiceVolume </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> extendedServiceVolume </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isApprovedUsing </verb_concept><noun_concept> RadioFrequencyArea </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. TerminalSegmentPoint extendedServiceVolume set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A1 Error AIXM Model It is obligatory that each SegmentPoint specialisation TerminalSegmentPoint with assigned pointChoice.SignificantPoint.fixDesignatedPoint value has pointChoice.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isLocatedAt DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. TerminalSegmentPoint pointChoice.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A2 Error AIXM Model It is obligatory that each SegmentPoint specialisation TerminalSegmentPoint with assigned pointChoice.SignificantPoint.navaidSystem value has pointChoice.SignificantPoint.navaidSystem value resolved-into exactly one isLocatedAt Navaid <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. TerminalSegmentPoint pointChoice.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A3 Error AIXM Model It is obligatory that each SegmentPoint specialisation TerminalSegmentPoint with assigned pointChoice.SignificantPoint.aimingPoint value has pointChoice.SignificantPoint.aimingPoint value resolved-into exactly one isLocatedAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. TerminalSegmentPoint pointChoice.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A4 Error AIXM Model It is obligatory that each SegmentPoint specialisation TerminalSegmentPoint with assigned pointChoice.SignificantPoint.runwayPoint value has pointChoice.SignificantPoint.runwayPoint value resolved-into exactly one isLocatedAt RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. TerminalSegmentPoint pointChoice.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A5 Error AIXM Model It is obligatory that each SegmentPoint specialisation TerminalSegmentPoint with assigned pointChoice.SignificantPoint.airportReferencePoint value has pointChoice.SignificantPoint.airportReferencePoint value resolved-into exactly one isLocatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. TerminalSegmentPoint pointChoice.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A6 Error Error AIXM Model It is obligatory that each SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice.SignificantPoint.fixDesignatedPoint value has pointChoice.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isLocatedAt DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. EnRouteSegmentPoint pointChoice.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A7 Error Error AIXM Model It is obligatory that each SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice.SignificantPoint.navaidSystem value has pointChoice.SignificantPoint.navaidSystem value resolved-into exactly one isLocatedAt Navaid <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. EnRouteSegmentPoint pointChoice.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A8 Error Error AIXM Model It is obligatory that each SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice.SignificantPoint.aimingPoint value has pointChoice.SignificantPoint.aimingPoint value resolved-into exactly one isLocatedAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. EnRouteSegmentPoint pointChoice.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52A9 Error Error AIXM Model It is obligatory that each SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice.SignificantPoint.runwayPoint value has pointChoice.SignificantPoint.runwayPoint value resolved-into exactly one isLocatedAt RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. EnRouteSegmentPoint pointChoice.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52AA Error Error AIXM Model It is obligatory that each SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice.SignificantPoint.airportReferencePoint value has pointChoice.SignificantPoint.airportReferencePoint value resolved-into exactly one isLocatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. EnRouteSegmentPoint pointChoice.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52AD Error AIXM Model It is obligatory that each AirportGroundService specialisation PassengerService with assigned airportHeliport value has airportHeliport value resolved-into exactly one isProvidedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> PassengerService </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. PassengerService airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52AE Error AIXM Model It is obligatory that each AirportGroundService specialisation AirportSuppliesService with assigned airportHeliport value has airportHeliport value resolved-into exactly one isProvidedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportSuppliesService </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AirportSuppliesService airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52AF Error AIXM Model It is obligatory that each AirportGroundService specialisation AircraftGroundService with assigned airportHeliport value has airportHeliport value resolved-into exactly one isProvidedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AircraftGroundService </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AircraftGroundService airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52B0 Error AIXM Model It is obligatory that each AirportGroundService specialisation AirportClearanceService with assigned airportHeliport value has airportHeliport value resolved-into exactly one isProvidedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportClearanceService </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AirportClearanceService airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1A52B1 Error AIXM Model It is obligatory that each AirportGroundService specialisation FireFightingService with assigned airportHeliport value has airportHeliport value resolved-into exactly one isProvidedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> FireFightingService </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. FireFightingService airportHeliport set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-1AB3FC Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation WorkareaActivity with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> WorkareaActivity </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. WorkareaActivity specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class) (EAD profile)
AIXM-5.1_RULE-5B4F1 Warning ICAO Annex 14 Table A5-1; V2 Table A1-1 It is prohibited that a NavaidEquipment specialisation Azimuth with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 3.0 M <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 3.0 M The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 3.0 M Azimuth location All Standard (ICAO, industry, etc.) Accuracy (horizontal) MLS/ILS components
AIXM-5.1_RULE-5B4F2 Warning ICAO Annex 14 Table A5-1; V2 Table A1-1 It is prohibited that a NavaidEquipment specialisation Localizer with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 3.0 M <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 3.0 M The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 3.0 M Localizer location All Standard (ICAO, industry, etc.) Accuracy (horizontal) MLS/ILS components
AIXM-5.1_RULE-5B4F3 Warning ICAO Annex 14 Table A5-1; V2 Table A1-1 It is prohibited that a NavaidEquipment specialisation Glidepath with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 3.0 M <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 3.0 M The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 3.0 M Glidepath location All Standard (ICAO, industry, etc.) Accuracy (horizontal) MLS/ILS components
AIXM-5.1_RULE-5B4F4 Warning ICAO Annex 14 Table A5-1; V2 Table A1-1 It is prohibited that a NavaidEquipment specialisation Elevation with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 3.0 M <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 3.0 M The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 3.0 M Elevation location All Standard (ICAO, industry, etc.) Accuracy (horizontal) MLS/ILS components
AIXM-5.1_RULE-5B4F5 Warning ICAO Annex 14 Table A5-1; V2 Table A1-1 It is prohibited that a NavaidEquipment specialisation Elevation with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 10.0 FT <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 10.0 FT The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 10.0 FT Elevation location All Standard (ICAO, industry, etc.) Accuracy (horizontal) MLS/ILS components
AIXM-5.1_RULE-5B4F6 Warning ICAO Annex 14 Table A5-1; V2 Table A1-1 It is prohibited that a NavaidEquipment specialisation Localizer with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 10.0 FT <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 10.0 FT The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 10.0 FT Localizer location All Standard (ICAO, industry, etc.) Accuracy (horizontal) MLS/ILS components
AIXM-5.1_RULE-5B4F7 Warning ICAO Annex 14 Table A5-1; V2 Table A1-1 It is prohibited that a NavaidEquipment specialisation Azimuth with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 10.0 FT <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 10.0 FT The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 10.0 FT Azimuth location All Standard (ICAO, industry, etc.) Accuracy (horizontal) MLS/ILS components
AIXM-5.1_RULE-5B4F8 Warning ICAO Annex 14 Table A5-1; V2 Table A1-1 It is prohibited that a NavaidEquipment specialisation Glidepath with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 10.0 FT <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 10.0 FT The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 10.0 FT Glidepath location All Standard (ICAO, industry, etc.) Accuracy (horizontal) MLS/ILS components
AIXM-5.1_RULE-D5611 Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that Airspace with type equal-to ('FIR','UIR','FIR_P','UIR_P') has geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface coordinates expressed with less than 2 decimals <keyword> It is prohibited that </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('FIR','UIR','FIR_P','UIR_P') </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface </noun_concept> Longitude and Latitude of ('FIR','UIR','FIR_P','UIR_P') boundary points shall be published with at least 2 decimals resolution. Longitude and Latitude of ('FIR','UIR','FIR_P','UIR_P') boundary points shall be published with at least 2 decimals resolution. AirspaceVolume Surface baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Airspace type ('FIR','UIR','FIR_P','UIR_P')
AIXM-5.1_RULE-D5612 Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that Airspace with type equal-to ('CTA','CTA_P','CTR','CTR_P') has geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface coordinates expressed with less than 4 decimals <keyword> It is prohibited that </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('CTA','CTA_P','CTR','CTR_P') </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface </noun_concept> Longitude and Latitude of ('CTA','CTA_P','CTR','CTR_P') boundary points shall be published with at least 4 decimals resolution. Longitude and Latitude of ('CTA','CTA_P','CTR','CTR_P') boundary points shall be published with at least 4 decimals resolution. AirspaceVolume Surface baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Airspace type ('CTA','CTA_P','CTR','CTR_P')
AIXM-5.1_RULE-D5613 Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that Airspace with type equal-to ('P','R','D') has geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface coordinates expressed with less than 2 decimals <keyword> It is prohibited that </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('P','R','D') </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface </noun_concept> Longitude and Latitude of ('P','R','D') boundary points shall be published with at least 2 decimals resolution. Longitude and Latitude of ('P','R','D') boundary points shall be published with at least 2 decimals resolution. AirspaceVolume Surface baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Airspace type ('P','R','D')
AIXM-5.1_RULE-DAC00 Warning FAA FNS-NDS Tech Spec Scenario ID: 25 It is prohibited that an AirportHeliportTimeSlice with not exactly one assigned availability value belongsTo Event with scenario equal-to '25' <keyword> It is prohibited that an </keyword><noun_concept> AirportHeliportTimeSlice </noun_concept><keyword> with not exactly one assigned </keyword><noun_concept> availability </noun_concept><keyword> value </keyword><verb_concept> belongsTo </verb_concept><noun_concept> Event </noun_concept><keyword> with </keyword><noun_concept> scenario </noun_concept><keyword> equal-to </keyword><name> '25' </name> If the event scenario is "aerodrome closure" (id=25), there should be a single availability If the event scenario is "aerodrome closure" (id=25), there should be a single availability AirportHeliport All Standard (ICAO, industry, etc.) Event (FAA) - 25 - only one availability element
AIXM-5.1_RULE-46119 Warning ICAO Annex 15 Table A7-2 It is prohibited that an AirportHeliport with assigned ARP.ElevatedPoint.geoidUndulation value has ARP.ElevatedPoint.geoidUndulation.uom not equal-to ('FT','M') <keyword> It is prohibited that an </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> ARP.ElevatedPoint.geoidUndulation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> ARP.ElevatedPoint.geoidUndulation.uom </noun_concept><keyword> not equal-to </keyword><name> ('FT','M') </name> WGS-84 geoid undulation at AirportHeliport ARP shall be published with 1m or 1ft resolution WGS-84 geoid undulation at AirportHeliport ARP shall be published with 1m or 1ft resolution AirportHeliport geoidUndulation All Recommended practice (ICAO, industry, etc.) Resolution (vertical) - WGS-84 geoid undulation at AirportHeliport ARP
AIXM-5.1_RULE-4611A Warning ICAO Annex 15 Table A7-2 It is prohibited that an TouchDownLiftOff with assigned aimingPoint.ElevatedPoint.geoidUndulation value has aimingPoint.ElevatedPoint.geoidUndulation.uom not equal-to ('FT','M') <keyword> It is prohibited that an </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with assigned </keyword><noun_concept> aimingPoint.ElevatedPoint.geoidUndulation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> aimingPoint.ElevatedPoint.geoidUndulation.uom </noun_concept><keyword> not equal-to </keyword><name> ('FT','M') </name> WGS-84 geoid undulation at TouchDownLiftOff aimingPoint shall be published with 1m or 1ft resolution WGS-84 geoid undulation at TouchDownLiftOff aimingPoint shall be published with 1m or 1ft resolution TouchDownLiftOff geoidUndulation All Recommended practice (ICAO, industry, etc.) Resolution (vertical) - WGS-84 geoid undulation at TouchDownLiftOff aimingPoint
AIXM-5.1_RULE-1AB3F1 Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentDeparture with assigned guidanceFacility.GuidanceService.radar value has guidanceFacility.GuidanceService.radar value resolved-into exactly one isBasedOn RadarSystem <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> with assigned </keyword><noun_concept> guidanceFacility.GuidanceService.radar </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> guidanceFacility.GuidanceService.radar </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> RadarSystem </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentDeparture guidanceFacility.GuidanceService.radar set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AB3F2 Error AIXM Model It is obligatory that each Procedure specialisation StandardInstrumentArrival with assigned guidanceFacility.GuidanceService.radar value has guidanceFacility.GuidanceService.radar value resolved-into exactly one isBasedOn RadarSystem <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentArrival </noun_concept><keyword> with assigned </keyword><noun_concept> guidanceFacility.GuidanceService.radar </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> guidanceFacility.GuidanceService.radar </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> RadarSystem </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. StandardInstrumentArrival guidanceFacility.GuidanceService.radar set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AB3F3 Error AIXM Model It is obligatory that each Procedure specialisation InstrumentApproachProcedure with assigned guidanceFacility.GuidanceService.radar value has guidanceFacility.GuidanceService.radar value resolved-into exactly one isBasedOn RadarSystem <keyword> It is obligatory that each </keyword><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept><keyword> with assigned </keyword><noun_concept> guidanceFacility.GuidanceService.radar </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> guidanceFacility.GuidanceService.radar </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> RadarSystem </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. InstrumentApproachProcedure guidanceFacility.GuidanceService.radar set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AB3F4 Error AIXM Model It is obligatory that each NavaidEquipment specialisation DirectionFinder with assigned authority.AuthorityForNavaidEquipment.theOrganisationAuthority value has authority.AuthorityForNavaidEquipment.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept><keyword> with assigned </keyword><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority.AuthorityForNavaidEquipment.theOrganisationAuthority </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. DirectionFinder authority.AuthorityForNavaidEquipment.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AB3F5 AIXM Model It is obligatory that each SurveillanceRadar specialisation SecondarySurveillanceRadar with assigned groundStation.SurveillanceGroundStation.theUnit value has groundStation.SurveillanceGroundStation.theUnit value resolved-into exactly one radarScopeIsLocatedAt Unit <keyword> It is obligatory that each </keyword><noun_concept> SurveillanceRadar </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SecondarySurveillanceRadar </noun_concept><keyword> with assigned </keyword><noun_concept> groundStation.SurveillanceGroundStation.theUnit </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> groundStation.SurveillanceGroundStation.theUnit </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> radarScopeIsLocatedAt </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. SecondarySurveillanceRadar groundStation.SurveillanceGroundStation.theUnit set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AB3F6 AIXM Model It is obligatory that each SurveillanceRadar specialisation PrimarySurveillanceRadar with assigned groundStation.SurveillanceGroundStation.theUnit value has groundStation.SurveillanceGroundStation.theUnit value resolved-into exactly one radarScopeIsLocatedAt Unit <keyword> It is obligatory that each </keyword><noun_concept> SurveillanceRadar </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> PrimarySurveillanceRadar </noun_concept><keyword> with assigned </keyword><noun_concept> groundStation.SurveillanceGroundStation.theUnit </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> groundStation.SurveillanceGroundStation.theUnit </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> radarScopeIsLocatedAt </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. PrimarySurveillanceRadar groundStation.SurveillanceGroundStation.theUnit set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AB3F8 Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation AltimeterSourceStatus with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AltimeterSourceStatus </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AltimeterSourceStatus specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AB3F9 AIXM Model It is obligatory that each PropertiesWithSchedule specialisation FlightConditionCombination with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> FlightConditionCombination </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. FlightConditionCombination specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AB3FA Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation UnitAvailability with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> UnitAvailability </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. UnitAvailability specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AB3FB Error AIXM Model It is obligatory that each PropertiesWithSchedule specialisation VerticalStructureLightingStatus with assigned specialDateAuthority value has specialDateAuthority value resolved-into exactly one appliesSpecialDatesOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> PropertiesWithSchedule </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VerticalStructureLightingStatus </noun_concept><keyword> with assigned </keyword><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> specialDateAuthority </noun_concept><keyword> value </keyword><keyword> resolved-into exactly one </keyword><verb_concept> appliesSpecialDatesOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. VerticalStructureLightingStatus specialDateAuthority set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the class)
AIXM-5.1_RULE-1AA069 Warning ICAO Annex 15 Table A7-1 It is prohibited that AirspaceVolume is-property-of Airspace with type equal-to ('P','R','D') and AirspaceVolume dependsOn Airspace with geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface coordinates expressed with less than 2 decimals <keyword> It is prohibited that </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('P','R','D') </name><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> dependsOn </verb_concept><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface </noun_concept> Longitude and Latitude of ('P','R','D') boundary points shall be aggregated with Airspace that have boundary points published with at least 2 decimals resolution Longitude and Latitude of ('P','R','D') boundary points shall be aggregated with Airspace that have boundary points published with at least 2 decimals resolution AirspaceVolume set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Airspace type ('P','R','D') (with volume dependencies)
AIXM-5.1_RULE-1AA06A Warning ICAO Annex 15 Table A7-1 It is prohibited that AirspaceVolume is-property-of Airspace with type equal-to ('CTA','CTA_P','CTR','CTR_P') and AirspaceVolume dependsOn Airspace with geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface coordinates expressed with less than 4 decimals <keyword> It is prohibited that </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('CTA','CTA_P','CTR','CTR_P') </name><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> dependsOn </verb_concept><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface </noun_concept> Longitude and Latitude of ('CTA','CTA_P','CTR','CTR_P') boundary points shall be aggregated with Airspace that have boundary points published with at least 4 decimals resolution Longitude and Latitude of ('CTA','CTA_P','CTR','CTR_P') boundary points shall be aggregated with Airspace that have boundary points published with at least 4 decimals resolution AirspaceVolume set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Airspace type ('CTA','CTA_P','CTR','CTR_P') (with volume dependencies)
AIXM-5.1_RULE-1AA06B Warning ICAO Annex 15 Table A7-1 It is prohibited that AirspaceVolume is-property-of Airspace with type equal-to ('FIR','UIR','FIR_P','UIR_P') and AirspaceVolume dependsOn Airspace with geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface coordinates expressed with less than 2 decimals <keyword> It is prohibited that </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('FIR','UIR','FIR_P','UIR_P') </name><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> dependsOn </verb_concept><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.horizontalProjection.Surface </noun_concept> Longitude and Latitude of ('FIR','UIR','FIR_P','UIR_P') boundary points shall be aggregated with Airspace that have boundary points published with at least 2 decimals resolution Longitude and Latitude of ('FIR','UIR','FIR_P','UIR_P') boundary points shall be aggregated with Airspace that have boundary points published with at least 2 decimals resolution AirspaceVolume set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Airspace type ('FIR','UIR','FIR_P','UIR_P') (with volume dependencies)
AIXM-5.1_RULE-16B49 Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation VOR has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of VOR shall be published with 1 sec resolution (aerodrome navaid equipment) Latitude and Longitude of VOR shall be published with 1 sec resolution (aerodrome navaid equipment) VOR location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - VOR (EAD profile)
AIXM-5.1_RULE-16B52 Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation DME has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of DME shall be published with 1 sec resolution (aerodrome navaid equipment) Latitude and Longitude of DME shall be published with 1 sec resolution (aerodrome navaid equipment) DME location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - DME (EAD profile)
AIXM-5.1_RULE-16B53 Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation MarkerBeacon has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of MarkerBeacon shall be published with 1 sec resolution (aerodrome navaid equipment) Latitude and Longitude of MarkerBeacon shall be published with 1 sec resolution (aerodrome navaid equipment) MarkerBeacon location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - MarkerBeacon (EAD profile)
AIXM-5.1_RULE-16B54 Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation NDB has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of NDB shall be published with 1 sec resolution (aerodrome navaid equipment) Latitude and Longitude of NDB shall be published with 1 sec resolution (aerodrome navaid equipment) NDB location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - NDB (EAD profile)
AIXM-5.1_RULE-16B57 Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation TACAN has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of TACAN shall be published with 1 sec resolution (aerodrome navaid equipment) Latitude and Longitude of TACAN shall be published with 1 sec resolution (aerodrome navaid equipment) TACAN location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - TACAN (EAD profile)
AIXM-5.1_RULE-16B58 Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation Glidepath has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Glidepath shall be published with 1/10 sec resolution (aerodrome navaid equipment) Latitude and Longitude of Glidepath shall be published with 1/10 sec resolution (aerodrome navaid equipment) Glidepath location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Glidepath (EAD profile)
AIXM-5.1_RULE-16B59 Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation Azimuth has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Azimuth shall be published with 1/10 sec resolution (aerodrome navaid equipment) Latitude and Longitude of Azimuth shall be published with 1/10 sec resolution (aerodrome navaid equipment) Azimuth location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Azimuth (EAD profile)
AIXM-5.1_RULE-16B5A Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation Localizer has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Localizer shall be published with 1/10 sec resolution (aerodrome navaid equipment) Latitude and Longitude of Localizer shall be published with 1/10 sec resolution (aerodrome navaid equipment) Localizer location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Localizer (EAD profile)
AIXM-5.1_RULE-16B5B Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation Elevation has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Elevation shall be published with 1/10 sec resolution (aerodrome navaid equipment) Latitude and Longitude of Elevation shall be published with 1/10 sec resolution (aerodrome navaid equipment) Elevation location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Elevation (EAD profile)
AIXM-5.1_RULE-33C21 Warning ICAO Annex 15 Table A7-2 It is prohibited that a RunwayCentrelinePoint with role equal-to 'THR' and with assigned location.ElevatedPoint. geoidUndulation value has location.ElevatedPoint. geoidUndulation.uom not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'THR' </name><keyword> and with assigned </keyword><noun_concept> location.ElevatedPoint. geoidUndulation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint. geoidUndulation.uom </noun_concept><keyword> not equal-to </keyword><name> ('FT','M') </name> geoidUndulation at runway or FATO threshold (role=THR), TLOF geometric centre , non-precision approaches shall be published with 1m or 1ft resolution geoidUndulation at runway or FATO threshold (role=THR), TLOF geometric centre , non-precision approaches shall be published with 1m or 1ft resolution RunwayCentrelinePoint geoidUndulation baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (vertical) - geoidUndulation at RWY/FATO (all)
AIXM-5.1_RULE-33C22 Warning ICAO Annex 15 Table A7-2 It is prohibited that a RunwayCentrelinePoint with role equal-to 'THR' and with assigned location.ElevatedPoint. elevation value has location.ElevatedPoint. elevation.uom not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'THR' </name><keyword> and with assigned </keyword><noun_concept> location.ElevatedPoint. elevation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint. elevation.uom </noun_concept><keyword> not equal-to </keyword><name> ('FT','M') </name> elevation at runway or FATO threshold (role=THR), TLOF geometric centre , non-precision approaches shall be published with 1m or 1ft resolution elevation at runway or FATO threshold (role=THR), TLOF geometric centre , non-precision approaches shall be published with 1m or 1ft resolution RunwayCentrelinePoint elevation baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (vertical) - elevation at RWY/FATO (all)
AIXM-5.1_RULE-156C61 Error AIXM Model It is obligatory that each ProcedureDME with assigned segmentLeg value has segmentLeg value resolved-into exactly one isEvaluatedFor SegmentLeg specialisation ArrivalLeg or DepartureLeg or ApproachLeg specialisation ArrivalFeederLeg or InitialLeg or IntermediateLeg or FinalLeg or MissedApproachLeg <keyword> It is obligatory that each </keyword><noun_concept> ProcedureDME </noun_concept><keyword> with assigned </keyword><noun_concept> segmentLeg </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> segmentLeg </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isEvaluatedFor </verb_concept><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalLeg </noun_concept><keyword> or </keyword><noun_concept> DepartureLeg </noun_concept><keyword> or </keyword><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalFeederLeg </noun_concept><keyword> or </keyword><noun_concept> InitialLeg </noun_concept><keyword> or </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> or </keyword><noun_concept> FinalLeg </noun_concept><keyword> or </keyword><noun_concept> MissedApproachLeg </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ProcedureDME segmentLeg set of snapshots Minimal data rule Referential integrity towards SegmentLeg
AIXM-5.1_RULE-156C62 Error AIXM Model It is obligatory that each ProcedureTransition with assigned transitionLeg.ProcedureTransitionLeg.theSegmentLeg value has transitionLeg.ProcedureTransitionLeg.theSegmentLeg value resolved-into exactly one isComposedOf SegmentLeg specialisation ArrivalLeg or DepartureLeg or ApproachLeg specialisation ArrivalFeederLeg or InitialLeg or IntermediateLeg or FinalLeg or MissedApproachLeg <keyword> It is obligatory that each </keyword><noun_concept> ProcedureTransition </noun_concept><keyword> with assigned </keyword><noun_concept> transitionLeg.ProcedureTransitionLeg.theSegmentLeg </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> transitionLeg.ProcedureTransitionLeg.theSegmentLeg </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> SegmentLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalLeg </noun_concept><keyword> or </keyword><noun_concept> DepartureLeg </noun_concept><keyword> or </keyword><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalFeederLeg </noun_concept><keyword> or </keyword><noun_concept> InitialLeg </noun_concept><keyword> or </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> or </keyword><noun_concept> FinalLeg </noun_concept><keyword> or </keyword><noun_concept> MissedApproachLeg </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ProcedureTransition transitionLeg.ProcedureTransitionLeg.theSegmentLeg set of snapshots Minimal data rule Referential integrity towards SegmentLeg
AIXM-5.1_RULE-BB037 Error AIXM Model It is obligatory that each DepartureLeg with assigned departure value has departure value resolved-into exactly one isPartOf Procedure specialisation StandardInstrumentDeparture <keyword> It is obligatory that each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with assigned </keyword><noun_concept> departure </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> departure </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isPartOf </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. DepartureLeg departure set of snapshots Minimal data rule Referential integrity - first level of inheritance (for both the class and the targetClass) (EAD profile)
AIXM-5.1_RULE-BB038 Error AIXM Model It is obligatory that each ArrivalLeg with assigned arrival value has arrival value resolved-into exactly one isPartOf Procedure specialisation StandardInstrumentArrival <keyword> It is obligatory that each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> arrival </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> arrival </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isPartOf </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentArrival </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. ArrivalLeg arrival set of snapshots Minimal data rule Referential integrity - first level of inheritance (for both the class and the targetClass) (EAD profile)
AIXM-5.1_RULE-BB039 Error AIXM Model It is obligatory that each CheckpointVOR with assigned checkPointFacility value has checkPointFacility value resolved-into exactly one references NavaidEquipment specialisation VOR <keyword> It is obligatory that each </keyword><noun_concept> CheckpointVOR </noun_concept><keyword> with assigned </keyword><noun_concept> checkPointFacility </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> checkPointFacility </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> references </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. CheckpointVOR checkPointFacility set of snapshots Minimal data rule Referential integrity - first level of inheritance (for both the class and the targetClass) (EAD profile)
AIXM-5.1_RULE-5C491 Warning ICAO Annex 15 Table A7-1 Each CheckpointINS with assigned position value shall have position.ElevatedPoint coordinates expressed with at least 6 decimals <keyword> Each </keyword><noun_concept> CheckpointINS </noun_concept><keyword> with assigned </keyword><noun_concept> position </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> position.ElevatedPoint </noun_concept> Latitude and longitude of CheckpointINS position shall be published with at least 6 decimals resolution Latitude and longitude of CheckpointINS position shall be published with at least 6 decimals resolution CheckpointINS ElevatedPoint All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - CheckpointINS position
AIXM-5.1_RULE-5C492 Warning Warning ICAO Annex 15 Table A7-1 Each AirportHeliport with assigned ARP value shall have ARP.ElevatedPoint coordinates expressed with at least 4 decimals <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> ARP </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> ARP.ElevatedPoint </noun_concept> Latitude and longitude of AirportHeliport ARP shall be published with at least 4 decimals resolution Latitude and longitude of AirportHeliport ARP shall be published with at least 4 decimals resolution AirportHeliport ElevatedPoint All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - AirportHeliport ARP
AIXM-5.1_RULE-5C493 Warning ICAO Annex 15 Table A7-1 Each AircraftStand with assigned location value shall have location.ElevatedPoint coordinates expressed with at least 6 decimals <keyword> Each </keyword><noun_concept> AircraftStand </noun_concept><keyword> with assigned </keyword><noun_concept> location </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and longitude of AircraftStand location shall be published with at least 6 decimals resolution Latitude and longitude of AircraftStand location shall be published with at least 6 decimals resolution AircraftStand ElevatedPoint All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - AircraftStand location
AIXM-5.1_RULE-5C494 Warning ICAO Annex 15 Table A7-1 Each TouchDownLiftOff with assigned aimingPoint value shall have aimingPoint.ElevatedPoint coordinates expressed with at least 6 decimals <keyword> Each </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with assigned </keyword><noun_concept> aimingPoint </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> aimingPoint.ElevatedPoint </noun_concept> Latitude and longitude of TouchDownLiftOff aimingPoint shall be published with at least 6 decimals resolution Latitude and longitude of TouchDownLiftOff aimingPoint shall be published with at least 6 decimals resolution TouchDownLiftOff ElevatedPoint All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - TouchDownLiftOff aimingPoint
AIXM-5.1_RULE-5C495 Warning ICAO Annex 15 Table A7-1 Each TaxiHoldingPosition with assigned location value shall have location.ElevatedPoint coordinates expressed with at least 6 decimals <keyword> Each </keyword><noun_concept> TaxiHoldingPosition </noun_concept><keyword> with assigned </keyword><noun_concept> location </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and longitude of TaxiHoldingPosition location shall be published with at least 6 decimals resolution Latitude and longitude of TaxiHoldingPosition location shall be published with at least 6 decimals resolution TaxiHoldingPosition ElevatedPoint All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - TaxiHoldingPosition location
AIXM-5.1_RULE-33069 Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'VOR_DME' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type VOR_DME, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type VOR_DME, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type VOR_DME when used at aerodrome
AIXM-5.1_RULE-3306A Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'VORTAC' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type VORTAC, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type VORTAC, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type VORTAC when used at aerodrome
AIXM-5.1_RULE-3306B Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'DME' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type DME, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type DME, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type DME when used at aerodrome
AIXM-5.1_RULE-3306C Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'TACAN' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type TACAN, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type TACAN, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type TACAN when used at aerodrome
AIXM-5.1_RULE-3306D Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'VOR' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type VOR, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type VOR, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type VOR when used at aerodrome
AIXM-5.1_RULE-3306E Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'NDB' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type NDB, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type NDB, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type NDB when used at aerodrome
AIXM-5.1_RULE-3306F Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'MKR' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type MKR, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type MKR, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type MKR when used at aerodrome
AIXM-5.1_RULE-33071 Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'NDB_MKR' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type NDB_MKR, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type NDB_MKR, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type NDB_MKR when used at aerodrome
AIXM-5.1_RULE-33072 Warning Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'NDB_DME' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type NDB_DME, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type NDB_DME, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type NDB_DME when used at aerodrome
AIXM-5.1_RULE-33073 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'DF' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type DF, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type DF, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type DF when used at aerodrome
AIXM-5.1_RULE-104411 Warning ICAO Annex 15 Appendix 7-1 It is prohibited that a VerticalStructure has part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> VerticalStructure </noun_concept><verb_concept> has </verb_concept><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface </noun_concept> Latitude and longitude of obstacles in Area 1 shall be published with 1 sec resolution. Note: to keep it simple, this rule is applied to all obstacles. More demanding requirements for Area 2 and 3 are specified through separate rules. Latitude and longitude of obstacles in Area 1 shall be published with 1 sec resolution. Note: to keep it simple, this rule is applied to all obstacles. More demanding requirements for Area 2 and 3 are specified through separate rules. VerticalStructure ANY;NO_REF Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Obstacles in Area 1
AIXM-5.1_RULE-104412 Warning ICAO Annex 15 Appendix 7-1 It is prohibited that a VerticalStructure has part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> VerticalStructure </noun_concept><verb_concept> has </verb_concept><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint </noun_concept> Latitude and longitude of obstacles in Area 1 shall be published with 1 sec resolution. Note: to keep it simple, this rule is applied to all obstacles. More demanding requirements for Area 2 and 3 are specified through separate rules. Latitude and longitude of obstacles in Area 1 shall be published with 1 sec resolution. Note: to keep it simple, this rule is applied to all obstacles. More demanding requirements for Area 2 and 3 are specified through separate rules. VerticalStructure ANY;NO_REF Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Obstacles in Area 1
AIXM-5.1_RULE-104413 Warning ICAO Annex 15 Appendix 7-1 It is prohibited that a VerticalStructure has part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> VerticalStructure </noun_concept><verb_concept> has </verb_concept><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve </noun_concept> Latitude and longitude of obstacles in Area 1 shall be published with 1 sec resolution. Note: to keep it simple, this rule is applied to all obstacles. More demanding requirements for Area 2 and 3 are specified through separate rules. Latitude and longitude of obstacles in Area 1 shall be published with 1 sec resolution. Note: to keep it simple, this rule is applied to all obstacles. More demanding requirements for Area 2 and 3 are specified through separate rules. VerticalStructure ANY;NO_REF Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Obstacles in Area 1
AIXM-5.1_RULE-57E41 Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'CTA' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'FT' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'CTA' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of CTA boundary points shall be better than 300.0 FT The horizontal accuracy of CTA boundary points shall be better than 300.0 FT Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace CTA
AIXM-5.1_RULE-57E42 Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'CTA' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'M' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'CTA' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of CTA boundary points shall be better than 100.0 M The horizontal accuracy of CTA boundary points shall be better than 100.0 M Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace CTA
AIXM-5.1_RULE-57E43 Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'CTA_P' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'FT' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'CTA_P' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of CTA_P boundary points shall be better than 300.0 FT The horizontal accuracy of CTA_P boundary points shall be better than 300.0 FT Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace CTA_P
AIXM-5.1_RULE-57E44 Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'CTA_P' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'M' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'CTA_P' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of CTA_P boundary points shall be better than 100.0 M The horizontal accuracy of CTA_P boundary points shall be better than 100.0 M Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace CTA_P
AIXM-5.1_RULE-57E45 Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'CTR' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'FT' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'CTR' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of CTR boundary points shall be better than 300.0 FT The horizontal accuracy of CTR boundary points shall be better than 300.0 FT Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace CTR
AIXM-5.1_RULE-57E46 Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'CTR' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'M' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'CTR' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of CTR boundary points shall be better than 100.0 M The horizontal accuracy of CTR boundary points shall be better than 100.0 M Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace CTR
AIXM-5.1_RULE-57E47 Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'CTR_P' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'FT' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'CTR_P' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of CTR_P boundary points shall be better than 300.0 FT The horizontal accuracy of CTR_P boundary points shall be better than 300.0 FT Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace CTR_P
AIXM-5.1_RULE-57E48 Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'CTR_P' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'M' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'CTR_P' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of CTR_P boundary points shall be better than 100.0 M The horizontal accuracy of CTR_P boundary points shall be better than 100.0 M Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace CTR_P
AIXM-5.1_RULE-57E49 Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'D' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'KM' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 2.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'D' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'KM' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of D boundary points shall be better than 2.0 KM The horizontal accuracy of D boundary points shall be better than 2.0 KM Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace D
AIXM-5.1_RULE-57E4A Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'FIR' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'KM' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 2.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'FIR' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'KM' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of FIR boundary points shall be better than 2.0 KM The horizontal accuracy of FIR boundary points shall be better than 2.0 KM Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace FIR
AIXM-5.1_RULE-57E4B Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'FIR_P' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'KM' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 2.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'FIR_P' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'KM' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of FIR_P boundary points shall be better than 2.0 KM The horizontal accuracy of FIR_P boundary points shall be better than 2.0 KM Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace FIR_P
AIXM-5.1_RULE-57E4C Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'P' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'KM' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 2.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'P' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'KM' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of P boundary points shall be better than 2.0 KM The horizontal accuracy of P boundary points shall be better than 2.0 KM Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace P
AIXM-5.1_RULE-57E4D Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'R' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'KM' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 2.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'R' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'KM' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of R boundary points shall be better than 2.0 KM The horizontal accuracy of R boundary points shall be better than 2.0 KM Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace R
AIXM-5.1_RULE-57E4E Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'UIR' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'KM' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 2.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'UIR' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'KM' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of UIR boundary points shall be better than 2.0 KM The horizontal accuracy of UIR boundary points shall be better than 2.0 KM Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace UIR
AIXM-5.1_RULE-57E4F Warning ICAO Annex 14 Table A5-1 It is prohibited that an Airspace with type equal-to 'UIR_P' and with assigned geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value and with geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom equal-to 'KM' has geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy value higher-than 2.0 <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'UIR_P' </name><keyword> and with assigned </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'KM' </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceVolume.horizontalProjection.Surface.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of UIR_P boundary points shall be better than 2.0 KM The horizontal accuracy of UIR_P boundary points shall be better than 2.0 KM Airspace horizontalAccuracy Recommended practice (ICAO, industry, etc.) Accuracy (horizontal) - Airspace UIR_P
AIXM-5.1_RULE-D9C61 Warning ICAO Annex 15 Table A7-2 It is prohibited that a DME with assigned location.ElevatedPoint.elevation value has assigned location.ElevatedPoint.elevation.uom value not equal-to ('FT', 'M') <keyword> It is prohibited that a </keyword><noun_concept> DME </noun_concept><keyword> with assigned </keyword><noun_concept> location.ElevatedPoint.elevation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.elevation.uom </noun_concept><keyword> value </keyword><keyword> not equal-to </keyword><name> ('FT', 'M') </name> DME elevation must have a minimal resolution of 30 m (100 ft) Note: the only think that can be verified in this case is the use of either FT or M as unit on measurement. A value such as "200 M" cannot be assumed to break this rule because maybe this is the exact elevation value. DME elevation must have a minimal resolution of 30 m (100 ft) Note: the only think that can be verified in this case is the use of either FT or M as unit on measurement. A value such as "200 M" cannot be assumed to break this rule because maybe this is the exact elevation value. DME location All Recommended practice (ICAO, industry, etc.) Resolution (vertical) - DME
AIXM-5.1_RULE-D9C62 Warning ICAO Annex 15 Table A7-2 It is prohibited that a TouchDownLiftOff with assigned aimingPoint.ElevatedPoint.elevation value has assigned aimingPoint.ElevatedPoint.elevation.uom value not equal-to ('FT', 'M') <keyword> It is prohibited that a </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with assigned </keyword><noun_concept> aimingPoint.ElevatedPoint.elevation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> aimingPoint.ElevatedPoint.elevation.uom </noun_concept><keyword> value </keyword><keyword> not equal-to </keyword><name> ('FT', 'M') </name> TouchDownLiftOff elevation must have a minimal resolution of 1 m (1 ft) Note: the only think that can be verified in this case is the use of either FT or M as unit on measurement. A value such as "200 M" cannot be assumed to break this rule because maybe this is the exact elevation value. TouchDownLiftOff elevation must have a minimal resolution of 1 m (1 ft) Note: the only think that can be verified in this case is the use of either FT or M as unit on measurement. A value such as "200 M" cannot be assumed to break this rule because maybe this is the exact elevation value. TouchDownLiftOff aimingPoint All Recommended practice (ICAO, industry, etc.) Resolution (vertical) - TouchDownLiftOff
AIXM-5.1_RULE-E679 Warning Warning ICAO Annex 14 Table A5-1 It is prohibited that a AirportHeliport with ARP.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has ARP.ElevatedPoint.horizontalAccuracy value higher-than 30 M <keyword> It is prohibited that a </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with </keyword><noun_concept> ARP.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> ARP.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of the AirportHeliport ARP shall be better than 30 M The horizontal accuracy of the AirportHeliport ARP shall be better than 30 M AirportHeliport ARP All Standard (ICAO, industry, etc.) Accuracy (horizontal) AirportHeliport location
AIXM-5.1_RULE-E67F Warning Warning ICAO Annex 14 Table A5-1 It is prohibited that a AirportHeliport with ARP.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has ARP.ElevatedPoint.horizontalAccuracy value higher-than 100 FT <keyword> It is prohibited that a </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with </keyword><noun_concept> ARP.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> ARP.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of the AirportHeliport ARP shall be better than 100 FT The horizontal accuracy of the AirportHeliport ARP shall be better than 100 FT AirportHeliport ARP All Standard (ICAO, industry, etc.) Accuracy (horizontal) AirportHeliport location
AIXM-5.1_RULE-E680 Warning ICAO Annex 14 Table A5-1 It is prohibited that a AircraftStand with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 0.5 M <keyword> It is prohibited that a </keyword><noun_concept> AircraftStand </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of the AircraftStand location shall be better than 0.5 M The horizontal accuracy of the AircraftStand location shall be better than 0.5 M AircraftStand location All Standard (ICAO, industry, etc.) Accuracy (horizontal) AircraftStand location
AIXM-5.1_RULE-E681 Warning ICAO Annex 14 Table A5-1 It is prohibited that a TouchDownLiftOff with aimingPoint.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has aimingPoint.ElevatedPoint.horizontalAccuracy value higher-than 1.0 M <keyword> It is prohibited that a </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with </keyword><noun_concept> aimingPoint.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> aimingPoint.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of the TouchDownLiftOff aimingPoint shall be better than 1.0 M The horizontal accuracy of the TouchDownLiftOff aimingPoint shall be better than 1.0 M TouchDownLiftOff aimingPoint All Standard (ICAO, industry, etc.) Accuracy (horizontal) TouchDownLiftOff location
AIXM-5.1_RULE-E682 Warning ICAO Annex 14 Table A5-1 It is prohibited that a TouchDownLiftOff with aimingPoint.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has aimingPoint.ElevatedPoint.horizontalAccuracy value higher-than 3.0 FT <keyword> It is prohibited that a </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with </keyword><noun_concept> aimingPoint.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> aimingPoint.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of the TouchDownLiftOff aimingPoint shall be better than 3.0 FT The horizontal accuracy of the TouchDownLiftOff aimingPoint shall be better than 3.0 FT TouchDownLiftOff aimingPoint All Standard (ICAO, industry, etc.) Accuracy (horizontal) TouchDownLiftOff location
AIXM-5.1_RULE-E683 Warning ICAO Annex 14 Table A5-1 It is prohibited that a AircraftStand with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 1.5 FT <keyword> It is prohibited that a </keyword><noun_concept> AircraftStand </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of the AircraftStand location shall be better than 1.5 FT The horizontal accuracy of the AircraftStand location shall be better than 1.5 FT AircraftStand location All Standard (ICAO, industry, etc.) Accuracy (horizontal) AircraftStand location
AIXM-5.1_RULE-D5229 Error AIXM 4.5 AIXM 4.5 It is prohibited that a NavaidComponent is-property-of Navaid with type equal-to ('VOR', 'VOR_DME', 'VORTAC') and NavaidComponent has providesNavigableLocation equal-to 'YES' and not NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('VOR', 'VOR_DME', 'VORTAC') </name><keyword> and </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> has </verb_concept><noun_concept> providesNavigableLocation </noun_concept><keyword> equal-to </keyword><name> 'YES' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> Navaid with type ('VOR', 'VOR_DME', 'VORTAC') cannot have its navigable location provided by a NavaidEquipment different from VOR Found Navaid type ('VOR', 'VOR_DME', 'VORTAC') and navigable location provided by another equipment than VOR Navaid providesNavigableLocation baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) Navaid navigable location equipment
AIXM-5.1_RULE-D522A Error AIXM 4.5 AIXM 4.5 It is prohibited that a NavaidComponent is-property-of Navaid with type equal-to 'DME' and NavaidComponent has providesNavigableLocation equal-to 'YES' and not NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><keyword> and </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> has </verb_concept><noun_concept> providesNavigableLocation </noun_concept><keyword> equal-to </keyword><name> 'YES' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> Navaid with type 'DME' cannot have its navigable location provided by a NavaidEquipment different from DME Found Navaid type 'DME' and navigable location provided by another equipment than DME Navaid providesNavigableLocation baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) Navaid navigable location equipment
AIXM-5.1_RULE-D522B Error AIXM 4.5 AIXM 4.5 It is prohibited that a NavaidComponent is-property-of Navaid with type equal-to 'MKR' and NavaidComponent has providesNavigableLocation equal-to 'YES' and not NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><keyword> and </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> has </verb_concept><noun_concept> providesNavigableLocation </noun_concept><keyword> equal-to </keyword><name> 'YES' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> Navaid with type 'MKR' cannot have its navigable location provided by a NavaidEquipment different from MarkerBeacon Found Navaid type 'MKR' and navigable location provided by another equipment than MarkerBeacon Navaid providesNavigableLocation baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) Navaid navigable location equipment
AIXM-5.1_RULE-D522C Error AIXM 4.5 AIXM 4.5 It is prohibited that a NavaidComponent is-property-of Navaid with type equal-to ('NDB', 'NDB_MKR', 'NDB_DME') and NavaidComponent has providesNavigableLocation equal-to 'YES' and not NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('NDB', 'NDB_MKR', 'NDB_DME') </name><keyword> and </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> has </verb_concept><noun_concept> providesNavigableLocation </noun_concept><keyword> equal-to </keyword><name> 'YES' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> Navaid with type ('NDB', 'NDB_MKR', 'NDB_DME') cannot have its navigable location provided by a NavaidEquipment different from NDB Found Navaid type ('NDB', 'NDB_MKR', 'NDB_DME') and navigable location provided by another equipment than NDB Navaid providesNavigableLocation baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) Navaid navigable location equipment
AIXM-5.1_RULE-D522D Error AIXM 4.5 AIXM 4.5 It is prohibited that a NavaidComponent is-property-of Navaid with type equal-to 'TACAN' and NavaidComponent has providesNavigableLocation equal-to 'YES' and not NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><keyword> and </keyword><noun_concept> NavaidComponent </noun_concept><verb_concept> has </verb_concept><noun_concept> providesNavigableLocation </noun_concept><keyword> equal-to </keyword><name> 'YES' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> Navaid with type 'TACAN' cannot have its navigable location provided by a NavaidEquipment different from TACAN Found Navaid type 'TACAN' and navigable location provided by another equipment than TACAN Navaid providesNavigableLocation baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) Navaid navigable location equipment
AIXM-5.1_RULE-EC159 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'VOR_DME' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of VOR_DME shall be better than 100.0 M The horizontal accuracy of Navaid of VOR_DME shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type VOR_DME
AIXM-5.1_RULE-EC15A Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'VORTAC' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of VORTAC shall be better than 100.0 M The horizontal accuracy of Navaid of VORTAC shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type VORTAC
AIXM-5.1_RULE-EC15B Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'DME' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of DME shall be better than 100.0 M The horizontal accuracy of Navaid of DME shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type DME
AIXM-5.1_RULE-EC15C Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'TACAN' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of TACAN shall be better than 100.0 M The horizontal accuracy of Navaid of TACAN shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type TACAN
AIXM-5.1_RULE-EC15D Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'VOR' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of VOR shall be better than 100.0 M The horizontal accuracy of Navaid of VOR shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type VOR
AIXM-5.1_RULE-EC15E Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'NDB' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of NDB shall be better than 100.0 M The horizontal accuracy of Navaid of NDB shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type NDB
AIXM-5.1_RULE-EC15F Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'MKR' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of MKR shall be better than 100.0 M The horizontal accuracy of Navaid of MKR shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type MKR
AIXM-5.1_RULE-EC160 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'SDF' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of SDF shall be better than 100.0 M The horizontal accuracy of Navaid of SDF shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type SDF
AIXM-5.1_RULE-EC161 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'NDB_MKR' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of NDB_MKR shall be better than 100.0 M The horizontal accuracy of Navaid of NDB_MKR shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type NDB_MKR
AIXM-5.1_RULE-EC162 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'NDB_DME' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of NDB_DME shall be better than 100.0 M The horizontal accuracy of Navaid of NDB_DME shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type NDB_DME
AIXM-5.1_RULE-EC163 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'DF' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of DF shall be better than 100.0 M The horizontal accuracy of Navaid of DF shall be better than 100.0 M Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type DF
AIXM-5.1_RULE-EC164 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'VOR_DME' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of VOR_DME shall be better than 300.0 FT The horizontal accuracy of Navaid of VOR_DME shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type VOR_DME
AIXM-5.1_RULE-EC165 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'VORTAC' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of VORTAC shall be better than 300.0 FT The horizontal accuracy of Navaid of VORTAC shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type VORTAC
AIXM-5.1_RULE-EC166 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'DME' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of DME shall be better than 300.0 FT The horizontal accuracy of Navaid of DME shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type DME
AIXM-5.1_RULE-EC167 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'TACAN' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of TACAN shall be better than 300.0 FT The horizontal accuracy of Navaid of TACAN shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type TACAN
AIXM-5.1_RULE-EC168 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'VOR' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of VOR shall be better than 300.0 FT The horizontal accuracy of Navaid of VOR shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type VOR
AIXM-5.1_RULE-EC169 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'NDB' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of NDB shall be better than 300.0 FT The horizontal accuracy of Navaid of NDB shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type NDB
AIXM-5.1_RULE-EC16A Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'MKR' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of MKR shall be better than 300.0 FT The horizontal accuracy of Navaid of MKR shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type MKR
AIXM-5.1_RULE-EC16B Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'SDF' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of SDF shall be better than 300.0 FT The horizontal accuracy of Navaid of SDF shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type SDF
AIXM-5.1_RULE-EC16C Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'NDB_MKR' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of NDB_MKR shall be better than 300.0 FT The horizontal accuracy of Navaid of NDB_MKR shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type NDB_MKR
AIXM-5.1_RULE-EC16D Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'NDB_DME' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of NDB_DME shall be better than 300.0 FT The horizontal accuracy of Navaid of NDB_DME shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type NDB_DME
AIXM-5.1_RULE-EC16E Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a Navaid with type equal-to 'DF' and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.horizontalAccuracy value higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><keyword> and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The horizontal accuracy of Navaid of DF shall be better than 300.0 FT The horizontal accuracy of Navaid of DF shall be better than 300.0 FT Navaid location.ElevatedPoint.HorizontalAccuracy baseline outside delta, snapshot, set of snapshots Recommended practice Accuracy (horizontal) - Navaid type DF
AIXM-5.1_RULE-EC541 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice.SignificantPoint. navaidSystem isLocatedAt Navaid with location. ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' and with location. ElevatedPoint.horizontalAccuracy higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint. navaidSystem </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> location. ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and with </keyword><noun_concept> location. ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy of the location of Navaid used as en-route significant point shall be better than 300.0 FT The horizontal accuracy of the location of Navaid used as en-route significant point shall be better than 300.0 FT EnRouteSegmentPoint navaidSystem set of snapshots Recommended practice Accuracy (horizontal) - EnRouteSegmentPoint
AIXM-5.1_RULE-EC542 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice.SignificantPoint. fixDesignatedPoint isLocatedAt DesignatedPoint with location. Point.horizontalAccuracy.uom equal-to 'M' and with location. Point.horizontalAccuracy higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint. fixDesignatedPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept><keyword> with </keyword><noun_concept> location. Point.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and with </keyword><noun_concept> location. Point.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy of the location of DesignatedPoint used as en-route significant point shall be better than 100.0 M The horizontal accuracy of the location of DesignatedPoint used as en-route significant point shall be better than 100.0 M EnRouteSegmentPoint fixDesignatedPoint set of snapshots Recommended practice Accuracy (horizontal) - EnRouteSegmentPoint
AIXM-5.1_RULE-EC543 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice.SignificantPoint. fixDesignatedPoint isLocatedAt DesignatedPoint with location. Point.horizontalAccuracy.uom equal-to 'FT' and with location. Point.horizontalAccuracy higher-than 300.0 <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint. fixDesignatedPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept><keyword> with </keyword><noun_concept> location. Point.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and with </keyword><noun_concept> location. Point.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy of the location of DesignatedPoint used as en-route significant point shall be better than 300.0 FT The horizontal accuracy of the location of DesignatedPoint used as en-route significant point shall be better than 300.0 FT EnRouteSegmentPoint fixDesignatedPoint set of snapshots Recommended practice Accuracy (horizontal) - EnRouteSegmentPoint
AIXM-5.1_RULE-EC544 Warning ICAO Annex 11 Appendix 5, Table 1 It is prohibited that a SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice.SignificantPoint. navaidSystem isLocatedAt Navaid with location. ElevatedPoint.horizontalAccuracy.uom equal-to 'M' and with location. ElevatedPoint.horizontalAccuracy higher-than 100.0 <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint. navaidSystem </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> location. ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and with </keyword><noun_concept> location. ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy of the location of Navaid used as en-route significant point shall be better than 100.0 M The horizontal accuracy of the location of Navaid used as en-route significant point shall be better than 100.0 M EnRouteSegmentPoint navaidSystem set of snapshots Recommended practice Accuracy (horizontal) - EnRouteSegmentPoint
AIXM-5.1_RULE-DE699 Warning ICAO Annex 14 Volume 1 Table A5-1; Volume 2 Table A1-1 It is prohibited that an ApronElement with assigned extent. ElevatedSurface.horizontalAccuracy has extent. ElevatedSurface.horizontalAccuracy.uom equal-to 'M ' and extent. ElevatedSurface.horizontalAccuracy higher-than 1.0 <keyword> It is prohibited that an </keyword><noun_concept> ApronElement </noun_concept><keyword> with assigned </keyword><noun_concept> extent. ElevatedSurface.horizontalAccuracy </noun_concept><verb_concept> has </verb_concept><noun_concept> extent. ElevatedSurface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M </name><name> ' </name><keyword> and </keyword><noun_concept> extent. ElevatedSurface.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The accuracy of the ApronElement extent shall be better than 1.0 M The accuracy of the ApronElement extent shall be better than 1.0 M ApronElement ElevatedSurface extent All Standard (ICAO, industry, etc.) Accuracy (horizontal) - ApronElement extent (Annex 14)
AIXM-5.1_RULE-DE69B Warning ICAO Annex 14 Volume 1 Table A5-1; Volume 2 Table A1-1 It is prohibited that an TaxiHoldingPosition with assigned location. ElevatedPoint.horizontalAccuracy has location. ElevatedPoint.horizontalAccuracy.uom equal-to 'M ' and location. ElevatedPoint.horizontalAccuracy higher-than 0.5 <keyword> It is prohibited that an </keyword><noun_concept> TaxiHoldingPosition </noun_concept><keyword> with assigned </keyword><noun_concept> location. ElevatedPoint.horizontalAccuracy </noun_concept><verb_concept> has </verb_concept><noun_concept> location. ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M </name><name> ' </name><keyword> and </keyword><noun_concept> location. ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The accuracy of the TaxiHoldingPosition location shall be better than 0.5 M The accuracy of the TaxiHoldingPosition location shall be better than 0.5 M TaxiHoldingPosition ElevatedPoint location All Standard (ICAO, industry, etc.) Accuracy (horizontal) - TaxiHoldingPosition location (Annex 14)
AIXM-5.1_RULE-DE69C Warning ICAO Annex 14 Volume 1 Table A5-1; Volume 2 Table A1-1 It is prohibited that an RunwayCentrelinePoint with assigned location. ElevatedPoint.horizontalAccuracy has location. ElevatedPoint.horizontalAccuracy.uom equal-to 'M ' and location. ElevatedPoint.horizontalAccuracy higher-than 1.0 <keyword> It is prohibited that an </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with assigned </keyword><noun_concept> location. ElevatedPoint.horizontalAccuracy </noun_concept><verb_concept> has </verb_concept><noun_concept> location. ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M </name><name> ' </name><keyword> and </keyword><noun_concept> location. ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The accuracy of the RunwayCentrelinePoint location shall be better than 1.0 M The accuracy of the RunwayCentrelinePoint location shall be better than 1.0 M RunwayCentrelinePoint ElevatedPoint location All Standard (ICAO, industry, etc.) Accuracy (horizontal) - RunwayCentrelinePoint location (Annex 14)
AIXM-5.1_RULE-DE69D Warning ICAO Annex 14 Volume 1 Table A5-1; Volume 2 Table A1-1 It is prohibited that an DeicingArea with assigned extent. ElevatedSurface.horizontalAccuracy has extent. ElevatedSurface.horizontalAccuracy.uom equal-to 'M ' and extent. ElevatedSurface.horizontalAccuracy higher-than 1.0 <keyword> It is prohibited that an </keyword><noun_concept> DeicingArea </noun_concept><keyword> with assigned </keyword><noun_concept> extent. ElevatedSurface.horizontalAccuracy </noun_concept><verb_concept> has </verb_concept><noun_concept> extent. ElevatedSurface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M </name><name> ' </name><keyword> and </keyword><noun_concept> extent. ElevatedSurface.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The accuracy of the DeicingArea extent shall be better than 1.0 M The accuracy of the DeicingArea extent shall be better than 1.0 M DeicingArea ElevatedSurface extent All Standard (ICAO, industry, etc.) Accuracy (horizontal) - DeicingArea extent (Annex 14)
AIXM-5.1_RULE-DE69E Warning ICAO Annex 14 Volume 1 Table A5-1; Volume 2 Table A1-1 It is prohibited that an CheckpointINS with assigned position. ElevatedPoint.horizontalAccuracy has position. ElevatedPoint.horizontalAccuracy.uom equal-to 'M ' and position. ElevatedPoint.horizontalAccuracy higher-than 0.5 <keyword> It is prohibited that an </keyword><noun_concept> CheckpointINS </noun_concept><keyword> with assigned </keyword><noun_concept> position. ElevatedPoint.horizontalAccuracy </noun_concept><verb_concept> has </verb_concept><noun_concept> position. ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M </name><name> ' </name><keyword> and </keyword><noun_concept> position. ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The accuracy of the CheckpointINS position shall be better than 0.5 M The accuracy of the CheckpointINS position shall be better than 0.5 M CheckpointINS ElevatedPoint position All Standard (ICAO, industry, etc.) Accuracy (horizontal) - CheckpointINS position (Annex 14)
AIXM-5.1_RULE-DE6A0 Warning ICAO Annex 14 Volume 1 Table A5-1; Volume 2 Table A1-1 It is prohibited that an SpecialNavigationStation with assigned position. ElevatedPoint.horizontalAccuracy has position. ElevatedPoint.horizontalAccuracy.uom equal-to 'M ' and position. ElevatedPoint.horizontalAccuracy higher-than 1.0 <keyword> It is prohibited that an </keyword><noun_concept> SpecialNavigationStation </noun_concept><keyword> with assigned </keyword><noun_concept> position. ElevatedPoint.horizontalAccuracy </noun_concept><verb_concept> has </verb_concept><noun_concept> position. ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M </name><name> ' </name><keyword> and </keyword><noun_concept> position. ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The accuracy of the SpecialNavigationStation position shall be better than 1.0 M The accuracy of the SpecialNavigationStation position shall be better than 1.0 M SpecialNavigationStation ElevatedPoint position All Standard (ICAO, industry, etc.) Accuracy (horizontal) - SpecialNavigationStation position (Annex 14)
AIXM-5.1_RULE-D6D81 Warning Warning ICAO Annex 11 Table A5-2; Volume 2 Table A1-2 It is prohibited that AirportHeliport with assigned ARP.ElevatedPoint.verticalAccuracy value and ARP.ElevatedPoint.verticalAccuracy.uom equal-to 'M' has ARP.ElevatedPoint.verticalAccuracy value higher-than 0.5 <keyword> It is prohibited that </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> ARP.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ARP.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> ARP.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> higher-than </keyword> The accuracy of the AirportHeliport ARP.ElevatedPoint.verticalAccuracy shall be not less than 0.5 Found AirportHeliport with insufficient vertical accuracy (ARP.ElevatedPoint.verticalAccuracy) AirportHeliport ARP.ElevatedPoint.verticalAccuracy Standard (ICAO, industry, etc.) Accuracy (vertical) - AirportHeliport
AIXM-5.1_RULE-D6D8A Warning ICAO Annex 11 Table A5-2; Volume 2 Table A1-2 It is prohibited that RunwayCentrelinePoint with assigned location.ElevatedPoint.verticalAccuracy value and location.ElevatedPoint.verticalAccuracy.uom equal-to 'M' has location.ElevatedPoint.verticalAccuracy value higher-than 0.25 <keyword> It is prohibited that </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with assigned </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> higher-than </keyword> The accuracy of the RunwayCentrelinePoint location.ElevatedPoint.verticalAccuracy shall be not less than 0.25 Found RunwayCentrelinePoint with insufficient vertical accuracy (location.ElevatedPoint.verticalAccuracy) RunwayCentrelinePoint location.ElevatedPoint.verticalAccuracy Standard (ICAO, industry, etc.) Accuracy (vertical) - RunwayCentrelinePoint
AIXM-5.1_RULE-D6D8B Warning ICAO Annex 11 Table A5-2; Volume 2 Table A1-2 It is prohibited that DME with assigned location.ElevatedPoint.verticalAccuracy value and location.ElevatedPoint.verticalAccuracy.uom equal-to 'M' has location.ElevatedPoint.verticalAccuracy value higher-than 30 <keyword> It is prohibited that </keyword><noun_concept> DME </noun_concept><keyword> with assigned </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> higher-than </keyword> The accuracy of the DME location.ElevatedPoint.verticalAccuracy shall be not less than 30 Found DME with insufficient vertical accuracy (location.ElevatedPoint.verticalAccuracy) DME location.ElevatedPoint.verticalAccuracy Standard (ICAO, industry, etc.) Accuracy (vertical) - DME
AIXM-5.1_RULE-D6D8C Warning ICAO Annex 11 Table A5-2; Volume 2 Table A1-2 It is prohibited that GuidanceLine with assigned extent.ElevatedCurve.verticalAccuracy value and extent.ElevatedCurve.verticalAccuracy.uom equal-to 'M' has extent.ElevatedCurve.verticalAccuracy value higher-than 1 <keyword> It is prohibited that </keyword><noun_concept> GuidanceLine </noun_concept><keyword> with assigned </keyword><noun_concept> extent.ElevatedCurve.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> extent.ElevatedCurve.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> extent.ElevatedCurve.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> higher-than </keyword> The accuracy of the GuidanceLine extent.ElevatedCurve.verticalAccuracy shall be not less than 1 Found GuidanceLine with insufficient vertical accuracy (extent.ElevatedCurve.verticalAccuracy) GuidanceLine extent.ElevatedCurve.verticalAccuracy Standard (ICAO, industry, etc.) Accuracy (vertical) - GuidanceLine
AIXM-5.1_RULE-D6D8D Warning Warning ICAO Annex 11 Table A5-2; Volume 2 Table A1-2 It is prohibited that DME with assigned location.ElevatedPoint.verticalAccuracy value and location.ElevatedPoint.verticalAccuracy.uom equal-to 'FT' has location.ElevatedPoint.verticalAccuracy value higher-than 100 <keyword> It is prohibited that </keyword><noun_concept> DME </noun_concept><keyword> with assigned </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> higher-than </keyword> The accuracy of the DME location.ElevatedPoint.verticalAccuracy shall be not less than 100 Found DME with insufficient vertical accuracy (location.ElevatedPoint.verticalAccuracy) DME location.ElevatedPoint.verticalAccuracy Standard (ICAO, industry, etc.) Accuracy (vertical) - DME
AIXM-5.1_RULE-D6D8E Warning ICAO Annex 11 Table A5-2; Volume 2 Table A1-2 It is prohibited that TouchDownLiftOff with assigned aimingPoint.ElevatedPoint.verticalAccuracy value and aimingPoint.ElevatedPoint.verticalAccuracy.uom equal-to 'M' has aimingPoint.ElevatedPoint.verticalAccuracy value higher-than 0.5 <keyword> It is prohibited that </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with assigned </keyword><noun_concept> aimingPoint.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> aimingPoint.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> aimingPoint.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value </keyword><keyword> higher-than </keyword> The accuracy of the TouchDownLiftOff aimingPoint.ElevatedPoint.verticalAccuracy shall be not less than 0.5 Found TouchDownLiftOff with insufficient vertical accuracy (aimingPoint.ElevatedPoint.verticalAccuracy) TouchDownLiftOff aimingPoint.ElevatedPoint.verticalAccuracy Standard (ICAO, industry, etc.) Accuracy (vertical) - TouchDownLiftOff
AIXM-5.1_RULE-26161 ICAO Annex 15 Table A7-5 It is prohibited that a RunwayCentrelinePoint with role equal-to 'THR' and with assigned navaidEquipment.NavaidEquipment specialisation Elevation value has navaidEquipment.NavaidEquipmentDistance.distance.uom not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'THR' </name><keyword> and with assigned </keyword><noun_concept> navaidEquipment.NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> navaidEquipment.NavaidEquipmentDistance.distance.uom </noun_concept><keyword> not equal-to </keyword><name> ('FT','M') </name> The following distances shall be published with 1m or 1ft resolution: ILS localizer antenna-runway end / ILS glide slope antenna-threshold / ILS marker-threshold / ILS DME antenna-threshold / MLS azimuth antenna-runway end / MLS elevation antenna-threshold / MLS DME/P antenna-threshold. The following distances shall be published with 1m or 1ft resolution: ILS localizer antenna-runway end / ILS glide slope antenna-threshold / ILS marker-threshold / ILS DME antenna-threshold / MLS azimuth antenna-runway end / MLS elevation antenna-threshold / MLS DME/P antenna-threshold. Elevation distance set of snapshots Standard (ICAO, industry, etc.) Resolution (distance) - Navaid and runway threshold or runway end
AIXM-5.1_RULE-26162 ICAO Annex 15 Table A7-5 It is prohibited that a RunwayCentrelinePoint with role equal-to 'END' and with assigned navaidEquipment.NavaidEquipment specialisation Localizer value has navaidEquipment.NavaidEquipmentDistance.distance.uom not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'END' </name><keyword> and with assigned </keyword><noun_concept> navaidEquipment.NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> navaidEquipment.NavaidEquipmentDistance.distance.uom </noun_concept><keyword> not equal-to </keyword><name> ('FT','M') </name> The following distances shall be published with 1m or 1ft resolution: ILS localizer antenna-runway end / ILS glide slope antenna-threshold / ILS marker-threshold / ILS DME antenna-threshold / MLS azimuth antenna-runway end / MLS elevation antenna-threshold / MLS DME/P antenna-threshold. The following distances shall be published with 1m or 1ft resolution: ILS localizer antenna-runway end / ILS glide slope antenna-threshold / ILS marker-threshold / ILS DME antenna-threshold / MLS azimuth antenna-runway end / MLS elevation antenna-threshold / MLS DME/P antenna-threshold. Localizer distance set of snapshots Standard (ICAO, industry, etc.) Resolution (distance) - Navaid and runway threshold or runway end
AIXM-5.1_RULE-26163 ICAO Annex 15 Table A7-5 It is prohibited that a RunwayCentrelinePoint with role equal-to 'THR' and with assigned navaidEquipment.NavaidEquipment specialisation Glidepath value has navaidEquipment.NavaidEquipmentDistance.distance.uom not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'THR' </name><keyword> and with assigned </keyword><noun_concept> navaidEquipment.NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> navaidEquipment.NavaidEquipmentDistance.distance.uom </noun_concept><keyword> not equal-to </keyword><name> ('FT','M') </name> The following distances shall be published with 1m or 1ft resolution: ILS localizer antenna-runway end / ILS glide slope antenna-threshold / ILS marker-threshold / ILS DME antenna-threshold / MLS azimuth antenna-runway end / MLS elevation antenna-threshold / MLS DME/P antenna-threshold. The following distances shall be published with 1m or 1ft resolution: ILS localizer antenna-runway end / ILS glide slope antenna-threshold / ILS marker-threshold / ILS DME antenna-threshold / MLS azimuth antenna-runway end / MLS elevation antenna-threshold / MLS DME/P antenna-threshold. Glidepath distance set of snapshots Standard (ICAO, industry, etc.) Resolution (distance) - Navaid and runway threshold or runway end
AIXM-5.1_RULE-26164 ICAO Annex 15 Table A7-5 It is prohibited that a RunwayCentrelinePoint with role equal-to 'END' and with assigned navaidEquipment.NavaidEquipment specialisation Azimuth value has navaidEquipment.NavaidEquipmentDistance.distance.uom not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'END' </name><keyword> and with assigned </keyword><noun_concept> navaidEquipment.NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> navaidEquipment.NavaidEquipmentDistance.distance.uom </noun_concept><keyword> not equal-to </keyword><name> ('FT','M') </name> The following distances shall be published with 1m or 1ft resolution: ILS localizer antenna-runway end / ILS glide slope antenna-threshold / ILS marker-threshold / ILS DME antenna-threshold / MLS azimuth antenna-runway end / MLS elevation antenna-threshold / MLS DME/P antenna-threshold. The following distances shall be published with 1m or 1ft resolution: ILS localizer antenna-runway end / ILS glide slope antenna-threshold / ILS marker-threshold / ILS DME antenna-threshold / MLS azimuth antenna-runway end / MLS elevation antenna-threshold / MLS DME/P antenna-threshold. Azimuth distance set of snapshots Standard (ICAO, industry, etc.) Resolution (distance) - Navaid and runway threshold or runway end
AIXM-5.1_RULE-1A8511 Error AIXM Model It is obligatory that each AeronauticalGroundLight with assigned structureBeacon value has structureBeacon value resolved-into exactly one markingPositionOf VerticalStructure <keyword> It is obligatory that each </keyword><noun_concept> AeronauticalGroundLight </noun_concept><keyword> with assigned </keyword><noun_concept> structureBeacon </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> structureBeacon </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> markingPositionOf </verb_concept><noun_concept> VerticalStructure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AeronauticalGroundLight structureBeacon set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8512 Error Error AIXM Model It is obligatory that each AeronauticalGroundLight with assigned aerodromeBeacon value has aerodromeBeacon value resolved-into exactly one markingTheSiteOf AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AeronauticalGroundLight </noun_concept><keyword> with assigned </keyword><noun_concept> aerodromeBeacon </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> aerodromeBeacon </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> markingTheSiteOf </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AeronauticalGroundLight aerodromeBeacon set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8513 Error AIXM Model It is obligatory that each AircraftStand with assigned apronLocation value has apronLocation value resolved-into exactly one isLocatedOn ApronElement <keyword> It is obligatory that each </keyword><noun_concept> AircraftStand </noun_concept><keyword> with assigned </keyword><noun_concept> apronLocation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> apronLocation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedOn </verb_concept><noun_concept> ApronElement </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AircraftStand apronLocation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8514 Error Error AIXM Model It is obligatory that each AirportHeliport with assigned responsibleOrganisation.AirportHeliportResponsibilityOrganisation.theOrganisationAuthority value has responsibleOrganisation.AirportHeliportResponsibilityOrganisation.theOrganisationAuthority value resolved-into exactly one isUnderResponsibilityOf OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> responsibleOrganisation.AirportHeliportResponsibilityOrganisation.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> responsibleOrganisation.AirportHeliportResponsibilityOrganisation.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUnderResponsibilityOf </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirportHeliport responsibleOrganisation.AirportHeliportResponsibilityOrganisation.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8516 Error AIXM Model It is obligatory that each AirportHeliportCollocation with assigned hostAirport value has hostAirport value resolved-into exactly one isHostedBy AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AirportHeliportCollocation </noun_concept><keyword> with assigned </keyword><noun_concept> hostAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> hostAirport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isHostedBy </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirportHeliportCollocation hostAirport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8517 Error AIXM Model It is obligatory that each AirportHeliportCollocation with assigned dependentAirport value has dependentAirport value resolved-into exactly one hosts AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AirportHeliportCollocation </noun_concept><keyword> with assigned </keyword><noun_concept> dependentAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> dependentAirport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hosts </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirportHeliportCollocation dependentAirport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8518 Error AIXM Model It is obligatory that each AirportHotSpot with assigned affectedAirport value has affectedAirport value resolved-into exactly one isLocatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AirportHotSpot </noun_concept><keyword> with assigned </keyword><noun_concept> affectedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> affectedAirport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirportHotSpot affectedAirport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8519 Error AIXM Model It is obligatory that each Airspace with assigned protectedRoute value has protectedRoute value resolved-into exactly one protectsRoute Route <keyword> It is obligatory that each </keyword><noun_concept> Airspace </noun_concept><keyword> with assigned </keyword><noun_concept> protectedRoute </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> protectedRoute </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> protectsRoute </verb_concept><noun_concept> Route </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Airspace protectedRoute set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A851A Error AIXM Model It is obligatory that each AirspaceLayer with assigned discreteLevelSeries value has discreteLevelSeries value resolved-into exactly one isRestrictedTo StandardLevelColumn <keyword> It is obligatory that each </keyword><noun_concept> AirspaceLayer </noun_concept><keyword> with assigned </keyword><noun_concept> discreteLevelSeries </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> discreteLevelSeries </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isRestrictedTo </verb_concept><noun_concept> StandardLevelColumn </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirspaceLayer discreteLevelSeries set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A851B Error AIXM Model It is obligatory that each AirTrafficManagementService with assigned clientAirspace value has clientAirspace value resolved-into exactly one manages Airspace <keyword> It is obligatory that each </keyword><noun_concept> AirTrafficManagementService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> manages </verb_concept><noun_concept> Airspace </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirTrafficManagementService clientAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A851C Error AIXM Model It is obligatory that each AngleIndication with assigned fix value has fix value resolved-into exactly one locates DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> AngleIndication </noun_concept><keyword> with assigned </keyword><noun_concept> fix </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> fix </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> locates </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AngleIndication fix set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A851D Error AIXM Model It is obligatory that each AngleIndication with assigned pointChoice.SignificantPoint.fixDesignatedPoint value has pointChoice.SignificantPoint.fixDesignatedPoint value resolved-into exactly one uses DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> AngleIndication </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AngleIndication pointChoice.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A851E Error AIXM Model It is obligatory that each AngleIndication with assigned pointChoice.SignificantPoint.navaidSystem value has pointChoice.SignificantPoint.navaidSystem value resolved-into exactly one uses Navaid <keyword> It is obligatory that each </keyword><noun_concept> AngleIndication </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AngleIndication pointChoice.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A851F Error AIXM Model It is obligatory that each ApproachLightingSystem with assigned servedRunwayDirection value has servedRunwayDirection value resolved-into exactly one serves RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> ApproachLightingSystem </noun_concept><keyword> with assigned </keyword><noun_concept> servedRunwayDirection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> servedRunwayDirection </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> serves </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ApproachLightingSystem servedRunwayDirection set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8520 Error AIXM Model It is obligatory that each Apron with assigned associatedAirportHeliport value has associatedAirportHeliport value resolved-into exactly one isSituatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> Apron </noun_concept><keyword> with assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedAirportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Apron associatedAirportHeliport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8521 Error AIXM Model It is obligatory that each ApronElement with assigned supplyService value has supplyService value resolved-into exactly one isProvidedWith AirportSuppliesService <keyword> It is obligatory that each </keyword><noun_concept> ApronElement </noun_concept><keyword> with assigned </keyword><noun_concept> supplyService </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> supplyService </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedWith </verb_concept><noun_concept> AirportSuppliesService </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ApronElement supplyService set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8522 Error AIXM Model It is obligatory that each ApronElement with assigned associatedApron value has associatedApron value resolved-into exactly one describesPartOf Apron <keyword> It is obligatory that each </keyword><noun_concept> ApronElement </noun_concept><keyword> with assigned </keyword><noun_concept> associatedApron </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedApron </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> describesPartOf </verb_concept><noun_concept> Apron </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ApronElement associatedApron set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8523 Error AIXM Model It is obligatory that each ArrestingGear with assigned runwayDirection value has runwayDirection value resolved-into exactly one isUsedOn RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> ArrestingGear </noun_concept><keyword> with assigned </keyword><noun_concept> runwayDirection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> runwayDirection </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUsedOn </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ArrestingGear runwayDirection set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8524 Error AIXM Model It is obligatory that each AuthorityForAirspace with assigned assignedAirspace value has assignedAirspace value resolved-into exactly one isResponsibleFor Airspace <keyword> It is obligatory that each </keyword><noun_concept> AuthorityForAirspace </noun_concept><keyword> with assigned </keyword><noun_concept> assignedAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> assignedAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isResponsibleFor </verb_concept><noun_concept> Airspace </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AuthorityForAirspace assignedAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8525 Error AIXM Model It is obligatory that each AuthorityForAirspace with assigned responsibleOrganisation value has responsibleOrganisation value resolved-into exactly one is OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> AuthorityForAirspace </noun_concept><keyword> with assigned </keyword><noun_concept> responsibleOrganisation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> responsibleOrganisation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AuthorityForAirspace responsibleOrganisation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8526 Error AIXM Model It is obligatory that each ChangeOverPoint with assigned location.SignificantPoint.navaidSystem value has location.SignificantPoint.navaidSystem value resolved-into exactly one isLocatedAt Navaid <keyword> It is obligatory that each </keyword><noun_concept> ChangeOverPoint </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ChangeOverPoint location.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8527 Error AIXM Model It is obligatory that each ChangeOverPoint with assigned location.SignificantPoint.runwayPoint value has location.SignificantPoint.runwayPoint value resolved-into exactly one isLocatedAt RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> ChangeOverPoint </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ChangeOverPoint location.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8528 Error AIXM Model It is obligatory that each ChangeOverPoint with assigned location.SignificantPoint.airportReferencePoint value has location.SignificantPoint.airportReferencePoint value resolved-into exactly one isLocatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> ChangeOverPoint </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ChangeOverPoint location.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8529 Error AIXM Model It is obligatory that each ChangeOverPoint with assigned location.SignificantPoint.aimingPoint value has location.SignificantPoint.aimingPoint value resolved-into exactly one isLocatedAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> ChangeOverPoint </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ChangeOverPoint location.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A852A Error AIXM Model It is obligatory that each ChangeOverPoint with assigned location.SignificantPoint.fixDesignatedPoint value has location.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isLocatedAt DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> ChangeOverPoint </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ChangeOverPoint location.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A852B Error AIXM Model It is obligatory that each CirclingArea with assigned approach value has approach value resolved-into exactly one isUsedOn InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> CirclingArea </noun_concept><keyword> with assigned </keyword><noun_concept> approach </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approach </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUsedOn </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. CirclingArea approach set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A852C Error AIXM Model It is obligatory that each DesignatedPoint with assigned airportHeliport value has airportHeliport value resolved-into exactly one isAssociatedWith AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> DesignatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAssociatedWith </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DesignatedPoint airportHeliport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A852D Error AIXM Model It is obligatory that each DesignatedPoint with assigned aimingPoint value has aimingPoint value resolved-into exactly one isAtCentreOf TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> DesignatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAtCentreOf </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DesignatedPoint aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A852E Error AIXM Model It is obligatory that each DesignatedPoint with assigned runwayPoint value has runwayPoint value resolved-into exactly one isSituatedAt RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> DesignatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DesignatedPoint runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A852F Error AIXM Model It is obligatory that each DistanceIndication with assigned fix value has fix value resolved-into exactly one locates DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> DistanceIndication </noun_concept><keyword> with assigned </keyword><noun_concept> fix </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> fix </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> locates </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DistanceIndication fix set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8530 Error AIXM Model It is obligatory that each DistanceIndication with assigned pointChoice.SignificantPoint.navaidSystem value has pointChoice.SignificantPoint.navaidSystem value resolved-into exactly one uses Navaid <keyword> It is obligatory that each </keyword><noun_concept> DistanceIndication </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DistanceIndication pointChoice.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8531 Error AIXM Model It is obligatory that each DistanceIndication with assigned pointChoice.SignificantPoint.fixDesignatedPoint value has pointChoice.SignificantPoint.fixDesignatedPoint value resolved-into exactly one uses DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> DistanceIndication </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DistanceIndication pointChoice.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8532 Error AIXM Model It is obligatory that each GuidanceLine with assigned connectedApron value has connectedApron value resolved-into exactly one connects Apron <keyword> It is obligatory that each </keyword><noun_concept> GuidanceLine </noun_concept><keyword> with assigned </keyword><noun_concept> connectedApron </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> connectedApron </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> connects </verb_concept><noun_concept> Apron </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. GuidanceLine connectedApron set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8533 Error AIXM Model It is obligatory that each GuidanceLine with assigned connectedTouchDownLiftOff value has connectedTouchDownLiftOff value resolved-into exactly one connects TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> GuidanceLine </noun_concept><keyword> with assigned </keyword><noun_concept> connectedTouchDownLiftOff </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> connectedTouchDownLiftOff </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> connects </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. GuidanceLine connectedTouchDownLiftOff set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8534 Error AIXM Model It is obligatory that each GuidanceLine with assigned connectedRunwayCentrelinePoint value has connectedRunwayCentrelinePoint value resolved-into exactly one connectedRunwayCentrelinePoint RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> GuidanceLine </noun_concept><keyword> with assigned </keyword><noun_concept> connectedRunwayCentrelinePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> connectedRunwayCentrelinePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> connectedRunwayCentrelinePoint </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. GuidanceLine connectedRunwayCentrelinePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8535 Error AIXM Model It is obligatory that each GuidanceLine with assigned connectedTaxiway value has connectedTaxiway value resolved-into exactly one connects Taxiway <keyword> It is obligatory that each </keyword><noun_concept> GuidanceLine </noun_concept><keyword> with assigned </keyword><noun_concept> connectedTaxiway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> connectedTaxiway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> connects </verb_concept><noun_concept> Taxiway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. GuidanceLine connectedTaxiway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8536 Error AIXM Model It is obligatory that each GuidanceLine with assigned connectedStand value has connectedStand value resolved-into exactly one connects AircraftStand <keyword> It is obligatory that each </keyword><noun_concept> GuidanceLine </noun_concept><keyword> with assigned </keyword><noun_concept> connectedStand </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> connectedStand </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> connects </verb_concept><noun_concept> AircraftStand </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. GuidanceLine connectedStand set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8537 Error AIXM Model It is obligatory that each GuidanceLineLightSystem with assigned lightedGuidanceLine value has lightedGuidanceLine value resolved-into exactly one isProvidedFor GuidanceLine <keyword> It is obligatory that each </keyword><noun_concept> GuidanceLineLightSystem </noun_concept><keyword> with assigned </keyword><noun_concept> lightedGuidanceLine </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> lightedGuidanceLine </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedFor </verb_concept><noun_concept> GuidanceLine </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. GuidanceLineLightSystem lightedGuidanceLine set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8538 Error AIXM Model It is obligatory that each HoldingAssessment with assigned assessedHoldingPattern value has assessedHoldingPattern value resolved-into exactly one determines HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with assigned </keyword><noun_concept> assessedHoldingPattern </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> assessedHoldingPattern </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> determines </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. HoldingAssessment assessedHoldingPattern set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8539 Error AIXM Model It is obligatory that each InformationService with assigned clientHolding value has clientHolding value resolved-into exactly one concerns HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> InformationService </noun_concept><keyword> with assigned </keyword><noun_concept> clientHolding </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientHolding </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> concerns </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. InformationService clientHolding set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A853A Error AIXM Model It is obligatory that each InformationService with assigned clientAirport value has clientAirport value resolved-into exactly one concerns AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> InformationService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAirport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> concerns </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. InformationService clientAirport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A853B Error AIXM Model It is obligatory that each InformationService with assigned clientAirspace value has clientAirspace value resolved-into exactly one concerns Airspace <keyword> It is obligatory that each </keyword><noun_concept> InformationService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> concerns </verb_concept><noun_concept> Airspace </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. InformationService clientAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A853C Error AIXM Model It is obligatory that each InformationService with assigned navaidBroadcast value has navaidBroadcast value resolved-into exactly one broadcastsOn VOR <keyword> It is obligatory that each </keyword><noun_concept> InformationService </noun_concept><keyword> with assigned </keyword><noun_concept> navaidBroadcast </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> navaidBroadcast </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> broadcastsOn </verb_concept><noun_concept> VOR </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. InformationService navaidBroadcast set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A853D Error AIXM Model It is obligatory that each LandingTakeoffAreaCollection with assigned runway value has runway value resolved-into exactly one isLocatedAt RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> LandingTakeoffAreaCollection </noun_concept><keyword> with assigned </keyword><noun_concept> runway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> runway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. LandingTakeoffAreaCollection runway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A853E Error AIXM Model It is obligatory that each LandingTakeoffAreaCollection with assigned TLOF value has TLOF value resolved-into exactly one isLocatedAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> LandingTakeoffAreaCollection </noun_concept><keyword> with assigned </keyword><noun_concept> TLOF </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> TLOF </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. LandingTakeoffAreaCollection TLOF set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A853F Error AIXM Model It is obligatory that each Navaid with assigned servedAirport value has servedAirport value resolved-into exactly one usedForHomingAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> servedAirport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> usedForHomingAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Navaid servedAirport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8540 Error AIXM Model It is obligatory that each Navaid with assigned touchDownLiftOff value has touchDownLiftOff value resolved-into exactly one isInstalledAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> touchDownLiftOff </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> touchDownLiftOff </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isInstalledAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Navaid touchDownLiftOff set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8541 Error AIXM Model It is obligatory that each Navaid with assigned runwayDirection value has runwayDirection value resolved-into exactly one isInstalledAt RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> runwayDirection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> runwayDirection </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isInstalledAt </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Navaid runwayDirection set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8542 Error AIXM Model It is obligatory that each NavigationArea with assigned departure value has departure value resolved-into exactly one protects StandardInstrumentDeparture <keyword> It is obligatory that each </keyword><noun_concept> NavigationArea </noun_concept><keyword> with assigned </keyword><noun_concept> departure </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> departure </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> protects </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. NavigationArea departure set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8543 Error AIXM Model It is obligatory that each NavigationArea with assigned centrePoint.SignificantPoint.navaidSystem value has centrePoint.SignificantPoint.navaidSystem value resolved-into exactly one isBasedOn Navaid <keyword> It is obligatory that each </keyword><noun_concept> NavigationArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. NavigationArea centrePoint.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8544 Error AIXM Model It is obligatory that each NavigationArea with assigned centrePoint.SignificantPoint.runwayPoint value has centrePoint.SignificantPoint.runwayPoint value resolved-into exactly one isBasedOn RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> NavigationArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. NavigationArea centrePoint.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8545 Error AIXM Model It is obligatory that each NavigationArea with assigned centrePoint.SignificantPoint.airportReferencePoint value has centrePoint.SignificantPoint.airportReferencePoint value resolved-into exactly one isBasedOn AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> NavigationArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. NavigationArea centrePoint.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8546 Error AIXM Model It is obligatory that each NavigationArea with assigned centrePoint.SignificantPoint.aimingPoint value has centrePoint.SignificantPoint.aimingPoint value resolved-into exactly one isBasedOn TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> NavigationArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. NavigationArea centrePoint.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8547 Error AIXM Model It is obligatory that each NavigationArea with assigned centrePoint.SignificantPoint.fixDesignatedPoint value has centrePoint.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isBasedOn DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> NavigationArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. NavigationArea centrePoint.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8548 Error AIXM Model It is obligatory that each ObstacleArea with assigned obstacle value has obstacle value resolved-into exactly one hasObstacle VerticalStructure <keyword> It is obligatory that each </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with assigned </keyword><noun_concept> obstacle </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> obstacle </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ObstacleArea obstacle set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8549 Error AIXM Model It is obligatory that each ObstacleArea with assigned reference.ObstacleAreaOrigin.ownerAirport value has reference.ObstacleAreaOrigin.ownerAirport value resolved-into exactly one isDefinedFor AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with assigned </keyword><noun_concept> reference.ObstacleAreaOrigin.ownerAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> reference.ObstacleAreaOrigin.ownerAirport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isDefinedFor </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ObstacleArea reference.ObstacleAreaOrigin.ownerAirport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A854A Error AIXM Model It is obligatory that each ObstacleArea with assigned reference.ObstacleAreaOrigin.ownerRunway value has reference.ObstacleAreaOrigin.ownerRunway value resolved-into exactly one isDefinedFor RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with assigned </keyword><noun_concept> reference.ObstacleAreaOrigin.ownerRunway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> reference.ObstacleAreaOrigin.ownerRunway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isDefinedFor </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ObstacleArea reference.ObstacleAreaOrigin.ownerRunway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A854B Error AIXM Model It is obligatory that each ObstacleArea with assigned reference.ObstacleAreaOrigin.ownerOrganisation value has reference.ObstacleAreaOrigin.ownerOrganisation value resolved-into exactly one isDefinedFor OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with assigned </keyword><noun_concept> reference.ObstacleAreaOrigin.ownerOrganisation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> reference.ObstacleAreaOrigin.ownerOrganisation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isDefinedFor </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ObstacleArea reference.ObstacleAreaOrigin.ownerOrganisation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A854C Error AIXM Model It is obligatory that each Obstruction with assigned verticalStructureObstruction value has verticalStructureObstruction value resolved-into exactly one isRepresentedBy VerticalStructure <keyword> It is obligatory that each </keyword><noun_concept> Obstruction </noun_concept><keyword> with assigned </keyword><noun_concept> verticalStructureObstruction </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> verticalStructureObstruction </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isRepresentedBy </verb_concept><noun_concept> VerticalStructure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Obstruction verticalStructureObstruction set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A854E Error AIXM Model It is obligatory that each PointReference with assigned facilityDistance value has facilityDistance value resolved-into exactly one isBasedOnDistance DistanceIndication <keyword> It is obligatory that each </keyword><noun_concept> PointReference </noun_concept><keyword> with assigned </keyword><noun_concept> facilityDistance </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> facilityDistance </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOnDistance </verb_concept><noun_concept> DistanceIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. PointReference facilityDistance set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A854F Error AIXM Model It is obligatory that each PointReference with assigned facilityAngle.AngleUse.theAngleIndication value has facilityAngle.AngleUse.theAngleIndication value resolved-into exactly one isBasedOnAngle AngleIndication <keyword> It is obligatory that each </keyword><noun_concept> PointReference </noun_concept><keyword> with assigned </keyword><noun_concept> facilityAngle.AngleUse.theAngleIndication </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> facilityAngle.AngleUse.theAngleIndication </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOnAngle </verb_concept><noun_concept> AngleIndication </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. PointReference facilityAngle.AngleUse.theAngleIndication set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8550 Error AIXM Model It is obligatory that each ProcedureDME with assigned DME value has DME value resolved-into exactly one uses DME <keyword> It is obligatory that each </keyword><noun_concept> ProcedureDME </noun_concept><keyword> with assigned </keyword><noun_concept> DME </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> DME </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> DME </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ProcedureDME DME set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8552 Error AIXM Model It is obligatory that each ProcedureTransition with assigned transitionLeg value has transitionLeg value resolved-into exactly one isComposedOf SegmentLeg <keyword> It is obligatory that each </keyword><noun_concept> ProcedureTransition </noun_concept><keyword> with assigned </keyword><noun_concept> transitionLeg </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> transitionLeg </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> SegmentLeg </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ProcedureTransition transitionLeg set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8554 Error AIXM Model It is obligatory that each RadioFrequencyArea with assigned equipment.EquipmentChoice.frequency value has equipment.EquipmentChoice.frequency value resolved-into exactly one limits RadioCommunicationChannel <keyword> It is obligatory that each </keyword><noun_concept> RadioFrequencyArea </noun_concept><keyword> with assigned </keyword><noun_concept> equipment.EquipmentChoice.frequency </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> equipment.EquipmentChoice.frequency </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> limits </verb_concept><noun_concept> RadioCommunicationChannel </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RadioFrequencyArea equipment.EquipmentChoice.frequency set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8555 Error AIXM Model It is obligatory that each RadioFrequencyArea with assigned equipment.EquipmentChoice.specialNavigationStation value has equipment.EquipmentChoice.specialNavigationStation value resolved-into exactly one limits SpecialNavigationStation <keyword> It is obligatory that each </keyword><noun_concept> RadioFrequencyArea </noun_concept><keyword> with assigned </keyword><noun_concept> equipment.EquipmentChoice.specialNavigationStation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> equipment.EquipmentChoice.specialNavigationStation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> limits </verb_concept><noun_concept> SpecialNavigationStation </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RadioFrequencyArea equipment.EquipmentChoice.specialNavigationStation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8556 Error AIXM Model It is obligatory that each Route with assigned userOrganisation value has userOrganisation value resolved-into exactly one isUsedBy OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> Route </noun_concept><keyword> with assigned </keyword><noun_concept> userOrganisation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> userOrganisation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUsedBy </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Route userOrganisation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8557 Error AIXM Model It is obligatory that each RouteDME with assigned referencedDME value has referencedDME value resolved-into exactly one uses DME <keyword> It is obligatory that each </keyword><noun_concept> RouteDME </noun_concept><keyword> with assigned </keyword><noun_concept> referencedDME </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> referencedDME </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> DME </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RouteDME referencedDME set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8558 Error AIXM Model It is obligatory that each RoutePortion with assigned referencedRoute value has referencedRoute value resolved-into exactly one isPartOf Route <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> referencedRoute </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> referencedRoute </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isPartOf </verb_concept><noun_concept> Route </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion referencedRoute set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A855B Error AIXM Model It is obligatory that each RoutePortion with assigned end.SignificantPoint.aimingPoint value has end.SignificantPoint.aimingPoint value resolved-into exactly one endsAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion end.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A855C Error AIXM Model It is obligatory that each RoutePortion with assigned end.SignificantPoint.runwayPoint value has end.SignificantPoint.runwayPoint value resolved-into exactly one endsAt RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion end.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A855D Error AIXM Model It is obligatory that each RoutePortion with assigned end.SignificantPoint.airportReferencePoint value has end.SignificantPoint.airportReferencePoint value resolved-into exactly one endsAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion end.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8560 Error AIXM Model It is obligatory that each RoutePortion with assigned start.SignificantPoint.aimingPoint value has start.SignificantPoint.aimingPoint value resolved-into exactly one startsAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion start.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8561 Error AIXM Model It is obligatory that each RoutePortion with assigned start.SignificantPoint.runwayPoint value has start.SignificantPoint.runwayPoint value resolved-into exactly one startsAt RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion start.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8562 Error AIXM Model It is obligatory that each RoutePortion with assigned start.SignificantPoint.airportReferencePoint value has start.SignificantPoint.airportReferencePoint value resolved-into exactly one startsAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion start.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8565 Error AIXM Model It is obligatory that each RoutePortion with assigned intermediatePoint.SignificantPoint.aimingPoint value has intermediatePoint.SignificantPoint.aimingPoint value resolved-into exactly one passesThrough TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> intermediatePoint.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> intermediatePoint.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> passesThrough </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion intermediatePoint.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8566 Error AIXM Model It is obligatory that each RoutePortion with assigned intermediatePoint.SignificantPoint.runwayPoint value has intermediatePoint.SignificantPoint.runwayPoint value resolved-into exactly one passesThrough RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> intermediatePoint.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> intermediatePoint.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> passesThrough </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion intermediatePoint.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8567 Error AIXM Model It is obligatory that each RoutePortion with assigned intermediatePoint.SignificantPoint.airportReferencePoint value has intermediatePoint.SignificantPoint.airportReferencePoint value resolved-into exactly one passesThrough AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> intermediatePoint.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> intermediatePoint.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> passesThrough </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion intermediatePoint.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8568 Error Error AIXM Model It is obligatory that each RouteSegment with assigned routeFormed value has routeFormed value resolved-into exactly one routeFormed Route <keyword> It is obligatory that each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> routeFormed </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> routeFormed </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> routeFormed </verb_concept><noun_concept> Route </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RouteSegment routeFormed set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8569 Error AIXM Model It is obligatory that each RulesProcedures with assigned affectedLocation value has affectedLocation value resolved-into exactly one appliesAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> RulesProcedures </noun_concept><keyword> with assigned </keyword><noun_concept> affectedLocation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> affectedLocation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RulesProcedures affectedLocation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A856A Error AIXM Model It is obligatory that each RulesProcedures with assigned affectedArea value has affectedArea value resolved-into exactly one appliesWithin Airspace <keyword> It is obligatory that each </keyword><noun_concept> RulesProcedures </noun_concept><keyword> with assigned </keyword><noun_concept> affectedArea </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> affectedArea </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> appliesWithin </verb_concept><noun_concept> Airspace </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RulesProcedures affectedArea set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A856B Error AIXM Model It is obligatory that each Runway with assigned associatedAirportHeliport value has associatedAirportHeliport value resolved-into exactly one isSituatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedAirportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Runway associatedAirportHeliport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A856C Error AIXM Model It is obligatory that each RunwayCentrelinePoint with assigned onRunway value has onRunway value resolved-into exactly one isLocatedOn RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with assigned </keyword><noun_concept> onRunway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> onRunway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedOn </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayCentrelinePoint onRunway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A856D Error AIXM Model It is obligatory that each RunwayDirection with assigned usedRunway value has usedRunway value resolved-into exactly one uses Runway <keyword> It is obligatory that each </keyword><noun_concept> RunwayDirection </noun_concept><keyword> with assigned </keyword><noun_concept> usedRunway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> usedRunway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> Runway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayDirection usedRunway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A856E Error AIXM Model It is obligatory that each RunwayDirection with assigned startingElement value has startingElement value resolved-into exactly one hasStart RunwayElement <keyword> It is obligatory that each </keyword><noun_concept> RunwayDirection </noun_concept><keyword> with assigned </keyword><noun_concept> startingElement </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> startingElement </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hasStart </verb_concept><noun_concept> RunwayElement </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayDirection startingElement set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A856F Error AIXM Model It is obligatory that each RunwayElement with assigned associatedRunway value has associatedRunway value resolved-into exactly one describesPartOf Runway <keyword> It is obligatory that each </keyword><noun_concept> RunwayElement </noun_concept><keyword> with assigned </keyword><noun_concept> associatedRunway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedRunway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> describesPartOf </verb_concept><noun_concept> Runway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayElement associatedRunway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8570 Error AIXM Model It is obligatory that each SafeAltitudeArea with assigned location value has location value resolved-into exactly one isDefinedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> SafeAltitudeArea </noun_concept><keyword> with assigned </keyword><noun_concept> location </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isDefinedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SafeAltitudeArea location set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8571 Error AIXM Model It is obligatory that each SafeAltitudeArea with assigned centrePoint.SignificantPoint.navaidSystem value has centrePoint.SignificantPoint.navaidSystem value resolved-into exactly one isBasedOn Navaid <keyword> It is obligatory that each </keyword><noun_concept> SafeAltitudeArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SafeAltitudeArea centrePoint.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8572 Error AIXM Model It is obligatory that each SafeAltitudeArea with assigned centrePoint.SignificantPoint.runwayPoint value has centrePoint.SignificantPoint.runwayPoint value resolved-into exactly one isBasedOn RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> SafeAltitudeArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SafeAltitudeArea centrePoint.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8573 Error AIXM Model It is obligatory that each SafeAltitudeArea with assigned centrePoint.SignificantPoint.airportReferencePoint value has centrePoint.SignificantPoint.airportReferencePoint value resolved-into exactly one isBasedOn AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> SafeAltitudeArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SafeAltitudeArea centrePoint.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8574 Error AIXM Model It is obligatory that each SafeAltitudeArea with assigned centrePoint.SignificantPoint.aimingPoint value has centrePoint.SignificantPoint.aimingPoint value resolved-into exactly one isBasedOn TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> SafeAltitudeArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SafeAltitudeArea centrePoint.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8575 Error AIXM Model It is obligatory that each SafeAltitudeArea with assigned centrePoint.SignificantPoint.fixDesignatedPoint value has centrePoint.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isBasedOn DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> SafeAltitudeArea </noun_concept><keyword> with assigned </keyword><noun_concept> centrePoint.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> centrePoint.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SafeAltitudeArea centrePoint.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8576 Error AIXM Model It is obligatory that each SearchRescueService with assigned clientAirspace value has clientAirspace value resolved-into exactly one services Airspace <keyword> It is obligatory that each </keyword><noun_concept> SearchRescueService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> services </verb_concept><noun_concept> Airspace </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SearchRescueService clientAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8577 Error Error AIXM Model It is obligatory that each SegmentPoint with assigned pointChoice.SignificantPoint.navaidSystem value has pointChoice.SignificantPoint.navaidSystem value resolved-into exactly one isLocatedAt Navaid <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SegmentPoint pointChoice.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8578 Error Error AIXM Model It is obligatory that each SegmentPoint with assigned pointChoice.SignificantPoint.fixDesignatedPoint value has pointChoice.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isLocatedAt DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> SegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SegmentPoint pointChoice.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8579 Error AIXM Model It is obligatory that each SignificantPointInAirspace with assigned containingAirspace value has containingAirspace value resolved-into exactly one isSituatedWithin Airspace <keyword> It is obligatory that each </keyword><noun_concept> SignificantPointInAirspace </noun_concept><keyword> with assigned </keyword><noun_concept> containingAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> containingAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedWithin </verb_concept><noun_concept> Airspace </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SignificantPointInAirspace containingAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A857A Error AIXM Model It is obligatory that each SignificantPointInAirspace with assigned location.SignificantPoint.fixDesignatedPoint value has location.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isLocatedAt DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> SignificantPointInAirspace </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SignificantPointInAirspace location.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A857B Error AIXM Model It is obligatory that each SignificantPointInAirspace with assigned location.SignificantPoint.airportReferencePoint value has location.SignificantPoint.airportReferencePoint value resolved-into exactly one isLocatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> SignificantPointInAirspace </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SignificantPointInAirspace location.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A857C Error AIXM Model It is obligatory that each SignificantPointInAirspace with assigned location.SignificantPoint.navaidSystem value has location.SignificantPoint.navaidSystem value resolved-into exactly one isLocatedAt Navaid <keyword> It is obligatory that each </keyword><noun_concept> SignificantPointInAirspace </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SignificantPointInAirspace location.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A857D Error AIXM Model It is obligatory that each SignificantPointInAirspace with assigned location.SignificantPoint.runwayPoint value has location.SignificantPoint.runwayPoint value resolved-into exactly one isLocatedAt RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> SignificantPointInAirspace </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SignificantPointInAirspace location.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A857E Error AIXM Model It is obligatory that each SignificantPointInAirspace with assigned location.SignificantPoint.aimingPoint value has location.SignificantPoint.aimingPoint value resolved-into exactly one isLocatedAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> SignificantPointInAirspace </noun_concept><keyword> with assigned </keyword><noun_concept> location.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SignificantPointInAirspace location.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A857F Error AIXM Model It is obligatory that each SpecialDate with assigned authority value has authority value resolved-into exactly one isAssociatedWith OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> SpecialDate </noun_concept><keyword> with assigned </keyword><noun_concept> authority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> authority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAssociatedWith </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SpecialDate authority set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8580 Error AIXM Model It is obligatory that each SpecialNavigationStation with assigned systemChain value has systemChain value resolved-into exactly one systemChain SpecialNavigationSystem <keyword> It is obligatory that each </keyword><noun_concept> SpecialNavigationStation </noun_concept><keyword> with assigned </keyword><noun_concept> systemChain </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> systemChain </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> systemChain </verb_concept><noun_concept> SpecialNavigationSystem </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SpecialNavigationStation systemChain set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8581 Error AIXM Model It is obligatory that each SpecialNavigationStation with assigned responsibleOrganisation.AuthorityForSpecialNavigationStation.theOrganisationAuthority value has responsibleOrganisation.AuthorityForSpecialNavigationStation.theOrganisationAuthority value resolved-into exactly one isMaintainedBy OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> SpecialNavigationStation </noun_concept><keyword> with assigned </keyword><noun_concept> responsibleOrganisation.AuthorityForSpecialNavigationStation.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> responsibleOrganisation.AuthorityForSpecialNavigationStation.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMaintainedBy </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SpecialNavigationStation responsibleOrganisation.AuthorityForSpecialNavigationStation.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8582 Error AIXM Model It is obligatory that each SpecialNavigationSystem with assigned responsibleOrganisation.AuthorityForSpecialNavigationSystem.theOrganisationAuthority value has responsibleOrganisation.AuthorityForSpecialNavigationSystem.theOrganisationAuthority value resolved-into exactly one isMaintainedBy OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> SpecialNavigationSystem </noun_concept><keyword> with assigned </keyword><noun_concept> responsibleOrganisation.AuthorityForSpecialNavigationSystem.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> responsibleOrganisation.AuthorityForSpecialNavigationSystem.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMaintainedBy </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SpecialNavigationSystem responsibleOrganisation.AuthorityForSpecialNavigationSystem.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8583 Error AIXM Model It is obligatory that each StandardLevelColumn with assigned levelTable value has levelTable value resolved-into exactly one belongsTo StandardLevelTable <keyword> It is obligatory that each </keyword><noun_concept> StandardLevelColumn </noun_concept><keyword> with assigned </keyword><noun_concept> levelTable </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> levelTable </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> belongsTo </verb_concept><noun_concept> StandardLevelTable </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. StandardLevelColumn levelTable set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8584 Error AIXM Model It is obligatory that each StandardLevelSector with assigned applicableLevelColumn value has applicableLevelColumn value resolved-into exactly one uses StandardLevelColumn <keyword> It is obligatory that each </keyword><noun_concept> StandardLevelSector </noun_concept><keyword> with assigned </keyword><noun_concept> applicableLevelColumn </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> applicableLevelColumn </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> uses </verb_concept><noun_concept> StandardLevelColumn </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. StandardLevelSector applicableLevelColumn set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8585 Error AIXM Model It is obligatory that each StandardLevelSector with assigned applicableAirspace value has applicableAirspace value resolved-into exactly one isAppliedInto Airspace <keyword> It is obligatory that each </keyword><noun_concept> StandardLevelSector </noun_concept><keyword> with assigned </keyword><noun_concept> applicableAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> applicableAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAppliedInto </verb_concept><noun_concept> Airspace </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. StandardLevelSector applicableAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8586 Error AIXM Model It is obligatory that each SurveyControlPoint with assigned associatedAirportHeliport value has associatedAirportHeliport value resolved-into exactly one isSituatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> SurveyControlPoint </noun_concept><keyword> with assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedAirportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. SurveyControlPoint associatedAirportHeliport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8587 Error AIXM Model It is obligatory that each TaxiHoldingPosition with assigned associatedGuidanceLine value has associatedGuidanceLine value resolved-into exactly one isLocatedAt GuidanceLine <keyword> It is obligatory that each </keyword><noun_concept> TaxiHoldingPosition </noun_concept><keyword> with assigned </keyword><noun_concept> associatedGuidanceLine </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedGuidanceLine </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> GuidanceLine </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TaxiHoldingPosition associatedGuidanceLine set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8588 Error AIXM Model It is obligatory that each TaxiHoldingPosition with assigned protectedRunway value has protectedRunway value resolved-into exactly one preventsEntryOn Runway <keyword> It is obligatory that each </keyword><noun_concept> TaxiHoldingPosition </noun_concept><keyword> with assigned </keyword><noun_concept> protectedRunway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> protectedRunway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> preventsEntryOn </verb_concept><noun_concept> Runway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TaxiHoldingPosition protectedRunway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8589 Error AIXM Model It is obligatory that each TaxiHoldingPositionLightSystem with assigned taxiHolding value has taxiHolding value resolved-into exactly one isProvidedFor TaxiHoldingPosition <keyword> It is obligatory that each </keyword><noun_concept> TaxiHoldingPositionLightSystem </noun_concept><keyword> with assigned </keyword><noun_concept> taxiHolding </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> taxiHolding </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedFor </verb_concept><noun_concept> TaxiHoldingPosition </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TaxiHoldingPositionLightSystem taxiHolding set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A858A Error AIXM Model It is obligatory that each Taxiway with assigned associatedAirportHeliport value has associatedAirportHeliport value resolved-into exactly one isSituatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> Taxiway </noun_concept><keyword> with assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedAirportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Taxiway associatedAirportHeliport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A858B Error AIXM Model It is obligatory that each TaxiwayElement with assigned associatedTaxiway value has associatedTaxiway value resolved-into exactly one describesPartOf Taxiway <keyword> It is obligatory that each </keyword><noun_concept> TaxiwayElement </noun_concept><keyword> with assigned </keyword><noun_concept> associatedTaxiway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedTaxiway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> describesPartOf </verb_concept><noun_concept> Taxiway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TaxiwayElement associatedTaxiway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A858C Error AIXM Model It is obligatory that each TaxiwayMarking with assigned markedElement value has markedElement value resolved-into exactly one isPaintedOn TaxiwayElement <keyword> It is obligatory that each </keyword><noun_concept> TaxiwayMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedElement </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedElement </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isPaintedOn </verb_concept><noun_concept> TaxiwayElement </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TaxiwayMarking markedElement set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A858D Error AIXM Model It is obligatory that each TerminalArrivalArea with assigned approachRNAV value has approachRNAV value resolved-into exactly one isFeederFor InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> TerminalArrivalArea </noun_concept><keyword> with assigned </keyword><noun_concept> approachRNAV </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approachRNAV </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isFeederFor </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TerminalArrivalArea approachRNAV set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A858E Error AIXM Model It is obligatory that each TerminalArrivalArea with assigned IAF.SignificantPoint.fixDesignatedPoint value has IAF.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isUsedForAngle DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> TerminalArrivalArea </noun_concept><keyword> with assigned </keyword><noun_concept> IAF.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> IAF.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUsedForAngle </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TerminalArrivalArea IAF.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A858F Error AIXM Model It is obligatory that each TerminalArrivalArea with assigned IF.SignificantPoint.fixDesignatedPoint value has IF.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isUsedForDistance DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> TerminalArrivalArea </noun_concept><keyword> with assigned </keyword><noun_concept> IF.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> IF.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUsedForDistance </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TerminalArrivalArea IF.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8590 Error AIXM Model It is obligatory that each TouchDownLiftOff with assigned associatedAirportHeliport value has associatedAirportHeliport value resolved-into exactly one isSituatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedAirportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TouchDownLiftOff associatedAirportHeliport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8591 Error AIXM Model It is obligatory that each TouchDownLiftOff with assigned approachTakeOffArea value has approachTakeOffArea value resolved-into exactly one isSituatedOn Runway <keyword> It is obligatory that each </keyword><noun_concept> TouchDownLiftOff </noun_concept><keyword> with assigned </keyword><noun_concept> approachTakeOffArea </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approachTakeOffArea </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedOn </verb_concept><noun_concept> Runway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TouchDownLiftOff approachTakeOffArea set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8592 Error AIXM Model It is obligatory that each Unit with assigned ownerOrganisation value has ownerOrganisation value resolved-into exactly one isSupervisedBy OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> Unit </noun_concept><keyword> with assigned </keyword><noun_concept> ownerOrganisation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> ownerOrganisation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSupervisedBy </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Unit ownerOrganisation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8593 Error AIXM Model It is obligatory that each Unit with assigned airportLocation value has airportLocation value resolved-into exactly one isLocatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> Unit </noun_concept><keyword> with assigned </keyword><noun_concept> airportLocation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportLocation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Unit airportLocation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8594 Error AIXM Model It is obligatory that each Unit with assigned relatedUnit value has relatedUnit value resolved-into exactly one dependsOn Unit <keyword> It is obligatory that each </keyword><noun_concept> Unit </noun_concept><keyword> with assigned </keyword><noun_concept> relatedUnit </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> relatedUnit </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> dependsOn </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Unit relatedUnit set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8595 Error AIXM Model It is obligatory that each VerticalStructure with assigned supportedService value has supportedService value resolved-into exactly one supports Service <keyword> It is obligatory that each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> supportedService </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> supportedService </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> supports </verb_concept><noun_concept> Service </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. VerticalStructure supportedService set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8596 Error AIXM Model It is obligatory that each VerticalStructure with assigned hostedUnit value has hostedUnit value resolved-into exactly one hosts Unit <keyword> It is obligatory that each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> hostedUnit </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> hostedUnit </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hosts </verb_concept><noun_concept> Unit </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. VerticalStructure hostedUnit set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8597 Error AIXM Model It is obligatory that each VerticalStructure with assigned hostedOrganisation value has hostedOrganisation value resolved-into exactly one hosts OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> hostedOrganisation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> hostedOrganisation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hosts </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. VerticalStructure hostedOrganisation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8598 Error AIXM Model It is obligatory that each VerticalStructure with assigned hostedSpecialNavStation value has hostedSpecialNavStation value resolved-into exactly one hosts SpecialNavigationStation <keyword> It is obligatory that each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> hostedSpecialNavStation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> hostedSpecialNavStation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hosts </verb_concept><noun_concept> SpecialNavigationStation </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. VerticalStructure hostedSpecialNavStation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A8599 Error AIXM Model It is obligatory that each VerticalStructure with assigned hostedPassengerService value has hostedPassengerService value resolved-into exactly one hosts PassengerService <keyword> It is obligatory that each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> hostedPassengerService </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> hostedPassengerService </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hosts </verb_concept><noun_concept> PassengerService </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. VerticalStructure hostedPassengerService set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A859A Error AIXM Model It is obligatory that each VerticalStructure with assigned marker value has marker value resolved-into exactly one isMarkedBy MarkerBeacon <keyword> It is obligatory that each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> marker </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> marker </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedBy </verb_concept><noun_concept> MarkerBeacon </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. VerticalStructure marker set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A859B Error AIXM Model It is obligatory that each FinalLeg with assigned finalPathAlignmentPoint.SignificantPoint.aimingPoint value has finalPathAlignmentPoint.SignificantPoint.aimingPoint value resolved-into exactly one isAlignedBy TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> finalPathAlignmentPoint.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> finalPathAlignmentPoint.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAlignedBy </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. FinalLeg finalPathAlignmentPoint.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A859C Error AIXM Model It is obligatory that each FinalLeg with assigned finalPathAlignmentPoint.SignificantPoint.fixDesignatedPoint value has finalPathAlignmentPoint.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isAlignedBy DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> finalPathAlignmentPoint.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> finalPathAlignmentPoint.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAlignedBy </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. FinalLeg finalPathAlignmentPoint.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A859D Error AIXM Model It is obligatory that each FinalLeg with assigned finalPathAlignmentPoint.SignificantPoint.airportReferencePoint value has finalPathAlignmentPoint.SignificantPoint.airportReferencePoint value resolved-into exactly one isAlignedBy AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> finalPathAlignmentPoint.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> finalPathAlignmentPoint.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAlignedBy </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. FinalLeg finalPathAlignmentPoint.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A859E Error AIXM Model It is obligatory that each FinalLeg with assigned finalPathAlignmentPoint.SignificantPoint.navaidSystem value has finalPathAlignmentPoint.SignificantPoint.navaidSystem value resolved-into exactly one isAlignedBy Navaid <keyword> It is obligatory that each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> finalPathAlignmentPoint.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> finalPathAlignmentPoint.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAlignedBy </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. FinalLeg finalPathAlignmentPoint.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A859F Error AIXM Model It is obligatory that each FinalLeg with assigned finalPathAlignmentPoint.SignificantPoint.runwayPoint value has finalPathAlignmentPoint.SignificantPoint.runwayPoint value resolved-into exactly one isAlignedBy RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> finalPathAlignmentPoint.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> finalPathAlignmentPoint.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAlignedBy </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. FinalLeg finalPathAlignmentPoint.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A0 Error AIXM Model It is obligatory that each AirTrafficControlService with assigned clientAirport value has clientAirport value resolved-into exactly one controlsAirspaceOf AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> AirTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAirport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> controlsAirspaceOf </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirTrafficControlService clientAirport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A1 Error AIXM Model It is obligatory that each GroundTrafficControlService with assigned clientAirport value has clientAirport value resolved-into exactly one controls AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> GroundTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAirport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> controls </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. GroundTrafficControlService clientAirport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A2 Error AIXM Model It is obligatory that each AirTrafficControlService with assigned clientAirspace value has clientAirspace value resolved-into exactly one controls Airspace <keyword> It is obligatory that each </keyword><noun_concept> AirTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> controls </verb_concept><noun_concept> Airspace </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirTrafficControlService clientAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A3 Error AIXM Model It is obligatory that each AirTrafficControlService with assigned clientHolding value has clientHolding value resolved-into exactly one controls HoldingPattern <keyword> It is obligatory that each </keyword><noun_concept> AirTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> clientHolding </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientHolding </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> controls </verb_concept><noun_concept> HoldingPattern </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirTrafficControlService clientHolding set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A4 Error AIXM Model It is obligatory that each TouchDownLiftOffSafeArea with assigned protectedTouchDownLiftOff value has protectedTouchDownLiftOff value resolved-into exactly one protects TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> TouchDownLiftOffSafeArea </noun_concept><keyword> with assigned </keyword><noun_concept> protectedTouchDownLiftOff </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> protectedTouchDownLiftOff </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> protects </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TouchDownLiftOffSafeArea protectedTouchDownLiftOff set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A5 Error AIXM Model It is obligatory that each RunwayProtectArea with assigned protectedRunwayDirection value has protectedRunwayDirection value resolved-into exactly one protects RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> RunwayProtectArea </noun_concept><keyword> with assigned </keyword><noun_concept> protectedRunwayDirection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> protectedRunwayDirection </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> protects </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayProtectArea protectedRunwayDirection set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A6 Error AIXM Model It is obligatory that each RunwayProtectAreaLightSystem with assigned lightedArea value has lightedArea value resolved-into exactly one isProvidedFor RunwayProtectArea <keyword> It is obligatory that each </keyword><noun_concept> RunwayProtectAreaLightSystem </noun_concept><keyword> with assigned </keyword><noun_concept> lightedArea </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> lightedArea </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedFor </verb_concept><noun_concept> RunwayProtectArea </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayProtectAreaLightSystem lightedArea set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A7 Error AIXM Model It is obligatory that each TouchDownLiftOffLightSystem with assigned lightedTouchDownLiftOff value has lightedTouchDownLiftOff value resolved-into exactly one isProvidedFor TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> TouchDownLiftOffLightSystem </noun_concept><keyword> with assigned </keyword><noun_concept> lightedTouchDownLiftOff </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> lightedTouchDownLiftOff </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedFor </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TouchDownLiftOffLightSystem lightedTouchDownLiftOff set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A8 Error AIXM Model It is obligatory that each VisualGlideSlopeIndicator with assigned runwayDirection value has runwayDirection value resolved-into exactly one providesGuidanceFor RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> VisualGlideSlopeIndicator </noun_concept><keyword> with assigned </keyword><noun_concept> runwayDirection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> runwayDirection </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> providesGuidanceFor </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. VisualGlideSlopeIndicator runwayDirection set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85A9 Error AIXM Model It is obligatory that each TaxiwayLightSystem with assigned lightedTaxiway value has lightedTaxiway value resolved-into exactly one isProvidedFor Taxiway <keyword> It is obligatory that each </keyword><noun_concept> TaxiwayLightSystem </noun_concept><keyword> with assigned </keyword><noun_concept> lightedTaxiway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> lightedTaxiway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedFor </verb_concept><noun_concept> Taxiway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TaxiwayLightSystem lightedTaxiway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85AA Error AIXM Model It is obligatory that each ApronLightSystem with assigned lightedApron value has lightedApron value resolved-into exactly one isProvidedFor Apron <keyword> It is obligatory that each </keyword><noun_concept> ApronLightSystem </noun_concept><keyword> with assigned </keyword><noun_concept> lightedApron </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> lightedApron </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedFor </verb_concept><noun_concept> Apron </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ApronLightSystem lightedApron set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85AB Error AIXM Model It is obligatory that each RunwayDirectionLightSystem with assigned associatedRunwayDirection value has associatedRunwayDirection value resolved-into exactly one isProvidedFor RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> RunwayDirectionLightSystem </noun_concept><keyword> with assigned </keyword><noun_concept> associatedRunwayDirection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedRunwayDirection </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedFor </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayDirectionLightSystem associatedRunwayDirection set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85AC Error AIXM Model It is obligatory that each AirspaceActivation with assigned user value has user value resolved-into exactly one hasUser OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> AirspaceActivation </noun_concept><keyword> with assigned </keyword><noun_concept> user </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> user </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hasUser </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirspaceActivation user set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85AD Error AIXM Model It is obligatory that each RoutePortion with assigned intermediatePoint.SignificantPoint.fixDesignatedPoint value has intermediatePoint.SignificantPoint.fixDesignatedPoint value resolved-into exactly one passesThrough DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> intermediatePoint.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> intermediatePoint.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> passesThrough </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion intermediatePoint.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85AE Error AIXM Model It is obligatory that each RoutePortion with assigned start.SignificantPoint.navaidSystem value has start.SignificantPoint.navaidSystem value resolved-into exactly one startsAt Navaid <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion start.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85AF Error AIXM Model It is obligatory that each RoutePortion with assigned end.SignificantPoint.navaidSystem value has end.SignificantPoint.navaidSystem value resolved-into exactly one endsAt Navaid <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion end.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85B0 Error AIXM Model It is obligatory that each RoutePortion with assigned end.SignificantPoint.fixDesignatedPoint value has end.SignificantPoint.fixDesignatedPoint value resolved-into exactly one endsAt DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion end.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85B1 Error AIXM Model It is obligatory that each RoutePortion with assigned intermediatePoint.SignificantPoint.navaidSystem value has intermediatePoint.SignificantPoint.navaidSystem value resolved-into exactly one passesThrough Navaid <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> intermediatePoint.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> intermediatePoint.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> passesThrough </verb_concept><noun_concept> Navaid </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion intermediatePoint.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85B2 Error AIXM Model It is obligatory that each RoutePortion with assigned start.SignificantPoint.fixDesignatedPoint value has start.SignificantPoint.fixDesignatedPoint value resolved-into exactly one startsAt DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> RoutePortion </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RoutePortion start.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85B5 Error AIXM Model It is obligatory that each OrganisationAuthority with assigned relatedOrganisationAuthority.OrganisationAuthorityAssociation.theOrganisationAuthority value has relatedOrganisationAuthority.OrganisationAuthorityAssociation.theOrganisationAuthority value resolved-into exactly one hasLinksWith OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> OrganisationAuthority </noun_concept><keyword> with assigned </keyword><noun_concept> relatedOrganisationAuthority.OrganisationAuthorityAssociation.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> relatedOrganisationAuthority.OrganisationAuthorityAssociation.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hasLinksWith </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. OrganisationAuthority relatedOrganisationAuthority.OrganisationAuthorityAssociation.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85B6 Error AIXM Model It is obligatory that each AirspaceVolume with assigned contributorAirspace.AirspaceVolumeDependency.theAirspace value has contributorAirspace.AirspaceVolumeDependency.theAirspace value resolved-into exactly one dependsOn Airspace <keyword> It is obligatory that each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> contributorAirspace.AirspaceVolumeDependency.theAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> contributorAirspace.AirspaceVolumeDependency.theAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> dependsOn </verb_concept><noun_concept> Airspace </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. AirspaceVolume contributorAirspace.AirspaceVolumeDependency.theAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A85B7 Error AIXM Model It is obligatory that each GuidanceLineMarking with assigned markedGuidanceLine value has markedGuidanceLine value resolved-into exactly one isMarkedOn GuidanceLine <keyword> It is obligatory that each </keyword><noun_concept> GuidanceLineMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedGuidanceLine </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedGuidanceLine </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> GuidanceLine </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. GuidanceLineMarking markedGuidanceLine set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB00D Error AIXM Model It is obligatory that each DeicingAreaMarking with assigned markedDeicingArea value has markedDeicingArea value resolved-into exactly one isMarkedOn DeicingArea <keyword> It is obligatory that each </keyword><noun_concept> DeicingAreaMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedDeicingArea </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedDeicingArea </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> DeicingArea </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DeicingAreaMarking markedDeicingArea set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB012 Error AIXM Model It is obligatory that each ApronMarking with assigned markedApron value has markedApron value resolved-into exactly one isMarkedOn Apron <keyword> It is obligatory that each </keyword><noun_concept> ApronMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedApron </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedApron </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> Apron </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. ApronMarking markedApron set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB013 Error AIXM Model It is obligatory that each DeicingArea with assigned standLocation value has standLocation value resolved-into exactly one isLocatedAt AircraftStand <keyword> It is obligatory that each </keyword><noun_concept> DeicingArea </noun_concept><keyword> with assigned </keyword><noun_concept> standLocation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> standLocation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> AircraftStand </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DeicingArea standLocation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB014 Error AIXM Model It is obligatory that each DeicingArea with assigned associatedApron value has associatedApron value resolved-into exactly one isLocatedOn Apron <keyword> It is obligatory that each </keyword><noun_concept> DeicingArea </noun_concept><keyword> with assigned </keyword><noun_concept> associatedApron </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedApron </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedOn </verb_concept><noun_concept> Apron </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DeicingArea associatedApron set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB015 Error AIXM Model It is obligatory that each DeicingArea with assigned taxiwayLocation value has taxiwayLocation value resolved-into exactly one isLocatedOn Taxiway <keyword> It is obligatory that each </keyword><noun_concept> DeicingArea </noun_concept><keyword> with assigned </keyword><noun_concept> taxiwayLocation </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> taxiwayLocation </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isLocatedOn </verb_concept><noun_concept> Taxiway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. DeicingArea taxiwayLocation set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB01C Error AIXM Model It is obligatory that each NonMovementArea with assigned associatedAirportHeliport value has associatedAirportHeliport value resolved-into exactly one isSituatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> NonMovementArea </noun_concept><keyword> with assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedAirportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. NonMovementArea associatedAirportHeliport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB023 Error AIXM Model It is obligatory that each Road with assigned associatedAirport value has associatedAirport value resolved-into exactly one isSituatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> Road </noun_concept><keyword> with assigned </keyword><noun_concept> associatedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedAirport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Road associatedAirport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB024 Error AIXM Model It is obligatory that each Road with assigned accessibleStand value has accessibleStand value resolved-into exactly one givesAccessTo AircraftStand <keyword> It is obligatory that each </keyword><noun_concept> Road </noun_concept><keyword> with assigned </keyword><noun_concept> accessibleStand </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> accessibleStand </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> givesAccessTo </verb_concept><noun_concept> AircraftStand </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Road accessibleStand set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB025 Error AIXM Model It is obligatory that each RunwayBlastPad with assigned usedRunwayDirection value has usedRunwayDirection value resolved-into exactly one isUsedOn RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> RunwayBlastPad </noun_concept><keyword> with assigned </keyword><noun_concept> usedRunwayDirection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> usedRunwayDirection </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUsedOn </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayBlastPad usedRunwayDirection set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB026 Error AIXM Model It is obligatory that each RunwayMarking with assigned markedRunway value has markedRunway value resolved-into exactly one isMarkedOn Runway <keyword> It is obligatory that each </keyword><noun_concept> RunwayMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedRunway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedRunway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> Runway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayMarking markedRunway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB027 Error AIXM Model It is obligatory that each RunwayVisualRange with assigned associatedRunwayDirection value has associatedRunwayDirection value resolved-into exactly one providesVisualRangeFor RunwayDirection <keyword> It is obligatory that each </keyword><noun_concept> RunwayVisualRange </noun_concept><keyword> with assigned </keyword><noun_concept> associatedRunwayDirection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedRunwayDirection </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> providesVisualRangeFor </verb_concept><noun_concept> RunwayDirection </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. RunwayVisualRange associatedRunwayDirection set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB02A Error AIXM Model It is obligatory that each StandMarking with assigned markedStand value has markedStand value resolved-into exactly one isMarkedOn AircraftStand <keyword> It is obligatory that each </keyword><noun_concept> StandMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedStand </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedStand </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> AircraftStand </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. StandMarking markedStand set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB02B Error AIXM Model It is obligatory that each TaxiHoldingPositionMarking with assigned markedTaxiHold value has markedTaxiHold value resolved-into exactly one isMarkedOn TaxiHoldingPosition <keyword> It is obligatory that each </keyword><noun_concept> TaxiHoldingPositionMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedTaxiHold </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedTaxiHold </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> TaxiHoldingPosition </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TaxiHoldingPositionMarking markedTaxiHold set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB02C Error AIXM Model It is obligatory that each TaxiwayMarking with assigned markedTaxiway value has markedTaxiway value resolved-into exactly one isMarkedOn Taxiway <keyword> It is obligatory that each </keyword><noun_concept> TaxiwayMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedTaxiway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedTaxiway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> Taxiway </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TaxiwayMarking markedTaxiway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB02D Error AIXM Model It is obligatory that each TouchDownLiftOffMarking with assigned markedTouchDownLiftOff value has markedTouchDownLiftOff value resolved-into exactly one isMarkedOn TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> TouchDownLiftOffMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedTouchDownLiftOff </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedTouchDownLiftOff </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. TouchDownLiftOffMarking markedTouchDownLiftOff set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB02E Error AIXM Model It is obligatory that each WorkArea with assigned associatedAirportHeliport value has associatedAirportHeliport value resolved-into exactly one isSituatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> WorkArea </noun_concept><keyword> with assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedAirportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. WorkArea associatedAirportHeliport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A2F21 Warning AIXM Model Each Point . annotation . Note . propertyName shall not have assigned value other than ('horizontalAccuracy') <keyword> Each </keyword><noun_concept> Point </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('horizontalAccuracy') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Point All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F23 Warning AIXM Model Each AeronauticalGroundLight . annotation . Note . propertyName shall not have assigned value other than ('name', 'type', 'colour', 'flashing', 'structureBeacon', 'aerodromeBeacon', 'location') <keyword> Each </keyword><noun_concept> AeronauticalGroundLight </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'type', 'colour', 'flashing', 'structureBeacon', 'aerodromeBeacon', 'location') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AeronauticalGroundLight All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F24 Warning AIXM Model Each AircraftCharacteristic . annotation . Note . propertyName shall not have assigned value other than ('type', 'engine', 'numberEngine', 'typeAircraftICAO', 'aircraftLandingCategory', 'wingSpan', 'wingSpanInterpretation', 'classWingSpan', 'weight', 'weightInterpretation', 'passengers', 'passengersInterpretation', 'speed', 'speedInterpretation', 'wakeTurbulence', 'navigationEquipment', 'navigationSpecification', 'verticalSeparationCapability', 'antiCollisionAndSeparationEquipment', 'communicationEquipment', 'surveillanceEquipment') <keyword> Each </keyword><noun_concept> AircraftCharacteristic </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'engine', 'numberEngine', 'typeAircraftICAO', 'aircraftLandingCategory', 'wingSpan', 'wingSpanInterpretation', 'classWingSpan', 'weight', 'weightInterpretation', 'passengers', 'passengersInterpretation', 'speed', 'speedInterpretation', 'wakeTurbulence', 'navigationEquipment', 'navigationSpecification', 'verticalSeparationCapability', 'antiCollisionAndSeparationEquipment', 'communicationEquipment', 'surveillanceEquipment') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AircraftCharacteristic All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F25 Warning AIXM Model Each AircraftGroundService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'type') <keyword> Each </keyword><noun_concept> AircraftGroundService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'type') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AircraftGroundService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F26 Warning AIXM Model Each AircraftStand . annotation . Note . propertyName shall not have assigned value other than ('designator', 'type', 'visualDockingSystem', 'surfaceProperties', 'location', 'apronLocation', 'extent', 'contaminant', 'availability') <keyword> Each </keyword><noun_concept> AircraftStand </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'type', 'visualDockingSystem', 'surfaceProperties', 'location', 'apronLocation', 'extent', 'contaminant', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AircraftStand All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F27 Warning AIXM Model Each AirportClearanceService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'snowPlan') <keyword> Each </keyword><noun_concept> AirportClearanceService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'snowPlan') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportClearanceService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F29 Warning AIXM Model Each AirportHeliportAvailability . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus', 'warning', 'usage') <keyword> Each </keyword><noun_concept> AirportHeliportAvailability </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus', 'warning', 'usage') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportHeliportAvailability All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F2A Warning AIXM Model Each AirportHeliportCollocation . annotation . Note . propertyName shall not have assigned value other than ('type', 'hostAirport', 'dependentAirport') <keyword> Each </keyword><noun_concept> AirportHeliportCollocation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'hostAirport', 'dependentAirport') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportHeliportCollocation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F2B Warning AIXM Model Each AirportHeliportResponsibilityOrganisation . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'role', 'theOrganisationAuthority') <keyword> Each </keyword><noun_concept> AirportHeliportResponsibilityOrganisation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'role', 'theOrganisationAuthority') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportHeliportResponsibilityOrganisation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F2C Warning AIXM Model Each AirportHeliportUsage . annotation . Note . propertyName shall not have assigned value other than ('type', 'priorPermission', 'contact', 'selection', 'operation') <keyword> Each </keyword><noun_concept> AirportHeliportUsage </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'priorPermission', 'contact', 'selection', 'operation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportHeliportUsage All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F2D Warning AIXM Model Each AirportHotSpot . annotation . Note . propertyName shall not have assigned value other than ('designator', 'instruction', 'area', 'affectedAirport') <keyword> Each </keyword><noun_concept> AirportHotSpot </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'instruction', 'area', 'affectedAirport') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportHotSpot All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F2E Warning AIXM Model Each AirportSuppliesService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'fuelSupply', 'oilSupply', 'nitrogenSupply', 'oxygenSupply') <keyword> Each </keyword><noun_concept> AirportSuppliesService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'fuelSupply', 'oilSupply', 'nitrogenSupply', 'oxygenSupply') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportSuppliesService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F2F Warning Warning AIXM Model Each Airspace . annotation . Note . propertyName shall not have assigned value other than ('type', 'designator', 'localType', 'name', 'designatorICAO', 'controlType', 'upperLowerSeparation', 'class', 'protectedRoute', 'geometryComponent', 'activation') <keyword> Each </keyword><noun_concept> Airspace </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'designator', 'localType', 'name', 'designatorICAO', 'controlType', 'upperLowerSeparation', 'class', 'protectedRoute', 'geometryComponent', 'activation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Airspace All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F30 Warning AIXM Model Each AirspaceActivation . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'activity', 'status', 'levels', 'user', 'aircraft') <keyword> Each </keyword><noun_concept> AirspaceActivation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'activity', 'status', 'levels', 'user', 'aircraft') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirspaceActivation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F31 Warning AIXM Model Each AirspaceGeometryComponent . annotation . Note . propertyName shall not have assigned value other than ('operation', 'operationSequence', 'theAirspaceVolume') <keyword> Each </keyword><noun_concept> AirspaceGeometryComponent </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('operation', 'operationSequence', 'theAirspaceVolume') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirspaceGeometryComponent All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F32 Warning AIXM Model Each AirspaceLayer . annotation . Note . propertyName shall not have assigned value other than ('upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'altitudeInterpretation', 'discreteLevelSeries') <keyword> Each </keyword><noun_concept> AirspaceLayer </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'altitudeInterpretation', 'discreteLevelSeries') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirspaceLayer All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F33 Warning AIXM Model Each AirspaceLayerClass . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'classification', 'associatedLevels') <keyword> Each </keyword><noun_concept> AirspaceLayerClass </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'classification', 'associatedLevels') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirspaceLayerClass All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F34 Warning AIXM Model Each AirspaceVolume . annotation . Note . propertyName shall not have assigned value other than ('upperLimit', 'upperLimitReference', 'maximumLimit', 'maximumLimitReference', 'lowerLimit', 'lowerLimitReference', 'minimumLimit', 'minimumLimitReference', 'width', 'horizontalProjection', 'centreline', 'contributorAirspace') <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('upperLimit', 'upperLimitReference', 'maximumLimit', 'maximumLimitReference', 'lowerLimit', 'lowerLimitReference', 'minimumLimit', 'minimumLimitReference', 'width', 'horizontalProjection', 'centreline', 'contributorAirspace') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirspaceVolume All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F35 Warning AIXM Model Each AirspaceVolumeDependency . annotation . Note . propertyName shall not have assigned value other than ('dependency', 'theAirspace') <keyword> Each </keyword><noun_concept> AirspaceVolumeDependency </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('dependency', 'theAirspace') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirspaceVolumeDependency All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F36 Warning AIXM Model Each AirTrafficControlService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'radarAssisted', 'dataLinkEnabled', 'dataLinkChannel', 'type', 'clientAirport', 'clientAirspace', 'clientRoute', 'clientProcedure', 'clientHolding', 'clientAerialRefuelling', 'aircraftLocator') <keyword> Each </keyword><noun_concept> AirTrafficControlService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'radarAssisted', 'dataLinkEnabled', 'dataLinkChannel', 'type', 'clientAirport', 'clientAirspace', 'clientRoute', 'clientProcedure', 'clientHolding', 'clientAerialRefuelling', 'aircraftLocator') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirTrafficControlService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F37 Warning AIXM Model Each AirTrafficManagementService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'type', 'clientAirspace', 'clientAerialRefuelling', 'clientRoute') <keyword> Each </keyword><noun_concept> AirTrafficManagementService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'type', 'clientAirspace', 'clientAerialRefuelling', 'clientRoute') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirTrafficManagementService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F38 Warning AIXM Model Each AltitudeAdjustment . annotation . Note . propertyName shall not have assigned value other than ('altitudeAdjustmentType', 'primaryAlternateMinimum', 'altitudeAdjustment', 'localRemoteCode') <keyword> Each </keyword><noun_concept> AltitudeAdjustment </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('altitudeAdjustmentType', 'primaryAlternateMinimum', 'altitudeAdjustment', 'localRemoteCode') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AltitudeAdjustment All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F39 Warning AIXM Model Each AngleIndication . annotation . Note . propertyName shall not have assigned value other than ('angle', 'angleType', 'indicationDirection', 'trueAngle', 'cardinalDirection', 'minimumReceptionAltitude', 'fix', 'pointChoiceFixDesignatedPoint', 'pointChoiceNavaidSystem', 'pointChoicePosition', 'pointChoiceRunwayPoint', 'pointChoiceAimingPoint', 'pointChoiceAirportReferencePoint') <keyword> Each </keyword><noun_concept> AngleIndication </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('angle', 'angleType', 'indicationDirection', 'trueAngle', 'cardinalDirection', 'minimumReceptionAltitude', 'fix', 'pointChoiceFixDesignatedPoint', 'pointChoiceNavaidSystem', 'pointChoicePosition', 'pointChoiceRunwayPoint', 'pointChoiceAimingPoint', 'pointChoiceAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AngleIndication All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F3A Warning AIXM Model Each AngleUse . annotation . Note . propertyName shall not have assigned value other than ('alongCourseGuidance', 'theAngleIndication') <keyword> Each </keyword><noun_concept> AngleUse </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('alongCourseGuidance', 'theAngleIndication') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AngleUse All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F3B Warning AIXM Model Each ApproachAltitudeTable . annotation . Note . propertyName shall not have assigned value other than ('measurementPoint', 'altitude', 'altitudeReference') <keyword> Each </keyword><noun_concept> ApproachAltitudeTable </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('measurementPoint', 'altitude', 'altitudeReference') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApproachAltitudeTable All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F3C Warning AIXM Model Each ApproachCondition . annotation . Note . propertyName shall not have assigned value other than ('finalApproachPath', 'requiredNavigationPerformance', 'climbGradient', 'minimumSet', 'circlingRestriction', 'aircraftCategory', 'landingArea', 'altimeter', 'designSurface') <keyword> Each </keyword><noun_concept> ApproachCondition </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('finalApproachPath', 'requiredNavigationPerformance', 'climbGradient', 'minimumSet', 'circlingRestriction', 'aircraftCategory', 'landingArea', 'altimeter', 'designSurface') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApproachCondition All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F3D Warning AIXM Model Each ApproachDistanceTable . annotation . Note . propertyName shall not have assigned value other than ('startingMeasurementPoint', 'valueHAT', 'endingMeasurementPoint', 'distance') <keyword> Each </keyword><noun_concept> ApproachDistanceTable </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('startingMeasurementPoint', 'valueHAT', 'endingMeasurementPoint', 'distance') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApproachDistanceTable All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F3E Warning AIXM Model Each ApproachLightingSystem . annotation . Note . propertyName shall not have assigned value other than ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'classICAO', 'type', 'length', 'sequencedFlashing', 'alignmentIndicator', 'servedRunwayDirection') <keyword> Each </keyword><noun_concept> ApproachLightingSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'classICAO', 'type', 'length', 'sequencedFlashing', 'alignmentIndicator', 'servedRunwayDirection') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApproachLightingSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F3F Warning AIXM Model Each ApproachTimingTable . annotation . Note . propertyName shall not have assigned value other than ('startingMeasurementPoint', 'endingMeasurementPoint', 'time', 'speed') <keyword> Each </keyword><noun_concept> ApproachTimingTable </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('startingMeasurementPoint', 'endingMeasurementPoint', 'time', 'speed') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApproachTimingTable All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F40 Warning AIXM Model Each Apron . annotation . Note . propertyName shall not have assigned value other than ('name', 'abandoned', 'surfaceProperties', 'associatedAirportHeliport', 'contaminant', 'availability') <keyword> Each </keyword><noun_concept> Apron </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'abandoned', 'surfaceProperties', 'associatedAirportHeliport', 'contaminant', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Apron All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F41 Warning AIXM Model Each ApronAreaAvailability . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus', 'warning', 'usage') <keyword> Each </keyword><noun_concept> ApronAreaAvailability </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus', 'warning', 'usage') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApronAreaAvailability All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F42 Warning AIXM Model Each ApronAreaUsage . annotation . Note . propertyName shall not have assigned value other than ('type', 'priorPermission', 'contact', 'selection') <keyword> Each </keyword><noun_concept> ApronAreaUsage </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'priorPermission', 'contact', 'selection') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApronAreaUsage All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F43 Warning AIXM Model Each ApronElement . annotation . Note . propertyName shall not have assigned value other than ('type', 'jetwayAvailability', 'towingAvailability', 'dockingAvailability', 'groundPowerAvailability', 'length', 'width', 'associatedApron', 'surfaceProperties', 'extent', 'supplyService', 'availability') <keyword> Each </keyword><noun_concept> ApronElement </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'jetwayAvailability', 'towingAvailability', 'dockingAvailability', 'groundPowerAvailability', 'length', 'width', 'associatedApron', 'surfaceProperties', 'extent', 'supplyService', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApronElement All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F44 Warning AIXM Model Each ApronLightSystem . annotation . Note . propertyName shall not have assigned value other than ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'lightedApron') <keyword> Each </keyword><noun_concept> ApronLightSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'lightedApron') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApronLightSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F45 Warning AIXM Model Each ArrestingGear . annotation . Note . propertyName shall not have assigned value other than ('status', 'length', 'width', 'engageDevice', 'absorbType', 'bidirectional', 'location', 'runwayDirection', 'surfaceProperties', 'extentSurfaceExtent', 'extentCurveExtent', 'extentPointExtent') <keyword> Each </keyword><noun_concept> ArrestingGear </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('status', 'length', 'width', 'engageDevice', 'absorbType', 'bidirectional', 'location', 'runwayDirection', 'surfaceProperties', 'extentSurfaceExtent', 'extentCurveExtent', 'extentPointExtent') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ArrestingGear All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F46 Warning AIXM Model Each ArrivalFeederLeg . annotation . Note . propertyName shall not have assigned value other than ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'requiredNavigationPerformance') <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'requiredNavigationPerformance') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ArrivalFeederLeg All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F47 Warning AIXM Model Each ArrivalLeg . annotation . Note . propertyName shall not have assigned value other than ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'requiredNavigationPerformance', 'arrival') <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'requiredNavigationPerformance', 'arrival') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ArrivalLeg All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F48 Warning AIXM Model Each AuthorityForAirspace . annotation . Note . propertyName shall not have assigned value other than ('type', 'responsibleOrganisation', 'assignedAirspace') <keyword> Each </keyword><noun_concept> AuthorityForAirspace </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'responsibleOrganisation', 'assignedAirspace') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AuthorityForAirspace All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F49 Warning AIXM Model Each AuthorityForNavaidEquipment . annotation . Note . propertyName shall not have assigned value other than ('type', 'theOrganisationAuthority') <keyword> Each </keyword><noun_concept> AuthorityForNavaidEquipment </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'theOrganisationAuthority') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AuthorityForNavaidEquipment All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F4A Warning AIXM Model Each Azimuth . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'type', 'trueBearing', 'trueBearingAccuracy', 'magneticBearing', 'angleProportionalLeft', 'angleProportionalRight', 'angleCoverLeft', 'angleCoverRight', 'channel') <keyword> Each </keyword><noun_concept> Azimuth </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'type', 'trueBearing', 'trueBearingAccuracy', 'magneticBearing', 'angleProportionalLeft', 'angleProportionalRight', 'angleCoverLeft', 'angleCoverRight', 'channel') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Azimuth All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F4B Warning AIXM Model Each CallsignDetail . annotation . Note . propertyName shall not have assigned value other than ('callSign', 'language') <keyword> Each </keyword><noun_concept> CallsignDetail </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('callSign', 'language') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property CallsignDetail All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F4C Warning AIXM Model Each ChangeOverPoint . annotation . Note . propertyName shall not have assigned value other than ('distance', 'applicableRoutePortion', 'locationFixDesignatedPoint', 'locationNavaidSystem', 'locationPosition', 'locationRunwayPoint', 'locationAimingPoint', 'locationAirportReferencePoint') <keyword> Each </keyword><noun_concept> ChangeOverPoint </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('distance', 'applicableRoutePortion', 'locationFixDesignatedPoint', 'locationNavaidSystem', 'locationPosition', 'locationRunwayPoint', 'locationAimingPoint', 'locationAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ChangeOverPoint All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F4D Warning AIXM Model Each CheckpointINS . annotation . Note . propertyName shall not have assigned value other than ('category', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'altitudeInterpretation', 'distance', 'angle', 'position', 'airportHeliport') <keyword> Each </keyword><noun_concept> CheckpointINS </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('category', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'altitudeInterpretation', 'distance', 'angle', 'position', 'airportHeliport') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property CheckpointINS All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F4E Warning AIXM Model Each CheckpointVOR . annotation . Note . propertyName shall not have assigned value other than ('category', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'altitudeInterpretation', 'distance', 'angle', 'position', 'airportHeliport', 'checkPointFacility') <keyword> Each </keyword><noun_concept> CheckpointVOR </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('category', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'altitudeInterpretation', 'distance', 'angle', 'position', 'airportHeliport', 'checkPointFacility') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property CheckpointVOR All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F4F Warning AIXM Model Each CircleSector . annotation . Note . propertyName shall not have assigned value other than ('arcDirection', 'fromAngle', 'toAngle', 'angleType', 'angleDirectionReference', 'innerDistance', 'outerDistance', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference') <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('arcDirection', 'fromAngle', 'toAngle', 'angleType', 'angleDirectionReference', 'innerDistance', 'outerDistance', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property CircleSector All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F50 Warning AIXM Model Each CirclingArea . annotation . Note . propertyName shall not have assigned value other than ('extent', 'approach', 'condition', 'aircraftCategory', 'designSurface') <keyword> Each </keyword><noun_concept> CirclingArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('extent', 'approach', 'condition', 'aircraftCategory', 'designSurface') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property CirclingArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F51 Warning AIXM Model Each CirclingRestriction . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'sectorDescription', 'restrictionArea') <keyword> Each </keyword><noun_concept> CirclingRestriction </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'sectorDescription', 'restrictionArea') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property CirclingRestriction All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F52 Warning AIXM Model Each City . annotation . Note . propertyName shall not have assigned value other than ('name') <keyword> Each </keyword><noun_concept> City </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property City All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F53 Warning AIXM Model Each ConditionCombination . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'logicalOperator', 'weather', 'aircraft', 'flight', 'subCondition') <keyword> Each </keyword><noun_concept> ConditionCombination </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'logicalOperator', 'weather', 'aircraft', 'flight', 'subCondition') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ConditionCombination All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F54 Warning AIXM Model Each ContactInformation . annotation . Note . propertyName shall not have assigned value other than ('name', 'title', 'address', 'networkNode', 'phoneFax') <keyword> Each </keyword><noun_concept> ContactInformation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'title', 'address', 'networkNode', 'phoneFax') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ContactInformation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F55 Warning AIXM Model Each Curve . annotation . Note . propertyName shall not have assigned value other than ('horizontalAccuracy') <keyword> Each </keyword><noun_concept> Curve </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('horizontalAccuracy') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Curve All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F56 Warning AIXM Model Each DepartureArrivalCondition . annotation . Note . propertyName shall not have assigned value other than ('minimumEnrouteAltitude', 'minimumCrossingAtEnd', 'minimumCrossingAtEndReference', 'maximumCrossingAtEnd', 'maximumCrossingAtEndReference', 'engineType') <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('minimumEnrouteAltitude', 'minimumCrossingAtEnd', 'minimumCrossingAtEndReference', 'maximumCrossingAtEnd', 'maximumCrossingAtEndReference', 'engineType') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DepartureArrivalCondition All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F57 Warning AIXM Model Each DepartureLeg . annotation . Note . propertyName shall not have assigned value other than ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'requiredNavigationPerformance', 'minimumObstacleClearanceAltitude', 'departure', 'condition') <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'requiredNavigationPerformance', 'minimumObstacleClearanceAltitude', 'departure', 'condition') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DepartureLeg All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F58 Warning AIXM Model Each DesignatedPoint . annotation . Note . propertyName shall not have assigned value other than ('designator', 'type', 'name', 'location', 'aimingPoint', 'airportHeliport', 'runwayPoint') <keyword> Each </keyword><noun_concept> DesignatedPoint </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'type', 'name', 'location', 'aimingPoint', 'airportHeliport', 'runwayPoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DesignatedPoint All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F59 Warning AIXM Model Each DistanceIndication . annotation . Note . propertyName shall not have assigned value other than ('distance', 'minimumReceptionAltitude', 'type', 'fix', 'pointChoiceFixDesignatedPoint', 'pointChoiceNavaidSystem', 'pointChoicePosition', 'pointChoiceRunwayPoint', 'pointChoiceAimingPoint', 'pointChoiceAirportReferencePoint') <keyword> Each </keyword><noun_concept> DistanceIndication </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('distance', 'minimumReceptionAltitude', 'type', 'fix', 'pointChoiceFixDesignatedPoint', 'pointChoiceNavaidSystem', 'pointChoicePosition', 'pointChoiceRunwayPoint', 'pointChoiceAimingPoint', 'pointChoiceAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DistanceIndication All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F5A Warning AIXM Model Each DME . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'type', 'channel', 'ghostFrequency', 'displace') <keyword> Each </keyword><noun_concept> DME </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'type', 'channel', 'ghostFrequency', 'displace') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DME All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F5B Warning AIXM Model Each ElevatedCurve . annotation . Note . propertyName shall not have assigned value other than ('horizontalAccuracy', 'elevation', 'geoidUndulation', 'verticalDatum', 'verticalAccuracy') <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('horizontalAccuracy', 'elevation', 'geoidUndulation', 'verticalDatum', 'verticalAccuracy') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ElevatedCurve All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F5C Warning AIXM Model Each ElevatedPoint . annotation . Note . propertyName shall not have assigned value other than ('horizontalAccuracy', 'elevation', 'geoidUndulation', 'verticalDatum', 'verticalAccuracy') <keyword> Each </keyword><noun_concept> ElevatedPoint </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('horizontalAccuracy', 'elevation', 'geoidUndulation', 'verticalDatum', 'verticalAccuracy') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ElevatedPoint All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F5D Warning AIXM Model Each ElevatedSurface . annotation . Note . propertyName shall not have assigned value other than ('horizontalAccuracy', 'elevation', 'geoidUndulation', 'verticalDatum', 'verticalAccuracy') <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('horizontalAccuracy', 'elevation', 'geoidUndulation', 'verticalDatum', 'verticalAccuracy') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ElevatedSurface All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F5E Warning AIXM Model Each Elevation . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'angleNominal', 'angleMinimum', 'angleSpan', 'angleAccuracy') <keyword> Each </keyword><noun_concept> Elevation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'angleNominal', 'angleMinimum', 'angleSpan', 'angleAccuracy') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Elevation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F5F Warning AIXM Model Each EnRouteSegmentPoint . annotation . Note . propertyName shall not have assigned value other than ('reportingATC', 'flyOver', 'waypoint', 'radarGuidance', 'facilityMakeup', 'extendedServiceVolume', 'roleFreeFlight', 'roleRVSM', 'turnRadius', 'roleMilitaryTraining', 'pointChoiceFixDesignatedPoint', 'pointChoiceNavaidSystem', 'pointChoicePosition', 'pointChoiceRunwayPoint', 'pointChoiceAimingPoint', 'pointChoiceAirportReferencePoint') <keyword> Each </keyword><noun_concept> EnRouteSegmentPoint </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('reportingATC', 'flyOver', 'waypoint', 'radarGuidance', 'facilityMakeup', 'extendedServiceVolume', 'roleFreeFlight', 'roleRVSM', 'turnRadius', 'roleMilitaryTraining', 'pointChoiceFixDesignatedPoint', 'pointChoiceNavaidSystem', 'pointChoicePosition', 'pointChoiceRunwayPoint', 'pointChoiceAimingPoint', 'pointChoiceAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property EnRouteSegmentPoint All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F60 Warning AIXM Model Each EquipmentUnavailableAdjustment . annotation . Note . propertyName shall not have assigned value other than ('type', 'approachLightingInoperative', 'adjustmentINOPCol') <keyword> Each </keyword><noun_concept> EquipmentUnavailableAdjustment </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'approachLightingInoperative', 'adjustmentINOPCol') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property EquipmentUnavailableAdjustment All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F61 Warning AIXM Model Each EquipmentUnavailableAdjustmentColumn . annotation . Note . propertyName shall not have assigned value other than ('guidanceEquipment', 'landingSystemLights', 'equipmentRVR', 'visibilityAdjustment', 'approachLightingInoperative') <keyword> Each </keyword><noun_concept> EquipmentUnavailableAdjustmentColumn </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('guidanceEquipment', 'landingSystemLights', 'equipmentRVR', 'visibilityAdjustment', 'approachLightingInoperative') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property EquipmentUnavailableAdjustmentColumn All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F62 Warning AIXM Model Each FASDataBlock . annotation . Note . propertyName shall not have assigned value other than ('horizontalAlarmLimit', 'verticalAlarmLimit', 'thresholdCourseWidth', 'lengthOffset', 'cRCRemainder', 'operationType', 'serviceProviderSBAS', 'approachPerformanceDesignator', 'routeIndicator', 'referencePathDataSelector', 'referencePathIdentifier', 'codeICAO') <keyword> Each </keyword><noun_concept> FASDataBlock </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('horizontalAlarmLimit', 'verticalAlarmLimit', 'thresholdCourseWidth', 'lengthOffset', 'cRCRemainder', 'operationType', 'serviceProviderSBAS', 'approachPerformanceDesignator', 'routeIndicator', 'referencePathDataSelector', 'referencePathIdentifier', 'codeICAO') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FASDataBlock All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F63 Warning AIXM Model Each FinalLeg . annotation . Note . propertyName shall not have assigned value other than ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'guidanceSystem', 'landingSystemCategory', 'minimumBaroVnavTemperature', 'rnpDMEAuthorized', 'courseOffsetAngle', 'courseOffsetSide', 'courseCentrelineDistance', 'courseOffsetDistance', 'courseCentrelineIntersect', 'condition', 'visualDescentPoint', 'fASData', 'finalPathAlignmentPointFixDesignatedPoint', 'finalPathAlignmentPointNavaidSystem', 'finalPathAlignmentPointPosition', 'finalPathAlignmentPointRunwayPoint', 'finalPathAlignmentPointAimingPoint', 'finalPathAlignmentPointAirportReferencePoint') <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'guidanceSystem', 'landingSystemCategory', 'minimumBaroVnavTemperature', 'rnpDMEAuthorized', 'courseOffsetAngle', 'courseOffsetSide', 'courseCentrelineDistance', 'courseOffsetDistance', 'courseCentrelineIntersect', 'condition', 'visualDescentPoint', 'fASData', 'finalPathAlignmentPointFixDesignatedPoint', 'finalPathAlignmentPointNavaidSystem', 'finalPathAlignmentPointPosition', 'finalPathAlignmentPointRunwayPoint', 'finalPathAlignmentPointAimingPoint', 'finalPathAlignmentPointAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FinalLeg All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F64 Warning AIXM Model Each FinalProfile . annotation . Note . propertyName shall not have assigned value other than ('altitude', 'distance', 'timing') <keyword> Each </keyword><noun_concept> FinalProfile </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('altitude', 'distance', 'timing') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FinalProfile All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F65 Warning AIXM Model Each FireFightingService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'category', 'standard') <keyword> Each </keyword><noun_concept> FireFightingService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'category', 'standard') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FireFightingService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F66 Warning AIXM Model Each FlightCharacteristic . annotation . Note . propertyName shall not have assigned value other than ('type', 'rule', 'status', 'military', 'origin', 'purpose') <keyword> Each </keyword><noun_concept> FlightCharacteristic </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'rule', 'status', 'military', 'origin', 'purpose') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FlightCharacteristic All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F68 Warning AIXM Model Each Fuel . annotation . Note . propertyName shall not have assigned value other than ('category') <keyword> Each </keyword><noun_concept> Fuel </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('category') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Fuel All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F69 Warning AIXM Model Each GeoBorder . annotation . Note . propertyName shall not have assigned value other than ('name', 'type', 'border') <keyword> Each </keyword><noun_concept> GeoBorder </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'type', 'border') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property GeoBorder All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F6A Warning AIXM Model Each Glidepath . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'frequency', 'slope', 'angleAccuracy', 'rdh', 'rdhAccuracy') <keyword> Each </keyword><noun_concept> Glidepath </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'frequency', 'slope', 'angleAccuracy', 'rdh', 'rdhAccuracy') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Glidepath All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F6B Warning AIXM Model Each GroundLightingAvailability . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus') <keyword> Each </keyword><noun_concept> GroundLightingAvailability </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property GroundLightingAvailability All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F6C Warning AIXM Model Each GroundTrafficControlService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'radarAssisted', 'dataLinkEnabled', 'dataLinkChannel', 'type', 'clientAirport') <keyword> Each </keyword><noun_concept> GroundTrafficControlService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'radarAssisted', 'dataLinkEnabled', 'dataLinkChannel', 'type', 'clientAirport') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property GroundTrafficControlService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F6D Warning AIXM Model Each GuidanceLine . annotation . Note . propertyName shall not have assigned value other than ('designator', 'type', 'maxSpeed', 'usageDirection', 'connectedTouchDownLiftOff', 'connectedRunwayCentrelinePoint', 'connectedApron', 'connectedStand', 'extent', 'connectedTaxiway') <keyword> Each </keyword><noun_concept> GuidanceLine </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'type', 'maxSpeed', 'usageDirection', 'connectedTouchDownLiftOff', 'connectedRunwayCentrelinePoint', 'connectedApron', 'connectedStand', 'extent', 'connectedTaxiway') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property GuidanceLine All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F6E Warning AIXM Model Each GuidanceLineLightSystem . annotation . Note . propertyName shall not have assigned value other than ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'lightedGuidanceLine') <keyword> Each </keyword><noun_concept> GuidanceLineLightSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'lightedGuidanceLine') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property GuidanceLineLightSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F71 Warning AIXM Model Each HoldingPatternDistance . annotation . Note . propertyName shall not have assigned value other than ('length') <keyword> Each </keyword><noun_concept> HoldingPatternDistance </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('length') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property HoldingPatternDistance All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F72 Warning AIXM Model Each HoldingPatternDuration . annotation . Note . propertyName shall not have assigned value other than ('duration') <keyword> Each </keyword><noun_concept> HoldingPatternDuration </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('duration') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property HoldingPatternDuration All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F73 Warning AIXM Model Each HoldingUse . annotation . Note . propertyName shall not have assigned value other than ('holdingUse', 'instruction', 'instructedAltitude', 'instructionAltitudeReference', 'theHoldingPattern') <keyword> Each </keyword><noun_concept> HoldingUse </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('holdingUse', 'instruction', 'instructedAltitude', 'instructionAltitudeReference', 'theHoldingPattern') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property HoldingUse All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F74 Warning AIXM Model Each InformationService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'type', 'voice', 'dataLink', 'recorded', 'navaidBroadcast', 'clientAirspace', 'clientAirport', 'clientRoute', 'clientProcedure', 'clientHolding', 'clientAerialRefuelling') <keyword> Each </keyword><noun_concept> InformationService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'type', 'voice', 'dataLink', 'recorded', 'navaidBroadcast', 'clientAirspace', 'clientAirport', 'clientRoute', 'clientProcedure', 'clientHolding', 'clientAerialRefuelling') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property InformationService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F75 Warning AIXM Model Each InitialLeg . annotation . Note . propertyName shall not have assigned value other than ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'requiredNavigationPerformance') <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'requiredNavigationPerformance') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property InitialLeg All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F76 Warning AIXM Model Each InstrumentApproachProcedure . annotation . Note . propertyName shall not have assigned value other than ('communicationFailureInstruction', 'instruction', 'designCriteria', 'codingStandard', 'flightChecked', 'name', 'rNAV', 'availability', 'airportHeliport', 'aircraftCharacteristic', 'flightTransition', 'safeAltitude', 'approachPrefix', 'approachType', 'multipleIdentification', 'copterTrack', 'circlingIdentification', 'courseReversalInstruction', 'additionalEquipment', 'channelGNSS', 'wAASReliable', 'landing', 'missedInstruction', 'finalProfile', 'guidanceFacilityNavaid', 'guidanceFacilityRadar', 'guidanceFacilitySpecialNavigationSystem') <keyword> Each </keyword><noun_concept> InstrumentApproachProcedure </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('communicationFailureInstruction', 'instruction', 'designCriteria', 'codingStandard', 'flightChecked', 'name', 'rNAV', 'availability', 'airportHeliport', 'aircraftCharacteristic', 'flightTransition', 'safeAltitude', 'approachPrefix', 'approachType', 'multipleIdentification', 'copterTrack', 'circlingIdentification', 'courseReversalInstruction', 'additionalEquipment', 'channelGNSS', 'wAASReliable', 'landing', 'missedInstruction', 'finalProfile', 'guidanceFacilityNavaid', 'guidanceFacilityRadar', 'guidanceFacilitySpecialNavigationSystem') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property InstrumentApproachProcedure All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F77 Warning AIXM Model Each IntermediateLeg . annotation . Note . propertyName shall not have assigned value other than ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'requiredNavigationPerformance') <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'requiredNavigationPerformance') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property IntermediateLeg All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F78 Warning AIXM Model Each LandingTakeoffAreaCollection . annotation . Note . propertyName shall not have assigned value other than ('runway', 'tLOF') <keyword> Each </keyword><noun_concept> LandingTakeoffAreaCollection </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('runway', 'tLOF') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property LandingTakeoffAreaCollection All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F79 Warning AIXM Model Each LightActivation . annotation . Note . propertyName shall not have assigned value other than ('clicks', 'intensityLevel', 'activation') <keyword> Each </keyword><noun_concept> LightActivation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('clicks', 'intensityLevel', 'activation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property LightActivation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F7A Warning AIXM Model Each LightElement . annotation . Note . propertyName shall not have assigned value other than ('colour', 'intensityLevel', 'intensity', 'type', 'location', 'availability') <keyword> Each </keyword><noun_concept> LightElement </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('colour', 'intensityLevel', 'intensity', 'type', 'location', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property LightElement All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F7B Warning AIXM Model Each LightElementStatus . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'status') <keyword> Each </keyword><noun_concept> LightElementStatus </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'status') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property LightElementStatus All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F7C Warning AIXM Model Each Localizer . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'frequency', 'magneticBearing', 'magneticBearingAccuracy', 'trueBearing', 'trueBearingAccuracy', 'declination', 'widthCourse', 'widthCourseAccuracy', 'backCourseUsable') <keyword> Each </keyword><noun_concept> Localizer </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'frequency', 'magneticBearing', 'magneticBearingAccuracy', 'trueBearing', 'trueBearingAccuracy', 'declination', 'widthCourse', 'widthCourseAccuracy', 'backCourseUsable') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Localizer All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F7D Warning AIXM Model Each ManoeuvringAreaAvailability . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus', 'warning', 'usage') <keyword> Each </keyword><noun_concept> ManoeuvringAreaAvailability </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus', 'warning', 'usage') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ManoeuvringAreaAvailability All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F7E Warning AIXM Model Each ManoeuvringAreaUsage . annotation . Note . propertyName shall not have assigned value other than ('type', 'priorPermission', 'contact', 'selection', 'operation') <keyword> Each </keyword><noun_concept> ManoeuvringAreaUsage </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'priorPermission', 'contact', 'selection', 'operation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ManoeuvringAreaUsage All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F7F Warning AIXM Model Each MarkerBeacon . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'class', 'frequency', 'axisBearing', 'auralMorseCode') <keyword> Each </keyword><noun_concept> MarkerBeacon </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'class', 'frequency', 'axisBearing', 'auralMorseCode') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property MarkerBeacon All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F80 Warning AIXM Model Each Minima . annotation . Note . propertyName shall not have assigned value other than ('altitude', 'altitudeCode', 'altitudeReference', 'height', 'militaryHeight', 'radioHeight', 'heightCode', 'heightReference', 'visibility', 'militaryVisibility', 'mandatoryRVR', 'remoteAltimeterMinima', 'adjustmentINOP') <keyword> Each </keyword><noun_concept> Minima </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('altitude', 'altitudeCode', 'altitudeReference', 'height', 'militaryHeight', 'radioHeight', 'heightCode', 'heightReference', 'visibility', 'militaryVisibility', 'mandatoryRVR', 'remoteAltimeterMinima', 'adjustmentINOP') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Minima All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F81 Warning AIXM Model Each MissedApproachGroup . annotation . Note . propertyName shall not have assigned value other than ('instruction', 'alternateClimbInstruction', 'alternateClimbAltitude', 'altimeter') <keyword> Each </keyword><noun_concept> MissedApproachGroup </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('instruction', 'alternateClimbInstruction', 'alternateClimbAltitude', 'altimeter') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property MissedApproachGroup All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F82 Warning AIXM Model Each MissedApproachLeg . annotation . Note . propertyName shall not have assigned value other than ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'type', 'thresholdAfterMAPT', 'heightMAPT', 'requiredNavigationPerformance', 'condition') <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('endConditionDesignator', 'legPath', 'legTypeARINC', 'course', 'courseType', 'courseDirection', 'turnDirection', 'speedLimit', 'speedReference', 'speedInterpretation', 'bankAngle', 'length', 'duration', 'procedureTurnRequired', 'upperLimitAltitude', 'upperLimitReference', 'lowerLimitAltitude', 'lowerLimitReference', 'altitudeInterpretation', 'altitudeOverrideATC', 'altitudeOverrideReference', 'verticalAngle', 'startPoint', 'endPoint', 'trajectory', 'arcCentre', 'angle', 'distance', 'aircraftCategory', 'holding', 'designSurface', 'approach', 'type', 'thresholdAfterMAPT', 'heightMAPT', 'requiredNavigationPerformance', 'condition') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property MissedApproachLeg All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F83 Warning AIXM Model Each Navaid . annotation . Note . propertyName shall not have assigned value other than ('type', 'designator', 'name', 'flightChecked', 'purpose', 'signalPerformance', 'courseQuality', 'integrityLevel', 'touchDownLiftOff', 'navaidEquipment', 'location', 'runwayDirection', 'servedAirport', 'availability') <keyword> Each </keyword><noun_concept> Navaid </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'designator', 'name', 'flightChecked', 'purpose', 'signalPerformance', 'courseQuality', 'integrityLevel', 'touchDownLiftOff', 'navaidEquipment', 'location', 'runwayDirection', 'servedAirport', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Navaid All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F84 Warning AIXM Model Each NavaidComponent . annotation . Note . propertyName shall not have assigned value other than ('collocationGroup', 'markerPosition', 'providesNavigableLocation', 'theNavaidEquipment') <keyword> Each </keyword><noun_concept> NavaidComponent </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('collocationGroup', 'markerPosition', 'providesNavigableLocation', 'theNavaidEquipment') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property NavaidComponent All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F85 Warning AIXM Model Each NavaidEquipmentDistance . annotation . Note . propertyName shall not have assigned value other than ('distance', 'distanceAccuracy', 'theNavaidEquipment') <keyword> Each </keyword><noun_concept> NavaidEquipmentDistance </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('distance', 'distanceAccuracy', 'theNavaidEquipment') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property NavaidEquipmentDistance All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F86 Warning AIXM Model Each NavaidEquipmentMonitoring . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'monitored') <keyword> Each </keyword><noun_concept> NavaidEquipmentMonitoring </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'monitored') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property NavaidEquipmentMonitoring All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F87 Warning AIXM Model Each NavaidOperationalStatus . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus', 'signalType') <keyword> Each </keyword><noun_concept> NavaidOperationalStatus </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus', 'signalType') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property NavaidOperationalStatus All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F88 Warning AIXM Model Each NavigationArea . annotation . Note . propertyName shall not have assigned value other than ('navigationAreaType', 'minimumCeiling', 'minimumVisibility', 'departure', 'sector', 'centrePointFixDesignatedPoint', 'centrePointNavaidSystem', 'centrePointPosition', 'centrePointRunwayPoint', 'centrePointAimingPoint', 'centrePointAirportReferencePoint') <keyword> Each </keyword><noun_concept> NavigationArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('navigationAreaType', 'minimumCeiling', 'minimumVisibility', 'departure', 'sector', 'centrePointFixDesignatedPoint', 'centrePointNavaidSystem', 'centrePointPosition', 'centrePointRunwayPoint', 'centrePointAimingPoint', 'centrePointAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property NavigationArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F89 Warning AIXM Model Each NavigationAreaRestriction . annotation . Note . propertyName shall not have assigned value other than ('type', 'procedure', 'designSurface', 'sectorDefinition') <keyword> Each </keyword><noun_concept> NavigationAreaRestriction </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'procedure', 'designSurface', 'sectorDefinition') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property NavigationAreaRestriction All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F8A Warning AIXM Model Each NavigationAreaSector . annotation . Note . propertyName shall not have assigned value other than ('sectorDefinition', 'significantObstacle', 'extent', 'sectorCriteria') <keyword> Each </keyword><noun_concept> NavigationAreaSector </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('sectorDefinition', 'significantObstacle', 'extent', 'sectorCriteria') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property NavigationAreaSector All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F8B Warning AIXM Model Each NDB . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'frequency', 'class', 'emissionBand') <keyword> Each </keyword><noun_concept> NDB </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'frequency', 'class', 'emissionBand') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property NDB All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F8C Warning AIXM Model Each Nitrogen . annotation . Note . propertyName shall not have assigned value other than ('type') <keyword> Each </keyword><noun_concept> Nitrogen </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Nitrogen All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F8D Warning AIXM Model Each ObstacleArea . annotation . Note . propertyName shall not have assigned value other than ('type', 'obstructionIdSurfaceCondition', 'surfaceExtent', 'obstacle', 'referenceOwnerOrganisation', 'referenceOwnerRunway', 'referenceOwnerAirport') <keyword> Each </keyword><noun_concept> ObstacleArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'obstructionIdSurfaceCondition', 'surfaceExtent', 'obstacle', 'referenceOwnerOrganisation', 'referenceOwnerRunway', 'referenceOwnerAirport') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ObstacleArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F8E Warning AIXM Model Each ObstacleAssessmentArea . annotation . Note . propertyName shall not have assigned value other than ('type', 'sectionNumber', 'slope', 'assessedAltitude', 'slopeLowerAltitude', 'gradientLowHigh', 'surfaceZone', 'safetyRegulation', 'aircraftCategory', 'significantObstacle', 'surface', 'startingCurve') <keyword> Each </keyword><noun_concept> ObstacleAssessmentArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'sectionNumber', 'slope', 'assessedAltitude', 'slopeLowerAltitude', 'gradientLowHigh', 'surfaceZone', 'safetyRegulation', 'aircraftCategory', 'significantObstacle', 'surface', 'startingCurve') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ObstacleAssessmentArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F8F Warning AIXM Model Each ObstaclePlacement . annotation . Note . propertyName shall not have assigned value other than ('obstacleBearing', 'obstacleDistance', 'pointType', 'obstaclePlacement') <keyword> Each </keyword><noun_concept> ObstaclePlacement </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('obstacleBearing', 'obstacleDistance', 'pointType', 'obstaclePlacement') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ObstaclePlacement All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F90 Warning AIXM Model Each Obstruction . annotation . Note . propertyName shall not have assigned value other than ('requiredClearance', 'minimumAltitude', 'surfacePenetration', 'slopePenetration', 'controlling', 'closeIn', 'theVerticalStructure', 'adjustment', 'obstaclePlacement') <keyword> Each </keyword><noun_concept> Obstruction </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('requiredClearance', 'minimumAltitude', 'surfacePenetration', 'slopePenetration', 'controlling', 'closeIn', 'theVerticalStructure', 'adjustment', 'obstaclePlacement') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Obstruction All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F91 Warning AIXM Model Each Oil . annotation . Note . propertyName shall not have assigned value other than ('category') <keyword> Each </keyword><noun_concept> Oil </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('category') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Oil All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F92 Warning AIXM Model Each OnlineContact . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'network', 'linkage', 'protocol', 'eMail') <keyword> Each </keyword><noun_concept> OnlineContact </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'network', 'linkage', 'protocol', 'eMail') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property OnlineContact All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F93 Warning AIXM Model Each OrganisationAuthority . annotation . Note . propertyName shall not have assigned value other than ('name', 'designator', 'type', 'military', 'contact', 'relatedOrganisationAuthority') <keyword> Each </keyword><noun_concept> OrganisationAuthority </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'designator', 'type', 'military', 'contact', 'relatedOrganisationAuthority') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property OrganisationAuthority All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F94 Warning AIXM Model Each OrganisationAuthorityAssociation . annotation . Note . propertyName shall not have assigned value other than ('type', 'theOrganisationAuthority') <keyword> Each </keyword><noun_concept> OrganisationAuthorityAssociation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'theOrganisationAuthority') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property OrganisationAuthorityAssociation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F95 Warning AIXM Model Each Oxygen . annotation . Note . propertyName shall not have assigned value other than ('type') <keyword> Each </keyword><noun_concept> Oxygen </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Oxygen All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F96 Warning AIXM Model Each PassengerService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'type') <keyword> Each </keyword><noun_concept> PassengerService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'airportHeliport', 'type') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property PassengerService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F97 Warning AIXM Model Each PointReference . annotation . Note . propertyName shall not have assigned value other than ('role', 'priorFixTolerance', 'postFixTolerance', 'point', 'facilityAngle', 'facilityDistance', 'fixToleranceArea') <keyword> Each </keyword><noun_concept> PointReference </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('role', 'priorFixTolerance', 'postFixTolerance', 'point', 'facilityAngle', 'facilityDistance', 'fixToleranceArea') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property PointReference All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F98 Warning AIXM Model Each PostalAddress . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'deliveryPoint', 'city', 'administrativeArea', 'postalCode', 'country') <keyword> Each </keyword><noun_concept> PostalAddress </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'deliveryPoint', 'city', 'administrativeArea', 'postalCode', 'country') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property PostalAddress All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F99 Warning AIXM Model Each ProcedureAvailability . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'status') <keyword> Each </keyword><noun_concept> ProcedureAvailability </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'status') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ProcedureAvailability All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F9A Warning AIXM Model Each ProcedureDME . annotation . Note . propertyName shall not have assigned value other than ('criticalDME', 'satisfactory', 'dME', 'segmentLeg') <keyword> Each </keyword><noun_concept> ProcedureDME </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('criticalDME', 'satisfactory', 'dME', 'segmentLeg') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ProcedureDME All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F9B Warning AIXM Model Each ProcedureTransition . annotation . Note . propertyName shall not have assigned value other than ('transitionId', 'type', 'instruction', 'vectorHeading', 'departureRunwayTransition', 'trajectory', 'transitionLeg') <keyword> Each </keyword><noun_concept> ProcedureTransition </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('transitionId', 'type', 'instruction', 'vectorHeading', 'departureRunwayTransition', 'trajectory', 'transitionLeg') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ProcedureTransition All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F9C Warning AIXM Model Each ProcedureTransitionLeg . annotation . Note . propertyName shall not have assigned value other than ('seqNumberARINC', 'theSegmentLeg') <keyword> Each </keyword><noun_concept> ProcedureTransitionLeg </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('seqNumberARINC', 'theSegmentLeg') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ProcedureTransitionLeg All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F9D Warning AIXM Model Each RadioCommunicationChannel . annotation . Note . propertyName shall not have assigned value other than ('mode', 'rank', 'frequencyTransmission', 'frequencyReception', 'channel', 'logon', 'emissionType', 'selectiveCall', 'flightChecked', 'trafficDirection', 'location', 'availability') <keyword> Each </keyword><noun_concept> RadioCommunicationChannel </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('mode', 'rank', 'frequencyTransmission', 'frequencyReception', 'channel', 'logon', 'emissionType', 'selectiveCall', 'flightChecked', 'trafficDirection', 'location', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RadioCommunicationChannel All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F9E Warning AIXM Model Each RadioCommunicationOperationalStatus . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus') <keyword> Each </keyword><noun_concept> RadioCommunicationOperationalStatus </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RadioCommunicationOperationalStatus All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F9F Warning AIXM Model Each RadioFrequencyArea . annotation . Note . propertyName shall not have assigned value other than ('type', 'angleScallop', 'signalType', 'sector', 'extent', 'equipmentNavaidEquipment', 'equipmentFrequency', 'equipmentSpecialNavigationStation', 'equipmentRadar', 'equipmentPrecisionApproachRadar') <keyword> Each </keyword><noun_concept> RadioFrequencyArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'angleScallop', 'signalType', 'sector', 'extent', 'equipmentNavaidEquipment', 'equipmentFrequency', 'equipmentSpecialNavigationStation', 'equipmentRadar', 'equipmentPrecisionApproachRadar') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RadioFrequencyArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA0 Warning AIXM Model Each Route . annotation . Note . propertyName shall not have assigned value other than ('designatorPrefix', 'designatorSecondLetter', 'designatorNumber', 'multipleIdentifier', 'locationDesignator', 'name', 'type', 'flightRule', 'internationalUse', 'militaryUse', 'militaryTrainingType', 'userOrganisation') <keyword> Each </keyword><noun_concept> Route </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designatorPrefix', 'designatorSecondLetter', 'designatorNumber', 'multipleIdentifier', 'locationDesignator', 'name', 'type', 'flightRule', 'internationalUse', 'militaryUse', 'militaryTrainingType', 'userOrganisation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Route All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA1 Warning AIXM Model Each RouteAvailability . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'direction', 'cardinalDirection', 'status', 'levels') <keyword> Each </keyword><noun_concept> RouteAvailability </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'direction', 'cardinalDirection', 'status', 'levels') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RouteAvailability All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA2 Warning AIXM Model Each RouteDME . annotation . Note . propertyName shall not have assigned value other than ('criticalDME', 'satisfactory', 'referencedDME', 'applicableRoutePortion') <keyword> Each </keyword><noun_concept> RouteDME </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('criticalDME', 'satisfactory', 'referencedDME', 'applicableRoutePortion') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RouteDME All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA3 Warning AIXM Model Each RoutePortion . annotation . Note . propertyName shall not have assigned value other than ('referencedRoute', 'startFixDesignatedPoint', 'startNavaidSystem', 'startPosition', 'startRunwayPoint', 'startAimingPoint', 'startAirportReferencePoint', 'endFixDesignatedPoint', 'endNavaidSystem', 'endPosition', 'endRunwayPoint', 'endAimingPoint', 'endAirportReferencePoint', 'intermediatePointFixDesignatedPoint', 'intermediatePointNavaidSystem', 'intermediatePointPosition', 'intermediatePointRunwayPoint', 'intermediatePointAimingPoint', 'intermediatePointAirportReferencePoint') <keyword> Each </keyword><noun_concept> RoutePortion </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('referencedRoute', 'startFixDesignatedPoint', 'startNavaidSystem', 'startPosition', 'startRunwayPoint', 'startAimingPoint', 'startAirportReferencePoint', 'endFixDesignatedPoint', 'endNavaidSystem', 'endPosition', 'endRunwayPoint', 'endAimingPoint', 'endAirportReferencePoint', 'intermediatePointFixDesignatedPoint', 'intermediatePointNavaidSystem', 'intermediatePointPosition', 'intermediatePointRunwayPoint', 'intermediatePointAimingPoint', 'intermediatePointAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RoutePortion All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA4 Warning AIXM Model Each RouteSegment . annotation . Note . propertyName shall not have assigned value other than ('level', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'minimumObstacleClearanceAltitude', 'pathType', 'trueTrack', 'magneticTrack', 'reverseTrueTrack', 'reverseMagneticTrack', 'length', 'widthLeft', 'widthRight', 'turnDirection', 'signalGap', 'minimumEnrouteAltitude', 'minimumCrossingAtEnd', 'minimumCrossingAtEndReference', 'maximumCrossingAtEnd', 'maximumCrossingAtEndReference', 'navigationType', 'requiredNavigationPerformance', 'designatorSuffix', 'start', 'routeFormed', 'evaluationArea', 'curveExtent', 'end', 'availability') <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('level', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'minimumObstacleClearanceAltitude', 'pathType', 'trueTrack', 'magneticTrack', 'reverseTrueTrack', 'reverseMagneticTrack', 'length', 'widthLeft', 'widthRight', 'turnDirection', 'signalGap', 'minimumEnrouteAltitude', 'minimumCrossingAtEnd', 'minimumCrossingAtEndReference', 'maximumCrossingAtEnd', 'maximumCrossingAtEndReference', 'navigationType', 'requiredNavigationPerformance', 'designatorSuffix', 'start', 'routeFormed', 'evaluationArea', 'curveExtent', 'end', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RouteSegment All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA5 Warning AIXM Model Each RulesProcedures . annotation . Note . propertyName shall not have assigned value other than ('category', 'title', 'content', 'affectedLocation', 'affectedArea') <keyword> Each </keyword><noun_concept> RulesProcedures </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('category', 'title', 'content', 'affectedLocation', 'affectedArea') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RulesProcedures All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA6 Warning AIXM Model Each Runway . annotation . Note . propertyName shall not have assigned value other than ('designator', 'type', 'nominalLength', 'lengthAccuracy', 'nominalWidth', 'widthAccuracy', 'widthShoulder', 'lengthStrip', 'widthStrip', 'lengthOffset', 'widthOffset', 'abandoned', 'surfaceProperties', 'associatedAirportHeliport', 'overallContaminant', 'areaContaminant') <keyword> Each </keyword><noun_concept> Runway </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'type', 'nominalLength', 'lengthAccuracy', 'nominalWidth', 'widthAccuracy', 'widthShoulder', 'lengthStrip', 'widthStrip', 'lengthOffset', 'widthOffset', 'abandoned', 'surfaceProperties', 'associatedAirportHeliport', 'overallContaminant', 'areaContaminant') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Runway All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA7 Warning AIXM Model Each RunwayCentrelinePoint . annotation . Note . propertyName shall not have assigned value other than ('role', 'designator', 'location', 'onRunway', 'associatedDeclaredDistance', 'navaidEquipment') <keyword> Each </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('role', 'designator', 'location', 'onRunway', 'associatedDeclaredDistance', 'navaidEquipment') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayCentrelinePoint All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA8 Warning AIXM Model Each RunwayDeclaredDistance . annotation . Note . propertyName shall not have assigned value other than ('type', 'declaredValue') <keyword> Each </keyword><noun_concept> RunwayDeclaredDistance </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'declaredValue') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayDeclaredDistance All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FA9 Warning AIXM Model Each RunwayDeclaredDistanceValue . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'distance', 'distanceAccuracy') <keyword> Each </keyword><noun_concept> RunwayDeclaredDistanceValue </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'distance', 'distanceAccuracy') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayDeclaredDistanceValue All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FAA Warning AIXM Model Each RunwayDirection . annotation . Note . propertyName shall not have assigned value other than ('designator', 'trueBearing', 'trueBearingAccuracy', 'magneticBearing', 'patternVFR', 'slopeTDZ', 'elevationTDZ', 'elevationTDZAccuracy', 'approachMarkingType', 'approachMarkingCondition', 'classLightingJAR', 'precisionApproachGuidance', 'usedRunway', 'startingElement', 'availability') <keyword> Each </keyword><noun_concept> RunwayDirection </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'trueBearing', 'trueBearingAccuracy', 'magneticBearing', 'patternVFR', 'slopeTDZ', 'elevationTDZ', 'elevationTDZAccuracy', 'approachMarkingType', 'approachMarkingCondition', 'classLightingJAR', 'precisionApproachGuidance', 'usedRunway', 'startingElement', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayDirection All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FAB Warning AIXM Model Each RunwayDirectionLightSystem . annotation . Note . propertyName shall not have assigned value other than ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'associatedRunwayDirection') <keyword> Each </keyword><noun_concept> RunwayDirectionLightSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'associatedRunwayDirection') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayDirectionLightSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FAC Warning AIXM Model Each RunwayElement . annotation . Note . propertyName shall not have assigned value other than ('type', 'length', 'width', 'gradeSeparation', 'surfaceProperties', 'associatedRunway', 'extent', 'availability') <keyword> Each </keyword><noun_concept> RunwayElement </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'length', 'width', 'gradeSeparation', 'surfaceProperties', 'associatedRunway', 'extent', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayElement All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FAD Warning AIXM Model Each RunwayProtectArea . annotation . Note . propertyName shall not have assigned value other than ('width', 'length', 'lighting', 'obstacleFree', 'surfaceProperties', 'extent', 'type', 'status', 'protectedRunwayDirection') <keyword> Each </keyword><noun_concept> RunwayProtectArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('width', 'length', 'lighting', 'obstacleFree', 'surfaceProperties', 'extent', 'type', 'status', 'protectedRunwayDirection') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayProtectArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FAE Warning AIXM Model Each RunwayProtectAreaLightSystem . annotation . Note . propertyName shall not have assigned value other than ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'lightedArea') <keyword> Each </keyword><noun_concept> RunwayProtectAreaLightSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'lightedArea') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayProtectAreaLightSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FAF Warning AIXM Model Each SafeAltitudeArea . annotation . Note . propertyName shall not have assigned value other than ('safeAreaType', 'sector', 'location', 'centrePointFixDesignatedPoint', 'centrePointNavaidSystem', 'centrePointPosition', 'centrePointRunwayPoint', 'centrePointAimingPoint', 'centrePointAirportReferencePoint') <keyword> Each </keyword><noun_concept> SafeAltitudeArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('safeAreaType', 'sector', 'location', 'centrePointFixDesignatedPoint', 'centrePointNavaidSystem', 'centrePointPosition', 'centrePointRunwayPoint', 'centrePointAimingPoint', 'centrePointAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SafeAltitudeArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB0 Warning AIXM Model Each SafeAltitudeAreaSector . annotation . Note . propertyName shall not have assigned value other than ('bufferWidth', 'extent', 'significantObstacle', 'sectorDefinition') <keyword> Each </keyword><noun_concept> SafeAltitudeAreaSector </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('bufferWidth', 'extent', 'significantObstacle', 'sectorDefinition') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SafeAltitudeAreaSector All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB1 Warning AIXM Model Each SearchRescueService . annotation . Note . propertyName shall not have assigned value other than ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'type', 'clientAirspace', 'clientRoute') <keyword> Each </keyword><noun_concept> SearchRescueService </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightOperations', 'rank', 'compliantICAO', 'name', 'location', 'serviceProvider', 'callsign', 'radioCommunication', 'groundCommunication', 'availability', 'type', 'clientAirspace', 'clientRoute') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SearchRescueService All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB2 Warning AIXM Model Each SectorDesign . annotation . Note . propertyName shall not have assigned value other than ('turnDirection', 'designGradient', 'terminationAltitude', 'turnPermitted') <keyword> Each </keyword><noun_concept> SectorDesign </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('turnDirection', 'designGradient', 'terminationAltitude', 'turnPermitted') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SectorDesign All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB3 Warning AIXM Model Each ServiceOperationalStatus . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus') <keyword> Each </keyword><noun_concept> ServiceOperationalStatus </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ServiceOperationalStatus All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB4 Warning AIXM Model Each SignificantPointInAirspace . annotation . Note . propertyName shall not have assigned value other than ('type', 'relativeLocation', 'containingAirspace', 'locationFixDesignatedPoint', 'locationNavaidSystem', 'locationPosition', 'locationRunwayPoint', 'locationAimingPoint', 'locationAirportReferencePoint') <keyword> Each </keyword><noun_concept> SignificantPointInAirspace </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'relativeLocation', 'containingAirspace', 'locationFixDesignatedPoint', 'locationNavaidSystem', 'locationPosition', 'locationRunwayPoint', 'locationAimingPoint', 'locationAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SignificantPointInAirspace All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB5 Warning AIXM Model Each SpecialDate . annotation . Note . propertyName shall not have assigned value other than ('type', 'dateDay', 'dateYear', 'name', 'authority') <keyword> Each </keyword><noun_concept> SpecialDate </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'dateDay', 'dateYear', 'name', 'authority') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SpecialDate All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB6 Warning AIXM Model Each SpecialNavigationStation . annotation . Note . propertyName shall not have assigned value other than ('name', 'type', 'frequency', 'emission', 'systemChain', 'responsibleOrganisation', 'position', 'availability') <keyword> Each </keyword><noun_concept> SpecialNavigationStation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'type', 'frequency', 'emission', 'systemChain', 'responsibleOrganisation', 'position', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SpecialNavigationStation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB7 Warning AIXM Model Each SpecialNavigationStationStatus . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus') <keyword> Each </keyword><noun_concept> SpecialNavigationStationStatus </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SpecialNavigationStationStatus All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB8 Warning AIXM Model Each SpecialNavigationSystem . annotation . Note . propertyName shall not have assigned value other than ('type', 'designator', 'name', 'responsibleOrganisation') <keyword> Each </keyword><noun_concept> SpecialNavigationSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'designator', 'name', 'responsibleOrganisation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SpecialNavigationSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FB9 Warning AIXM Model Each StandardInstrumentArrival . annotation . Note . propertyName shall not have assigned value other than ('communicationFailureInstruction', 'instruction', 'designCriteria', 'codingStandard', 'flightChecked', 'name', 'rNAV', 'availability', 'airportHeliport', 'aircraftCharacteristic', 'flightTransition', 'safeAltitude', 'designator', 'arrival', 'guidanceFacilityNavaid', 'guidanceFacilityRadar', 'guidanceFacilitySpecialNavigationSystem') <keyword> Each </keyword><noun_concept> StandardInstrumentArrival </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('communicationFailureInstruction', 'instruction', 'designCriteria', 'codingStandard', 'flightChecked', 'name', 'rNAV', 'availability', 'airportHeliport', 'aircraftCharacteristic', 'flightTransition', 'safeAltitude', 'designator', 'arrival', 'guidanceFacilityNavaid', 'guidanceFacilityRadar', 'guidanceFacilitySpecialNavigationSystem') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property StandardInstrumentArrival All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FBA Warning AIXM Model Each StandardInstrumentDeparture . annotation . Note . propertyName shall not have assigned value other than ('communicationFailureInstruction', 'instruction', 'designCriteria', 'codingStandard', 'flightChecked', 'name', 'rNAV', 'availability', 'airportHeliport', 'aircraftCharacteristic', 'flightTransition', 'safeAltitude', 'designator', 'contingencyRoute', 'takeoff', 'guidanceFacilityNavaid', 'guidanceFacilityRadar', 'guidanceFacilitySpecialNavigationSystem') <keyword> Each </keyword><noun_concept> StandardInstrumentDeparture </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('communicationFailureInstruction', 'instruction', 'designCriteria', 'codingStandard', 'flightChecked', 'name', 'rNAV', 'availability', 'airportHeliport', 'aircraftCharacteristic', 'flightTransition', 'safeAltitude', 'designator', 'contingencyRoute', 'takeoff', 'guidanceFacilityNavaid', 'guidanceFacilityRadar', 'guidanceFacilitySpecialNavigationSystem') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property StandardInstrumentDeparture All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FBB Warning AIXM Model Each StandardLevel . annotation . Note . propertyName shall not have assigned value other than ('verticalDistance') <keyword> Each </keyword><noun_concept> StandardLevel </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('verticalDistance') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property StandardLevel All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FBC Warning AIXM Model Each StandardLevelColumn . annotation . Note . propertyName shall not have assigned value other than ('series', 'unitOfMeasurement', 'separation', 'level', 'levelTable') <keyword> Each </keyword><noun_concept> StandardLevelColumn </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('series', 'unitOfMeasurement', 'separation', 'level', 'levelTable') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property StandardLevelColumn All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FBD Warning AIXM Model Each StandardLevelSector . annotation . Note . propertyName shall not have assigned value other than ('flightRule', 'fromTrack', 'toTrack', 'angleType', 'applicableAirspace', 'applicableLevelColumn') <keyword> Each </keyword><noun_concept> StandardLevelSector </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightRule', 'fromTrack', 'toTrack', 'angleType', 'applicableAirspace', 'applicableLevelColumn') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property StandardLevelSector All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FBE Warning AIXM Model Each StandardLevelTable . annotation . Note . propertyName shall not have assigned value other than ('name', 'standardICAO') <keyword> Each </keyword><noun_concept> StandardLevelTable </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'standardICAO') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property StandardLevelTable All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FBF Warning AIXM Model Each Surface . annotation . Note . propertyName shall not have assigned value other than ('horizontalAccuracy') <keyword> Each </keyword><noun_concept> Surface </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('horizontalAccuracy') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Surface All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC0 Warning AIXM Model Each SurfaceCharacteristics . annotation . Note . propertyName shall not have assigned value other than ('composition', 'preparation', 'surfaceCondition', 'classPCN', 'pavementTypePCN', 'pavementSubgradePCN', 'maxTyrePressurePCN', 'evaluationMethodPCN', 'classLCN', 'weightSIWL', 'tyrePressureSIWL', 'weightAUW') <keyword> Each </keyword><noun_concept> SurfaceCharacteristics </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('composition', 'preparation', 'surfaceCondition', 'classPCN', 'pavementTypePCN', 'pavementSubgradePCN', 'maxTyrePressurePCN', 'evaluationMethodPCN', 'classLCN', 'weightSIWL', 'tyrePressureSIWL', 'weightAUW') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SurfaceCharacteristics All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC1 Warning AIXM Model Each SurveyControlPoint . annotation . Note . propertyName shall not have assigned value other than ('designator', 'associatedAirportHeliport', 'location') <keyword> Each </keyword><noun_concept> SurveyControlPoint </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'associatedAirportHeliport', 'location') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SurveyControlPoint All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC2 Warning AIXM Model Each TACAN . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'channel', 'declination') <keyword> Each </keyword><noun_concept> TACAN </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'channel', 'declination') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TACAN All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC3 Warning AIXM Model Each TaxiHoldingPosition . annotation . Note . propertyName shall not have assigned value other than ('landingCategory', 'status', 'associatedGuidanceLine', 'protectedRunway', 'location') <keyword> Each </keyword><noun_concept> TaxiHoldingPosition </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('landingCategory', 'status', 'associatedGuidanceLine', 'protectedRunway', 'location') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TaxiHoldingPosition All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC4 Warning AIXM Model Each TaxiHoldingPositionLightSystem . annotation . Note . propertyName shall not have assigned value other than ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'type', 'taxiHolding') <keyword> Each </keyword><noun_concept> TaxiHoldingPositionLightSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'type', 'taxiHolding') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TaxiHoldingPositionLightSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC5 Warning AIXM Model Each Taxiway . annotation . Note . propertyName shall not have assigned value other than ('designator', 'type', 'width', 'widthShoulder', 'length', 'abandoned', 'surfaceProperties', 'associatedAirportHeliport', 'contaminant', 'availability') <keyword> Each </keyword><noun_concept> Taxiway </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'type', 'width', 'widthShoulder', 'length', 'abandoned', 'surfaceProperties', 'associatedAirportHeliport', 'contaminant', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Taxiway All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC6 Warning AIXM Model Each TaxiwayElement . annotation . Note . propertyName shall not have assigned value other than ('type', 'length', 'width', 'gradeSeparation', 'surfaceProperties', 'associatedTaxiway', 'extent', 'availability') <keyword> Each </keyword><noun_concept> TaxiwayElement </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'length', 'width', 'gradeSeparation', 'surfaceProperties', 'associatedTaxiway', 'extent', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TaxiwayElement All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC7 Warning AIXM Model Each TaxiwayLightSystem . annotation . Note . propertyName shall not have assigned value other than ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'lightedTaxiway') <keyword> Each </keyword><noun_concept> TaxiwayLightSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'lightedTaxiway') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TaxiwayLightSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC8 Warning AIXM Model Each TelephoneContact . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'voice', 'facsimile') <keyword> Each </keyword><noun_concept> TelephoneContact </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'voice', 'facsimile') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TelephoneContact All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FC9 Warning AIXM Model Each TerminalArrivalArea . annotation . Note . propertyName shall not have assigned value other than ('arrivalAreaType', 'outerBufferWidth', 'lateralBufferWidth', 'buffer', 'sector', 'approachRNAV', 'iFFixDesignatedPoint', 'iFNavaidSystem', 'iFPosition', 'iFRunwayPoint', 'iFAimingPoint', 'iFAirportReferencePoint', 'iAFFixDesignatedPoint', 'iAFNavaidSystem', 'iIAFPosition', 'iIAFRunwayPoint', 'iAFAimingPoint', 'iAFAirportReferencePoint') <keyword> Each </keyword><noun_concept> TerminalArrivalArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('arrivalAreaType', 'outerBufferWidth', 'lateralBufferWidth', 'buffer', 'sector', 'approachRNAV', 'iFFixDesignatedPoint', 'iFNavaidSystem', 'iFPosition', 'iFRunwayPoint', 'iFAimingPoint', 'iFAirportReferencePoint', 'iAFFixDesignatedPoint', 'iAFNavaidSystem', 'iIAFPosition', 'iIAFRunwayPoint', 'iAFAimingPoint', 'iAFAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TerminalArrivalArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FCA Warning AIXM Model Each TerminalArrivalAreaSector . annotation . Note . propertyName shall not have assigned value other than ('flyByCode', 'procedureTurnRequired', 'altitudeDescription', 'sectorDefinition', 'extent', 'significantObstacle') <keyword> Each </keyword><noun_concept> TerminalArrivalAreaSector </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flyByCode', 'procedureTurnRequired', 'altitudeDescription', 'sectorDefinition', 'extent', 'significantObstacle') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TerminalArrivalAreaSector All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FCB Warning AIXM Model Each TerminalSegmentPoint . annotation . Note . propertyName shall not have assigned value other than ('reportingATC', 'flyOver', 'waypoint', 'radarGuidance', 'facilityMakeup', 'extendedServiceVolume', 'role', 'leadRadial', 'leadDME', 'indicatorFACF', 'pointChoiceFixDesignatedPoint', 'pointChoiceNavaidSystem', 'pointChoicePosition', 'pointChoiceRunwayPoint', 'pointChoiceAimingPoint', 'pointChoiceAirportReferencePoint') <keyword> Each </keyword><noun_concept> TerminalSegmentPoint </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('reportingATC', 'flyOver', 'waypoint', 'radarGuidance', 'facilityMakeup', 'extendedServiceVolume', 'role', 'leadRadial', 'leadDME', 'indicatorFACF', 'pointChoiceFixDesignatedPoint', 'pointChoiceNavaidSystem', 'pointChoicePosition', 'pointChoiceRunwayPoint', 'pointChoiceAimingPoint', 'pointChoiceAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TerminalSegmentPoint All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FCC Warning AIXM Model Each Timesheet . annotation . Note . propertyName shall not have assigned value other than ('timeReference', 'startDate', 'endDate', 'day', 'dayTil', 'startTime', 'startEvent', 'startTimeRelativeEvent', 'startEventInterpretation', 'endTime', 'endEvent', 'endTimeRelativeEvent', 'endEventInterpretation', 'daylightSavingAdjust', 'excluded') <keyword> Each </keyword><noun_concept> Timesheet </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeReference', 'startDate', 'endDate', 'day', 'dayTil', 'startTime', 'startEvent', 'startTimeRelativeEvent', 'startEventInterpretation', 'endTime', 'endEvent', 'endTimeRelativeEvent', 'endEventInterpretation', 'daylightSavingAdjust', 'excluded') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Timesheet All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FCD Warning AIXM Model Each TouchDownLiftOff . annotation . Note . propertyName shall not have assigned value other than ('designator', 'length', 'width', 'slope', 'helicopterClass', 'abandoned', 'aimingPoint', 'extent', 'surfaceProperties', 'associatedAirportHeliport', 'approachTakeOffArea', 'contaminant', 'availability') <keyword> Each </keyword><noun_concept> TouchDownLiftOff </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'length', 'width', 'slope', 'helicopterClass', 'abandoned', 'aimingPoint', 'extent', 'surfaceProperties', 'associatedAirportHeliport', 'approachTakeOffArea', 'contaminant', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TouchDownLiftOff All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FCE Warning AIXM Model Each TouchDownLiftOffLightSystem . annotation . Note . propertyName shall not have assigned value other than ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'lightedTouchDownLiftOff') <keyword> Each </keyword><noun_concept> TouchDownLiftOffLightSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'position', 'lightedTouchDownLiftOff') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TouchDownLiftOffLightSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FCF Warning AIXM Model Each TouchDownLiftOffSafeArea . annotation . Note . propertyName shall not have assigned value other than ('width', 'length', 'lighting', 'obstacleFree', 'surfaceProperties', 'extent', 'protectedTouchDownLiftOff') <keyword> Each </keyword><noun_concept> TouchDownLiftOffSafeArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('width', 'length', 'lighting', 'obstacleFree', 'surfaceProperties', 'extent', 'protectedTouchDownLiftOff') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TouchDownLiftOffSafeArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FD0 Warning AIXM Model Each Unit . annotation . Note . propertyName shall not have assigned value other than ('name', 'type', 'compliantICAO', 'designator', 'military', 'position', 'airportLocation', 'ownerOrganisation', 'contact', 'relatedUnit', 'availability') <keyword> Each </keyword><noun_concept> Unit </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'type', 'compliantICAO', 'designator', 'military', 'position', 'airportLocation', 'ownerOrganisation', 'contact', 'relatedUnit', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Unit All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FD1 Warning AIXM Model Each UnitDependency . annotation . Note . propertyName shall not have assigned value other than ('type', 'theUnit') <keyword> Each </keyword><noun_concept> UnitDependency </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'theUnit') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property UnitDependency All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FD2 Warning AIXM Model Each VerticalStructure . annotation . Note . propertyName shall not have assigned value other than ('name', 'type', 'lighted', 'markingICAOStandard', 'group', 'length', 'width', 'radius', 'lightingICAOStandard', 'synchronisedLighting', 'marker', 'part', 'hostedPassengerService', 'supportedGroundLight', 'hostedNavaidEquipment', 'hostedSpecialNavStation', 'hostedUnit', 'hostedOrganisation', 'supportedService', 'lightingAvailability') <keyword> Each </keyword><noun_concept> VerticalStructure </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'type', 'lighted', 'markingICAOStandard', 'group', 'length', 'width', 'radius', 'lightingICAOStandard', 'synchronisedLighting', 'marker', 'part', 'hostedPassengerService', 'supportedGroundLight', 'hostedNavaidEquipment', 'hostedSpecialNavStation', 'hostedUnit', 'hostedOrganisation', 'supportedService', 'lightingAvailability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property VerticalStructure All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FD3 Warning AIXM Model Each VerticalStructurePart . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'verticalExtent', 'verticalExtentAccuracy', 'type', 'constructionStatus', 'markingPattern', 'markingFirstColour', 'markingSecondColour', 'mobile', 'frangible', 'visibleMaterial', 'designator', 'lighting', 'horizontalProjectionSurfaceExtent', 'horizontalProjectionLinearExtent', 'horizontalProjectionLocation') <keyword> Each </keyword><noun_concept> VerticalStructurePart </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'verticalExtent', 'verticalExtentAccuracy', 'type', 'constructionStatus', 'markingPattern', 'markingFirstColour', 'markingSecondColour', 'mobile', 'frangible', 'visibleMaterial', 'designator', 'lighting', 'horizontalProjectionSurfaceExtent', 'horizontalProjectionLinearExtent', 'horizontalProjectionLocation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property VerticalStructurePart All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FD4 Warning AIXM Model Each VisualGlideSlopeIndicator . annotation . Note . propertyName shall not have assigned value other than ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'type', 'position', 'numberBox', 'portable', 'slopeAngle', 'minimumEyeHeightOverThreshold', 'runwayDirection') <keyword> Each </keyword><noun_concept> VisualGlideSlopeIndicator </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('emergencyLighting', 'intensityLevel', 'colour', 'element', 'availability', 'type', 'position', 'numberBox', 'portable', 'slopeAngle', 'minimumEyeHeightOverThreshold', 'runwayDirection') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property VisualGlideSlopeIndicator All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FD5 Warning AIXM Model Each VOR . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'type', 'frequency', 'zeroBearingDirection', 'declination') <keyword> Each </keyword><noun_concept> VOR </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'type', 'frequency', 'zeroBearingDirection', 'declination') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property VOR All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FD6 Warning AIXM Model Each HoldingPattern . annotation . Note . propertyName shall not have assigned value other than ('type', 'outboundCourse', 'outboundCourseType', 'inboundCourse', 'turnDirection', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'speedLimit', 'instruction', 'nonStandardHolding', 'outboundLegSpanEndPoint', 'outboundLegSpanEndDistance', 'outboundLegSpanEndTime', 'holdingPoint', 'extent') <keyword> Each </keyword><noun_concept> HoldingPattern </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'outboundCourse', 'outboundCourseType', 'inboundCourse', 'turnDirection', 'upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'speedLimit', 'instruction', 'nonStandardHolding', 'outboundLegSpanEndPoint', 'outboundLegSpanEndDistance', 'outboundLegSpanEndTime', 'holdingPoint', 'extent') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property HoldingPattern All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2FD7 Warning AIXM Model Each AirportHeliport . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'locationIndicatorICAO', 'designatorIATA', 'type', 'certifiedICAO', 'privateUse', 'controlType', 'fieldElevation', 'fieldElevationAccuracy', 'verticalDatum', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'magneticVariationChange', 'referenceTemperature', 'altimeterCheckLocation', 'secondaryPowerSupply', 'windDirectionIndicator', 'landingDirectionIndicator', 'transitionAltitude', 'transitionLevel', 'lowestTemperature', 'abandoned', 'certificationDate', 'certificationExpirationDate', 'contaminant', 'servedCity', 'responsibleOrganisation', 'aRP', 'aviationBoundary', 'altimeterSource', 'contact', 'availability') <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'locationIndicatorICAO', 'designatorIATA', 'type', 'certifiedICAO', 'privateUse', 'controlType', 'fieldElevation', 'fieldElevationAccuracy', 'verticalDatum', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'magneticVariationChange', 'referenceTemperature', 'altimeterCheckLocation', 'secondaryPowerSupply', 'windDirectionIndicator', 'landingDirectionIndicator', 'transitionAltitude', 'transitionLevel', 'lowestTemperature', 'abandoned', 'certificationDate', 'certificationExpirationDate', 'contaminant', 'servedCity', 'responsibleOrganisation', 'aRP', 'aviationBoundary', 'altimeterSource', 'contact', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportHeliport All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC396 Warning AIXM Model Each AirportProtectionAreaMarking . annotation . Note . propertyName shall not have assigned value other than ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedProtectionArea') <keyword> Each </keyword><noun_concept> AirportProtectionAreaMarking </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedProtectionArea') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportProtectionAreaMarking All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC39B Warning AIXM Model Each ApronMarking . annotation . Note . propertyName shall not have assigned value other than ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedApron') <keyword> Each </keyword><noun_concept> ApronMarking </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedApron') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApronMarking All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC39F Warning AIXM Model Each DeicingArea . annotation . Note . propertyName shall not have assigned value other than ('associatedApron', 'taxiwayLocation', 'standLocation', 'surfaceProperties', 'extent', 'availability') <keyword> Each </keyword><noun_concept> DeicingArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('associatedApron', 'taxiwayLocation', 'standLocation', 'surfaceProperties', 'extent', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DeicingArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A0 Warning AIXM Model Each DeicingAreaMarking . annotation . Note . propertyName shall not have assigned value other than ('markingICAOStandard', 'condition', 'element', 'markedDeicingArea') <keyword> Each </keyword><noun_concept> DeicingAreaMarking </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('markingICAOStandard', 'condition', 'element', 'markedDeicingArea') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DeicingAreaMarking All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3AA Warning AIXM Model Each GuidanceLineMarking . annotation . Note . propertyName shall not have assigned value other than ('markingICAOStandard', 'condition', 'element', 'markedGuidanceLine') <keyword> Each </keyword><noun_concept> GuidanceLineMarking </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('markingICAOStandard', 'condition', 'element', 'markedGuidanceLine') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property GuidanceLineMarking All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3AC Warning AIXM Model Each MarkingElement . annotation . Note . propertyName shall not have assigned value other than ('colour', 'style', 'extentCurveExtent', 'extentSurfaceExtent', 'extentLocation') <keyword> Each </keyword><noun_concept> MarkingElement </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('colour', 'style', 'extentCurveExtent', 'extentSurfaceExtent', 'extentLocation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property MarkingElement All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3AE Warning AIXM Model Each NonMovementArea . annotation . Note . propertyName shall not have assigned value other than ('associatedAirportHeliport', 'extent') <keyword> Each </keyword><noun_concept> NonMovementArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('associatedAirportHeliport', 'extent') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property NonMovementArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B7 Warning AIXM Model Each Road . annotation . Note . propertyName shall not have assigned value other than ('designator', 'status', 'type', 'abandoned', 'associatedAirport', 'surfaceProperties', 'accessibleStand', 'surfaceExtent') <keyword> Each </keyword><noun_concept> Road </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'status', 'type', 'abandoned', 'associatedAirport', 'surfaceProperties', 'accessibleStand', 'surfaceExtent') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Road All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B8 Warning AIXM Model Each RunwayBlastPad . annotation . Note . propertyName shall not have assigned value other than ('length', 'status', 'usedRunwayDirection', 'extent', 'surfaceProperties') <keyword> Each </keyword><noun_concept> RunwayBlastPad </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('length', 'status', 'usedRunwayDirection', 'extent', 'surfaceProperties') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayBlastPad All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3BA Warning AIXM Model Each RunwayMarking . annotation . Note . propertyName shall not have assigned value other than ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedRunway') <keyword> Each </keyword><noun_concept> RunwayMarking </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedRunway') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayMarking All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3BC Warning AIXM Model Each RunwayVisualRange . annotation . Note . propertyName shall not have assigned value other than ('readingPosition', 'associatedRunwayDirection', 'location') <keyword> Each </keyword><noun_concept> RunwayVisualRange </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('readingPosition', 'associatedRunwayDirection', 'location') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayVisualRange All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C1 Warning AIXM Model Each StandMarking . annotation . Note . propertyName shall not have assigned value other than ('markingICAOStandard', 'condition', 'element', 'markedStand') <keyword> Each </keyword><noun_concept> StandMarking </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('markingICAOStandard', 'condition', 'element', 'markedStand') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property StandMarking All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C4 Warning AIXM Model Each TaxiHoldingPositionMarking . annotation . Note . propertyName shall not have assigned value other than ('markingICAOStandard', 'condition', 'element', 'markedTaxiHold') <keyword> Each </keyword><noun_concept> TaxiHoldingPositionMarking </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('markingICAOStandard', 'condition', 'element', 'markedTaxiHold') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TaxiHoldingPositionMarking All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C6 Warning AIXM Model Each TaxiwayMarking . annotation . Note . propertyName shall not have assigned value other than ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedTaxiway', 'markedElement') <keyword> Each </keyword><noun_concept> TaxiwayMarking </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedTaxiway', 'markedElement') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TaxiwayMarking All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C8 Warning AIXM Model Each TouchDownLiftOffMarking . annotation . Note . propertyName shall not have assigned value other than ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedTouchDownLiftOff') <keyword> Each </keyword><noun_concept> TouchDownLiftOffMarking </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('markingICAOStandard', 'condition', 'element', 'markingLocation', 'markedTouchDownLiftOff') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TouchDownLiftOffMarking All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3CC Warning AIXM Model Each WorkArea . annotation . Note . propertyName shall not have assigned value other than ('type', 'plannedOperational', 'associatedAirportHeliport', 'extent', 'activation') <keyword> Each </keyword><noun_concept> WorkArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'plannedOperational', 'associatedAirportHeliport', 'extent', 'activation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property WorkArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3CD Warning AIXM Model Each WorkareaActivity . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'isActive') <keyword> Each </keyword><noun_concept> WorkareaActivity </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'isActive') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property WorkareaActivity All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1ADB05 Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation DirectionFinder has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of DirectionFinder shall be published with 1 sec resolution (aerodrome navaid equipment) Latitude and Longitude of DirectionFinder shall be published with 1 sec resolution (aerodrome navaid equipment) DirectionFinder location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - DirectionFinder
AIXM-5.1_RULE-1ADB0A Warning ICAO Annex 15 Table A7-1 It is prohibited that a NavaidEquipment specialisation SDF has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of SDF shall be published with 1 sec resolution (aerodrome navaid equipment) Latitude and Longitude of SDF shall be published with 1 sec resolution (aerodrome navaid equipment) SDF location All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - SDF
AIXM-5.1_RULE-1AE2D1 ICAO Annex 11 Each UnplannedHolding with authorizedAltitude.uom equal-to ('FL', 'SM') shall have authorizedAltitude value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> UnplannedHolding </noun_concept><keyword> with </keyword><noun_concept> authorizedAltitude.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> authorizedAltitude </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have at 1, 2 or 3 digits Found UnplannedHolding with authorizedAltitude value that does not correspond to 'FL' (or 'SM') as unit of measurement UnplannedHolding authorizedAltitude All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1AE2D8 ICAO Annex 11 Each AerialRefuellingAnchor with refuellingBaseLevel.uom equal-to ('FL', 'SM') shall have refuellingBaseLevel value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> AerialRefuellingAnchor </noun_concept><keyword> with </keyword><noun_concept> refuellingBaseLevel.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> refuellingBaseLevel </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have at 1, 2 or 3 digits Found AerialRefuellingAnchor with refuellingBaseLevel value that does not correspond to 'FL' (or 'SM') as unit of measurement AerialRefuellingAnchor refuellingBaseLevel All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1AE2D9 ICAO Annex 11 Each FlightRestrictionLevel with lowerLevel.uom equal-to ('FL', 'SM') shall have lowerLevel value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> FlightRestrictionLevel </noun_concept><keyword> with </keyword><noun_concept> lowerLevel.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> lowerLevel </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have at 1, 2 or 3 digits Found FlightRestrictionLevel with lowerLevel value that does not correspond to 'FL' (or 'SM') as unit of measurement FlightRestrictionLevel lowerLevel All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1AE2E7 ICAO Annex 11 Each FlightRestrictionLevel with upperLevel.uom equal-to ('FL', 'SM') shall have upperLevel value expressed with 1, 2 or 3 digits <keyword> Each </keyword><noun_concept> FlightRestrictionLevel </noun_concept><keyword> with </keyword><noun_concept> upperLevel.uom </noun_concept><keyword> equal-to </keyword><name> ('FL', 'SM') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> upperLevel </noun_concept> If the unit of measurement for an altitude is 'FL' (flight level) or 'SM' (standard meters), then the value should have at 1, 2 or 3 digits Found FlightRestrictionLevel with upperLevel value that does not correspond to 'FL' (or 'SM') as unit of measurement FlightRestrictionLevel upperLevel All Recommended practice (ICAO, industry, etc.) Flight Levels (FL) and Standard Meters (SM) number of digits
AIXM-5.1_RULE-1A13C9 Warning AIXM Model Each AirspaceLayer with assigned upperLimit value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> AirspaceLayer </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimit without vertical reference (upperLimitReference) AirspaceLayer upperLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13CA Warning AIXM Model Each AirspaceLayer with assigned lowerLimit value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> AirspaceLayer </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimit without vertical reference (lowerLimitReference) AirspaceLayer lowerLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13CB Error Error AIXM Model Each AirspaceVolume with assigned upperLimit value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimit without vertical reference (upperLimitReference) AirspaceVolume upperLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13CC Error AIXM Model Each AirspaceVolume with assigned maximumLimit value shall have assigned maximumLimitReference value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> maximumLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> maximumLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found maximumLimit without vertical reference (maximumLimitReference) AirspaceVolume maximumLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13CD Error Error AIXM Model Each AirspaceVolume with assigned lowerLimit value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimit without vertical reference (lowerLimitReference) AirspaceVolume lowerLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13CE Error AIXM Model Each AirspaceVolume with assigned minimumLimit value shall have assigned minimumLimitReference value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> minimumLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found minimumLimit without vertical reference (minimumLimitReference) AirspaceVolume minimumLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13CF Warning AIXM Model Each ApproachAltitudeTable with assigned altitude value shall have assigned altitudeReference value <keyword> Each </keyword><noun_concept> ApproachAltitudeTable </noun_concept><keyword> with assigned </keyword><noun_concept> altitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found altitude without vertical reference (altitudeReference) ApproachAltitudeTable altitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D0 Warning AIXM Model Each CircleSector with assigned upperLimit value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimit without vertical reference (upperLimitReference) CircleSector upperLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D1 Warning AIXM Model Each CircleSector with assigned lowerLimit value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> CircleSector </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimit without vertical reference (lowerLimitReference) CircleSector lowerLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D2 Warning AIXM Model Each DepartureArrivalCondition with assigned minimumCrossingAtEnd value shall have assigned minimumCrossingAtEndReference value <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><keyword> with assigned </keyword><noun_concept> minimumCrossingAtEnd </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumCrossingAtEndReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found minimumCrossingAtEnd without vertical reference (minimumCrossingAtEndReference) DepartureArrivalCondition minimumCrossingAtEnd N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D3 Warning AIXM Model Each DepartureArrivalCondition with assigned maximumCrossingAtEnd value shall have assigned maximumCrossingAtEndReference value <keyword> Each </keyword><noun_concept> DepartureArrivalCondition </noun_concept><keyword> with assigned </keyword><noun_concept> maximumCrossingAtEnd </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> maximumCrossingAtEndReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found maximumCrossingAtEnd without vertical reference (maximumCrossingAtEndReference) DepartureArrivalCondition maximumCrossingAtEnd N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D4 Warning AIXM Model Each HoldingAssessment with assigned upperLimit value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimit without vertical reference (upperLimitReference) HoldingAssessment upperLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D5 Warning AIXM Model Each HoldingAssessment with assigned lowerLimit value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimit without vertical reference (lowerLimitReference) HoldingAssessment lowerLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D6 Warning AIXM Model Each HoldingUse with assigned instructedAltitude value shall have assigned instructionAltitudeReference value <keyword> Each </keyword><noun_concept> HoldingUse </noun_concept><keyword> with assigned </keyword><noun_concept> instructedAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> instructionAltitudeReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found instructedAltitude without vertical reference (instructionAltitudeReference) HoldingUse instructedAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D7 Warning AIXM Model Each Minima with assigned altitude value shall have assigned altitudeReference value <keyword> Each </keyword><noun_concept> Minima </noun_concept><keyword> with assigned </keyword><noun_concept> altitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found altitude without vertical reference (altitudeReference) Minima altitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D8 Warning AIXM Model Each NavigationSystemCheckpoint with assigned upperLimit value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> NavigationSystemCheckpoint </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimit without vertical reference (upperLimitReference) NavigationSystemCheckpoint upperLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13D9 Warning AIXM Model Each NavigationSystemCheckpoint with assigned lowerLimit value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> NavigationSystemCheckpoint </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimit without vertical reference (lowerLimitReference) NavigationSystemCheckpoint lowerLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13DA Error AIXM Model Each RouteSegment with assigned upperLimit value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimit without vertical reference (upperLimitReference) RouteSegment upperLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13DB Error AIXM Model Each RouteSegment with assigned lowerLimit value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimit without vertical reference (lowerLimitReference) RouteSegment lowerLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13DC Warning AIXM Model Each RouteSegment with assigned minimumCrossingAtEnd value shall have assigned minimumCrossingAtEndReference value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> minimumCrossingAtEnd </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumCrossingAtEndReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found minimumCrossingAtEnd without vertical reference (minimumCrossingAtEndReference) RouteSegment minimumCrossingAtEnd N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13DD Warning AIXM Model Each RouteSegment with assigned maximumCrossingAtEnd value shall have assigned maximumCrossingAtEndReference value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> with assigned </keyword><noun_concept> maximumCrossingAtEnd </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> maximumCrossingAtEndReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found maximumCrossingAtEnd without vertical reference (maximumCrossingAtEndReference) RouteSegment maximumCrossingAtEnd N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13DE Warning AIXM Model Each DepartureLeg with assigned upperLimitAltitude value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimitAltitude without vertical reference (upperLimitReference) DepartureLeg upperLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13DF Warning AIXM Model Each DepartureLeg with assigned lowerLimitAltitude value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimitAltitude without vertical reference (lowerLimitReference) DepartureLeg lowerLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E0 Warning AIXM Model Each DepartureLeg with assigned altitudeOverrideATC value shall have assigned altitudeOverrideReference value <keyword> Each </keyword><noun_concept> DepartureLeg </noun_concept><keyword> with assigned </keyword><noun_concept> altitudeOverrideATC </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeOverrideReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found altitudeOverrideATC without vertical reference (altitudeOverrideReference) DepartureLeg altitudeOverrideATC N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E1 Warning AIXM Model Each ArrivalLeg with assigned altitudeOverrideATC value shall have assigned altitudeOverrideReference value <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> altitudeOverrideATC </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeOverrideReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found altitudeOverrideATC without vertical reference (altitudeOverrideReference) ArrivalLeg altitudeOverrideATC N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E2 Warning AIXM Model Each ArrivalLeg with assigned lowerLimitAltitude value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimitAltitude without vertical reference (lowerLimitReference) ArrivalLeg lowerLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E3 Warning AIXM Model Each ArrivalLeg with assigned upperLimitAltitude value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> ArrivalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimitAltitude without vertical reference (upperLimitReference) ArrivalLeg upperLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E4 Warning AIXM Model Each ArrivalFeederLeg with assigned altitudeOverrideATC value shall have assigned altitudeOverrideReference value <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with assigned </keyword><noun_concept> altitudeOverrideATC </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeOverrideReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found altitudeOverrideATC without vertical reference (altitudeOverrideReference) ArrivalFeederLeg altitudeOverrideATC N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E5 Warning AIXM Model Each ArrivalFeederLeg with assigned lowerLimitAltitude value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimitAltitude without vertical reference (lowerLimitReference) ArrivalFeederLeg lowerLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E6 Warning AIXM Model Each ArrivalFeederLeg with assigned upperLimitAltitude value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimitAltitude without vertical reference (upperLimitReference) ArrivalFeederLeg upperLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E7 Warning AIXM Model Each InitialLeg with assigned upperLimitAltitude value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimitAltitude without vertical reference (upperLimitReference) InitialLeg upperLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E8 Warning AIXM Model Each InitialLeg with assigned lowerLimitAltitude value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimitAltitude without vertical reference (lowerLimitReference) InitialLeg lowerLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13E9 Warning AIXM Model Each FinalLeg with assigned upperLimitAltitude value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimitAltitude without vertical reference (upperLimitReference) FinalLeg upperLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13EA Warning AIXM Model Each InitialLeg with assigned altitudeOverrideATC value shall have assigned altitudeOverrideReference value <keyword> Each </keyword><noun_concept> InitialLeg </noun_concept><keyword> with assigned </keyword><noun_concept> altitudeOverrideATC </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeOverrideReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found altitudeOverrideATC without vertical reference (altitudeOverrideReference) InitialLeg altitudeOverrideATC N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13EB Warning AIXM Model Each FinalLeg with assigned altitudeOverrideATC value shall have assigned altitudeOverrideReference value <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> altitudeOverrideATC </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeOverrideReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found altitudeOverrideATC without vertical reference (altitudeOverrideReference) FinalLeg altitudeOverrideATC N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13EC Warning AIXM Model Each FinalLeg with assigned lowerLimitAltitude value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimitAltitude without vertical reference (lowerLimitReference) FinalLeg lowerLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13ED Warning AIXM Model Each MissedApproachLeg with assigned altitudeOverrideATC value shall have assigned altitudeOverrideReference value <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with assigned </keyword><noun_concept> altitudeOverrideATC </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeOverrideReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found altitudeOverrideATC without vertical reference (altitudeOverrideReference) MissedApproachLeg altitudeOverrideATC N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13EE Warning AIXM Model Each MissedApproachLeg with assigned lowerLimitAltitude value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimitAltitude without vertical reference (lowerLimitReference) MissedApproachLeg lowerLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13EF Warning AIXM Model Each IntermediateLeg with assigned upperLimitAltitude value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimitAltitude without vertical reference (upperLimitReference) IntermediateLeg upperLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13F0 Warning AIXM Model Each IntermediateLeg with assigned lowerLimitAltitude value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimitAltitude without vertical reference (lowerLimitReference) IntermediateLeg lowerLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13F1 Warning AIXM Model Each IntermediateLeg with assigned altitudeOverrideATC value shall have assigned altitudeOverrideReference value <keyword> Each </keyword><noun_concept> IntermediateLeg </noun_concept><keyword> with assigned </keyword><noun_concept> altitudeOverrideATC </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> altitudeOverrideReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found altitudeOverrideATC without vertical reference (altitudeOverrideReference) IntermediateLeg altitudeOverrideATC N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13F2 Warning AIXM Model Each MissedApproachLeg with assigned upperLimitAltitude value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> MissedApproachLeg </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimitAltitude </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimitAltitude without vertical reference (upperLimitReference) MissedApproachLeg upperLimitAltitude N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13F3 Warning AIXM Model Each CheckpointINS with assigned upperLimit value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> CheckpointINS </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimit without vertical reference (upperLimitReference) CheckpointINS upperLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13F4 Warning AIXM Model Each CheckpointINS with assigned lowerLimit value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> CheckpointINS </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimit without vertical reference (lowerLimitReference) CheckpointINS lowerLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13F5 Warning AIXM Model Each CheckpointVOR with assigned upperLimit value shall have assigned upperLimitReference value <keyword> Each </keyword><noun_concept> CheckpointVOR </noun_concept><keyword> with assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found upperLimit without vertical reference (upperLimitReference) CheckpointVOR upperLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1A13F6 Warning AIXM Model Each CheckpointVOR with assigned lowerLimit value shall have assigned lowerLimitReference value <keyword> Each </keyword><noun_concept> CheckpointVOR </noun_concept><keyword> with assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword> For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified. Found lowerLimit without vertical reference (lowerLimitReference) CheckpointVOR lowerLimit N/A Minimal data rule Vertical limits must have vertical reference
AIXM-5.1_RULE-1AB009 AIXM Model It is obligatory that each AerialRefuelling with assigned managingOrganisation.AuthorityForAerialRefuelling.theOrganisationAuthority value has managingOrganisation.AuthorityForAerialRefuelling.theOrganisationAuthority value resolved-into exactly one isManagedBy OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> AerialRefuelling </noun_concept><keyword> with assigned </keyword><noun_concept> managingOrganisation.AuthorityForAerialRefuelling.theOrganisationAuthority </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> managingOrganisation.AuthorityForAerialRefuelling.theOrganisationAuthority </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isManagedBy </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model AerialRefuelling managingOrganisation.AuthorityForAerialRefuelling.theOrganisationAuthority set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB00A AIXM Model It is obligatory that each AerialRefuelling with assigned protectingAirspace value has protectingAirspace value resolved-into exactly one isProtectedBy Airspace <keyword> It is obligatory that each </keyword><noun_concept> AerialRefuelling </noun_concept><keyword> with assigned </keyword><noun_concept> protectingAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> protectingAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProtectedBy </verb_concept><noun_concept> Airspace </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model AerialRefuelling protectingAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB00B AIXM Model It is obligatory that each AerialRefuelling with assigned oppositeTrack value has oppositeTrack value resolved-into exactly one definesOppositeDirectionTrack AerialRefuelling <keyword> It is obligatory that each </keyword><noun_concept> AerialRefuelling </noun_concept><keyword> with assigned </keyword><noun_concept> oppositeTrack </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> oppositeTrack </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> definesOppositeDirectionTrack </verb_concept><noun_concept> AerialRefuelling </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model AerialRefuelling oppositeTrack set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB00C Error AIXM Model It is obligatory that each AirportHeliport with assigned altimeterSource value has altimeterSource value resolved-into exactly one utilizes AltimeterSource <keyword> It is obligatory that each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> altimeterSource </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> altimeterSource </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> utilizes </verb_concept><noun_concept> AltimeterSource </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model AirportHeliport altimeterSource set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB00E AIXM Model It is obligatory that each AirspaceBorderCrossing with assigned enteredAirspace value has enteredAirspace value resolved-into exactly one goesInto Airspace <keyword> It is obligatory that each </keyword><noun_concept> AirspaceBorderCrossing </noun_concept><keyword> with assigned </keyword><noun_concept> enteredAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> enteredAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> goesInto </verb_concept><noun_concept> Airspace </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model AirspaceBorderCrossing enteredAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB00F AIXM Model It is obligatory that each AirspaceBorderCrossing with assigned exitedAirspace value has exitedAirspace value resolved-into exactly one comesFrom Airspace <keyword> It is obligatory that each </keyword><noun_concept> AirspaceBorderCrossing </noun_concept><keyword> with assigned </keyword><noun_concept> exitedAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> exitedAirspace </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> comesFrom </verb_concept><noun_concept> Airspace </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model AirspaceBorderCrossing exitedAirspace set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB010 AIXM Model It is obligatory that each AirTrafficManagementService with assigned clientAerialRefuelling value has clientAerialRefuelling value resolved-into exactly one schedules AerialRefuelling <keyword> It is obligatory that each </keyword><noun_concept> AirTrafficManagementService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAerialRefuelling </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAerialRefuelling </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> schedules </verb_concept><noun_concept> AerialRefuelling </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model AirTrafficManagementService clientAerialRefuelling set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB011 Error AIXM Model It is obligatory that each ApproachCondition with assigned altimeter value has altimeter value resolved-into exactly one identifies AltimeterSource <keyword> It is obligatory that each </keyword><noun_concept> ApproachCondition </noun_concept><keyword> with assigned </keyword><noun_concept> altimeter </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> altimeter </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> identifies </verb_concept><noun_concept> AltimeterSource </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model ApproachCondition altimeter set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB016 AIXM Model It is obligatory that each FlightConditionElement with assigned flightCondition.FlightConditionElementChoice.borderCrossingCodition value has flightCondition.FlightConditionElementChoice.borderCrossingCodition value resolved-into exactly one is AirspaceBorderCrossing <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> flightCondition.FlightConditionElementChoice.borderCrossingCodition </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> flightCondition.FlightConditionElementChoice.borderCrossingCodition </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> AirspaceBorderCrossing </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement flightCondition.FlightConditionElementChoice.borderCrossingCodition set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB018 AIXM Model It is obligatory that each HoldingAssessment with assigned unplannedHolding value has unplannedHolding value resolved-into exactly one determines UnplannedHolding <keyword> It is obligatory that each </keyword><noun_concept> HoldingAssessment </noun_concept><keyword> with assigned </keyword><noun_concept> unplannedHolding </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> unplannedHolding </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> determines </verb_concept><noun_concept> UnplannedHolding </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model HoldingAssessment unplannedHolding set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB019 AIXM Model It is obligatory that each InformationService with assigned clientAerialRefuelling value has clientAerialRefuelling value resolved-into exactly one concerns AerialRefuelling <keyword> It is obligatory that each </keyword><noun_concept> InformationService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAerialRefuelling </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAerialRefuelling </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> concerns </verb_concept><noun_concept> AerialRefuelling </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model InformationService clientAerialRefuelling set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB01A AIXM Model It is obligatory that each MarkingBuoy with assigned markedSeaplaneLandingArea value has markedSeaplaneLandingArea value resolved-into exactly one isMarkedOn SeaplaneLandingArea <keyword> It is obligatory that each </keyword><noun_concept> MarkingBuoy </noun_concept><keyword> with assigned </keyword><noun_concept> markedSeaplaneLandingArea </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedSeaplaneLandingArea </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> SeaplaneLandingArea </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model MarkingBuoy markedSeaplaneLandingArea set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB01B Error AIXM Model It is obligatory that each MissedApproachGroup with assigned altimeter value has altimeter value resolved-into exactly one identifies AltimeterSource <keyword> It is obligatory that each </keyword><noun_concept> MissedApproachGroup </noun_concept><keyword> with assigned </keyword><noun_concept> altimeter </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> altimeter </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> identifies </verb_concept><noun_concept> AltimeterSource </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model MissedApproachGroup altimeter set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB01D AIXM Model It is obligatory that each PassengerLoadingBridge with assigned associatedStand value has associatedStand value resolved-into exactly one hasLoadingStand AircraftStand <keyword> It is obligatory that each </keyword><noun_concept> PassengerLoadingBridge </noun_concept><keyword> with assigned </keyword><noun_concept> associatedStand </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> associatedStand </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hasLoadingStand </verb_concept><noun_concept> AircraftStand </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model PassengerLoadingBridge associatedStand set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB01E Error AIXM Model It is obligatory that each RadarSystem with assigned office value has office value resolved-into exactly one isManagedBy OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> RadarSystem </noun_concept><keyword> with assigned </keyword><noun_concept> office </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> office </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isManagedBy </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model RadarSystem office set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB01F Error AIXM Model It is obligatory that each RadarSystem with assigned PARRunway value has PARRunway value resolved-into exactly one isUtilised Runway <keyword> It is obligatory that each </keyword><noun_concept> RadarSystem </noun_concept><keyword> with assigned </keyword><noun_concept> PARRunway </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> PARRunway </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUtilised </verb_concept><noun_concept> Runway </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model RadarSystem PARRunway set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB020 Error AIXM Model It is obligatory that each RadarSystem with assigned airportHeliport value has airportHeliport value resolved-into exactly one isSituatedAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> RadarSystem </noun_concept><keyword> with assigned </keyword><noun_concept> airportHeliport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> airportHeliport </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model RadarSystem airportHeliport set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB021 AIXM Model It is obligatory that each RadioFrequencyArea with assigned equipment.EquipmentChoice.radar value has equipment.EquipmentChoice.radar value resolved-into exactly one limits SecondarySurveillanceRadar <keyword> It is obligatory that each </keyword><noun_concept> RadioFrequencyArea </noun_concept><keyword> with assigned </keyword><noun_concept> equipment.EquipmentChoice.radar </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> equipment.EquipmentChoice.radar </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> limits </verb_concept><noun_concept> SecondarySurveillanceRadar </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model RadioFrequencyArea equipment.EquipmentChoice.radar set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB022 Error AIXM Model It is obligatory that each RadioFrequencyArea with assigned equipment.EquipmentChoice.precisionApproachRadar value has equipment.EquipmentChoice.precisionApproachRadar value resolved-into exactly one limits PrecisionApproachRadar <keyword> It is obligatory that each </keyword><noun_concept> RadioFrequencyArea </noun_concept><keyword> with assigned </keyword><noun_concept> equipment.EquipmentChoice.precisionApproachRadar </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> equipment.EquipmentChoice.precisionApproachRadar </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> limits </verb_concept><noun_concept> PrecisionApproachRadar </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model RadioFrequencyArea equipment.EquipmentChoice.precisionApproachRadar set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB028 AIXM Model It is obligatory that each SeaplaneLandingArea with assigned rampSite value has rampSite value resolved-into exactly one hasRampSite SeaplaneRampSite <keyword> It is obligatory that each </keyword><noun_concept> SeaplaneLandingArea </noun_concept><keyword> with assigned </keyword><noun_concept> rampSite </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> rampSite </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hasRampSite </verb_concept><noun_concept> SeaplaneRampSite </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model SeaplaneLandingArea rampSite set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB029 AIXM Model It is obligatory that each SeaplaneLandingArea with assigned dockSite value has dockSite value resolved-into exactly one hasDockSite FloatingDockSite <keyword> It is obligatory that each </keyword><noun_concept> SeaplaneLandingArea </noun_concept><keyword> with assigned </keyword><noun_concept> dockSite </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> dockSite </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hasDockSite </verb_concept><noun_concept> FloatingDockSite </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model SeaplaneLandingArea dockSite set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB02F AIXM Model It is obligatory that each AirTrafficControlService with assigned clientAerialRefuelling value has clientAerialRefuelling value resolved-into exactly one controls AerialRefuelling <keyword> It is obligatory that each </keyword><noun_concept> AirTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> clientAerialRefuelling </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientAerialRefuelling </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> controls </verb_concept><noun_concept> AerialRefuelling </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model AirTrafficControlService clientAerialRefuelling set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB030 Error AIXM Model It is obligatory that each AirTrafficControlService with assigned aircraftLocator value has aircraftLocator value resolved-into exactly one isAssistedBy DirectionFinder <keyword> It is obligatory that each </keyword><noun_concept> AirTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> aircraftLocator </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> aircraftLocator </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAssistedBy </verb_concept><noun_concept> DirectionFinder </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model AirTrafficControlService aircraftLocator set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB031 AIXM Model It is obligatory that each DirectFlightSegment with assigned end.SignificantPoint.fixDesignatedPoint value has end.SignificantPoint.fixDesignatedPoint value resolved-into exactly one endsAt DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment end.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB032 AIXM Model It is obligatory that each DirectFlightSegment with assigned end.SignificantPoint.navaidSystem value has end.SignificantPoint.navaidSystem value resolved-into exactly one endsAt Navaid <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> Navaid </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment end.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB033 AIXM Model It is obligatory that each DirectFlightSegment with assigned end.SignificantPoint.aimingPoint value has end.SignificantPoint.aimingPoint value resolved-into exactly one endsAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment end.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB034 AIXM Model It is obligatory that each DirectFlightSegment with assigned end.SignificantPoint.runwayPoint value has end.SignificantPoint.runwayPoint value resolved-into exactly one endsAt RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment end.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB035 AIXM Model It is obligatory that each DirectFlightSegment with assigned end.SignificantPoint.airportReferencePoint value has end.SignificantPoint.airportReferencePoint value resolved-into exactly one endsAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> end.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> end.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> endsAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment end.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB036 AIXM Model It is obligatory that each DirectFlightSegment with assigned start.SignificantPoint.fixDesignatedPoint value has start.SignificantPoint.fixDesignatedPoint value resolved-into exactly one startsAt DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment start.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB037 AIXM Model It is obligatory that each DirectFlightSegment with assigned start.SignificantPoint.navaidSystem value has start.SignificantPoint.navaidSystem value resolved-into exactly one startsAt Navaid <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> Navaid </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment start.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB038 AIXM Model It is obligatory that each DirectFlightSegment with assigned start.SignificantPoint.aimingPoint value has start.SignificantPoint.aimingPoint value resolved-into exactly one startsAt TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment start.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB039 AIXM Model It is obligatory that each DirectFlightSegment with assigned start.SignificantPoint.runwayPoint value has start.SignificantPoint.runwayPoint value resolved-into exactly one startsAt RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment start.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB03A AIXM Model It is obligatory that each DirectFlightSegment with assigned start.SignificantPoint.airportReferencePoint value has start.SignificantPoint.airportReferencePoint value resolved-into exactly one startsAt AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> with assigned </keyword><noun_concept> start.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> start.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> startsAt </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model DirectFlightSegment start.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB03B AIXM Model It is obligatory that each FlightConditionElement with assigned flightCondition.FlightConditionElementChoice.airportHeliportCondition value has flightCondition.FlightConditionElementChoice.airportHeliportCondition value resolved-into exactly one is AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> flightCondition.FlightConditionElementChoice.airportHeliportCondition </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> flightCondition.FlightConditionElementChoice.airportHeliportCondition </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement flightCondition.FlightConditionElementChoice.airportHeliportCondition set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB03C AIXM Model It is obligatory that each FlightConditionElement with assigned flightCondition.FlightConditionElementChoice.airspaceCondition value has flightCondition.FlightConditionElementChoice.airspaceCondition value resolved-into exactly one is Airspace <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> flightCondition.FlightConditionElementChoice.airspaceCondition </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> flightCondition.FlightConditionElementChoice.airspaceCondition </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> Airspace </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement flightCondition.FlightConditionElementChoice.airspaceCondition set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB03D AIXM Model It is obligatory that each FlightConditionElement with assigned significantPointCondition.FlightConditionElementChoice.fixDesignatedPoint value has significantPointCondition.FlightConditionElementChoice.fixDesignatedPoint value resolved-into exactly one is DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> significantPointCondition.FlightConditionElementChoice.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> significantPointCondition.FlightConditionElementChoice.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement significantPointCondition.FlightConditionElementChoice.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB03E AIXM Model It is obligatory that each FlightConditionElement with assigned significantPointCondition.FlightConditionElementChoice.navaidSystem value has significantPointCondition.FlightConditionElementChoice.navaidSystem value resolved-into exactly one is Navaid <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> significantPointCondition.FlightConditionElementChoice.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> significantPointCondition.FlightConditionElementChoice.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> Navaid </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement significantPointCondition.FlightConditionElementChoice.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB03F AIXM Model It is obligatory that each FlightConditionElement with assigned significantPointCondition.FlightConditionElementChoice.aimingPoint value has significantPointCondition.FlightConditionElementChoice.aimingPoint value resolved-into exactly one is TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> significantPointCondition.FlightConditionElementChoice.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> significantPointCondition.FlightConditionElementChoice.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement significantPointCondition.FlightConditionElementChoice.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB040 AIXM Model It is obligatory that each FlightConditionElement with assigned significantPointCondition.FlightConditionElementChoice.runwayPoint value has significantPointCondition.FlightConditionElementChoice.runwayPoint value resolved-into exactly one is RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> significantPointCondition.FlightConditionElementChoice.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> significantPointCondition.FlightConditionElementChoice.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement significantPointCondition.FlightConditionElementChoice.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB041 AIXM Model It is obligatory that each FlightConditionElement with assigned significantPointCondition.FlightConditionElementChoice.airportReferencePoint value has significantPointCondition.FlightConditionElementChoice.airportReferencePoint value resolved-into exactly one is AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> significantPointCondition.FlightConditionElementChoice.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> significantPointCondition.FlightConditionElementChoice.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement significantPointCondition.FlightConditionElementChoice.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB042 AIXM Model It is obligatory that each FlightConditionElement with assigned flightCondition.FlightConditionElementChoice.organisationCondition value has flightCondition.FlightConditionElementChoice.organisationCondition value resolved-into exactly one is OrganisationAuthority <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> flightCondition.FlightConditionElementChoice.organisationCondition </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> flightCondition.FlightConditionElementChoice.organisationCondition </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> OrganisationAuthority </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement flightCondition.FlightConditionElementChoice.organisationCondition set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB043 AIXM Model It is obligatory that each FlightConditionElement with assigned flightCondition.FlightConditionElementChoice.standardInstrumentArrivalCondition value has flightCondition.FlightConditionElementChoice.standardInstrumentArrivalCondition value resolved-into exactly one is StandardInstrumentArrival <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> flightCondition.FlightConditionElementChoice.standardInstrumentArrivalCondition </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> flightCondition.FlightConditionElementChoice.standardInstrumentArrivalCondition </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> StandardInstrumentArrival </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement flightCondition.FlightConditionElementChoice.standardInstrumentArrivalCondition set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB044 AIXM Model It is obligatory that each FlightConditionElement with assigned flightCondition.FlightConditionElementChoice.aerialRefuellingCondition value has flightCondition.FlightConditionElementChoice.aerialRefuellingCondition value resolved-into exactly one is AerialRefuelling <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> flightCondition.FlightConditionElementChoice.aerialRefuellingCondition </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> flightCondition.FlightConditionElementChoice.aerialRefuellingCondition </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> AerialRefuelling </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement flightCondition.FlightConditionElementChoice.aerialRefuellingCondition set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB045 AIXM Model It is obligatory that each FlightConditionElement with assigned flightCondition.FlightConditionElementChoice.standardInstrumentDepartureCondition value has flightCondition.FlightConditionElementChoice.standardInstrumentDepartureCondition value resolved-into exactly one is StandardInstrumentDeparture <keyword> It is obligatory that each </keyword><noun_concept> FlightConditionElement </noun_concept><keyword> with assigned </keyword><noun_concept> flightCondition.FlightConditionElementChoice.standardInstrumentDepartureCondition </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> flightCondition.FlightConditionElementChoice.standardInstrumentDepartureCondition </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> is </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightConditionElement flightCondition.FlightConditionElementChoice.standardInstrumentDepartureCondition set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB046 AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.airportHeliportElement value has element.FlightRoutingElementChoice.airportHeliportElement value resolved-into exactly one isBasedOn AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.airportHeliportElement </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.airportHeliportElement </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.airportHeliportElement set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB047 AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.airspaceElement value has element.FlightRoutingElementChoice.airspaceElement value resolved-into exactly one isBasedOn Airspace <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.airspaceElement </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.airspaceElement </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> Airspace </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.airspaceElement set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB048 AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.pointElement.SignificantPoint.fixDesignatedPoint value has element.FlightRoutingElementChoice.pointElement.SignificantPoint.fixDesignatedPoint value resolved-into exactly one isBasedOn DesignatedPoint <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> DesignatedPoint </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.pointElement.SignificantPoint.fixDesignatedPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB049 AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.pointElement.SignificantPoint.navaidSystem value has element.FlightRoutingElementChoice.pointElement.SignificantPoint.navaidSystem value resolved-into exactly one isBasedOn Navaid <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.navaidSystem </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> Navaid </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.pointElement.SignificantPoint.navaidSystem set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB04A AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.pointElement.SignificantPoint.aimingPoint value has element.FlightRoutingElementChoice.pointElement.SignificantPoint.aimingPoint value resolved-into exactly one isBasedOn TouchDownLiftOff <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.aimingPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.aimingPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> TouchDownLiftOff </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.pointElement.SignificantPoint.aimingPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB04B AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.pointElement.SignificantPoint.runwayPoint value has element.FlightRoutingElementChoice.pointElement.SignificantPoint.runwayPoint value resolved-into exactly one isBasedOn RunwayCentrelinePoint <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.runwayPoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.runwayPoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.pointElement.SignificantPoint.runwayPoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB04C AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.pointElement.SignificantPoint.airportReferencePoint value has element.FlightRoutingElementChoice.pointElement.SignificantPoint.airportReferencePoint value resolved-into exactly one isBasedOn AirportHeliport <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.airportReferencePoint </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.pointElement.SignificantPoint.airportReferencePoint </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> AirportHeliport </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.pointElement.SignificantPoint.airportReferencePoint set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB04D AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.standardInstrumentArrivalElement value has element.FlightRoutingElementChoice.standardInstrumentArrivalElement value resolved-into exactly one isBasedOn StandardInstrumentArrival <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.standardInstrumentArrivalElement </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.standardInstrumentArrivalElement </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> StandardInstrumentArrival </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.standardInstrumentArrivalElement set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB04E AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.aerialRefuellingElement value has element.FlightRoutingElementChoice.aerialRefuellingElement value resolved-into exactly one isBasedOn AerialRefuelling <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.aerialRefuellingElement </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.aerialRefuellingElement </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> AerialRefuelling </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.aerialRefuellingElement set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1AB04F AIXM Model It is obligatory that each FlightRoutingElement with assigned element.FlightRoutingElementChoice.standardInstrumentDepartureElement value has element.FlightRoutingElementChoice.standardInstrumentDepartureElement value resolved-into exactly one isBasedOn StandardInstrumentDeparture <keyword> It is obligatory that each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> with assigned </keyword><noun_concept> element.FlightRoutingElementChoice.standardInstrumentDepartureElement </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> element.FlightRoutingElementChoice.standardInstrumentDepartureElement </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isBasedOn </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept> The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model The feature instances actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model FlightRoutingElement element.FlightRoutingElementChoice.standardInstrumentDepartureElement set of snapshots Minimal data rule Referential integrity
AIXM-5.1_RULE-1A2F22 AIXM Model Each AerialRefuelling . annotation . Note . propertyName shall not have assigned value other than ('designatorPrefix', 'designatorNumber', 'designatorSuffix', 'designatorDirection', 'name', 'type', 'radarBeaconSetting', 'xbandRadarSetting', 'tankerChannel', 'receiverChannel', 'helicopterRoute', 'specialRefuelling', 'bidirectionalUse', 'reverseDirectionTurn', 'availability', 'protectingAirspace', 'track', 'anchor', 'oppositeTrack', 'managingOrganisation') <keyword> Each </keyword><noun_concept> AerialRefuelling </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designatorPrefix', 'designatorNumber', 'designatorSuffix', 'designatorDirection', 'name', 'type', 'radarBeaconSetting', 'xbandRadarSetting', 'tankerChannel', 'receiverChannel', 'helicopterRoute', 'specialRefuelling', 'bidirectionalUse', 'reverseDirectionTurn', 'availability', 'protectingAirspace', 'track', 'anchor', 'oppositeTrack', 'managingOrganisation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AerialRefuelling All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F67 AIXM Model Each FlightConditionCombination . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'logicalOperator', 'element') <keyword> Each </keyword><noun_concept> FlightConditionCombination </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'logicalOperator', 'element') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FlightConditionCombination All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A2F6F AIXM Model Each HoldingAssessment . annotation . Note . propertyName shall not have assigned value other than ('upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'speedLimit', 'patternTemplate', 'turbulentAir', 'legLengthToward', 'legLengthAway', 'holdingPoint', 'unplannedHolding', 'assessedHoldingPattern', 'obstacleAssessment') <keyword> Each </keyword><noun_concept> HoldingAssessment </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('upperLimit', 'upperLimitReference', 'lowerLimit', 'lowerLimitReference', 'speedLimit', 'patternTemplate', 'turbulentAir', 'legLengthToward', 'legLengthAway', 'holdingPoint', 'unplannedHolding', 'assessedHoldingPattern', 'obstacleAssessment') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property HoldingAssessment All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC391 AIXM Model Each AerialRefuellingAnchor . annotation . Note . propertyName shall not have assigned value other than ('outboundCourse', 'outboundCourseType', 'inboundCourse', 'turnDirection', 'speedLimit', 'legSeparation', 'legLength', 'refuellingBaseLevel', 'refuellingBaseLevelReference', 'extent', 'verticalExtent', 'point') <keyword> Each </keyword><noun_concept> AerialRefuellingAnchor </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('outboundCourse', 'outboundCourseType', 'inboundCourse', 'turnDirection', 'speedLimit', 'legSeparation', 'legLength', 'refuellingBaseLevel', 'refuellingBaseLevelReference', 'extent', 'verticalExtent', 'point') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AerialRefuellingAnchor All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC392 AIXM Model Each AerialRefuellingPoint . annotation . Note . propertyName shall not have assigned value other than ('reportingATC', 'flyOver', 'waypoint', 'radarGuidance', 'facilityMakeup', 'extendedServiceVolume', 'sequence', 'usageType') <keyword> Each </keyword><noun_concept> AerialRefuellingPoint </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('reportingATC', 'flyOver', 'waypoint', 'radarGuidance', 'facilityMakeup', 'extendedServiceVolume', 'sequence', 'usageType') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AerialRefuellingPoint All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC393 AIXM Model Each AerialRefuellingTrack . annotation . Note . propertyName shall not have assigned value other than ('extent', 'point', 'verticalExtent') <keyword> Each </keyword><noun_concept> AerialRefuellingTrack </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('extent', 'point', 'verticalExtent') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AerialRefuellingTrack All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC394 AIXM Model Each AircraftStandContamination . annotation . Note . propertyName shall not have assigned value other than ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer') <keyword> Each </keyword><noun_concept> AircraftStandContamination </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AircraftStandContamination All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC395 AIXM Model Each AirportHeliportContamination . annotation . Note . propertyName shall not have assigned value other than ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer') <keyword> Each </keyword><noun_concept> AirportHeliportContamination </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirportHeliportContamination All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC397 AIXM Model Each AirspaceBorderCrossing . annotation . Note . propertyName shall not have assigned value other than ('exitedAirspace', 'enteredAirspace') <keyword> Each </keyword><noun_concept> AirspaceBorderCrossing </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('exitedAirspace', 'enteredAirspace') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AirspaceBorderCrossing All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC398 Warning AIXM Model Each AltimeterSource . annotation . Note . propertyName shall not have assigned value other than ('isRemote', 'isPrimary', 'availability') <keyword> Each </keyword><noun_concept> AltimeterSource </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('isRemote', 'isPrimary', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AltimeterSource All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC399 Warning AIXM Model Each AltimeterSourceStatus . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus') <keyword> Each </keyword><noun_concept> AltimeterSourceStatus </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AltimeterSourceStatus All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC39A AIXM Model Each ApronContamination . annotation . Note . propertyName shall not have assigned value other than ('type', 'theOrganisationAuthority') <keyword> Each </keyword><noun_concept> ApronContamination </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'theOrganisationAuthority') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property ApronContamination All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC39C AIXM Model Each AuthorityForAerialRefuelling . annotation . Note . propertyName shall not have assigned value other than ('type', 'theOrganisationAuthority') <keyword> Each </keyword><noun_concept> AuthorityForAerialRefuelling </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'theOrganisationAuthority') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AuthorityForAerialRefuelling All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC39D Warning AIXM Model Each AuthorityForSpecialNavigationStation . annotation . Note . propertyName shall not have assigned value other than ('type', 'theOrganisationAuthority') <keyword> Each </keyword><noun_concept> AuthorityForSpecialNavigationStation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'theOrganisationAuthority') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AuthorityForSpecialNavigationStation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC39E Warning AIXM Model Each AuthorityForSpecialNavigationSystem . annotation . Note . propertyName shall not have assigned value other than ('type', 'theOrganisationAuthority') <keyword> Each </keyword><noun_concept> AuthorityForSpecialNavigationSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'theOrganisationAuthority') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property AuthorityForSpecialNavigationSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A1 AIXM Model Each DirectFlightClass . annotation . Note . propertyName shall not have assigned value other than ('exceedLength') <keyword> Each </keyword><noun_concept> DirectFlightClass </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('exceedLength') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DirectFlightClass All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A2 Warning AIXM Model Each DirectionFinder . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'doppler', 'informationProvision') <keyword> Each </keyword><noun_concept> DirectionFinder </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'doppler', 'informationProvision') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DirectionFinder All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A3 AIXM Model Each FlightConditionCircumstance . annotation . Note . propertyName shall not have assigned value other than ('referenceLocation', 'relationWithLocation') <keyword> Each </keyword><noun_concept> FlightConditionCircumstance </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('referenceLocation', 'relationWithLocation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FlightConditionCircumstance All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A4 AIXM Model Each FlightConditionElement . annotation . Note . propertyName shall not have assigned value other than ('index', 'operationalCondition', 'flightLevel', 'flightConditionAirportHeliportCondition', 'flightConditionStandardInstrumentDepartureCondition', 'flightConditionRoutePortionCondition', 'flightConditionOrganisationCondition', 'significantPointConditionFixDesignatedPoint', 'significantPointConditionNavaidSystem', 'significantPointConditionPosition', 'significantPointConditionRunwayPoint', 'significantPointConditionAimingPoint', 'significantPointConditionAirportReferencePoint', 'flightConditionDirectFlightCondition', 'flightConditionAircraft', 'flightConditionBorderCrossingCondition', 'flightConditionAirspaceCondition', 'flightConditionFlight', 'flightConditionStandardInstrumentArrivalCondition', 'flightConditionOperand', 'flightConditionWeather', 'flightConditionAerialRefuellingCondition') <keyword> Each </keyword><noun_concept> FlightConditionElement </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('index', 'operationalCondition', 'flightLevel', 'flightConditionAirportHeliportCondition', 'flightConditionStandardInstrumentDepartureCondition', 'flightConditionRoutePortionCondition', 'flightConditionOrganisationCondition', 'significantPointConditionFixDesignatedPoint', 'significantPointConditionNavaidSystem', 'significantPointConditionPosition', 'significantPointConditionRunwayPoint', 'significantPointConditionAimingPoint', 'significantPointConditionAirportReferencePoint', 'flightConditionDirectFlightCondition', 'flightConditionAircraft', 'flightConditionBorderCrossingCondition', 'flightConditionAirspaceCondition', 'flightConditionFlight', 'flightConditionStandardInstrumentArrivalCondition', 'flightConditionOperand', 'flightConditionWeather', 'flightConditionAerialRefuellingCondition') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FlightConditionElement All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A5 AIXM Model Each FlightRestriction . annotation . Note . propertyName shall not have assigned value other than ('designator', 'type', 'instruction', 'flight', 'regulatedRoute') <keyword> Each </keyword><noun_concept> FlightRestriction </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'type', 'instruction', 'flight', 'regulatedRoute') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FlightRestriction All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A6 AIXM Model Each FlightRestrictionLevel . annotation . Note . propertyName shall not have assigned value other than ('upperLevel', 'upperLevelReference', 'lowerLevel', 'lowerLevelReference') <keyword> Each </keyword><noun_concept> FlightRestrictionLevel </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('upperLevel', 'upperLevelReference', 'lowerLevel', 'lowerLevelReference') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FlightRestrictionLevel All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A7 AIXM Model Each FlightRestrictionRoute . annotation . Note . propertyName shall not have assigned value other than ('priorPermission', 'routeElement', 'contact') <keyword> Each </keyword><noun_concept> FlightRestrictionRoute </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('priorPermission', 'routeElement', 'contact') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FlightRestrictionRoute All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A8 AIXM Model Each FlightRoutingElement . annotation . Note . propertyName shall not have assigned value other than ('orderNumber', 'speed', 'speedReference', 'speedCriteria', 'flightLevel', 'elementDirectFlightElement', 'elementRoutePortionElement', 'elementStandardInstrumentDepartureElement', 'elementStandardInstrumentArrivalElement', 'pointElementFixDesignatedPoint', 'pointElementNavaidSystem', 'pointElementPosition', 'pointElementRunwayPoint', 'pointElementAimingPoint', 'pointElementAirportReferencePoint', 'elementAirspaceElement', 'elementAirportHeliportElement', 'elementAerialRefuellingElement') <keyword> Each </keyword><noun_concept> FlightRoutingElement </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('orderNumber', 'speed', 'speedReference', 'speedCriteria', 'flightLevel', 'elementDirectFlightElement', 'elementRoutePortionElement', 'elementStandardInstrumentDepartureElement', 'elementStandardInstrumentArrivalElement', 'pointElementFixDesignatedPoint', 'pointElementNavaidSystem', 'pointElementPosition', 'pointElementRunwayPoint', 'pointElementAimingPoint', 'pointElementAirportReferencePoint', 'elementAirspaceElement', 'elementAirportHeliportElement', 'elementAerialRefuellingElement') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FlightRoutingElement All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3A9 AIXM Model Each FloatingDockSite . annotation . Note . propertyName shall not have assigned value other than ('extent') <keyword> Each </keyword><noun_concept> FloatingDockSite </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('extent') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property FloatingDockSite All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3AB AIXM Model Each MarkingBuoy . annotation . Note . propertyName shall not have assigned value other than ('designator', 'type', 'colour', 'theSeaplaneLandingArea', 'location') <keyword> Each </keyword><noun_concept> MarkingBuoy </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'type', 'colour', 'theSeaplaneLandingArea', 'location') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property MarkingBuoy All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3AD AIXM Model Each Meteorology . annotation . Note . propertyName shall not have assigned value other than ('flightConditions', 'visibility', 'visibilityInterpretation', 'runwayVisualRange', 'runwayVisualRangeInterpretation') <keyword> Each </keyword><noun_concept> Meteorology </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('flightConditions', 'visibility', 'visibilityInterpretation', 'runwayVisualRange', 'runwayVisualRangeInterpretation') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Meteorology All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3AF AIXM Model Each PassengerLoadingBridge . annotation . Note . propertyName shall not have assigned value other than ('type', 'extent', 'associatedStand') <keyword> Each </keyword><noun_concept> PassengerLoadingBridge </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'extent', 'associatedStand') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property PassengerLoadingBridge All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B0 AIXM Model Each PilotControlledLighting . annotation . Note . propertyName shall not have assigned value other than ('type', 'duration', 'intensitySteps', 'standByIntensity', 'radioFrequency', 'activationInstruction', 'controlledLightIntensity', 'activatedGroundLighting') <keyword> Each </keyword><noun_concept> PilotControlledLighting </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'duration', 'intensitySteps', 'standByIntensity', 'radioFrequency', 'activationInstruction', 'controlledLightIntensity', 'activatedGroundLighting') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property PilotControlledLighting All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B1 Warning AIXM Model Each PrecisionApproachRadar . annotation . Note . propertyName shall not have assigned value other than ('name', 'serialNumber', 'range', 'rangeAccuracy', 'dualChannel', 'movingTargetIndicator', 'standbyPower', 'digital', 'militaryUseOnly', 'specialUseOnly', 'specialAircraftOnly', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'contact', 'location', 'precisionApproachRadarType', 'slope', 'slopeAccuracy', 'reflector') <keyword> Each </keyword><noun_concept> PrecisionApproachRadar </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'serialNumber', 'range', 'rangeAccuracy', 'dualChannel', 'movingTargetIndicator', 'standbyPower', 'digital', 'militaryUseOnly', 'specialUseOnly', 'specialAircraftOnly', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'contact', 'location', 'precisionApproachRadarType', 'slope', 'slopeAccuracy', 'reflector') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property PrecisionApproachRadar All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B2 AIXM Model Each PrimarySurveillanceRadar . annotation . Note . propertyName shall not have assigned value other than ('name', 'serialNumber', 'range', 'rangeAccuracy', 'dualChannel', 'movingTargetIndicator', 'standbyPower', 'digital', 'militaryUseOnly', 'specialUseOnly', 'specialAircraftOnly', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'contact', 'location', 'verticalCoverageAltitude', 'verticalCoverageDistance', 'verticalCoverageAzimuth', 'antennaTiltFixed', 'tiltAngle', 'automatedRadarTerminalSystem', 'groundStation', 'type') <keyword> Each </keyword><noun_concept> PrimarySurveillanceRadar </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'serialNumber', 'range', 'rangeAccuracy', 'dualChannel', 'movingTargetIndicator', 'standbyPower', 'digital', 'militaryUseOnly', 'specialUseOnly', 'specialAircraftOnly', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'contact', 'location', 'verticalCoverageAltitude', 'verticalCoverageDistance', 'verticalCoverageAzimuth', 'antennaTiltFixed', 'tiltAngle', 'automatedRadarTerminalSystem', 'groundStation', 'type') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property PrimarySurveillanceRadar All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B3 AIXM Model Each RadarComponent . annotation . Note . propertyName shall not have assigned value other than ('collocationGroup', 'theRadarEquipment') <keyword> Each </keyword><noun_concept> RadarComponent </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('collocationGroup', 'theRadarEquipment') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RadarComponent All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B4 Warning AIXM Model Each RadarSystem . annotation . Note . propertyName shall not have assigned value other than ('type', 'model', 'generalTerrainMonitor', 'broadcastIdentifier', 'radarEquipment', 'office', 'airportHeliport', 'pARRunway', 'location') <keyword> Each </keyword><noun_concept> RadarSystem </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'model', 'generalTerrainMonitor', 'broadcastIdentifier', 'radarEquipment', 'office', 'airportHeliport', 'pARRunway', 'location') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RadarSystem All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B5 AIXM Model Each Reflector . annotation . Note . propertyName shall not have assigned value other than ('type', 'touchdownReflector') <keyword> Each </keyword><noun_concept> Reflector </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('type', 'touchdownReflector') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Reflector All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B6 AIXM Model Each Ridge . annotation . Note . propertyName shall not have assigned value other than ('side', 'distance', 'depth') <keyword> Each </keyword><noun_concept> Ridge </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('side', 'distance', 'depth') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property Ridge All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3B9 AIXM Model Each RunwayContamination . annotation . Note . propertyName shall not have assigned value other than ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer', 'clearedLength', 'clearedWidth', 'clearedSide', 'furtherClearanceLength', 'furtherClearanceWidth', 'obscuredLightsSide', 'clearedLengthBegin', 'taxiwayAvailable', 'apronAvailable') <keyword> Each </keyword><noun_concept> RunwayContamination </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer', 'clearedLength', 'clearedWidth', 'clearedSide', 'furtherClearanceLength', 'furtherClearanceWidth', 'obscuredLightsSide', 'clearedLengthBegin', 'taxiwayAvailable', 'apronAvailable') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwayContamination All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3BB AIXM Model Each RunwaySectionContamination . annotation . Note . propertyName shall not have assigned value other than ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer', 'section') <keyword> Each </keyword><noun_concept> RunwaySectionContamination </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer', 'section') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property RunwaySectionContamination All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3BD Warning AIXM Model Each SDF . annotation . Note . propertyName shall not have assigned value other than ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'frequency', 'magneticBearing', 'trueBearing') <keyword> Each </keyword><noun_concept> SDF </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('designator', 'name', 'emissionClass', 'mobile', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'flightChecked', 'location', 'authority', 'monitoring', 'availability', 'frequency', 'magneticBearing', 'trueBearing') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SDF All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3BE AIXM Model Each SeaplaneRampSite . annotation . Note . propertyName shall not have assigned value other than ('extent', 'centreline') <keyword> Each </keyword><noun_concept> SeaplaneRampSite </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('extent', 'centreline') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SeaplaneRampSite All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3BF AIXM Model Each SeaplaneLandingArea . annotation . Note . propertyName shall not have assigned value other than ('rampSite', 'dockSite', 'extent', 'availability') <keyword> Each </keyword><noun_concept> SeaplaneLandingArea </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('rampSite', 'dockSite', 'extent', 'availability') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SeaplaneLandingArea All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C0 AIXM Model Each SecondarySurveillanceRadar . annotation . Note . propertyName shall not have assigned value other than ('name', 'serialNumber', 'range', 'rangeAccuracy', 'dualChannel', 'movingTargetIndicator', 'standbyPower', 'digital', 'militaryUseOnly', 'specialUseOnly', 'specialAircraftOnly', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'contact', 'location', 'verticalCoverageAltitude', 'verticalCoverageDistance', 'verticalCoverageAzimuth', 'antennaTiltFixed', 'tiltAngle', 'automatedRadarTerminalSystem', 'groundStation', 'transponder', 'autonomous', 'monopulse') <keyword> Each </keyword><noun_concept> SecondarySurveillanceRadar </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('name', 'serialNumber', 'range', 'rangeAccuracy', 'dualChannel', 'movingTargetIndicator', 'standbyPower', 'digital', 'militaryUseOnly', 'specialUseOnly', 'specialAircraftOnly', 'magneticVariation', 'magneticVariationAccuracy', 'dateMagneticVariation', 'contact', 'location', 'verticalCoverageAltitude', 'verticalCoverageDistance', 'verticalCoverageAzimuth', 'antennaTiltFixed', 'tiltAngle', 'automatedRadarTerminalSystem', 'groundStation', 'transponder', 'autonomous', 'monopulse') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SecondarySurveillanceRadar All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C2 AIXM Model Each SurfaceContaminationLayer . annotation . Note . propertyName shall not have assigned value other than ('layerOrder', 'type', 'extent') <keyword> Each </keyword><noun_concept> SurfaceContaminationLayer </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('layerOrder', 'type', 'extent') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SurfaceContaminationLayer All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C3 AIXM Model Each SurveillanceGroundStation . annotation . Note . propertyName shall not have assigned value other than ('videoMap', 'theUnit') <keyword> Each </keyword><noun_concept> SurveillanceGroundStation </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('videoMap', 'theUnit') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property SurveillanceGroundStation All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C5 AIXM Model Each TaxiwayContamination . annotation . Note . propertyName shall not have assigned value other than ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer', 'clearedWidth') <keyword> Each </keyword><noun_concept> TaxiwayContamination </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer', 'clearedWidth') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TaxiwayContamination All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C7 AIXM Model Each TouchDownLiftOffContamination . annotation . Note . propertyName shall not have assigned value other than ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer') <keyword> Each </keyword><noun_concept> TouchDownLiftOffContamination </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('observationTime', 'depth', 'frictionCoefficient', 'frictionEstimation', 'frictionDevice', 'obscuredLights', 'furtherClearanceTime', 'furtherTotalClearance', 'nextObservationTime', 'proportion', 'criticalRidge', 'layer') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property TouchDownLiftOffContamination All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3C9 AIXM Model Each UnitAvailability . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'operationalStatus') <keyword> Each </keyword><noun_concept> UnitAvailability </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'operationalStatus') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property UnitAvailability All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3CA AIXM Model Each UnplannedHolding . annotation . Note . propertyName shall not have assigned value other than ('unplannedHolding', 'authorizedAltitude', 'altitudeReference', 'controlledAirspace', 'holdingPoint') <keyword> Each </keyword><noun_concept> UnplannedHolding </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('unplannedHolding', 'authorizedAltitude', 'altitudeReference', 'controlledAirspace', 'holdingPoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property UnplannedHolding All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3CB Warning AIXM Model Each VerticalStructureLightingStatus . annotation . Note . propertyName shall not have assigned value other than ('timeInterval', 'specialDateAuthority', 'status') <keyword> Each </keyword><noun_concept> VerticalStructureLightingStatus </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('timeInterval', 'specialDateAuthority', 'status') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property VerticalStructureLightingStatus All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1AC3CE AIXM Model Each DirectFlightSegment . annotation . Note . propertyName shall not have assigned value other than ('startFixDesignatedPoint', 'startNavaidSystem', 'startPosition', 'startRunwayPoint', 'startAimingPoint', 'startAirportReferencePoint', 'endFixDesignatedPoint', 'endNavaidSystem', 'endPosition', 'endRunwayPoint', 'endAimingPoint', 'endAirportReferencePoint') <keyword> Each </keyword><noun_concept> DirectFlightSegment </noun_concept><noun_concept> annotation </noun_concept><noun_concept> Note </noun_concept><noun_concept> propertyName </noun_concept><keyword> shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><keyword> value </keyword><keyword> other </keyword><keyword> than </keyword><name> ('startFixDesignatedPoint', 'startNavaidSystem', 'startPosition', 'startRunwayPoint', 'startAimingPoint', 'startAirportReferencePoint', 'endFixDesignatedPoint', 'endNavaidSystem', 'endPosition', 'endRunwayPoint', 'endAimingPoint', 'endAirportReferencePoint') </name> The propertyName of any Note should refer to an existing property. Found Note with propertyName referring to non-existing feature property DirectFlightSegment All Data consistency rule Notes propertyName values consistent with model
AIXM-5.1_RULE-1A3311 AIXM 4.5 AIXM 4.5 Each FlightRestrictionLevel shall have assigned lowerLevelReference value <keyword> Each </keyword><noun_concept> FlightRestrictionLevel </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLevelReference </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found FlightRestrictionLevel without lowerLevelReference value. Backwards mapping to AIXM 4.5 will not be possible. FlightRestrictionLevel lowerLevelReference N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A331F AIXM 4.5 AIXM 4.5 Each FlightRestrictionLevel shall have assigned lowerLevel value <keyword> Each </keyword><noun_concept> FlightRestrictionLevel </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLevel </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found FlightRestrictionLevel without lowerLevel value. Backwards mapping to AIXM 4.5 will not be possible. FlightRestrictionLevel lowerLevel N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A332B AIXM 4.5 AIXM 4.5 Each FlightRoutingElement shall have assigned orderNumber value <keyword> Each </keyword><noun_concept> FlightRoutingElement </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> orderNumber </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found FlightRoutingElement without orderNumber value. Backwards mapping to AIXM 4.5 will not be possible. FlightRoutingElement orderNumber N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A335B AIXM 4.5 AIXM 4.5 Each DirectFlightSegment shall have assigned start value <keyword> Each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> start </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DirectFlightSegment without start value. Backwards mapping to AIXM 4.5 will not be possible. DirectFlightSegment start N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3363 AIXM 4.5 AIXM 4.5 Each FlightRestrictionRoute shall have assigned routeElement.FlightRoutingElement value <keyword> Each </keyword><noun_concept> FlightRestrictionRoute </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> routeElement.FlightRoutingElement </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found FlightRestrictionRoute without routeElement.FlightRoutingElement value. Backwards mapping to AIXM 4.5 will not be possible. FlightRestrictionRoute routeElement.FlightRoutingElement N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3365 AIXM 4.5 AIXM 4.5 Each AirspaceBorderCrossing shall have assigned enteredAirspace value <keyword> Each </keyword><noun_concept> AirspaceBorderCrossing </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> enteredAirspace </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirspaceBorderCrossing without enteredAirspace value. Backwards mapping to AIXM 4.5 will not be possible. AirspaceBorderCrossing enteredAirspace N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A337A AIXM 4.5 AIXM 4.5 Each AirspaceBorderCrossing shall have assigned exitedAirspace value <keyword> Each </keyword><noun_concept> AirspaceBorderCrossing </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> exitedAirspace </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirspaceBorderCrossing without exitedAirspace value. Backwards mapping to AIXM 4.5 will not be possible. AirspaceBorderCrossing exitedAirspace N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3392 AIXM 4.5 AIXM 4.5 Each DirectFlightSegment shall have assigned end value <keyword> Each </keyword><noun_concept> DirectFlightSegment </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> end </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DirectFlightSegment without end value. Backwards mapping to AIXM 4.5 will not be possible. DirectFlightSegment end N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33A7 AIXM 4.5 AIXM 4.5 Each FlightRestriction shall have assigned flight.FlightConditionCombination.element.FlightConditionElement value <keyword> Each </keyword><noun_concept> FlightRestriction </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> flight.FlightConditionCombination.element.FlightConditionElement </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found FlightRestriction without flight.FlightConditionCombination.element.FlightConditionElement value. Backwards mapping to AIXM 4.5 will not be possible. FlightRestriction flight.FlightConditionCombination.element.FlightConditionElement N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33AA AIXM 4.5 AIXM 4.5 Each FlightRestriction shall have assigned type value <keyword> Each </keyword><noun_concept> FlightRestriction </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found FlightRestriction without type value. Backwards mapping to AIXM 4.5 will not be possible. FlightRestriction type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33B1 AIXM 4.5 AIXM 4.5 Each FlightRestriction shall have assigned designator value <keyword> Each </keyword><noun_concept> FlightRestriction </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found FlightRestriction without designator value. Backwards mapping to AIXM 4.5 will not be possible. FlightRestriction designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33C1 AIXM 4.5 AIXM 4.5 Each DirectFlightClass shall have assigned exceedLength value <keyword> Each </keyword><noun_concept> DirectFlightClass </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> exceedLength </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DirectFlightClass without exceedLength value. Backwards mapping to AIXM 4.5 will not be possible. DirectFlightClass exceedLength N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-DC371 Warning ICAO Annex 14 Table A5-2 Each DME with assigned location.ElevatedPoint.verticalAccuracy value and location.ElevatedPoint.verticalAccuracy.uom equal-to 'M' and type equal-to 'PRECISION' shall have location.ElevatedPoint.verticalAccuracy lower-or-equal-to 3.0 <keyword> Each </keyword><noun_concept> DME </noun_concept><keyword> with assigned </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value and </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'PRECISION' </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> lower-or-equal-to </keyword> DME/P elevation accuracy shall be equal or better than 3 m or 10 ft DME/P elevation accuracy shall be equal or better than 3 m or 10 ft DME verticalAccuracy baseline outside delta, snapshot, set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - DME/P
AIXM-5.1_RULE-DC372 Warning ICAO Annex 14 Table A5-2 Each DME with assigned location.ElevatedPoint.verticalAccuracy value and location.ElevatedPoint.verticalAccuracy.uom equal-to 'FT' and type equal-to 'PRECISION' shall have location.ElevatedPoint.verticalAccuracy lower-or-equal-to 10.0 <keyword> Each </keyword><noun_concept> DME </noun_concept><keyword> with assigned </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> value and </keyword><noun_concept> location.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'PRECISION' </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> lower-or-equal-to </keyword> DME/P elevation accuracy shall be equal or better than 3 m or 10 ft DME/P elevation accuracy shall be equal or better than 3 m or 10 ft DME verticalAccuracy baseline outside delta, snapshot, set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - DME/P
AIXM-5.1_RULE-1A330C Error AIXM 4.5 Each MarkerBeacon shall have assigned frequency value <keyword> Each </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found MarkerBeacon without frequency value. Backwards mapping to AIXM 4.5 will not be possible. MarkerBeacon frequency N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A330E Warning AIXM 4.5 Each Route shall have assigned designatorSecondLetter value <keyword> Each </keyword><noun_concept> Route </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designatorSecondLetter </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Route without designatorSecondLetter value. Backwards mapping to AIXM 4.5 will not be possible. Route designatorSecondLetter N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A330F Error Error AIXM 4.5 Each GeoBorder shall have assigned border.Curve value <keyword> Each </keyword><noun_concept> GeoBorder </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> border.Curve </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found GeoBorder without border.Curve value. Backwards mapping to AIXM 4.5 will not be possible. GeoBorder border.Curve N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3312 Error Error AIXM 4.5 Each VOR shall have assigned designator value <keyword> Each </keyword><noun_concept> VOR </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found VOR without designator value. Backwards mapping to AIXM 4.5 will not be possible. VOR designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3316 Error AIXM 4.5 Each NDB shall have assigned authority value <keyword> Each </keyword><noun_concept> NDB </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> authority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found NDB without authority value. Backwards mapping to AIXM 4.5 will not be possible. NDB authority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3317 Error AIXM 4.5 Each RunwayDirection shall have assigned usedRunway value <keyword> Each </keyword><noun_concept> RunwayDirection </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> usedRunway </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RunwayDirection without usedRunway value. Backwards mapping to AIXM 4.5 will not be possible. RunwayDirection usedRunway N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3318 Error Error AIXM 4.5 Each GeoBorder shall have assigned type value <keyword> Each </keyword><noun_concept> GeoBorder </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found GeoBorder without type value. Backwards mapping to AIXM 4.5 will not be possible. GeoBorder type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3321 Error AIXM 4.5 Each DME shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> DME </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DME without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. DME location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3322 Error AIXM 4.5 Each AirportHeliport shall have assigned type value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliport without type value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliport type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3328 Error Error AIXM 4.5 Each VOR shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> VOR </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found VOR without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. VOR location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3336 Error AIXM 4.5 Each Airspace shall have assigned type value <keyword> Each </keyword><noun_concept> Airspace </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Airspace without type value. Backwards mapping to AIXM 4.5 will not be possible. Airspace type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A333C Error AIXM 4.5 Each AirportHeliport shall have assigned name value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> name </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliport without name value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliport name N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A333E Error AIXM 4.5 Each NDB shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> NDB </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found NDB without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. NDB location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3348 Error AIXM 4.5 Each NDB shall have assigned designator value <keyword> Each </keyword><noun_concept> NDB </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found NDB without designator value. Backwards mapping to AIXM 4.5 will not be possible. NDB designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A334A Error AIXM 4.5 Each NDB shall have assigned frequency value <keyword> Each </keyword><noun_concept> NDB </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found NDB without frequency value. Backwards mapping to AIXM 4.5 will not be possible. NDB frequency N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3350 Error AIXM 4.5 Each DME shall have assigned designator value <keyword> Each </keyword><noun_concept> DME </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DME without designator value. Backwards mapping to AIXM 4.5 will not be possible. DME designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3351 Error AIXM 4.5 Each RouteSegment shall have assigned navigationType value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> navigationType </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RouteSegment without navigationType value. Backwards mapping to AIXM 4.5 will not be possible. RouteSegment navigationType N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3356 Error AIXM 4.5 Each TACAN shall have assigned channel value <keyword> Each </keyword><noun_concept> TACAN </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> channel </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TACAN without channel value. Backwards mapping to AIXM 4.5 will not be possible. TACAN channel N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3358 Error AIXM 4.5 Each MarkerBeacon shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found MarkerBeacon without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. MarkerBeacon location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A335C Error AIXM 4.5 Each Unit shall have assigned ownerOrganisation value <keyword> Each </keyword><noun_concept> Unit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> ownerOrganisation </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Unit without ownerOrganisation value. Backwards mapping to AIXM 4.5 will not be possible. Unit ownerOrganisation N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3360 Error AIXM 4.5 Each MarkerBeacon shall have assigned auralMorseCode value <keyword> Each </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> auralMorseCode </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found MarkerBeacon without auralMorseCode value. Backwards mapping to AIXM 4.5 will not be possible. MarkerBeacon auralMorseCode N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3367 Error Error AIXM 4.5 Each AirportHeliport shall have assigned designator value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliport without designator value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliport designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3368 Error AIXM 4.5 Each DesignatedPoint shall have assigned designator value <keyword> Each </keyword><noun_concept> DesignatedPoint </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DesignatedPoint without designator value. Backwards mapping to AIXM 4.5 will not be possible. DesignatedPoint designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A336B Error AIXM 4.5 Each RunwayDirection shall have assigned designator value <keyword> Each </keyword><noun_concept> RunwayDirection </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RunwayDirection without designator value. Backwards mapping to AIXM 4.5 will not be possible. RunwayDirection designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A336C Error AIXM 4.5 Each OrganisationAuthority shall have assigned type value <keyword> Each </keyword><noun_concept> OrganisationAuthority </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found OrganisationAuthority without type value. Backwards mapping to AIXM 4.5 will not be possible. OrganisationAuthority type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A336E Error AIXM 4.5 Each TACAN shall have assigned authority value <keyword> Each </keyword><noun_concept> TACAN </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> authority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TACAN without authority value. Backwards mapping to AIXM 4.5 will not be possible. TACAN authority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3371 Error AIXM 4.5 Each DesignatedPoint shall have assigned type value <keyword> Each </keyword><noun_concept> DesignatedPoint </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DesignatedPoint without type value. Backwards mapping to AIXM 4.5 will not be possible. DesignatedPoint type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3384 Error AIXM 4.5 Each DesignatedPoint shall have assigned location.Point.pos value <keyword> Each </keyword><noun_concept> DesignatedPoint </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.Point.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DesignatedPoint without location.Point.pos value. Backwards mapping to AIXM 4.5 will not be possible. DesignatedPoint location.Point.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3387 Error AIXM 4.5 Each Runway shall have assigned designator value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Runway without designator value. Backwards mapping to AIXM 4.5 will not be possible. Runway designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3389 Error AIXM 4.5 Each TACAN shall have assigned location.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> TACAN </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> location.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TACAN without location.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. TACAN location.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A338A Error AIXM 4.5 Each VOR shall have assigned type value <keyword> Each </keyword><noun_concept> VOR </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found VOR without type value. Backwards mapping to AIXM 4.5 will not be possible. VOR type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A3395 Warning AIXM 4.5 Each Route shall have assigned designatorNumber value <keyword> Each </keyword><noun_concept> Route </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designatorNumber </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Route without designatorNumber value. Backwards mapping to AIXM 4.5 will not be possible. Route designatorNumber N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A339C Error Error AIXM 4.5 Each Route shall have assigned locationDesignator value <keyword> Each </keyword><noun_concept> Route </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> locationDesignator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Route without locationDesignator value. Backwards mapping to AIXM 4.5 will not be possible. Route locationDesignator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33A3 Error AIXM 4.5 Each AirportHeliport shall have assigned ARP.ElevatedPoint.pos value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> ARP.ElevatedPoint.pos </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliport without ARP.ElevatedPoint.pos value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliport ARP.ElevatedPoint.pos N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33A6 Error AIXM 4.5 Each AuthorityForAirspace shall have assigned assignedAirspace value <keyword> Each </keyword><noun_concept> AuthorityForAirspace </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> assignedAirspace </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AuthorityForAirspace without assignedAirspace value. Backwards mapping to AIXM 4.5 will not be possible. AuthorityForAirspace assignedAirspace N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33A9 Error AIXM 4.5 Each Airspace shall have assigned designator value <keyword> Each </keyword><noun_concept> Airspace </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Airspace without designator value. Backwards mapping to AIXM 4.5 will not be possible. Airspace designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33AB Error AIXM 4.5 Each DME shall have assigned authority value <keyword> Each </keyword><noun_concept> DME </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> authority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found DME without authority value. Backwards mapping to AIXM 4.5 will not be possible. DME authority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33AC Error AIXM 4.5 Each Runway shall have assigned associatedAirportHeliport value <keyword> Each </keyword><noun_concept> Runway </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> associatedAirportHeliport </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Runway without associatedAirportHeliport value. Backwards mapping to AIXM 4.5 will not be possible. Runway associatedAirportHeliport N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33B0 Error AIXM 4.5 Each AuthorityForAirspace shall have assigned responsibleOrganisation value <keyword> Each </keyword><noun_concept> AuthorityForAirspace </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> responsibleOrganisation </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AuthorityForAirspace without responsibleOrganisation value. Backwards mapping to AIXM 4.5 will not be possible. AuthorityForAirspace responsibleOrganisation N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33B5 Error AIXM 4.5 Each GeoBorder shall have assigned name value <keyword> Each </keyword><noun_concept> GeoBorder </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> name </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found GeoBorder without name value. Backwards mapping to AIXM 4.5 will not be possible. GeoBorder name N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33BA Error AIXM 4.5 Each VOR shall have assigned authority value <keyword> Each </keyword><noun_concept> VOR </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> authority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found VOR without authority value. Backwards mapping to AIXM 4.5 will not be possible. VOR authority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33C0 Error AIXM 4.5 Each VOR shall have assigned frequency value <keyword> Each </keyword><noun_concept> VOR </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found VOR without frequency value. Backwards mapping to AIXM 4.5 will not be possible. VOR frequency N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33C5 Error AIXM 4.5 Each AirportHeliport shall have assigned responsibleOrganisation value <keyword> Each </keyword><noun_concept> AirportHeliport </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> responsibleOrganisation </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliport without responsibleOrganisation value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliport responsibleOrganisation N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33C8 Error AIXM 4.5 Each VOR shall have assigned zeroBearingDirection value <keyword> Each </keyword><noun_concept> VOR </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> zeroBearingDirection </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found VOR without zeroBearingDirection value. Backwards mapping to AIXM 4.5 will not be possible. VOR zeroBearingDirection N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33CB Error AIXM 4.5 Each TACAN shall have assigned designator value <keyword> Each </keyword><noun_concept> TACAN </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found TACAN without designator value. Backwards mapping to AIXM 4.5 will not be possible. TACAN designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33D5 Error AIXM 4.5 Each OrganisationAuthority shall have assigned name value <keyword> Each </keyword><noun_concept> OrganisationAuthority </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> name </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found OrganisationAuthority without name value. Backwards mapping to AIXM 4.5 will not be possible. OrganisationAuthority name N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33D7 Error AIXM 4.5 Each MarkerBeacon shall have assigned authority value <keyword> Each </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> authority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found MarkerBeacon without authority value. Backwards mapping to AIXM 4.5 will not be possible. MarkerBeacon authority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33DB Error AIXM 4.5 Each Navaid shall have assigned type value <keyword> Each </keyword><noun_concept> Navaid </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Navaid without type value. Backwards mapping to AIXM 4.5 will not be possible. Navaid type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33DF Error AIXM 4.5 Each MarkerBeacon shall have assigned designator value <keyword> Each </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found MarkerBeacon without designator value. Backwards mapping to AIXM 4.5 will not be possible. MarkerBeacon designator N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E0 Error AIXM 4.5 Each Airspace shall have assigned geometryComponent value <keyword> Each </keyword><noun_concept> Airspace </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> geometryComponent </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Airspace without geometryComponent value. Backwards mapping to AIXM 4.5 will not be possible. Airspace geometryComponent N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E1 Error AIXM 4.5 Each AirspaceGeometryComponent shall have assigned theAirspaceVolume value <keyword> Each </keyword><noun_concept> AirspaceGeometryComponent </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theAirspaceVolume </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirspaceGeometryComponent without theAirspaceVolume value. Backwards mapping to AIXM 4.5 will not be possible. AirspaceGeometryComponent theAirspaceVolume N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E2 Error AIXM 4.5 Each AirspaceVolumeDependency shall have assigned theAirspace value <keyword> Each </keyword><noun_concept> AirspaceVolumeDependency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theAirspace </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirspaceVolumeDependency without theAirspace value. Backwards mapping to AIXM 4.5 will not be possible. AirspaceVolumeDependency theAirspace N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E3 Error AIXM 4.5 Each AirspaceVolumeDependency shall have assigned dependency value <keyword> Each </keyword><noun_concept> AirspaceVolumeDependency </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> dependency </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirspaceVolumeDependency without dependency value. Backwards mapping to AIXM 4.5 will not be possible. AirspaceVolumeDependency dependency N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33E4 Error AIXM 4.5 Each AirportHeliportResponsibilityOrganisation shall have assigned theOrganisationAuthority value <keyword> Each </keyword><noun_concept> AirportHeliportResponsibilityOrganisation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theOrganisationAuthority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AirportHeliportResponsibilityOrganisation without theOrganisationAuthority value. Backwards mapping to AIXM 4.5 will not be possible. AirportHeliportResponsibilityOrganisation theOrganisationAuthority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33EB Error AIXM 4.5 Each OrganisationAuthorityAssociation shall have assigned theOrganisationAuthority value <keyword> Each </keyword><noun_concept> OrganisationAuthorityAssociation </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theOrganisationAuthority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found OrganisationAuthorityAssociation without theOrganisationAuthority value. Backwards mapping to AIXM 4.5 will not be possible. OrganisationAuthorityAssociation theOrganisationAuthority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33EC Error AIXM 4.5 Each AuthorityForNavaidEquipment shall have assigned theOrganisationAuthority value <keyword> Each </keyword><noun_concept> AuthorityForNavaidEquipment </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theOrganisationAuthority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found AuthorityForNavaidEquipment without theOrganisationAuthority value. Backwards mapping to AIXM 4.5 will not be possible. AuthorityForNavaidEquipment theOrganisationAuthority N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33EF Error AIXM 4.5 Each RouteSegment shall have assigned routeFormed value <keyword> Each </keyword><noun_concept> RouteSegment </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> routeFormed </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found RouteSegment without routeFormed value. Backwards mapping to AIXM 4.5 will not be possible. RouteSegment routeFormed N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33F1 Error AIXM 4.5 Each Unit shall have assigned compliantICAO value <keyword> Each </keyword><noun_concept> Unit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> compliantICAO </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Unit without compliantICAO value. Backwards mapping to AIXM 4.5 will not be possible. Unit compliantICAO N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33F2 Error AIXM 4.5 Each Unit shall have assigned type value <keyword> Each </keyword><noun_concept> Unit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Unit without type value. Backwards mapping to AIXM 4.5 will not be possible. Unit type N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1A33F3 Error AIXM 4.5 Each Unit shall have assigned name value <keyword> Each </keyword><noun_concept> Unit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> name </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version. Found Unit without name value. Backwards mapping to AIXM 4.5 will not be possible. Unit name N/A Minimal data rule Minimal feature properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-54791 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'VOR_DME' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type VOR_DME shall be published with 1 sec resolution Latitude and Longitude of Navaid of type VOR_DME shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type VOR_DME
AIXM-5.1_RULE-54792 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'VORTAC' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type VORTAC shall be published with 1 sec resolution Latitude and Longitude of Navaid of type VORTAC shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type VORTAC
AIXM-5.1_RULE-54793 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'DME' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type DME shall be published with 1 sec resolution Latitude and Longitude of Navaid of type DME shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type DME
AIXM-5.1_RULE-54794 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'TACAN' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type TACAN shall be published with 1 sec resolution Latitude and Longitude of Navaid of type TACAN shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type TACAN
AIXM-5.1_RULE-54795 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'VOR' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type VOR shall be published with 1 sec resolution Latitude and Longitude of Navaid of type VOR shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type VOR
AIXM-5.1_RULE-54796 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'NDB' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type NDB shall be published with 1 sec resolution Latitude and Longitude of Navaid of type NDB shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type NDB
AIXM-5.1_RULE-54797 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'MKR' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type MKR shall be published with 1 sec resolution Latitude and Longitude of Navaid of type MKR shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type MKR
AIXM-5.1_RULE-54798 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'SDF' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type SDF shall be published with 1 sec resolution Latitude and Longitude of Navaid of type SDF shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type SDF
AIXM-5.1_RULE-54799 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'NDB_MKR' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type NDB_MKR shall be published with 1 sec resolution Latitude and Longitude of Navaid of type NDB_MKR shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type NDB_MKR
AIXM-5.1_RULE-5479A Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'NDB_DME' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type NDB_DME shall be published with 1 sec resolution Latitude and Longitude of Navaid of type NDB_DME shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type NDB_DME
AIXM-5.1_RULE-5479B Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'DF' has location.ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type DF shall be published with 1 sec resolution Latitude and Longitude of Navaid of type DF shall be published with 1 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type DF
AIXM-5.1_RULE-5479C Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'ILS_DME' has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS_DME' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type ILS_DME shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type ILS_DME shall be published with 1/10 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type ILS_DME
AIXM-5.1_RULE-5479D Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'MLS_DME' has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS_DME' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type MLS_DME shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type MLS_DME shall be published with 1/10 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type MLS_DME
AIXM-5.1_RULE-5479E Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'LOC_DME' has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC_DME' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type LOC_DME shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type LOC_DME shall be published with 1/10 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type LOC_DME
AIXM-5.1_RULE-5479F Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'MLS' has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type MLS shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type MLS shall be published with 1/10 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type MLS
AIXM-5.1_RULE-547A0 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'TLS' has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type TLS shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type TLS shall be published with 1/10 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type TLS
AIXM-5.1_RULE-547A1 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'LOC' has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type LOC shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type LOC shall be published with 1/10 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type LOC
AIXM-5.1_RULE-547A2 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'ILS' has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type ILS shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type ILS shall be published with 1/10 sec resolution Navaid type, location baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type ILS
AIXM-5.1_RULE-1AA451 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with assigned servedAirport value isComposedOf NavaidEquipment specialisation VOR with location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of VOR, when used for aerodrome operations, shall be published with 1/10 sec resolution Latitude and Longitude of VOR, when used for aerodrome operations, shall be published with 1/10 sec resolution Navaid set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - VOR when used at aerodrome (EAD profile)
AIXM-5.1_RULE-1AA452 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with assigned servedAirport value isComposedOf NavaidEquipment specialisation DME with location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of DME, when used for aerodrome operations, shall be published with 1/10 sec resolution Latitude and Longitude of DME, when used for aerodrome operations, shall be published with 1/10 sec resolution Navaid set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - DME when used at aerodrome (EAD profile)
AIXM-5.1_RULE-1AA453 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with assigned servedAirport value isComposedOf NavaidEquipment specialisation MarkerBeacon with location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of MarkerBeacon, when used for aerodrome operations, shall be published with 1/10 sec resolution Latitude and Longitude of MarkerBeacon, when used for aerodrome operations, shall be published with 1/10 sec resolution Navaid set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - MarkerBeacon when used at aerodrome (EAD profile)
AIXM-5.1_RULE-1AA454 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with assigned servedAirport value isComposedOf NavaidEquipment specialisation NDB with location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of NDB, when used for aerodrome operations, shall be published with 1/10 sec resolution Latitude and Longitude of NDB, when used for aerodrome operations, shall be published with 1/10 sec resolution Navaid set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - NDB when used at aerodrome (EAD profile)
AIXM-5.1_RULE-1AA457 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with assigned servedAirport value isComposedOf NavaidEquipment specialisation TACAN with location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of TACAN, when used for aerodrome operations, shall be published with 1/10 sec resolution Latitude and Longitude of TACAN, when used for aerodrome operations, shall be published with 1/10 sec resolution Navaid set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - TACAN when used at aerodrome (EAD profile)
AIXM-5.1_RULE-BB804 Error AIXM Model It is obligatory that each ApproachLeg specialisation ArrivalFeederLeg with assigned approach value has approach value resolved-into exactly one isPartOf Procedure specialisation InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ArrivalFeederLeg </noun_concept><keyword> with assigned </keyword><noun_concept> approach </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approach </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isPartOf </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. ArrivalFeederLeg approach set of snapshots Minimal data rule Referential integrity - second level of inheritance for the class and first level of inheritance for the targetClass (EAD profile)
AIXM-5.1_RULE-BB805 Error AIXM Model It is obligatory that each ApproachLeg specialisation InitialLeg with assigned approach value has approach value resolved-into exactly one isPartOf Procedure specialisation InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InitialLeg </noun_concept><keyword> with assigned </keyword><noun_concept> approach </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approach </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isPartOf </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. InitialLeg approach set of snapshots Minimal data rule Referential integrity - second level of inheritance for the class and first level of inheritance for the targetClass (EAD profile)
AIXM-5.1_RULE-BB806 Error AIXM Model It is obligatory that each ApproachLeg specialisation IntermediateLeg with assigned approach value has approach value resolved-into exactly one isPartOf Procedure specialisation InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> IntermediateLeg </noun_concept><keyword> with assigned </keyword><noun_concept> approach </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approach </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isPartOf </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. IntermediateLeg approach set of snapshots Minimal data rule Referential integrity - second level of inheritance for the class and first level of inheritance for the targetClass (EAD profile)
AIXM-5.1_RULE-BB807 Error AIXM Model It is obligatory that each ApproachLeg specialisation FinalLeg with assigned approach value has approach value resolved-into exactly one isPartOf Procedure specialisation InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> FinalLeg </noun_concept><keyword> with assigned </keyword><noun_concept> approach </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approach </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isPartOf </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. FinalLeg approach set of snapshots Minimal data rule Referential integrity - second level of inheritance for the class and first level of inheritance for the targetClass (EAD profile)
AIXM-5.1_RULE-BB808 Error AIXM Model It is obligatory that each ApproachLeg specialisation MissedApproachLeg with assigned approach value has approach value resolved-into exactly one isPartOf Procedure specialisation InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> ApproachLeg </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MissedApproachLeg </noun_concept><keyword> with assigned </keyword><noun_concept> approach </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approach </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isPartOf </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. MissedApproachLeg approach set of snapshots Minimal data rule Referential integrity - second level of inheritance for the class and first level of inheritance for the targetClass (EAD profile)
AIXM-5.1_RULE-68011 Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy higher-than 3.0 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA2 shall be better than 3.0 M The elevation/height accuracy obstacles in AREA2 shall be better than 3.0 M VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA2
AIXM-5.1_RULE-68012 Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy higher-than 1.0 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA2 shall be better than 1.0 FT The elevation/height accuracy obstacles in AREA2 shall be better than 1.0 FT VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA2
AIXM-5.1_RULE-68013 Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy higher-than 1.0 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA2 shall be better than 1.0 FT The elevation/height accuracy obstacles in AREA2 shall be better than 1.0 FT VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA2
AIXM-5.1_RULE-68014 Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy higher-than 0.5 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA3 shall be better than 0.5 M The elevation/height accuracy obstacles in AREA3 shall be better than 0.5 M VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA3
AIXM-5.1_RULE-68015 Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy higher-than 1.0 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA2 shall be better than 1.0 FT The elevation/height accuracy obstacles in AREA2 shall be better than 1.0 FT VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA2
AIXM-5.1_RULE-68016 Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy higher-than 3.0 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA2 shall be better than 3.0 M The elevation/height accuracy obstacles in AREA2 shall be better than 3.0 M VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA2
AIXM-5.1_RULE-68017 Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy higher-than 3.0 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA2 shall be better than 3.0 M The elevation/height accuracy obstacles in AREA2 shall be better than 3.0 M VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA2
AIXM-5.1_RULE-68018 Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy higher-than 0.1 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA3 shall be better than 0.1 FT The elevation/height accuracy obstacles in AREA3 shall be better than 0.1 FT VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA3
AIXM-5.1_RULE-68019 Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy higher-than 0.1 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA3 shall be better than 0.1 FT The elevation/height accuracy obstacles in AREA3 shall be better than 0.1 FT VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA3
AIXM-5.1_RULE-6801A Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy higher-than 0.5 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA3 shall be better than 0.5 M The elevation/height accuracy obstacles in AREA3 shall be better than 0.5 M VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA3
AIXM-5.1_RULE-6801B Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy higher-than 0.1 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA3 shall be better than 0.1 FT The elevation/height accuracy obstacles in AREA3 shall be better than 0.1 FT VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA3
AIXM-5.1_RULE-6801C Warning ICAO Annex 14 Table A5-2 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy higher-than 0.5 <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve.verticalAccuracy </noun_concept><keyword> higher-than </keyword> The elevation/height accuracy obstacles in AREA3 shall be better than 0.5 M The elevation/height accuracy obstacles in AREA3 shall be better than 0.5 M VerticalStructure verticalAccuracy set of snapshots Standard (ICAO, industry, etc.) Accuracy (vertical) - Obstacles in AREA3
AIXM-5.1_RULE-156879 Error AIXM Model AIXM Model It is obligatory that each NavigationAreaRestriction with assigned procedure value has procedure value resolved-into exactly one isAppliedTo Procedure specialisation StandardInstrumentDeparture or StandardInstrumentArrival or InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> NavigationAreaRestriction </noun_concept><keyword> with assigned </keyword><noun_concept> procedure </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> procedure </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAppliedTo </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> or </keyword><noun_concept> StandardInstrumentArrival </noun_concept><keyword> or </keyword><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Referential integrity error: the NavigationAreaRestriction association " isAppliedTo" Procedure (StandardInstrumentDeparture, StandardInstrumentArrival or InstrumentApproachProcedure) cannot be resolved. NavigationAreaRestriction procedure set of snapshots Minimal data rule Referential integrity - towards Procedure
AIXM-5.1_RULE-15687A Error AIXM Model AIXM Model It is obligatory that each InformationService with assigned clientProcedure value has clientProcedure value resolved-into exactly one concerns Procedure specialisation StandardInstrumentDeparture or StandardInstrumentArrival or InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> InformationService </noun_concept><keyword> with assigned </keyword><noun_concept> clientProcedure </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> clientProcedure </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> concerns </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> or </keyword><noun_concept> StandardInstrumentArrival </noun_concept><keyword> or </keyword><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. Referential integrity error: the InformationService association " concerns" Procedure (StandardInstrumentDeparture, StandardInstrumentArrival or InstrumentApproachProcedure) cannot be resolved. InformationService clientProcedure set of snapshots Minimal data rule Referential integrity - towards Procedure
AIXM-5.1_RULE-1A17B1 Error Error AIXM 4.5 Character 1 data type It is prohibited that an OrganisationAuthority has designator with assigned value pattern not equal-to '([A-Z]|[0-9])+([ \+\-/]?([A-Z]|[0-9])+)*' <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> OrganisationAuthority </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> with </keyword><keyword> assigned value </keyword><keyword> not </keyword><keyword> equal-to </keyword><name> '([A-Z]|[0-9])+([ \+\-/]?([A-Z]|[0-9])+)*' </name> OrganisationAuthority. designator cannot have two consecutive special characters and cannot start with a special character. Found OrganisationAuthority. designator value that has two consecutive special characters (space, +, -, /) or that starts with a special character. This is not allowed in AIXM 4.5 and would block the backwards mapping OrganisationAuthority designator All Standard (ICAO, industry, etc.) Character1 - legacy limitation for special characters
AIXM-5.1_RULE-1A17B2 Warning AIXM 4.5 Character 1 data type It is prohibited that an StandardInstrumentDeparture has designator with assigned value pattern not equal-to '([A-Z]|[0-9])+([ \+\-/]?([A-Z]|[0-9])+)*' <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> StandardInstrumentDeparture </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> with </keyword><keyword> assigned value </keyword><keyword> not </keyword><keyword> equal-to </keyword><name> '([A-Z]|[0-9])+([ \+\-/]?([A-Z]|[0-9])+)*' </name> StandardInstrumentDeparture.designator cannot have two consecutive special characters and cannot start with a special character. Found StandardInstrumentDeparture.designator value that has two consecutive special characters (space, +, -, /) or that starts with a special character. This is not allowed in AIXM 4.5 and would block the backwards mapping StandardInstrumentDeparture designator All Standard (ICAO, industry, etc.) Character1 - legacy limitation for special characters
AIXM-5.1_RULE-1A17B3 AIXM 4.5 Character 1 data type It is prohibited that an FlightRestriction has designator with assigned value pattern not equal-to '([A-Z]|[0-9])+([ \+\-/]?([A-Z]|[0-9])+)*' <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> FlightRestriction </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> with </keyword><keyword> assigned value </keyword><keyword> not </keyword><keyword> equal-to </keyword><name> '([A-Z]|[0-9])+([ \+\-/]?([A-Z]|[0-9])+)*' </name> FlightRestriction.designator cannot have two consecutive special characters and cannot start with a special character. Found FlightRestriction.designator value that has two consecutive special characters (space, +, -, /) or that starts with a special character. This is not allowed in AIXM 4.5 and would block the backwards mapping FlightRestriction designator All Standard (ICAO, industry, etc.) Character1 - legacy limitation for special characters
AIXM-5.1_RULE-1A17B4 Warning AIXM 4.5 Character 1 data type It is prohibited that an StandardInstrumentArrival has designator with assigned value pattern not equal-to '([A-Z]|[0-9])+([ \+\-/]?([A-Z]|[0-9])+)*' <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> StandardInstrumentArrival </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> with </keyword><keyword> assigned value </keyword><keyword> not </keyword><keyword> equal-to </keyword><name> '([A-Z]|[0-9])+([ \+\-/]?([A-Z]|[0-9])+)*' </name> StandardInstrumentArrival.designator cannot have two consecutive special characters and cannot start with a special character. Found StandardInstrumentArrival.designator value that has two consecutive special characters (space, +, -, /) or that starts with a special character. This is not allowed in AIXM 4.5 and would block the backwards mapping StandardInstrumentArrival designator All Standard (ICAO, industry, etc.) Character1 - legacy limitation for special characters
AIXM-5.1_RULE-C2561 AIXM Model Each AerialRefuelling shall have assigned designatorNumber value <keyword> Each </keyword><noun_concept> AerialRefuelling </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designatorNumber </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for the data to make sense Found AerialRefuelling without designatorNumber value. The data is not operationally usable. AerialRefuelling designatorNumber N/A Minimal data rule Minimal feature properties (other than due to AIXM 4.5)
AIXM-5.1_RULE-C2562 AIXM Model Each AerialRefuelling shall have assigned designatorPrefix value <keyword> Each </keyword><noun_concept> AerialRefuelling </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> designatorPrefix </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for the data to make sense Found AerialRefuelling without designatorPrefix value. The data is not operationally usable. AerialRefuelling designatorPrefix N/A Minimal data rule Minimal feature properties (other than due to AIXM 4.5)
AIXM-5.1_RULE-C2563 AIXM Model Each AuthorityForAerialRefuelling shall have assigned theOrganisationAuthority value <keyword> Each </keyword><noun_concept> AuthorityForAerialRefuelling </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> theOrganisationAuthority </noun_concept><keyword> value </keyword> For each instance of a feature/object, some properties are mandatory for the data to make sense Found AuthorityForAerialRefuelling without theOrganisationAuthority value. The data is not operationally usable. AuthorityForAerialRefuelling theOrganisationAuthority N/A Minimal data rule Minimal feature properties (other than due to AIXM 4.5)
AIXM-5.1_RULE-1A0BF9 Error AIXM 4.5 Business Rules It is prohibited that AirspaceVolume with assigned centreline value has assigned contributorAirspace value <keyword> It is prohibited that </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> centreline </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> contributorAirspace </noun_concept><keyword> value </keyword> An AirspaceVolume cannot have in the same time horizontalProjection, centreline and contributorAirspace Found AirspaceVolume with both centreline and contributorAirspace AirspaceVolume All Data consistency rule AirspaceVolume unique geometry
AIXM-5.1_RULE-1A0BFA Error AIXM 4.5 Business Rules It is prohibited that AirspaceVolume with assigned horizontalProjection value has assigned contributorAirspace value <keyword> It is prohibited that </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> horizontalProjection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> contributorAirspace </noun_concept><keyword> value </keyword> An AirspaceVolume cannot have in the same time horizontalProjection, centreline and contributorAirspace Found AirspaceVolume with both horizontalProjection and contributorAirspace AirspaceVolume All Data consistency rule AirspaceVolume unique geometry
AIXM-5.1_RULE-1A0BFB Error AIXM 4.5 Business Rules It is prohibited that AirspaceVolume with assigned horizontalProjection value has assigned centreline value <keyword> It is prohibited that </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> horizontalProjection </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> centreline </noun_concept><keyword> value </keyword> An AirspaceVolume cannot have in the same time horizontalProjection, centreline and contributorAirspace Found AirspaceVolume with both horizontalProjection and centreline AirspaceVolume All Data consistency rule AirspaceVolume unique geometry
AIXM-5.1_RULE-C2D31 Error AIXM 4.5 mapping It is prohibited that a RouteSegment.level has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment.level </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in RouteSegment.level are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in RouteSegment.level. Backward mapping to AIXM 4.5 not possible. RouteSegment level All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D32 Error AIXM 4.5 mapping It is prohibited that a AirspaceGeometryComponent.operation has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceGeometryComponent.operation </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in AirspaceGeometryComponent.operation are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in AirspaceGeometryComponent.operation. Backward mapping to AIXM 4.5 not possible. AirspaceGeometryComponent operation All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D33 Error AIXM 4.5 mapping It is prohibited that a MarkerBeacon. frequency.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> MarkerBeacon. frequency.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in MarkerBeacon. frequency.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in MarkerBeacon. frequency.uom. Backward mapping to AIXM 4.5 not possible. MarkerBeacon frequency.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D34 Error AIXM 4.5 mapping It is prohibited that a NDB. frequency.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NDB. frequency.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in NDB. frequency.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in NDB. frequency.uom. Backward mapping to AIXM 4.5 not possible. NDB frequency.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D35 Error AIXM 4.5 mapping It is prohibited that a VOR.frequency.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VOR.frequency.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in VOR.frequency.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in VOR.frequency.uom. Backward mapping to AIXM 4.5 not possible. VOR frequency.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D36 Error AIXM 4.5 mapping It is prohibited that a AirspaceVolume. minimumLimit.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume. minimumLimit.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in AirspaceVolume. minimumLimit.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in AirspaceVolume. minimumLimit.uom. Backward mapping to AIXM 4.5 not possible. AirspaceVolume minimumLimit.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D37 Error AIXM 4.5 mapping It is prohibited that a AirspaceVolume. maximumLimit.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume. maximumLimit.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in AirspaceVolume. maximumLimit.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in AirspaceVolume. maximumLimit.uom. Backward mapping to AIXM 4.5 not possible. AirspaceVolume maximumLimit.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D38 Error AIXM 4.5 mapping It is prohibited that a RouteSegment.lowerLimit.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment.lowerLimit.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in RouteSegment.lowerLimit.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in RouteSegment.lowerLimit.uom. Backward mapping to AIXM 4.5 not possible. RouteSegment lowerLimit.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D39 Error AIXM 4.5 mapping It is prohibited that a RouteSegment. upperLimit.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment. upperLimit.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in RouteSegment. upperLimit.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in RouteSegment. upperLimit.uom. Backward mapping to AIXM 4.5 not possible. RouteSegment upperLimit.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D3A Error AIXM 4.5 mapping It is prohibited that a AirportHeliport.fieldElevation.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHeliport.fieldElevation.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in AirportHeliport.fieldElevation.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in AirportHeliport.fieldElevation.uom. Backward mapping to AIXM 4.5 not possible. AirportHeliport fieldElevation.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D3B Error AIXM 4.5 mapping It is prohibited that a AirspaceVolume.upperLimit.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume.upperLimit.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in AirspaceVolume.upperLimit.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in AirspaceVolume.upperLimit.uom. Backward mapping to AIXM 4.5 not possible. AirspaceVolume upperLimit.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D3C Error AIXM 4.5 mapping It is prohibited that a AirspaceVolume. lowerLimit.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume. lowerLimit.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in AirspaceVolume. lowerLimit.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in AirspaceVolume. lowerLimit.uom. Backward mapping to AIXM 4.5 not possible. AirspaceVolume lowerLimit.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D3D Error AIXM 4.5 mapping It is prohibited that a RouteSegment.widthLeft.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment.widthLeft.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in RouteSegment.widthLeft.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in RouteSegment.widthLeft.uom. Backward mapping to AIXM 4.5 not possible. RouteSegment widthLeft.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D3E Error AIXM 4.5 mapping It is prohibited that a RouteSegment. widthRight.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment. widthRight.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in RouteSegment. widthRight.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in RouteSegment. widthRight.uom. Backward mapping to AIXM 4.5 not possible. RouteSegment widthRight.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D3F Error AIXM 4.5 mapping It is prohibited that a RouteSegment. length.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment. length.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in RouteSegment. length.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in RouteSegment. length.uom. Backward mapping to AIXM 4.5 not possible. RouteSegment length.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D40 Error AIXM 4.5 mapping It is prohibited that a AirspaceVolume.width.uom has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume.width.uom </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in AirspaceVolume.width.uom are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in AirspaceVolume.width.uom. Backward mapping to AIXM 4.5 not possible. AirspaceVolume width.uom All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D41 Error AIXM 4.5 mapping It is prohibited that a Route. designatorPrefix has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Route. designatorPrefix </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in Route. designatorPrefix are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in Route. designatorPrefix. Backward mapping to AIXM 4.5 not possible. Route designatorPrefix All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D42 Error AIXM 4.5 mapping It is prohibited that a Route. multipleIdentifier has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Route. multipleIdentifier </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in Route. multipleIdentifier are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in Route. multipleIdentifier. Backward mapping to AIXM 4.5 not possible. Route multipleIdentifier All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-C2D43 Error AIXM 4.5 mapping It is prohibited that a Route. designatorSecondLetter has assigned value equal-to 'OTHER' or has assigned value starting-with 'OTHER:' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Route. designatorSecondLetter </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><keyword> equal-to </keyword><name> 'OTHER' </name><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'OTHER:' </name> The values OTHER and OTHER:.. in Route. designatorSecondLetter are not supported for mapping to 4.5 Found unsupported values (OTHER or OTHER:...) in Route. designatorSecondLetter . Backward mapping to AIXM 4.5 not possible. Route designatorSecondLetter All Standard (ICAO, industry, etc.) OTHER values not supported for backward mapping
AIXM-5.1_RULE-4269 Error AIXM 4.5 AIXM 4.5 It is prohibited that an Airspace has at least 2 geometryComponent and Airspace has at most 9 geometryComponent and Airspace has designator longer than 9 characters <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> at least 2 </keyword><noun_concept> geometryComponent </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> at most 9 </keyword><noun_concept> geometryComponent </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept> In order to enable the automatic creation of PART type Airspace in AIXM 4.5, for an Airspace that has between 2 and 9 AirspaceVolume, the Airspace designator cannot have more than 9 characters. Found Airspace composed of multiple AirspaceVolume and which has a too long designator. Not possible to automatically generate a valid designator for the PART Airspace in AIXM 4.5 Airspace designator baseline outside delta, snapshot, set of snapshots Data consistency rule Airspace aggregation - designator size
AIXM-5.1_RULE-426A Error AIXM 4.5 AIXM 4.5 It is prohibited that an Airspace has at least 10 geometryComponent and Airspace has at most 99 geometryComponent and Airspace has designator longer than 8 characters <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> at least 10 </keyword><noun_concept> geometryComponent </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> at most 99 </keyword><noun_concept> geometryComponent </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept> In order to enable the automatic creation of PART type Airspace in AIXM 4.5, for an Airspace that has between 10 and 99 AirspaceVolume, the Airspace designator cannot have more than 8 characters. Found Airspace composed of multiple AirspaceVolume and which has a too long designator. Not possible to automatically generate a valid designator for the PART Airspace in AIXM 4.5 Airspace designator baseline outside delta, snapshot, set of snapshots Data consistency rule Airspace aggregation - designator size
AIXM-5.1_RULE-1B1D69 AIXM 4.5 AIXM 4.5 It is prohibited that at least one VOR and not Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> VOR </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> A Navaid service must be defined for each VOR equipment Note: this rule was originally introduced in the EAD:Error profile in order to protect the backwards mapping to AIXM 4.5. The rule does no longer seem to be required by EAD. Found VOR equipment not used by any Navaid. VOR baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) NavaidEquipment mandatory used by Navaid
AIXM-5.1_RULE-1B1D6A AIXM 4.5 AIXM 4.5 It is prohibited that at least one MarkerBeacon and not Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> A Navaid service must be defined for each MarkerBeacon equipment Note: this rule was originally introduced in the EAD:Error profile in order to protect the backwards mapping to AIXM 4.5. The rule does no longer seem to be required by EAD. Found MarkerBeacon equipment not used by any Navaid. MarkerBeacon baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) NavaidEquipment mandatory used by Navaid
AIXM-5.1_RULE-1B1D6B AIXM 4.5 AIXM 4.5 It is prohibited that at least one NDB and not Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> NDB </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> A Navaid service must be defined for each NDB equipment Note: this rule was originally introduced in the EAD:Error profile in order to protect the backwards mapping to AIXM 4.5. The rule does no longer seem to be required by EAD. Found NDB equipment not used by any Navaid. NDB baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) NavaidEquipment mandatory used by Navaid
AIXM-5.1_RULE-1B1D6C AIXM 4.5 AIXM 4.5 It is prohibited that at least one TACAN and not Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> TACAN </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> A Navaid service must be defined for each TACAN equipment Note: this rule was originally introduced in the EAD:Error profile in order to protect the backwards mapping to AIXM 4.5. The rule does no longer seem to be required by EAD. Found TACAN equipment not used by any Navaid. TACAN baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) NavaidEquipment mandatory used by Navaid
AIXM-5.1_RULE-1B1D6D AIXM 4.5 AIXM 4.5 It is prohibited that at least one DME and not Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment resolves-into NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> DME </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid.navaidEquipment.NavaidComponent.theNavaidEquipment </noun_concept><keyword> resolves-into </keyword><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> A Navaid service must be defined for each DME equipment Note: this rule was originally introduced in the EAD:Error profile in order to protect the backwards mapping to AIXM 4.5. The rule does no longer seem to be required by EAD. Found DME equipment not used by any Navaid. DME baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) NavaidEquipment mandatory used by Navaid
AIXM-5.1_RULE-1B30F1 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.GeodesicString.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.GeodesicString.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30F2 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30F3 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.CircleByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30F4 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.GeodesicString.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.GeodesicString.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30F5 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Circle.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.Circle.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30F6 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30F7 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcString.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcString.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30F8 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.LineStringSegment.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.LineStringSegment.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30F9 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Arc.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.Arc.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30FA Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.LineStringSegment.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.LineStringSegment.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30FB Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Geodesic.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.Geodesic.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30FC Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcString.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcString.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30FD Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcByCenterPoint.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30FE Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.CircleByCenterPoint.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.CircleByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B30FF Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Geodesic.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.Geodesic.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3100 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Geodesic.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.Geodesic.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3101 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcByCenterPoint.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3102 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.CircleByCenterPoint.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.CircleByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3103 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.GeodesicString.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.GeodesicString.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3104 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Arc.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.Arc.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3105 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcString.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcString.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3106 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Geodesic.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.Geodesic.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3107 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Circle.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.Circle.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3108 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Arc.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.Arc.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3109 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.LineStringSegment.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.LineStringSegment.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B310A Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.LineStringSegment.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.LineStringSegment.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B310B Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.GeodesicString.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.GeodesicString.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B310C Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Circle.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.Circle.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B310D Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.posList with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.CircleByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B310E Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcString.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcString.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B310F Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Circle.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.Circle.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B3110 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Arc.pos with not assigned srsName value and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside a Surface) with neither its own nor inherited srsName value Surface segments.Arc.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve positions
AIXM-5.1_RULE-1B09E1 Error Error Error AIXM Model Route model It is obligatory that each RouteSegment has assigned end.EnRouteSegmentPoint.pointChoice.SignificantPoint.navaidSystem value or has assigned end.EnRouteSegmentPoint.pointChoice.SignificantPoint.fixDesignatedPoint value or has assigned end.EnRouteSegmentPoint.pointChoice.SignificantPoint.position value <keyword> It is obligatory that </keyword><keyword> each </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> end.EnRouteSegmentPoint.pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> end.EnRouteSegmentPoint.pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> end.EnRouteSegmentPoint.pointChoice.SignificantPoint.position </noun_concept><keyword> value </keyword> RouteSegment must have end point at Navaid, DesignatedPoint or geographical position Found RouteSegment without end point at Navaid, DesignatedPoint or geographical position RouteSegment All Minimal data rule RouteSegment mandatory end point
AIXM-5.1_RULE-1B09E2 Error Error Error AIXM Model Route model It is obligatory that each RouteSegment has assigned start.EnRouteSegmentPoint.pointChoice.SignificantPoint.navaidSystem value or has assigned start.EnRouteSegmentPoint.pointChoice.SignificantPoint.fixDesignatedPoint value or has assigned start.EnRouteSegmentPoint.pointChoice.SignificantPoint.position value <keyword> It is obligatory that </keyword><keyword> each </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> start.EnRouteSegmentPoint.pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> start.EnRouteSegmentPoint.pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><keyword> or </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> start.EnRouteSegmentPoint.pointChoice.SignificantPoint.position </noun_concept><keyword> value </keyword> RouteSegment must have start point at Navaid, DesignatedPoint or geographical position Found RouteSegment without start point at Navaid, DesignatedPoint or geographical position RouteSegment All Minimal data rule RouteSegment mandatory start point
AIXM-5.1_RULE-9F6C9 Error AIXM 4.5 NUMBER formats It is prohibited that a NDB has assigned frequency value expressed with more than 4 decimals <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NDB </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword> The resolution of NDB.frequency cannot exceed 4 decimals for the mapping towards AIXM 4.5 to be possible. Found NDB.frequency with more than 4 decimals, mapping to AIXM 4.5 is not possible. NDB frequency All Recommended practice (ICAO, industry, etc.) Maximum resolution for AIXM 4.5 mapping
AIXM-5.1_RULE-9F6CA Error AIXM 4.5 NUMBER formats It is prohibited that a MarkerBeacon has assigned frequency value expressed with more than 4 decimals <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> MarkerBeacon </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword> The resolution of MarkerBeacon. frequency cannot exceed 4 decimals for the mapping towards AIXM 4.5 to be possible. Found MarkerBeacon. frequency with more than 4 decimals, mapping to AIXM 4.5 is not possible. MarkerBeacon frequency All Recommended practice (ICAO, industry, etc.) Maximum resolution for AIXM 4.5 mapping
AIXM-5.1_RULE-9F6CB Error AIXM 4.5 NUMBER formats It is prohibited that a VOR has assigned frequency value expressed with more than 4 decimals <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword> The resolution of VOR.frequency cannot exceed 4 decimals for the mapping towards AIXM 4.5 to be possible. Found VOR.frequency with more than 4 decimals, mapping to AIXM 4.5 is not possible. VOR frequency All Recommended practice (ICAO, industry, etc.) Maximum resolution for AIXM 4.5 mapping
AIXM-5.1_RULE-F07A9 Error EAD EAD It is prohibited that a RouteSegment has minimumObstacleClearanceAltitude equal-to ('FLOOR', 'CEILING') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><noun_concept> minimumObstacleClearanceAltitude </noun_concept><keyword> equal-to </keyword><name> ('FLOOR', 'CEILING') </name> RouteSegment cannot use coded values as minimumObstacleClearanceAltitude limits Found RouteSegment with coded minimumObstacleClearanceAltitude value that does not make sense RouteSegment minimumObstacleClearanceAltitude All Data consistency rule Vertical limits cannot be coded values
AIXM-5.1_RULE-F07AA Error EAD EAD It is prohibited that a RouteSegment has minimumEnrouteAltitude equal-to ('FLOOR', 'CEILING') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><noun_concept> minimumEnrouteAltitude </noun_concept><keyword> equal-to </keyword><name> ('FLOOR', 'CEILING') </name> RouteSegment cannot use coded values as minimumEnrouteAltitude limits Found RouteSegment with coded minimumEnrouteAltitude value that does not make sense RouteSegment minimumEnrouteAltitude All Data consistency rule Vertical limits cannot be coded values
AIXM-5.1_RULE-F07AB Error Error EAD EAD It is prohibited that a RouteSegment has lowerLimit equal-to ('FLOOR', 'CEILING') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><noun_concept> lowerLimit </noun_concept><keyword> equal-to </keyword><name> ('FLOOR', 'CEILING') </name> RouteSegment cannot use coded values as lowerLimit limits Found RouteSegment with coded lowerLimit value that does not make sense RouteSegment lowerLimit All Data consistency rule Vertical limits cannot be coded values
AIXM-5.1_RULE-F07AC Error Error EAD EAD It is prohibited that a RouteSegment has upperLimit equal-to ('FLOOR', 'CEILING') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><noun_concept> upperLimit </noun_concept><keyword> equal-to </keyword><name> ('FLOOR', 'CEILING') </name> RouteSegment cannot use coded values as upperLimit limits Found RouteSegment with coded upperLimit value that does not make sense RouteSegment upperLimit All Data consistency rule Vertical limits cannot be coded values
AIXM-5.1_RULE-F07AD Error EAD EAD It is prohibited that a AirspaceVolume has lowerLimit equal-to ('FLOOR', 'CEILING') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> lowerLimit </noun_concept><keyword> equal-to </keyword><name> ('FLOOR', 'CEILING') </name> AirspaceVolume cannot use coded values as lowerLimit limits Found AirspaceVolume with coded lowerLimit value that does not make sense AirspaceVolume lowerLimit All Data consistency rule Vertical limits cannot be coded values
AIXM-5.1_RULE-F07AE Error EAD EAD It is prohibited that a AirspaceVolume has upperLimit equal-to ('FLOOR', 'CEILING') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> upperLimit </noun_concept><keyword> equal-to </keyword><name> ('FLOOR', 'CEILING') </name> AirspaceVolume cannot use coded values as upperLimit limits Found AirspaceVolume with coded upperLimit value that does not make sense AirspaceVolume upperLimit All Data consistency rule Vertical limits cannot be coded values
AIXM-5.1_RULE-F07AF Error EAD EAD It is prohibited that a AirportHeliport has fieldElevation equal-to ('FLOOR', 'CEILING', 'GND', 'UNL') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHeliport </noun_concept><verb_concept> has </verb_concept><noun_concept> fieldElevation </noun_concept><keyword> equal-to </keyword><name> ('FLOOR', 'CEILING', 'GND', 'UNL') </name> AirportHeliport cannot use coded values as fieldElevation limits Found AirportHeliport with coded fieldElevation value that does not make sense AirportHeliport fieldElevation All Data consistency rule Vertical limits cannot be coded values
AIXM-5.1_RULE-F07B0 Error EAD EAD It is prohibited that a AirspaceVolume has maximumLimit equal-to ('FLOOR', 'CEILING') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> maximumLimit </noun_concept><keyword> equal-to </keyword><name> ('FLOOR', 'CEILING') </name> AirspaceVolume cannot use coded values as maximumLimit limits Found AirspaceVolume with coded maximumLimit value that does not make sense AirspaceVolume maximumLimit All Data consistency rule Vertical limits cannot be coded values
AIXM-5.1_RULE-F07B1 Error EAD EAD It is prohibited that a AirspaceVolume has minimumLimit equal-to ('FLOOR', 'CEILING') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> minimumLimit </noun_concept><keyword> equal-to </keyword><name> ('FLOOR', 'CEILING') </name> AirspaceVolume cannot use coded values as minimumLimit limits Found AirspaceVolume with coded minimumLimit value that does not make sense AirspaceVolume minimumLimit All Data consistency rule Vertical limits cannot be coded values
AIXM-5.1_RULE-1B0DC9 Error AIXM 4.5 Unit of measurement It is prohibited that a AirportHeliport has assigned fieldElevation.uom value equal-to ('FL', 'SM') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHeliport </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> fieldElevation.uom </noun_concept><keyword> value equal-to </keyword><name> ('FL', 'SM') </name> The unit of measurement for AirportHeliport.fieldElevation cannot take the values ('FL', 'SM'), because they cannot be mapped to AIXM 4.5 Found unit of measurement for AirportHeliport.fieldElevation that cannot be mapped to AIXM 4.5 - ('FL', 'SM') AirportHeliport fieldElevation All Data consistency rule Not allowed units of measurement
AIXM-5.1_RULE-1B0DCA Error AIXM 4.5 Unit of measurement It is prohibited that a RouteSegment has assigned widthLeft.uom value equal-to ('MI', 'CM') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> widthLeft.uom </noun_concept><keyword> value equal-to </keyword><name> ('MI', 'CM') </name> The unit of measurement for RouteSegment. widthLeft cannot take the values ('MI', 'CM'), because they cannot be mapped to AIXM 4.5 Found unit of measurement for RouteSegment. widthLeft that cannot be mapped to AIXM 4.5 - ('MI', 'CM') RouteSegment widthLeft All Data consistency rule Not allowed units of measurement
AIXM-5.1_RULE-1B0DCB Error AIXM 4.5 Unit of measurement It is prohibited that a RouteSegment has assigned widthRight.uom value equal-to ('MI', 'CM') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> widthRight.uom </noun_concept><keyword> value equal-to </keyword><name> ('MI', 'CM') </name> The unit of measurement for RouteSegment.widthRight cannot take the values ('MI', 'CM'), because they cannot be mapped to AIXM 4.5 Found unit of measurement for RouteSegment.widthRight that cannot be mapped to AIXM 4.5 - ('MI', 'CM') RouteSegment widthRight All Data consistency rule Not allowed units of measurement
AIXM-5.1_RULE-1B0DCC Error AIXM 4.5 Unit of measurement It is prohibited that a RouteSegment has assigned length.uom value equal-to ('MI', 'CM') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> length.uom </noun_concept><keyword> value equal-to </keyword><name> ('MI', 'CM') </name> The unit of measurement for RouteSegment.length cannot take the values ('MI', 'CM'), because they cannot be mapped to AIXM 4.5 Found unit of measurement for RouteSegment.length that cannot be mapped to AIXM 4.5 - ('MI', 'CM') RouteSegment length All Data consistency rule Not allowed units of measurement
AIXM-5.1_RULE-1B0DCD Error AIXM 4.5 Unit of measurement It is prohibited that a AirspaceVolume has assigned width.uom value equal-to ('MI', 'CM') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> width.uom </noun_concept><keyword> value equal-to </keyword><name> ('MI', 'CM') </name> The unit of measurement for AirspaceVolume.width cannot take the values ('MI', 'CM'), because they cannot be mapped to AIXM 4.5 Found unit of measurement for AirspaceVolume.width that cannot be mapped to AIXM 4.5 - ('MI', 'CM') AirspaceVolume width All Data consistency rule Not allowed units of measurement
AIXM-5.1_RULE-1B1599 Error AIXM 4.5 AIXM 4.5 It is prohibited that an Airspace has at least 10 geometryComponent and Airspace has at most 99 geometryComponent and Airspace has geometryComponent.AirspaceGeometryComponent.operationSequence longer than 2 characters <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> at least 10 </keyword><noun_concept> geometryComponent </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> at most 99 </keyword><noun_concept> geometryComponent </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceGeometryComponent.operationSequence </noun_concept> In order to enable the automatic creation of PART type Airspace in AIXM 4.5, for an Airspace that has between 10 and 99 AirspaceVolume, the operationSequence must have at most 2 characters. Found Airspace composed of multiple AirspaceVolume and which has a too long operationSequence number. Not possible to automatically generate a valid designator for the PART Airspace in AIXM 4.5 Airspace operationSequence All Data consistency rule Airspace aggregation - operation sequence value
AIXM-5.1_RULE-1B159A Error AIXM 4.5 AIXM 4.5 It is prohibited that an Airspace has at least 2 geometryComponent and Airspace has at most 9 geometryComponent and Airspace has geometryComponent.AirspaceGeometryComponent.operationSequence longer than 1 characters <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> at least 2 </keyword><noun_concept> geometryComponent </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> at most 9 </keyword><noun_concept> geometryComponent </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceGeometryComponent.operationSequence </noun_concept> In order to enable the automatic creation of PART type Airspace in AIXM 4.5, for an Airspace that has between 2 and 9 AirspaceVolume, the operationSequence must have at most 1 characters. Found Airspace composed of multiple AirspaceVolume and which has a too long operationSequence number. Not possible to automatically generate a valid designator for the PART Airspace in AIXM 4.5 Airspace operationSequence All Data consistency rule Airspace aggregation - operation sequence value
AIXM-5.1_RULE-1B2D0A Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and ElevatedCurve has segments.GeodesicString.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.GeodesicString.pointProperty.Point with not assigned srsName and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty) with neither its own nor inherited srsName value ElevatedCurve segments.GeodesicString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D0B Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and Curve has segments.Geodesic.pointProperty.Point.pos with not assigned srsName value and Curve has segments.Geodesic.pointProperty.Point with not assigned srsName and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty) with neither its own nor inherited srsName value Curve segments.Geodesic.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D0C Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.pointProperty.Point with not assigned srsName and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty) with neither its own nor inherited srsName value ElevatedCurve segments.CircleByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D0F Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and ElevatedCurve has segments.Arc.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.Arc.pointProperty.Point with not assigned srsName and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty) with neither its own nor inherited srsName value ElevatedCurve segments.Arc.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D14 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and Curve has segments.Arc.pointProperty.Point.pos with not assigned srsName value and Curve has segments.Arc.pointProperty.Point with not assigned srsName and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty) with neither its own nor inherited srsName value Curve segments.Arc.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D15 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and ElevatedCurve has segments.Geodesic.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.Geodesic.pointProperty.Point with not assigned srsName and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty) with neither its own nor inherited srsName value ElevatedCurve segments.Geodesic.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D16 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and Curve has segments.GeodesicString.pointProperty.Point.pos with not assigned srsName value and Curve has segments.GeodesicString.pointProperty.Point with not assigned srsName and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty) with neither its own nor inherited srsName value Curve segments.GeodesicString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D19 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and Curve has segments.LineStringSegment.pointProperty.Point.pos with not assigned srsName value and Curve has segments.LineStringSegment.pointProperty.Point with not assigned srsName and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty) with neither its own nor inherited srsName value Curve segments.LineStringSegment.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D1A Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and ElevatedCurve has segments.ArcString.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.ArcString.pointProperty.Point with not assigned srsName and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty) with neither its own nor inherited srsName value ElevatedCurve segments.ArcString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D1B Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and Curve has segments.CircleByCenterPoint.pointProperty.Point.pos with not assigned srsName value and Curve has segments.CircleByCenterPoint.pointProperty.Point with not assigned srsName and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty) with neither its own nor inherited srsName value Curve segments.CircleByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D1C Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and ElevatedCurve has segments.Circle.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.Circle.pointProperty.Point with not assigned srsName and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty) with neither its own nor inherited srsName value ElevatedCurve segments.Circle.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D1F Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and Curve has segments.ArcByCenterPoint.pointProperty.Point.pos with not assigned srsName value and Curve has segments.ArcByCenterPoint.pointProperty.Point with not assigned srsName and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty) with neither its own nor inherited srsName value Curve segments.ArcByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D24 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.pointProperty.Point with not assigned srsName and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty) with neither its own nor inherited srsName value ElevatedCurve segments.ArcByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D26 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and ElevatedCurve has segments.LineStringSegment.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.LineStringSegment.pointProperty.Point with not assigned srsName and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty) with neither its own nor inherited srsName value ElevatedCurve segments.LineStringSegment.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D27 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and Curve has segments.Circle.pointProperty.Point.pos with not assigned srsName value and Curve has segments.Circle.pointProperty.Point with not assigned srsName and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty) with neither its own nor inherited srsName value Curve segments.Circle.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B2D28 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and Curve has segments.ArcString.pointProperty.Point.pos with not assigned srsName value and Curve has segments.ArcString.pointProperty.Point with not assigned srsName and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty) with neither its own nor inherited srsName value Curve segments.ArcString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Curve pointProperty positions
AIXM-5.1_RULE-1B34D9 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.GeodesicString.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.GeodesicString.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.GeodesicString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34DA Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.GeodesicString.pointProperty.Point.pos with not assigned srsName value and Curve has segments.GeodesicString.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.GeodesicString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34DB Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcString.pointProperty.Point.pos with not assigned srsName value and Curve has segments.ArcString.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34DC Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Arc.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.Arc.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.Arc.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34DD Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Geodesic.pointProperty.Point.pos with not assigned srsName value and Curve has segments.Geodesic.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.Geodesic.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34DE Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34DF Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.LineStringSegment.pointProperty.Point.pos with not assigned srsName value and Curve has segments.LineStringSegment.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.LineStringSegment.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34E0 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcByCenterPoint.pointProperty.Point.pos with not assigned srsName value and Curve has segments.ArcByCenterPoint.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34E1 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.CircleByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34E2 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Circle.pointProperty.Point.pos with not assigned srsName value and Curve has segments.Circle.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.Circle.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34E3 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Geodesic.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.Geodesic.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.Geodesic.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34E4 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Arc.pointProperty.Point.pos with not assigned srsName value and Curve has segments.Arc.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.Arc.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34E5 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.CircleByCenterPoint.pointProperty.Point.pos with not assigned srsName value and Curve has segments.CircleByCenterPoint.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.CircleByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34E6 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Circle.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.Circle.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.Circle.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34E7 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.LineStringSegment.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.LineStringSegment.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.LineStringSegment.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B34E8 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Surface has not assigned srsName value and Surface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcString.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.ArcString.pointProperty.Point with not assigned srsName and Surface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> Surface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by Surface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside a Surface) with neither its own nor inherited srsName value Surface segments.ArcString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for Surface Curve pointProperty positions
AIXM-5.1_RULE-1B38C1 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Circle.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Circle.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38C2 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.GeodesicString.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.GeodesicString.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38C3 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38C4 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcByCenterPoint.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38C5 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.CircleByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38C6 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.LineStringSegment.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.LineStringSegment.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38C7 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.LineStringSegment.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.LineStringSegment.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38C8 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.CircleByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38C9 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Geodesic.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Geodesic.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38CA Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Arc.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Arc.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38CB Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.GeodesicString.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.GeodesicString.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38CC Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.LineStringSegment.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.LineStringSegment.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38CD Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Circle.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Circle.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38CE Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Arc.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Arc.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38CF Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Circle.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Circle.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D0 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Arc.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Arc.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D1 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Geodesic.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Geodesic.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D2 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.GeodesicString.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.GeodesicString.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D3 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Arc.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Arc.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D4 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Geodesic.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Geodesic.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D5 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcString.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcString.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D6 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D7 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcString.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcString.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D8 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcString.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcString.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38D9 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcByCenterPoint.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38DA Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.GeodesicString.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.GeodesicString.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38DB Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcString.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcString.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38DC Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Geodesic.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Geodesic.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38DD Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.CircleByCenterPoint.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.CircleByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38DE Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.LineStringSegment.pos with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.LineStringSegment.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38DF Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.CircleByCenterPoint.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.CircleByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-1B38E0 Error Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Circle.posList with not assigned srsName value and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Circle.posList All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve positions
AIXM-5.1_RULE-D7939 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy higher-than 15.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA2 shall be better than 15.0 FT Found obstacle in AREA2 with insufficient horizontal accuracy (ElevatedCurve) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.linearExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA2
AIXM-5.1_RULE-D793A Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy.uom equal-to 'M' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy higher-than 5.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA2 shall be better than 5.0 M Found obstacle in AREA2 with insufficient horizontal accuracy ( ElevatedCurve) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.linearExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA2
AIXM-5.1_RULE-D793B Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy higher-than 15.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA2 shall be better than 15.0 FT Found obstacle in AREA2 with insufficient horizontal accuracy (ElevatedPoint) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.location set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA2
AIXM-5.1_RULE-D793C Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.location. ElevatedPoint.horizontalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.location. ElevatedPoint.horizontalAccuracy higher-than 5.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.location. ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.location. ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA2 shall be better than 5.0 M Found obstacle in AREA2 with insufficient horizontal accuracy (ElevatedPoint) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.location set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA2
AIXM-5.1_RULE-D793D Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.horizontalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.horizontalAccuracy higher-than 15.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA2 shall be better than 15.0 FT Found obstacle in AREA2 with insufficient horizontal accuracy ( ElevatedSurface) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.surfaceExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA2
AIXM-5.1_RULE-D793E Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA2' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy higher-than 5.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA2' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA2 shall be better than 5.0 M Found obstacle in AREA2 with insufficient horizontal accuracy (ElevatedSurface) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.surfaceExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA2
AIXM-5.1_RULE-D793F Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.linearExtent. ElevatedCurve.horizontalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.linearExtent. ElevatedCurve.horizontalAccuracy higher-than 1.5 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.linearExtent. ElevatedCurve.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.linearExtent. ElevatedCurve.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA3 shall be better than 1.5 FT Found obstacle in AREA3 with insufficient horizontal accuracy ( ElevatedCurve) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.linearExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA3
AIXM-5.1_RULE-D7940 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy.uom equal-to 'M' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy higher-than 0.5 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA3 shall be better than 0.5 M Found obstacle in AREA3 with insufficient horizontal accuracy (ElevatedCurve) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.linearExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA3
AIXM-5.1_RULE-D7941 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy higher-than 1.5 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA3 shall be better than 1.5 FT Found obstacle in AREA3 with insufficient horizontal accuracy ( ElevatedPoint) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.location set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA3
AIXM-5.1_RULE-D7942 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy higher-than 0.5 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA3 shall be better than 0.5 M Found obstacle in AREA3 with insufficient horizontal accuracy (ElevatedPoint) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.location set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA3
AIXM-5.1_RULE-D7943 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.horizontalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.horizontalAccuracy higher-than 1.5 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA3 shall be better than 1.5 FT Found obstacle in AREA3 with insufficient horizontal accuracy (ElevatedSurface) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.surfaceExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA3
AIXM-5.1_RULE-D7944 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA3' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy higher-than 0.5 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA3' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA3 shall be better than 0.5 M Found obstacle in AREA3 with insufficient horizontal accuracy ( ElevatedSurface) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.surfaceExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA3
AIXM-5.1_RULE-D7945 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA1' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.linearExtent. ElevatedCurve.horizontalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.linearExtent. ElevatedCurve.horizontalAccuracy higher-than 150.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA1' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.linearExtent. ElevatedCurve.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.linearExtent. ElevatedCurve.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA1 shall be better than 150.0 FT Found obstacle in AREA1 with insufficient horizontal accuracy (ElevatedCurve) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.linearExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA1
AIXM-5.1_RULE-D7946 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA1' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy.uom equal-to 'M' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy higher-than 50.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA1' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA1 shall be better than 50.0 M Found obstacle in AREA1 with insufficient horizontal accuracy ( ElevatedCurve) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.linearExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA1
AIXM-5.1_RULE-D7947 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA1' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy higher-than 150.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA1' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA1 shall be better than 150.0 FT Found obstacle in AREA1 with insufficient horizontal accuracy (ElevatedPoint) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.location set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA1
AIXM-5.1_RULE-D7948 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA1' hasObstacle VerticalStructure with part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' and part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy higher-than 50.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA1' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart. horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA1 shall be better than 50.0 M Found obstacle in AREA1 with insufficient horizontal accuracy ( ElevatedPoint) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.location set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA1
AIXM-5.1_RULE-D7949 Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA1' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy.uom equal-to 'FT' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy higher-than 150.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA1' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA1 shall be better than 150.0 FT Found obstacle in AREA1 with insufficient horizontal accuracy (ElevatedSurface) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.surfaceExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA1
AIXM-5.1_RULE-D794A Warning ICAO Annex 15 Table A8-1 It is prohibited that an ObstacleArea with type equal-to 'AREA1' hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy.uom equal-to 'M' and part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy higher-than 50.0 <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'AREA1' </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry.surfaceExtent. ElevatedSurface.horizontalAccuracy </noun_concept><keyword> higher-than </keyword> The horizontal accuracy for obstacles in AREA1 shall be better than 50.0 M Found obstacle in AREA1 with insufficient horizontal accuracy (ElevatedSurface) ObstacleArea horizontalProjection.VerticalStructurePartGeometry.surfaceExtent set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) - Obstacle in AREA1
AIXM-5.1_RULE-1B2151 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment ( DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2152 Error Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment ( DME) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2153 Error Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment ( VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2154 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC' Navaid composed of incorrect equipment ( TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2155 Error Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment (NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2156 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment (TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2157 Error Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment (NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2158 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2159 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VORTAC' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VORTAC' Navaid composed of incorrect equipment (MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B215A Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment ( Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B215B Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_DME' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_DME' Navaid composed of incorrect equipment ( Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B215C Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment (Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B215D Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment (TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B215E Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VORTAC' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VORTAC' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B215F Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2160 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment (Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2161 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS_DME' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS_DME' Navaid composed of incorrect equipment (NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2162 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment (NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2163 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment ( Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2164 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC' Navaid composed of incorrect equipment ( DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2165 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_MKR' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_MKR' Navaid composed of incorrect equipment ( SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2166 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2167 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment (Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2168 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment ( NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2169 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS' Navaid composed of incorrect equipment ( Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B216A Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC' Navaid composed of incorrect equipment (Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B216B Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_DME' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_DME' Navaid composed of incorrect equipment (MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B216C Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VORTAC' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VORTAC' Navaid composed of incorrect equipment (Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B216D Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS_DME' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS_DME' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B216E Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR_DME' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR_DME' Navaid composed of incorrect equipment ( Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B216F Error Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR_DME' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR_DME' Navaid composed of incorrect equipment ( TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2170 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_DME' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_DME' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2171 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2172 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_MKR' isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_MKR' Navaid composed of incorrect equipment ( DME) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2173 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment ( DME) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2174 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS' Navaid composed of incorrect equipment ( DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2175 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2176 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2177 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment (DME) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2178 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2179 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment (MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B217A Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment (Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B217B Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC' Navaid composed of incorrect equipment ( NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B217C Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC_DME' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC_DME' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B217D Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment ( NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B217E Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC_DME' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC_DME' Navaid composed of incorrect equipment ( NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B217F Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2180 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment ( MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2181 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment ( Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2182 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment ( MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2183 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2184 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR_DME' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR_DME' Navaid composed of incorrect equipment (Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2185 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment ( TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2186 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment ( Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2187 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS_DME' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS_DME' Navaid composed of incorrect equipment (Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2188 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC' Navaid composed of incorrect equipment ( Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2189 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment (Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B218A Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment ( DME) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B218B Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment (Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B218C Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_MKR' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_MKR' Navaid composed of incorrect equipment (Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B218D Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment ( MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B218E Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS' Navaid composed of incorrect equipment ( TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B218F Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS' Navaid composed of incorrect equipment ( NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2190 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment ( SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2191 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VORTAC' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VORTAC' Navaid composed of incorrect equipment (Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2192 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC' Navaid composed of incorrect equipment ( Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2193 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment ( DME) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2194 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS_DME' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS_DME' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2195 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS_DME' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS_DME' Navaid composed of incorrect equipment ( Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2196 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC_DME' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC_DME' Navaid composed of incorrect equipment ( Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2197 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS_DME' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS_DME' Navaid composed of incorrect equipment (Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2198 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment (Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B2199 Error Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment ( VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B219A Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS_DME' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS_DME' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B219B Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment ( DME) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B219C Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_DME' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_DME' Navaid composed of incorrect equipment ( Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B219D Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment (Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B219E Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B219F Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment ( DME) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A0 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment ( Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A1 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC_DME' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC_DME' Navaid composed of incorrect equipment (Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A2 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A3 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS_DME' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS_DME' Navaid composed of incorrect equipment ( SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A4 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS_DME' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS_DME' Navaid composed of incorrect equipment (TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A5 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC_DME' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC_DME' Navaid composed of incorrect equipment ( TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A6 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment (MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A7 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR_DME' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR_DME' Navaid composed of incorrect equipment (MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A8 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS_DME' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS_DME' Navaid composed of incorrect equipment ( TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21A9 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS' Navaid composed of incorrect equipment ( Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21AA Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_MKR' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_MKR' Navaid composed of incorrect equipment (Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21AB Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VORTAC' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VORTAC' Navaid composed of incorrect equipment ( NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21AC Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment ( Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21AD Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment (Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21AE Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment ( MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21AF Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_DME' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_DME' Navaid composed of incorrect equipment ( TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B0 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment ( NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B1 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B2 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment ( Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B3 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS' Navaid composed of incorrect equipment (NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B4 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_MKR' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_MKR' Navaid composed of incorrect equipment ( Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B5 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR_DME' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR_DME' Navaid composed of incorrect equipment ( NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B6 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment ( Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B7 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment ( Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B8 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21B9 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR_DME' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR_DME' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21BA Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VORTAC' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VORTAC' Navaid composed of incorrect equipment (Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21BB Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC_DME' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC_DME' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21BC Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_MKR' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_MKR' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21BD Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_DME' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_DME' Navaid composed of incorrect equipment ( SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21BE Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment ( MarkerBeacon) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21BF Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR_DME' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR_DME' Navaid composed of incorrect equipment (Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C0 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_DME' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_DME' Navaid composed of incorrect equipment (Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C1 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C2 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment (Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C3 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment (Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C4 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C5 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VORTAC' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VORTAC' Navaid composed of incorrect equipment (Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C6 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C7 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C8 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS' Navaid composed of incorrect equipment ( Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21C9 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VORTAC' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VORTAC' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21CA Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment ( DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21CB Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC_DME' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC_DME' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21CC Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_MKR' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_MKR' Navaid composed of incorrect equipment (TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21CD Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TLS' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TLS' Navaid composed of incorrect equipment (Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21CE Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VORTAC' isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VORTAC' Navaid composed of incorrect equipment (DME) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21CF Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D0 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D1 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC' Navaid composed of incorrect equipment ( SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D2 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS_DME' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS_DME' Navaid composed of incorrect equipment ( DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D3 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'SDF' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'SDF' Navaid composed of incorrect equipment (Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D4 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_MKR' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_MKR' Navaid composed of incorrect equipment ( VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D5 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS_DME' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS_DME' Navaid composed of incorrect equipment ( SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D6 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D7 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D8 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment ( TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21D9 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21DA Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DF' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DF' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DF' Navaid composed of incorrect equipment ( Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21DB Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment ( NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21DC Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment ( Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21DD Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment (TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21DE Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_MKR' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_MKR' Navaid composed of incorrect equipment ( Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21DF Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_DME' isComposedOf NavaidEquipment specialisation Glidepath <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Glidepath </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_DME' Navaid composed of incorrect equipment (Glidepath) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E0 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment ( DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E1 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'DME' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'DME' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E2 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment (VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E3 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS_DME' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS_DME' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E4 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E5 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS_DME' isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS_DME' Navaid composed of incorrect equipment (NDB) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E6 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment (TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E7 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'TACAN' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'TACAN' Navaid composed of incorrect equipment ( SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E8 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MKR' isComposedOf NavaidEquipment specialisation Localizer <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MKR' Navaid composed of incorrect equipment ( Localizer) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21E9 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'LOC_DME' isComposedOf NavaidEquipment specialisation Azimuth <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LOC_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Azimuth </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'LOC_DME' Navaid composed of incorrect equipment ( Azimuth) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21EA Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS' Navaid composed of incorrect equipment ( VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21EB Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'MLS' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MLS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'MLS' Navaid composed of incorrect equipment (TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21EC Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR_DME' isComposedOf NavaidEquipment specialisation DirectionFinder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR_DME' Navaid composed of incorrect equipment (DirectionFinder) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21ED Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR_DME' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR_DME' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21EE Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB_DME' isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_DME' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB_DME' Navaid composed of incorrect equipment ( VOR) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21EF Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'ILS' isComposedOf NavaidEquipment specialisation SDF <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ILS' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'ILS' Navaid composed of incorrect equipment (SDF) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21F0 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'VOR' isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'VOR' Navaid composed of incorrect equipment (TACAN) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B21F1 Error AIXM Model Navaid model It is prohibited that a Navaid with assigned type equal-to 'NDB' isComposedOf NavaidEquipment specialisation Elevation <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Elevation </noun_concept> The Navaid type shall be consistent with the associated NavaidEquipment(s). Found 'NDB' Navaid composed of incorrect equipment (Elevation) Navaid type set of snapshots Data consistency rule Navaid type consitency with associated NavaidEquipment(s)
AIXM-5.1_RULE-1B3CA9 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcString.pointProperty.Point.pos with not assigned srsName value and Curve has segments.ArcString.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CAA Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.CircleByCenterPoint.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.CircleByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CAB Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.LineStringSegment.pointProperty.Point.pos with not assigned srsName value and Curve has segments.LineStringSegment.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.LineStringSegment.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CAC Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcString.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.ArcString.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CAD Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Circle.pointProperty.Point.pos with not assigned srsName value and Curve has segments.Circle.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Circle.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CAE Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.LineStringSegment.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.LineStringSegment.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.LineStringSegment.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CAF Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.GeodesicString.pointProperty.Point.pos with not assigned srsName value and Curve has segments.GeodesicString.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.GeodesicString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CB0 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.GeodesicString.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.GeodesicString.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.GeodesicString.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CB1 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.ArcByCenterPoint.pointProperty.Point.pos with not assigned srsName value and Curve has segments.ArcByCenterPoint.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CB2 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Arc.pointProperty.Point.pos with not assigned srsName value and Curve has segments.Arc.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Arc.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CB3 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Circle.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.Circle.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Circle.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CB4 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Geodesic.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.Geodesic.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Geodesic.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CB5 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.ArcByCenterPoint.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.ArcByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CB6 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve with not assigned srsName value and ElevatedCurve has segments.Arc.pointProperty.Point.pos with not assigned srsName value and ElevatedCurve has segments.Arc.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. ElevatedCurve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedCurve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Arc.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CB7 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.CircleByCenterPoint.pointProperty.Point.pos with not assigned srsName value and Curve has segments.CircleByCenterPoint.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.CircleByCenterPoint.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1B3CB8 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedSurface has not assigned srsName value and ElevatedSurface has patches.PolygonPatch.exterior.Ring.curveMember. Curve with not assigned srsName value and Curve has segments.Geodesic.pointProperty.Point.pos with not assigned srsName value and Curve has segments.Geodesic.pointProperty.Point with not assigned srsName and ElevatedSurface is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember. Curve </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pointProperty.Point </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> and </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve used by ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Curve.pointProperty inside an ElevatedSurface) with neither its own nor inherited srsName value ElevatedSurface segments.Geodesic.pointProperty.Point.pos All Minimal data rule GML Profile - mandatory CRS for ElevatedSurface Curve pointProperty positions
AIXM-5.1_RULE-1141F9 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a RouteSegment[1] isPartOf Route and RouteSegment[2] isPartOf Route and RouteSegment[1]. start.EnRouteSegmentPoint isLocatedAt SignificantPoint.navaidSystem.Navaid[1] and RouteSegment[2]. start.EnRouteSegmentPoint isLocatedAt SignificantPoint.navaidSystem.Navaid[1] and RouteSegment[1]. end.EnRouteSegmentPoint isLocatedAt SignificantPoint.navaidSystem.Navaid[2] and RouteSegment[2]. end.EnRouteSegmentPoint isLocatedAt SignificantPoint.navaidSystem.Navaid[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment[1] </noun_concept><verb_concept> isPartOf </verb_concept><noun_concept> Route </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2] </noun_concept><verb_concept> isPartOf </verb_concept><noun_concept> Route </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[1]. start.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.navaidSystem.Navaid[1] </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2]. start.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.navaidSystem.Navaid[1] </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[1]. end.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.navaidSystem.Navaid[2] </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2]. end.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.navaidSystem.Navaid[2] </noun_concept> There cannot exists two different RouteSegment that are part of same Route and start at the same SignificantPoint.navaidSystem.Navaid[1] and end at the same SignificantPoint.navaidSystem.Navaid[2] Found two different RouteSegment that are part of the same Route and start at the same SignificantPoint.navaidSystem.Navaid[1] and end at the same SignificantPoint.navaidSystem.Navaid[2]. Mapping to AIXM 4.5 is impossible. RouteSegment startsAt, endsAt set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for RouteSegment
AIXM-5.1_RULE-1141FA Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a RouteSegment[1] isPartOf Route and RouteSegment[2] isPartOf Route and RouteSegment[1]. start.EnRouteSegmentPoint isLocatedAt SignificantPoint.navaidSystem.Navaid and RouteSegment[2]. start.EnRouteSegmentPoint isLocatedAt SignificantPoint.navaidSystem.Navaid and RouteSegment[1]. end.EnRouteSegmentPoint isLocatedAt SignificantPoint.fixDesignatedPoint.DesignatedPoint and RouteSegment[2]. end.EnRouteSegmentPoint isLocatedAt SignificantPoint.fixDesignatedPoint.DesignatedPoint <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment[1] </noun_concept><verb_concept> isPartOf </verb_concept><noun_concept> Route </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2] </noun_concept><verb_concept> isPartOf </verb_concept><noun_concept> Route </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[1]. start.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.navaidSystem.Navaid </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2]. start.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.navaidSystem.Navaid </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[1]. end.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.fixDesignatedPoint.DesignatedPoint </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2]. end.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.fixDesignatedPoint.DesignatedPoint </noun_concept> There cannot exists two different RouteSegment that are part of same Route and start at the same SignificantPoint.navaidSystem.Navaid and end at the same SignificantPoint.fixDesignatedPoint.DesignatedPoint Found two different RouteSegment that are part of the same Route and start at the same SignificantPoint.navaidSystem.Navaid and end at the same SignificantPoint.fixDesignatedPoint.DesignatedPoint. Mapping to AIXM 4.5 is impossible. RouteSegment startsAt, endsAt set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for RouteSegment
AIXM-5.1_RULE-1141FB Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a RouteSegment[1] isPartOf Route and RouteSegment[2] isPartOf Route and RouteSegment[1]. start.EnRouteSegmentPoint isLocatedAt SignificantPoint.fixDesignatedPoint.DesignatedPoint and RouteSegment[2]. start.EnRouteSegmentPoint isLocatedAt SignificantPoint.fixDesignatedPoint.DesignatedPoint and RouteSegment[1]. end.EnRouteSegmentPoint isLocatedAt SignificantPoint.navaidSystem.Navaid and RouteSegment[2]. end.EnRouteSegmentPoint isLocatedAt SignificantPoint.navaidSystem.Navaid <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment[1] </noun_concept><verb_concept> isPartOf </verb_concept><noun_concept> Route </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2] </noun_concept><verb_concept> isPartOf </verb_concept><noun_concept> Route </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[1]. start.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.fixDesignatedPoint.DesignatedPoint </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2]. start.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.fixDesignatedPoint.DesignatedPoint </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[1]. end.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.navaidSystem.Navaid </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2]. end.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.navaidSystem.Navaid </noun_concept> There cannot exists two different RouteSegment that are part of same Route and start at the same SignificantPoint.fixDesignatedPoint.DesignatedPoint and end at the same SignificantPoint.navaidSystem.Navaid Found two different RouteSegment that are part of the same Route and start at the same SignificantPoint.fixDesignatedPoint.DesignatedPoint and end at the same SignificantPoint.navaidSystem.Navaid. Mapping to AIXM 4.5 is impossible. RouteSegment startsAt, endsAt set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for RouteSegment
AIXM-5.1_RULE-1141FC Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a RouteSegment[1] isPartOf Route and RouteSegment[2] isPartOf Route and RouteSegment[1]. start.EnRouteSegmentPoint isLocatedAt SignificantPoint.fixDesignatedPoint.DesignatedPoint[1] and RouteSegment[2]. start.EnRouteSegmentPoint isLocatedAt SignificantPoint.fixDesignatedPoint.DesignatedPoint[1] and RouteSegment[1]. end.EnRouteSegmentPoint isLocatedAt SignificantPoint.fixDesignatedPoint.DesignatedPoint[2] and RouteSegment[2]. end.EnRouteSegmentPoint isLocatedAt SignificantPoint.fixDesignatedPoint.DesignatedPoint[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment[1] </noun_concept><verb_concept> isPartOf </verb_concept><noun_concept> Route </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2] </noun_concept><verb_concept> isPartOf </verb_concept><noun_concept> Route </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[1]. start.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.fixDesignatedPoint.DesignatedPoint[1] </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2]. start.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.fixDesignatedPoint.DesignatedPoint[1] </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[1]. end.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.fixDesignatedPoint.DesignatedPoint[2] </noun_concept><keyword> and </keyword><noun_concept> RouteSegment[2]. end.EnRouteSegmentPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> SignificantPoint.fixDesignatedPoint.DesignatedPoint[2] </noun_concept> There cannot exists two different RouteSegment that are part of same Route and start at the same SignificantPoint.fixDesignatedPoint.DesignatedPoint[1] and end at the same SignificantPoint.fixDesignatedPoint.DesignatedPoint[2] Found two different RouteSegment that are part of the same Route and start at the same SignificantPoint.fixDesignatedPoint.DesignatedPoint[1] and end at the same SignificantPoint.fixDesignatedPoint.DesignatedPoint[2]. Mapping to AIXM 4.5 is impossible. RouteSegment startsAt, endsAt set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for RouteSegment
AIXM-5.1_RULE-1B5419 Warning AIXM 4.5 AIXM 4.5 mandatory properties It is prohibited that a VerticalStructurePart has not assigned horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.elevation value and has not assigned horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.elevation value and has not assigned horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.elevation value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VerticalStructurePart </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint.elevation </noun_concept><keyword> value </keyword><keyword> and </keyword><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve.elevation </noun_concept><keyword> value </keyword><keyword> and </keyword><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface.elevation </noun_concept><keyword> value </keyword> VerticalStructurePart must have elevation in order to ensure the backwards mapping to AIXM 4.5 Found VerticalStructurePart without any elevation value. Data cannot be mapped back to AIXM 4.5. VerticalStructurePart elevation All Minimal data rule Minimal VerticalStructurePart properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1B541A Warning AIXM 4.5 AIXM 4.5 mandatory properties It is prohibited that a VerticalStructurePart has not assigned horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint value and has not assigned horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve value and has not assigned horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VerticalStructurePart </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> horizontalProjection.VerticalStructurePartGeometry.location.ElevatedPoint </noun_concept><keyword> value </keyword><keyword> and </keyword><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> horizontalProjection.VerticalStructurePartGeometry.linearExtent.ElevatedCurve </noun_concept><keyword> value </keyword><keyword> and </keyword><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> horizontalProjection.VerticalStructurePartGeometry.surfaceExtent.ElevatedSurface </noun_concept><keyword> value </keyword> VerticalStructurePart must have horizontalProjection in order to ensure the backwards mapping to AIXM 4.5 Found VerticalStructurePart without any horizontalProjection value. Data cannot be mapped back to AIXM 4.5. VerticalStructurePart horizontalProjection All Minimal data rule Minimal VerticalStructurePart properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1DC93 Error EAD SDD It is prohibited that a AirportHeliport has assigned contaminant value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHeliport </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> contaminant </noun_concept><keyword> value </keyword> AirportHeliport.contaminant is not supported in EAD and cannot be upload by the data providers Found AirportHeliport instances in the data set with assigned contaminant value. This is not supported in the EAD. AirportHeliport contaminant All Recommended practice (ICAO, industry, etc.) AirportHeliport.contaminant not supported in EAD
AIXM-5.1_RULE-1DC94 Error EAD SDD It is prohibited that a AircraftStand has assigned contaminant value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AircraftStand </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> contaminant </noun_concept><keyword> value </keyword> AircraftStand. contaminant is not supported in EAD and cannot be upload by the data providers Found AircraftStand instances in the data set with assigned contaminant value. This is not supported in the EAD. AircraftStand contaminant All Recommended practice (ICAO, industry, etc.) AircraftStand. contaminant not supported in EAD
AIXM-5.1_RULE-1DC95 Error EAD SDD It is prohibited that a Apron has assigned contaminant value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Apron </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> contaminant </noun_concept><keyword> value </keyword> Apron.contaminant is not supported in EAD and cannot be upload by the data providers Found Apron instances in the data set with assigned contaminant value. This is not supported in the EAD. Apron contaminant All Recommended practice (ICAO, industry, etc.) Apron.contaminant not supported in EAD
AIXM-5.1_RULE-1DC99 Error EAD SDD It is prohibited that a TouchDownLiftOff has assigned contaminant value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TouchDownLiftOff </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> contaminant </noun_concept><keyword> value </keyword> TouchDownLiftOff.contaminant is not supported in EAD and cannot be upload by the data providers Found TouchDownLiftOff instances in the data set with assigned contaminant value. This is not supported in the EAD. TouchDownLiftOff contaminant All Recommended practice (ICAO, industry, etc.) TouchDownLiftOff.contaminant not supported in EAD
AIXM-5.1_RULE-1DC9A Error EAD SDD It is prohibited that a Taxiway has assigned contaminant value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Taxiway </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> contaminant </noun_concept><keyword> value </keyword> Taxiway.contaminant is not supported in EAD and cannot be upload by the data providers Found Taxiway instances in the data set with assigned contaminant value. This is not supported in the EAD. Taxiway contaminant All Recommended practice (ICAO, industry, etc.) Taxiway.contaminant not supported in EAD
AIXM-5.1_RULE-1DC9B EAD SDD It is prohibited that a VerticalStructure has assigned lightingAvailability value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VerticalStructure </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> lightingAvailability </noun_concept><keyword> value </keyword> VerticalStructure.lightingAvailability is not supported in EAD and cannot be upload by the data providers Found VerticalStructure instances in the data set with assigned lightingAvailability value. This is not supported in the EAD. VerticalStructure lightingAvailability All Recommended practice (ICAO, industry, etc.) VerticalStructure.lightingAvailability not supported in EAD
AIXM-5.1_RULE-1DC9C Error EAD SDD It is prohibited that a Runway has assigned areaContaminant value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Runway </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> areaContaminant </noun_concept><keyword> value </keyword> Runway.areaContaminant is not supported in EAD and cannot be upload by the data providers Found Runway instances in the data set with assigned areaContaminant value. This is not supported in the EAD. Runway areaContaminant All Recommended practice (ICAO, industry, etc.) Runway.areaContaminant not supported in EAD
AIXM-5.1_RULE-1DC9D EAD SDD It is prohibited that a Unit has assigned availability value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Unit </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> availability </noun_concept><keyword> value </keyword> Unit. availability is not supported in EAD and cannot be upload by the data providers Found Unit instances in the data set with assigned availability value. This is not supported in the EAD. Unit availability All Recommended practice (ICAO, industry, etc.) Unit. availability not supported in EAD
AIXM-5.1_RULE-1DCA0 Error EAD SDD It is prohibited that a Runway has assigned overallContaminant value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Runway </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> overallContaminant </noun_concept><keyword> value </keyword> Runway. overallContaminant is not supported in EAD and cannot be upload by the data providers Found Runway instances in the data set with assigned overallContaminant value. This is not supported in the EAD. Runway overallContaminant All Recommended practice (ICAO, industry, etc.) Runway. overallContaminant not supported in EAD
AIXM-5.1_RULE-1DCA1 Error EAD SDD It is prohibited that a InformationService has assigned clientAerialRefuelling value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> InformationService </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> clientAerialRefuelling </noun_concept><keyword> value </keyword> InformationService.clientAerialRefuelling is not supported in EAD and cannot be upload by the data providers Found InformationService instances in the data set with assigned clientAerialRefuelling value. This is not supported in the EAD. InformationService clientAerialRefuelling All Recommended practice (ICAO, industry, etc.) InformationService.clientAerialRefuelling not supported in EAD
AIXM-5.1_RULE-1DCA2 Error EAD SDD It is prohibited that a HoldingAssessment has assigned unplannedHolding value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> HoldingAssessment </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> unplannedHolding </noun_concept><keyword> value </keyword> HoldingAssessment. unplannedHolding is not supported in EAD and cannot be upload by the data providers Found HoldingAssessment instances in the data set with assigned unplannedHolding value. This is not supported in the EAD. HoldingAssessment unplannedHolding All Recommended practice (ICAO, industry, etc.) HoldingAssessment. unplannedHolding not supported in EAD
AIXM-5.1_RULE-1DCA3 Error EAD SDD It is prohibited that a AirTrafficManagementService has assigned clientAerialRefuelling value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirTrafficManagementService </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> clientAerialRefuelling </noun_concept><keyword> value </keyword> AirTrafficManagementService. clientAerialRefuelling is not supported in EAD and cannot be upload by the data providers Found AirTrafficManagementService instances in the data set with assigned clientAerialRefuelling value. This is not supported in the EAD. AirTrafficManagementService clientAerialRefuelling All Recommended practice (ICAO, industry, etc.) AirTrafficManagementService. clientAerialRefuelling not supported in EAD
AIXM-5.1_RULE-1DCA4 Error EAD SDD It is prohibited that a AirTrafficControlService has assigned clientAerialRefuelling value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirTrafficControlService </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> clientAerialRefuelling </noun_concept><keyword> value </keyword> AirTrafficControlService. clientAerialRefuelling is not supported in EAD and cannot be upload by the data providers Found AirTrafficControlService instances in the data set with assigned clientAerialRefuelling value. This is not supported in the EAD. AirTrafficControlService clientAerialRefuelling All Recommended practice (ICAO, industry, etc.) AirTrafficControlService. clientAerialRefuelling not supported in EAD
AIXM-5.1_RULE-1DCA5 Error EAD SDD It is prohibited that a PrecisionApproachRadar has assigned reflector value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> PrecisionApproachRadar </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> reflector </noun_concept><keyword> value </keyword> PrecisionApproachRadar.reflector is not supported in EAD and cannot be upload by the data providers Found PrecisionApproachRadar instances in the data set with assigned reflector value. This is not supported in the EAD. PrecisionApproachRadar reflector All Recommended practice (ICAO, industry, etc.) PrecisionApproachRadar.reflector not supported in EAD
AIXM-5.1_RULE-1B5801 Error Error EAD EAD Business Rules It is prohibited that a AirportHeliport has timeSlice[1].AirportHeliportTimeSlice.type equal-to 'AD' and has timeSlice[2].AirportHeliportTimeSlice.type equal-to 'HP' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHeliport </noun_concept><verb_concept> has </verb_concept><noun_concept> timeSlice[1].AirportHeliportTimeSlice.type </noun_concept><keyword> equal-to </keyword><name> 'AD' </name><keyword> and </keyword><verb_concept> has </verb_concept><noun_concept> timeSlice[2].AirportHeliportTimeSlice.type </noun_concept><keyword> equal-to </keyword><name> 'HP' </name> AirportHeliport type cannot change between "aerodrome" and "heliport" in EAD Found AirportHeliport with a type change (values " AD" and "HP"). This is not supported in EAD. AirportHeliport type set of snapshots Data consistency rule AirportHeliport type change (in EAD)
AIXM-5.1_RULE-1B5802 Error Error EAD EAD Business Rules It is prohibited that a AirportHeliport has timeSlice[1].AirportHeliportTimeSlice.type equal-to 'AH' and has timeSlice[2].AirportHeliportTimeSlice.type equal-to 'HP' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHeliport </noun_concept><verb_concept> has </verb_concept><noun_concept> timeSlice[1].AirportHeliportTimeSlice.type </noun_concept><keyword> equal-to </keyword><name> 'AH' </name><keyword> and </keyword><verb_concept> has </verb_concept><noun_concept> timeSlice[2].AirportHeliportTimeSlice.type </noun_concept><keyword> equal-to </keyword><name> 'HP' </name> AirportHeliport type cannot change between "aerodrome" and "heliport" in EAD Found AirportHeliport with a type change (values " AH" and "HP"). This is not supported in EAD. AirportHeliport type set of snapshots Data consistency rule AirportHeliport type change (in EAD)
AIXM-5.1_RULE-1583D1 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'NDB_MKR' and not Navaid isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> A Navaid of type 'NDB_MKR' must have at least one associated NDB equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'NDB_MKR' without any associated NDB equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1583D2 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'DME' and not Navaid isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> A Navaid of type 'DME' must have at least one associated DME equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'DME' without any associated DME equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1583D3 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VOR_DME' and not Navaid isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> A Navaid of type 'VOR_DME' must have at least one associated VOR equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'VOR_DME' without any associated VOR equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1583D4 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'TACAN' and not Navaid isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> A Navaid of type 'TACAN' must have at least one associated TACAN equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'TACAN' without any associated TACAN equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1583D5 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'MKR' and not Navaid isComposedOf NavaidEquipment specialisation MarkerBeacon <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon </noun_concept> A Navaid of type 'MKR' must have at least one associated MarkerBeacon equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'MKR' without any associated MarkerBeacon equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1583D6 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VOR_DME' and not Navaid isComposedOf NavaidEquipment specialisation DME <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME </noun_concept> A Navaid of type 'VOR_DME' must have at least one associated DME equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'VOR_DME' without any associated DME equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1583D7 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VORTAC' and not Navaid isComposedOf NavaidEquipment specialisation TACAN <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN </noun_concept> A Navaid of type 'VORTAC' must have at least one associated TACAN equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'VORTAC' without any associated TACAN equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1583D8 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VORTAC' and not Navaid isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> A Navaid of type 'VORTAC' must have at least one associated VOR equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'VORTAC' without any associated VOR equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1583D9 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VOR' and not Navaid isComposedOf NavaidEquipment specialisation VOR <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR </noun_concept> A Navaid of type 'VOR' must have at least one associated VOR equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'VOR' without any associated VOR equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1583DA Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'NDB' and not Navaid isComposedOf NavaidEquipment specialisation NDB <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><keyword> and </keyword><keyword> not </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB </noun_concept> A Navaid of type 'NDB' must have at least one associated NDB equipment. Note: this is complemented by another rule which requires at maximum one associated equipment of the same type. Found Navaid of type 'NDB' without any associated NDB equipment. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid mandatory equipment
AIXM-5.1_RULE-1170D9 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VOR_DME' and Navaid isComposedOf NavaidEquipment specialisation DME[1] and Navaid isComposedOf NavaidEquipment specialisation DME[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME[2] </noun_concept> A Navaid of type 'VOR_DME' must have maximum one associated DME equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'VOR_DME' associated with two DME equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-1170DA Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'NDB_MKR' and Navaid isComposedOf NavaidEquipment specialisation NDB[1] and Navaid isComposedOf NavaidEquipment specialisation NDB[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB_MKR' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB[2] </noun_concept> A Navaid of type 'NDB_MKR' must have maximum one associated NDB equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'NDB_MKR' associated with two NDB equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-1170DB Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'DME' and Navaid isComposedOf NavaidEquipment specialisation DME[1] and Navaid isComposedOf NavaidEquipment specialisation DME[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DME' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DME[2] </noun_concept> A Navaid of type 'DME' must have maximum one associated DME equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'DME' associated with two DME equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-1170DC Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'MKR' and Navaid isComposedOf NavaidEquipment specialisation MarkerBeacon[1] and Navaid isComposedOf NavaidEquipment specialisation MarkerBeacon[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'MKR' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> MarkerBeacon[2] </noun_concept> A Navaid of type 'MKR' must have maximum one associated MarkerBeacon equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'MKR' associated with two MarkerBeacon equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-1170DD Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'NDB' and Navaid isComposedOf NavaidEquipment specialisation NDB[1] and Navaid isComposedOf NavaidEquipment specialisation NDB[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'NDB' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> NDB[2] </noun_concept> A Navaid of type 'NDB' must have maximum one associated NDB equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'NDB' associated with two NDB equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-1170DE Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VOR' and Navaid isComposedOf NavaidEquipment specialisation VOR[1] and Navaid isComposedOf NavaidEquipment specialisation VOR[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR[2] </noun_concept> A Navaid of type 'VOR' must have maximum one associated VOR equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'VOR' associated with two VOR equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-1170DF Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'TACAN' and Navaid isComposedOf NavaidEquipment specialisation TACAN[1] and Navaid isComposedOf NavaidEquipment specialisation TACAN[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TACAN' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN[2] </noun_concept> A Navaid of type 'TACAN' must have maximum one associated TACAN equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'TACAN' associated with two TACAN equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-1170E0 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VORTAC' and Navaid isComposedOf NavaidEquipment specialisation VOR[1] and Navaid isComposedOf NavaidEquipment specialisation VOR[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR[2] </noun_concept> A Navaid of type 'VORTAC' must have maximum one associated VOR equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'VORTAC' associated with two VOR equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-1170E1 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VOR_DME' and Navaid isComposedOf NavaidEquipment specialisation VOR[1] and Navaid isComposedOf NavaidEquipment specialisation VOR[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOR_DME' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> VOR[2] </noun_concept> A Navaid of type 'VOR_DME' must have maximum one associated VOR equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'VOR_DME' associated with two VOR equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-1170E2 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Navaid has type equal-to 'VORTAC' and Navaid isComposedOf NavaidEquipment specialisation TACAN[1] and Navaid isComposedOf NavaidEquipment specialisation TACAN[2] <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VORTAC' </name><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN[1] </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TACAN[2] </noun_concept> A Navaid of type 'VORTAC' must have maximum one associated TACAN equipment. Note: this complements another rule that requires at least one such equipment to enter in the composition of the navaid. Found Navaid of type 'VORTAC' associated with two TACAN equipments. Backwards mapping to AIXM 4.5 is impossible. Navaid All Data consistency rule Navaid maximum equipment
AIXM-5.1_RULE-DA431 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a NDB[1] has designator equal-to NDB[2]. designator and NDB[1] isPlacedAt ElevatedPoint[1] and NDB[2] isPlacedAt ElevatedPoint[2] and the distance between ElevatedPoint[1] and ElevatedPoint[2] is lower-or-equal-to 60 M <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NDB[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> NDB[2]. designator </noun_concept><keyword> and </keyword><noun_concept> NDB[1] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[1] </noun_concept><keyword> and </keyword><noun_concept> NDB[2] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> and </keyword><noun_concept> ElevatedPoint[1] </noun_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> lower-or-equal-to </keyword> There cannot exists two different NDB that have identical values for designator and also for their position (within a tolerance of 1 second) Found two different NDB that have identical values for designator and that are located at the same position (within a tolerance of 1 second). Backwards mapping to AIXM 4.5 is impossible. NDB designator set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for NDB - attribute and position
AIXM-5.1_RULE-DA432 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a MarkerBeacon[1] has auralMorseCode equal-to MarkerBeacon[2]. auralMorseCode and MarkerBeacon[1] isPlacedAt ElevatedPoint[1] and MarkerBeacon[2] isPlacedAt ElevatedPoint[2] and the distance between ElevatedPoint[1] and ElevatedPoint[2] is lower-or-equal-to 60 M <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> MarkerBeacon[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> auralMorseCode </noun_concept><keyword> equal-to </keyword><noun_concept> MarkerBeacon[2]. auralMorseCode </noun_concept><keyword> and </keyword><noun_concept> MarkerBeacon[1] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[1] </noun_concept><keyword> and </keyword><noun_concept> MarkerBeacon[2] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> and </keyword><noun_concept> ElevatedPoint[1] </noun_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> lower-or-equal-to </keyword> There cannot exists two different MarkerBeacon that have identical values for auralMorseCode and also for their position (within a tolerance of 1 second) Found two different MarkerBeacon that have identical values for auralMorseCode and that are located at the same position (within a tolerance of 1 second). Backwards mapping to AIXM 4.5 is impossible. MarkerBeacon auralMorseCode set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for MarkerBeacon - attribute and position
AIXM-5.1_RULE-DA433 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a TACAN[1] has designator equal-to TACAN[2]. designator and TACAN[1] isPlacedAt ElevatedPoint[1] and TACAN[2] isPlacedAt ElevatedPoint[2] and the distance between ElevatedPoint[1] and ElevatedPoint[2] is lower-or-equal-to 60 M <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TACAN[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> TACAN[2]. designator </noun_concept><keyword> and </keyword><noun_concept> TACAN[1] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[1] </noun_concept><keyword> and </keyword><noun_concept> TACAN[2] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> and </keyword><noun_concept> ElevatedPoint[1] </noun_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> lower-or-equal-to </keyword> There cannot exists two different TACAN that have identical values for designator and also for their position (within a tolerance of 1 second) Found two different TACAN that have identical values for designator and that are located at the same position (within a tolerance of 1 second). Backwards mapping to AIXM 4.5 is impossible. TACAN designator set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for TACAN - attribute and position
AIXM-5.1_RULE-DA434 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a VOR[1] has designator equal-to VOR[2]. designator and VOR[1] isPlacedAt ElevatedPoint[1] and VOR[2] isPlacedAt ElevatedPoint[2] and the distance between ElevatedPoint[1] and ElevatedPoint[2] is lower-or-equal-to 60 M <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VOR[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> VOR[2]. designator </noun_concept><keyword> and </keyword><noun_concept> VOR[1] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[1] </noun_concept><keyword> and </keyword><noun_concept> VOR[2] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> and </keyword><noun_concept> ElevatedPoint[1] </noun_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> lower-or-equal-to </keyword> There cannot exists two different VOR that have identical values for designator and also for their position (within a tolerance of 1 second) Found two different VOR that have identical values for designator and that are located at the same position (within a tolerance of 1 second). Backwards mapping to AIXM 4.5 is impossible. VOR designator set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for VOR - attribute and position
AIXM-5.1_RULE-DA435 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a DesignatedPoint[1] has designator equal-to DesignatedPoint[2].designator and DesignatedPoint[1] isLocatedAt Point[1] and DesignatedPoint[2] isLocatedAt Point[2] and the distance between Point[1] and Point[2] is lower-or-equal-to 60 M <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DesignatedPoint[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> DesignatedPoint[2].designator </noun_concept><keyword> and </keyword><noun_concept> DesignatedPoint[1] </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> Point[1] </noun_concept><keyword> and </keyword><noun_concept> DesignatedPoint[2] </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> Point[2] </noun_concept><keyword> and </keyword><noun_concept> Point[1] </noun_concept><noun_concept> Point[2] </noun_concept><keyword> lower-or-equal-to </keyword> There cannot exists two different DesignatedPoint that have identical values for designator and also for their position (within a tolerance of 1 second) Found two different DesignatedPoint that have identical values for designator and that are located at the same position (within a tolerance of 1 second). Backwards mapping to AIXM 4.5 is impossible. DesignatedPoint designator set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for DesignatedPoint - attribute and position
AIXM-5.1_RULE-DA436 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a DME[1] has designator equal-to DME[2]. designator and DME[1] isPlacedAt ElevatedPoint[1] and DME[2] isPlacedAt ElevatedPoint[2] and the distance between ElevatedPoint[1] and ElevatedPoint[2] is lower-or-equal-to 60 M <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DME[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> DME[2]. designator </noun_concept><keyword> and </keyword><noun_concept> DME[1] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[1] </noun_concept><keyword> and </keyword><noun_concept> DME[2] </noun_concept><verb_concept> isPlacedAt </verb_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> and </keyword><noun_concept> ElevatedPoint[1] </noun_concept><noun_concept> ElevatedPoint[2] </noun_concept><keyword> lower-or-equal-to </keyword> There cannot exists two different DME that have identical values for designator and also for their position (within a tolerance of 1 second) Found two different DME that have identical values for designator and that are located at the same position (within a tolerance of 1 second). Backwards mapping to AIXM 4.5 is impossible. DME designator set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for DME - attribute and position
AIXM-5.1_RULE-1B4861 Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a Runway[1] has type equal-to Runway[2].type and Runway[1] has designator equal-to Runway[2]. designator and Runway[1] isSituatedAt AirportHeliport and Runway[2] isSituatedAt AirportHeliport <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Runway[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><noun_concept> Runway[2].type </noun_concept><keyword> and </keyword><noun_concept> Runway[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> Runway[2]. designator </noun_concept><keyword> and </keyword><noun_concept> Runway[1] </noun_concept><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept><keyword> and </keyword><noun_concept> Runway[2] </noun_concept><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept> There cannot exists two different Runway that have identical values for type and also for designator and isSituatedAt same AirportHeliport Found two different Runway that have identical values for type, designator and isSituatedAt same AirportHeliport. Backwards mapping to AIXM 4.5 is impossible. Runway designator type set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for Runway - two attributes and association
AIXM-5.1_RULE-1C4649 Error AIXM Model It is obligatory that each RadioFrequencyArea with assigned equipment.EquipmentChoice.navaidEquipment value has equipment.EquipmentChoice.navaidEquipment value resolved-into exactly one limits NavaidEquipment specialisation Localizer or Glidepath or VOR or TACAN or DME or NDB or MarkerBeacon or SDF or Elevation or Azimuth or DirectionFinder <keyword> It is obligatory that each </keyword><noun_concept> RadioFrequencyArea </noun_concept><keyword> with assigned </keyword><noun_concept> equipment.EquipmentChoice.navaidEquipment </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> equipment.EquipmentChoice.navaidEquipment </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> limits </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept><keyword> or </keyword><noun_concept> Glidepath </noun_concept><keyword> or </keyword><noun_concept> VOR </noun_concept><keyword> or </keyword><noun_concept> TACAN </noun_concept><keyword> or </keyword><noun_concept> DME </noun_concept><keyword> or </keyword><noun_concept> NDB </noun_concept><keyword> or </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> or </keyword><noun_concept> SDF </noun_concept><keyword> or </keyword><noun_concept> Elevation </noun_concept><keyword> or </keyword><noun_concept> Azimuth </noun_concept><keyword> or </keyword><noun_concept> DirectionFinder </noun_concept> Referential integrity towards NavaidEquipment Cannot resolve RadioFrequencyArea association limits towards a navaid equipment (Localizer, GlidePath, VOR, TACAN, DME, NDB, Markerbeacon, SDF, Elevation, Azimuth or DirectionFinder) RadioFrequencyArea equipment.EquipmentChoice.navaidEquipment set of snapshots Minimal data rule Referential integrity towards NavaidEquipment
AIXM-5.1_RULE-1C464A Error AIXM Model It is obligatory that each Navaid with assigned navaidEquipment value has navaidEquipment value resolved-into exactly one isComposedOf NavaidEquipment specialisation Localizer or Glidepath or VOR or TACAN or DME or NDB or MarkerBeacon or SDF or Elevation or Azimuth or DirectionFinder <keyword> It is obligatory that each </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> navaidEquipment </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> navaidEquipment </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept><keyword> or </keyword><noun_concept> Glidepath </noun_concept><keyword> or </keyword><noun_concept> VOR </noun_concept><keyword> or </keyword><noun_concept> TACAN </noun_concept><keyword> or </keyword><noun_concept> DME </noun_concept><keyword> or </keyword><noun_concept> NDB </noun_concept><keyword> or </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> or </keyword><noun_concept> SDF </noun_concept><keyword> or </keyword><noun_concept> Elevation </noun_concept><keyword> or </keyword><noun_concept> Azimuth </noun_concept><keyword> or </keyword><noun_concept> DirectionFinder </noun_concept> Referential integrity towards NavaidEquipment Cannot resolve Navaid association isComposedOf towards a navaid equipment (Localizer, GlidePath, VOR, TACAN, DME, NDB, Markerbeacon, SDF, Elevation, Azimuth or DirectionFinder) Navaid navaidEquipment set of snapshots Minimal data rule Referential integrity towards NavaidEquipment
AIXM-5.1_RULE-1C464B Error AIXM Model It is obligatory that each VerticalStructure with assigned hostedNavaidEquipment value has hostedNavaidEquipment value resolved-into exactly one hosts NavaidEquipment specialisation Localizer or Glidepath or VOR or TACAN or DME or NDB or MarkerBeacon or SDF or Elevation or Azimuth or DirectionFinder <keyword> It is obligatory that each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> hostedNavaidEquipment </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> hostedNavaidEquipment </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hosts </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept><keyword> or </keyword><noun_concept> Glidepath </noun_concept><keyword> or </keyword><noun_concept> VOR </noun_concept><keyword> or </keyword><noun_concept> TACAN </noun_concept><keyword> or </keyword><noun_concept> DME </noun_concept><keyword> or </keyword><noun_concept> NDB </noun_concept><keyword> or </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> or </keyword><noun_concept> SDF </noun_concept><keyword> or </keyword><noun_concept> Elevation </noun_concept><keyword> or </keyword><noun_concept> Azimuth </noun_concept><keyword> or </keyword><noun_concept> DirectionFinder </noun_concept> Referential integrity towards NavaidEquipment Cannot resolve VerticalStructure association hosts towards a navaid equipment (Localizer, GlidePath, VOR, TACAN, DME, NDB, Markerbeacon, SDF, Elevation, Azimuth or DirectionFinder) VerticalStructure hostedNavaidEquipment set of snapshots Minimal data rule Referential integrity towards NavaidEquipment
AIXM-5.1_RULE-1C464C Error AIXM Model It is obligatory that each RunwayCentrelinePoint with assigned navaidEquipment.NavaidEquipmentDistance.theNavaidEquipment value has navaidEquipment.NavaidEquipmentDistance.theNavaidEquipment value resolved-into exactly one hasEstablished NavaidEquipment specialisation Localizer or Glidepath or VOR or TACAN or DME or NDB or MarkerBeacon or SDF or Elevation or Azimuth or DirectionFinder <keyword> It is obligatory that each </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with assigned </keyword><noun_concept> navaidEquipment.NavaidEquipmentDistance.theNavaidEquipment </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> navaidEquipment.NavaidEquipmentDistance.theNavaidEquipment </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> hasEstablished </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> Localizer </noun_concept><keyword> or </keyword><noun_concept> Glidepath </noun_concept><keyword> or </keyword><noun_concept> VOR </noun_concept><keyword> or </keyword><noun_concept> TACAN </noun_concept><keyword> or </keyword><noun_concept> DME </noun_concept><keyword> or </keyword><noun_concept> NDB </noun_concept><keyword> or </keyword><noun_concept> MarkerBeacon </noun_concept><keyword> or </keyword><noun_concept> SDF </noun_concept><keyword> or </keyword><noun_concept> Elevation </noun_concept><keyword> or </keyword><noun_concept> Azimuth </noun_concept><keyword> or </keyword><noun_concept> DirectionFinder </noun_concept> Referential integrity towards NavaidEquipment Cannot resolve RunwayCentrelinePoint association hasEstablished towards a navaid equipment (Localizer, GlidePath, VOR, TACAN, DME, NDB, Markerbeacon, SDF, Elevation, Azimuth or DirectionFinder) RunwayCentrelinePoint navaidEquipment.NavaidEquipmentDistance.theNavaidEquipment set of snapshots Minimal data rule Referential integrity towards NavaidEquipment
AIXM-5.1_RULE-1B4C49 Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a AuthorityForAirspace[1] isResponsibleFor Airspace and AuthorityForAirspace[2] isResponsibleFor Airspace and AuthorityForAirspace[1] is OrganisationAuthority and AuthorityForAirspace[2] is OrganisationAuthority <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AuthorityForAirspace[1] </noun_concept><verb_concept> isResponsibleFor </verb_concept><noun_concept> Airspace </noun_concept><keyword> and </keyword><noun_concept> AuthorityForAirspace[2] </noun_concept><verb_concept> isResponsibleFor </verb_concept><noun_concept> Airspace </noun_concept><keyword> and </keyword><noun_concept> AuthorityForAirspace[1] </noun_concept><verb_concept> is </verb_concept><noun_concept> OrganisationAuthority </noun_concept><keyword> and </keyword><noun_concept> AuthorityForAirspace[2] </noun_concept><verb_concept> is </verb_concept><noun_concept> OrganisationAuthority </noun_concept> There cannot exists two different AuthorityForAirspace that isResponsibleFor the same Airspace and is the same OrganisationAuthority Found two different AuthorityForAirspace that isResponsibleFor the same Airspace and is the same OrganisationAuthority. Mapping to AIXM 4.5 is impossible. AuthorityForAirspace set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for AuthorityForAirspace - two associations
AIXM-5.1_RULE-1C59D1 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that Route[1] has assigned designatorPrefix and Route[1] has designatorPrefix equal-to Route[2].designatorPrefix and Route[1] has designatorSecondLetter equal-to Route[2].designatorSecondLetter and Route[1] has designatorNumber equal-to Route[2].designatorNumber and Route[1] has multipleIdentifier equal-to Route[2].multipleIdentifier and Route[1] has locationDesignator equal-to Route[2].locationDesignator <keyword> It is prohibited that </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> designatorPrefix </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><keyword> has </keyword><noun_concept> designatorPrefix </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorPrefix </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designatorSecondLetter </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorSecondLetter </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designatorNumber </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorNumber </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> multipleIdentifier </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].multipleIdentifier </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> locationDesignator </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].locationDesignator </noun_concept> There cannot exists two different Route that have identical and not-NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and locationDesignator respectively. Note: in case of NIL values for all these attributes, the name of the route should be different - this will be tested with a separate rule. Found two different Route that have identical non-NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and locationDesignator respectively Route designatorPrefix, designatorSecodLetter, designatorNumber, multipleIdentifie set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for Route - based on designator
AIXM-5.1_RULE-1C59D2 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that Route[1] has assigned designatorSecondLetter and Route[1] has designatorPrefix equal-to Route[2].designatorPrefix and Route[1] has designatorSecondLetter equal-to Route[2].designatorSecondLetter and Route[1] has designatorNumber equal-to Route[2].designatorNumber and Route[1] has multipleIdentifier equal-to Route[2].multipleIdentifier and Route[1] has locationDesignator equal-to Route[2].locationDesignator <keyword> It is prohibited that </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> designatorSecondLetter </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><keyword> has </keyword><noun_concept> designatorPrefix </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorPrefix </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designatorSecondLetter </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorSecondLetter </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designatorNumber </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorNumber </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> multipleIdentifier </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].multipleIdentifier </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> locationDesignator </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].locationDesignator </noun_concept> There cannot exists two different Route that have identical and not-NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and locationDesignator respectively. Note: in case of NIL values for all these attributes, the name of the route should be different - this will be tested with a separate rule. Found two different Route that have identical non-NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and locationDesignator respectively Route designatorPrefix, designatorSecodLetter, designatorNumber, multipleIdentifie set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for Route - based on designator
AIXM-5.1_RULE-1C59D3 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that Route[1] has assigned designatorNumber and Route[1] has designatorPrefix equal-to Route[2].designatorPrefix and Route[1] has designatorSecondLetter equal-to Route[2].designatorSecondLetter and Route[1] has designatorNumber equal-to Route[2].designatorNumber and Route[1] has multipleIdentifier equal-to Route[2].multipleIdentifier and Route[1] has locationDesignator equal-to Route[2].locationDesignator <keyword> It is prohibited that </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> designatorNumber </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><keyword> has </keyword><noun_concept> designatorPrefix </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorPrefix </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designatorSecondLetter </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorSecondLetter </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designatorNumber </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorNumber </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> multipleIdentifier </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].multipleIdentifier </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> locationDesignator </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].locationDesignator </noun_concept> There cannot exists two different Route that have identical and not-NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and locationDesignator respectively. Note: in case of NIL values for all these attributes, the name of the route should be different - this will be tested with a separate rule. Found two different Route that have identical non-NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and locationDesignator respectively Route designatorPrefix, designatorSecodLetter, designatorNumber, multipleIdentifie set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for Route - based on designator
AIXM-5.1_RULE-1C59D4 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that Route[1] has assigned multipleIdentifier and Route[1] has designatorPrefix equal-to Route[2].designatorPrefix and Route[1] has designatorSecondLetter equal-to Route[2].designatorSecondLetter and Route[1] has designatorNumber equal-to Route[2].designatorNumber and Route[1] has multipleIdentifier equal-to Route[2].multipleIdentifier and Route[1] has locationDesignator equal-to Route[2].locationDesignator <keyword> It is prohibited that </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> multipleIdentifier </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><keyword> has </keyword><noun_concept> designatorPrefix </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorPrefix </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designatorSecondLetter </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorSecondLetter </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designatorNumber </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].designatorNumber </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> multipleIdentifier </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].multipleIdentifier </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> locationDesignator </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].locationDesignator </noun_concept> There cannot exists two different Route that have identical and not-NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and locationDesignator respectively. Note: in case of NIL values for all these attributes, the name of the route should be different - this will be tested with a separate rule. Found two different Route that have identical non-NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and locationDesignator respectively Route designatorPrefix, designatorSecodLetter, designatorNumber, multipleIdentifie set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for Route - based on designator
AIXM-5.1_RULE-1C6D59 Error AIXM 4.5 Business Rules AIRSPACE It is prohibited that an AirspaceVolume has assigned minimumLimit value and AirspaceVolume has upperLimit.uom equal-to minimumLimit.uom and AirspaceVolume has upperLimitReference equal-to minimumLimitReference and AirspaceVolume has minimumLimit higher-or-equal-to upperLimit <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> minimumLimit </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><noun_concept> minimumLimit.uom </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><noun_concept> minimumLimitReference </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> minimumLimit </noun_concept><keyword> higher-or-equal-to </keyword><noun_concept> upperLimit </noun_concept> When expressed using the same unit of measurement and the same vertical reference, the value of the lower Limit (or minimum limit) cannot be higher than or equal-to the value of the upper limit (or maximum limit). Found Airspace with minimumLimit higher than or equal-to the upperLimit AirspaceVolume minimumLimit upperLimit All Data consistency rule AirspaceVolume cannot have lower limit higher than or equal-to upper limit
AIXM-5.1_RULE-1C6D5A Error AIXM 4.5 Business Rules AIRSPACE It is prohibited that an AirspaceVolume has assigned lowerLimit value and AirspaceVolume has maximumLimit.uom equal-to lowerLimit.uom and AirspaceVolume has maximumLimitReference equal-to lowerLimitReference and AirspaceVolume has lowerLimit higher-or-equal-to maximumLimit <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> maximumLimit.uom </noun_concept><keyword> equal-to </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> maximumLimitReference </noun_concept><keyword> equal-to </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> lowerLimit </noun_concept><keyword> higher-or-equal-to </keyword><noun_concept> maximumLimit </noun_concept> When expressed using the same unit of measurement and the same vertical reference, the value of the lower Limit (or minimum limit) cannot be higher than or equal-to the value of the upper limit (or maximum limit). Found Airspace with lowerLimit higher than or equal-to the maximumLimit AirspaceVolume maximumLimit lowerLimit All Data consistency rule AirspaceVolume cannot have lower limit higher than or equal-to upper limit
AIXM-5.1_RULE-1C6D5B Error AIXM 4.5 Business Rules AIRSPACE It is prohibited that an AirspaceVolume has assigned minimumLimit value and AirspaceVolume has maximumLimit.uom equal-to minimumLimit.uom and AirspaceVolume has maximumLimitReference equal-to minimumLimitReference and AirspaceVolume has minimumLimit higher-or-equal-to maximumLimit <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> minimumLimit </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> maximumLimit.uom </noun_concept><keyword> equal-to </keyword><noun_concept> minimumLimit.uom </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> maximumLimitReference </noun_concept><keyword> equal-to </keyword><noun_concept> minimumLimitReference </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> minimumLimit </noun_concept><keyword> higher-or-equal-to </keyword><noun_concept> maximumLimit </noun_concept> When expressed using the same unit of measurement and the same vertical reference, the value of the lower Limit (or minimum limit) cannot be higher than or equal-to the value of the upper limit (or maximum limit). Found Airspace with minimumLimit higher than or equal-to the maximumLimit AirspaceVolume maximumLimit minimumLimit All Data consistency rule AirspaceVolume cannot have lower limit higher than or equal-to upper limit
AIXM-5.1_RULE-1C6D5C Error AIXM 4.5 Business Rules AIRSPACE It is prohibited that an AirspaceVolume has assigned lowerLimit value and AirspaceVolume has upperLimit.uom equal-to lowerLimit.uom and AirspaceVolume has upperLimitReference equal-to lowerLimitReference and AirspaceVolume has lowerLimit higher-or-equal-to upperLimit <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> upperLimit.uom </noun_concept><keyword> equal-to </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> upperLimitReference </noun_concept><keyword> equal-to </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> has </verb_concept><noun_concept> lowerLimit </noun_concept><keyword> higher-or-equal-to </keyword><noun_concept> upperLimit </noun_concept> When expressed using the same unit of measurement and the same vertical reference, the value of the lower Limit (or minimum limit) cannot be higher than or equal-to the value of the upper limit (or maximum limit). Found Airspace with lowerLimit higher than or equal-to the upperLimit AirspaceVolume upperLimit lowerLimit All Data consistency rule AirspaceVolume cannot have lower limit higher than or equal-to upper limit
AIXM-5.1_RULE-1C7529 Error EAD Audit Extension It is prohibited that a TouchDownLiftOffLightSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TouchDownLiftOffLightSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TouchDownLiftOffLightSystem Found TouchDownLiftOffLightSystem with more than one Audit extension element TouchDownLiftOffLightSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C752A Error EAD Audit Extension It is prohibited that a RouteSegment has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RouteSegment Found RouteSegment with more than one Audit extension element RouteSegment auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C752B Error EAD Audit Extension It is prohibited that a RadioCommunicationChannel has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RadioCommunicationChannel </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RadioCommunicationChannel Found RadioCommunicationChannel with more than one Audit extension element RadioCommunicationChannel auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C752C Error EAD Audit Extension It is prohibited that a VerticalStructure has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VerticalStructure </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each VerticalStructure Found VerticalStructure with more than one Audit extension element VerticalStructure auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C752D Error EAD Audit Extension It is prohibited that a PrecisionApproachRadar has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> PrecisionApproachRadar </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each PrecisionApproachRadar Found PrecisionApproachRadar with more than one Audit extension element PrecisionApproachRadar auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C752E Error EAD Audit Extension It is prohibited that a AngleIndication has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AngleIndication </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AngleIndication Found AngleIndication with more than one Audit extension element AngleIndication auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C752F Error EAD Audit Extension It is prohibited that a OrganisationAuthority has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> OrganisationAuthority </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each OrganisationAuthority Found OrganisationAuthority with more than one Audit extension element OrganisationAuthority auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7530 Error EAD Audit Extension It is prohibited that a DeicingArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DeicingArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each DeicingArea Found DeicingArea with more than one Audit extension element DeicingArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7531 Error EAD Audit Extension It is prohibited that a TaxiwayMarking has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TaxiwayMarking </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TaxiwayMarking Found TaxiwayMarking with more than one Audit extension element TaxiwayMarking auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7532 Error EAD Audit Extension It is prohibited that a InitialLeg has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> InitialLeg </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each InitialLeg Found InitialLeg with more than one Audit extension element InitialLeg auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7533 Error EAD Audit Extension It is prohibited that a TaxiwayLightSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TaxiwayLightSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TaxiwayLightSystem Found TaxiwayLightSystem with more than one Audit extension element TaxiwayLightSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7534 Error EAD Audit Extension It is prohibited that a Runway has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Runway </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Runway Found Runway with more than one Audit extension element Runway auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7535 Error EAD Audit Extension It is prohibited that a SpecialNavigationSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SpecialNavigationSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SpecialNavigationSystem Found SpecialNavigationSystem with more than one Audit extension element SpecialNavigationSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7536 Error EAD Audit Extension It is prohibited that a SafeAltitudeArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SafeAltitudeArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SafeAltitudeArea Found SafeAltitudeArea with more than one Audit extension element SafeAltitudeArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7537 Error EAD Audit Extension It is prohibited that a RunwayDirectionLightSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayDirectionLightSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RunwayDirectionLightSystem Found RunwayDirectionLightSystem with more than one Audit extension element RunwayDirectionLightSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7538 Error EAD Audit Extension It is prohibited that a AuthorityForAirspace has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AuthorityForAirspace </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AuthorityForAirspace Found AuthorityForAirspace with more than one Audit extension element AuthorityForAirspace auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7539 Error EAD Audit Extension It is prohibited that a ObstacleArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ObstacleArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ObstacleArea Found ObstacleArea with more than one Audit extension element ObstacleArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C753A Error EAD Audit Extension It is prohibited that a DeicingAreaMarking has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DeicingAreaMarking </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each DeicingAreaMarking Found DeicingAreaMarking with more than one Audit extension element DeicingAreaMarking auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C753B Error EAD Audit Extension It is prohibited that a ArrivalFeederLeg has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ArrivalFeederLeg </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ArrivalFeederLeg Found ArrivalFeederLeg with more than one Audit extension element ArrivalFeederLeg auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C753C EAD Audit Extension It is prohibited that a UnplannedHolding has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> UnplannedHolding </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each UnplannedHolding Found UnplannedHolding with more than one Audit extension element UnplannedHolding auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C753D Error EAD Audit Extension It is prohibited that a Glidepath has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Glidepath </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Glidepath Found Glidepath with more than one Audit extension element Glidepath auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C753E Error EAD Audit Extension It is prohibited that a RunwayBlastPad has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayBlastPad </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RunwayBlastPad Found RunwayBlastPad with more than one Audit extension element RunwayBlastPad auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C753F Error EAD Audit Extension It is prohibited that a ApproachLightingSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ApproachLightingSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ApproachLightingSystem Found ApproachLightingSystem with more than one Audit extension element ApproachLightingSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7540 Error EAD Audit Extension It is prohibited that a RunwayDirection has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayDirection </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RunwayDirection Found RunwayDirection with more than one Audit extension element RunwayDirection auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7541 Error EAD Audit Extension It is prohibited that a Azimuth has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Azimuth </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Azimuth Found Azimuth with more than one Audit extension element Azimuth auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7542 Error EAD Audit Extension It is prohibited that a AirportClearanceService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportClearanceService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AirportClearanceService Found AirportClearanceService with more than one Audit extension element AirportClearanceService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7543 Error EAD Audit Extension It is prohibited that a ProcedureDME has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ProcedureDME </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ProcedureDME Found ProcedureDME with more than one Audit extension element ProcedureDME auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7544 Error EAD Audit Extension It is prohibited that a DME has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DME </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each DME Found DME with more than one Audit extension element DME auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7545 Error EAD Audit Extension It is prohibited that a WorkArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> WorkArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each WorkArea Found WorkArea with more than one Audit extension element WorkArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7546 EAD Audit Extension It is prohibited that a PrimarySurveillanceRadar has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> PrimarySurveillanceRadar </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each PrimarySurveillanceRadar Found PrimarySurveillanceRadar with more than one Audit extension element PrimarySurveillanceRadar auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7547 Error EAD Audit Extension It is prohibited that a Apron has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Apron </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Apron Found Apron with more than one Audit extension element Apron auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7548 EAD Audit Extension It is prohibited that a FloatingDockSite has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> FloatingDockSite </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each FloatingDockSite Found FloatingDockSite with more than one Audit extension element FloatingDockSite auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7549 Error EAD Audit Extension It is prohibited that a TaxiHoldingPositionMarking has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TaxiHoldingPositionMarking </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TaxiHoldingPositionMarking Found TaxiHoldingPositionMarking with more than one Audit extension element TaxiHoldingPositionMarking auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C754A Error EAD Audit Extension It is prohibited that a Elevation has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Elevation </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Elevation Found Elevation with more than one Audit extension element Elevation auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C754B Error EAD Audit Extension It is prohibited that a RunwayProtectAreaLightSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayProtectAreaLightSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RunwayProtectAreaLightSystem Found RunwayProtectAreaLightSystem with more than one Audit extension element RunwayProtectAreaLightSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C754C Error EAD Audit Extension It is prohibited that a FinalLeg has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> FinalLeg </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each FinalLeg Found FinalLeg with more than one Audit extension element FinalLeg auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C754D Error EAD Audit Extension It is prohibited that a StandardLevelColumn has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> StandardLevelColumn </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each StandardLevelColumn Found StandardLevelColumn with more than one Audit extension element StandardLevelColumn auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C754E Error EAD Audit Extension It is prohibited that a AircraftGroundService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AircraftGroundService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AircraftGroundService Found AircraftGroundService with more than one Audit extension element AircraftGroundService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C754F Error EAD Audit Extension It is prohibited that a MarkerBeacon has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> MarkerBeacon </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each MarkerBeacon Found MarkerBeacon with more than one Audit extension element MarkerBeacon auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7550 Error EAD Audit Extension It is prohibited that a TouchDownLiftOffMarking has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TouchDownLiftOffMarking </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TouchDownLiftOffMarking Found TouchDownLiftOffMarking with more than one Audit extension element TouchDownLiftOffMarking auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7551 Error EAD Audit Extension It is prohibited that a NonMovementArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NonMovementArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each NonMovementArea Found NonMovementArea with more than one Audit extension element NonMovementArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7552 EAD Audit Extension It is prohibited that a PilotControlledLighting has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> PilotControlledLighting </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each PilotControlledLighting Found PilotControlledLighting with more than one Audit extension element PilotControlledLighting auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7553 Error EAD Audit Extension It is prohibited that a ArrestingGear has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ArrestingGear </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ArrestingGear Found ArrestingGear with more than one Audit extension element ArrestingGear auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7554 Error EAD Audit Extension It is prohibited that a NDB has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NDB </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each NDB Found NDB with more than one Audit extension element NDB auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7555 Error EAD Audit Extension It is prohibited that a FireFightingService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> FireFightingService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each FireFightingService Found FireFightingService with more than one Audit extension element FireFightingService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7556 EAD Audit Extension It is prohibited that a SeaplaneRampSite has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SeaplaneRampSite </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SeaplaneRampSite Found SeaplaneRampSite with more than one Audit extension element SeaplaneRampSite auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7557 Error EAD Audit Extension It is prohibited that a SearchRescueService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SearchRescueService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SearchRescueService Found SearchRescueService with more than one Audit extension element SearchRescueService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7558 Error EAD Audit Extension It is prohibited that a InstrumentApproachProcedure has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> InstrumentApproachProcedure </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each InstrumentApproachProcedure Found InstrumentApproachProcedure with more than one Audit extension element InstrumentApproachProcedure auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7559 Error EAD Audit Extension It is prohibited that a PassengerService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> PassengerService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each PassengerService Found PassengerService with more than one Audit extension element PassengerService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C755A Error EAD Audit Extension It is prohibited that a ApronLightSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ApronLightSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ApronLightSystem Found ApronLightSystem with more than one Audit extension element ApronLightSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C755B Error EAD Audit Extension It is prohibited that a DistanceIndication has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DistanceIndication </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each DistanceIndication Found DistanceIndication with more than one Audit extension element DistanceIndication auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C755C Error EAD Audit Extension It is prohibited that a RunwayVisualRange has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayVisualRange </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RunwayVisualRange Found RunwayVisualRange with more than one Audit extension element RunwayVisualRange auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C755D Error EAD Audit Extension It is prohibited that a Localizer has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Localizer </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Localizer Found Localizer with more than one Audit extension element Localizer auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C755E Error EAD Audit Extension It is prohibited that a GuidanceLine has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> GuidanceLine </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each GuidanceLine Found GuidanceLine with more than one Audit extension element GuidanceLine auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C755F Error EAD Audit Extension It is prohibited that a AirportSuppliesService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportSuppliesService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AirportSuppliesService Found AirportSuppliesService with more than one Audit extension element AirportSuppliesService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7560 EAD Audit Extension It is prohibited that a PassengerLoadingBridge has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> PassengerLoadingBridge </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each PassengerLoadingBridge Found PassengerLoadingBridge with more than one Audit extension element PassengerLoadingBridge auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7561 Error EAD Audit Extension It is prohibited that a VisualGlideSlopeIndicator has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VisualGlideSlopeIndicator </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each VisualGlideSlopeIndicator Found VisualGlideSlopeIndicator with more than one Audit extension element VisualGlideSlopeIndicator auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7562 Error EAD Audit Extension It is prohibited that a Route has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Route </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Route Found Route with more than one Audit extension element Route auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7563 Error EAD Audit Extension It is prohibited that a HoldingAssessment has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> HoldingAssessment </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each HoldingAssessment Found HoldingAssessment with more than one Audit extension element HoldingAssessment auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7564 EAD Audit Extension It is prohibited that a AirspaceBorderCrossing has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceBorderCrossing </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AirspaceBorderCrossing Found AirspaceBorderCrossing with more than one Audit extension element AirspaceBorderCrossing auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7565 EAD Audit Extension It is prohibited that a MarkingBuoy has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> MarkingBuoy </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each MarkingBuoy Found MarkingBuoy with more than one Audit extension element MarkingBuoy auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7566 Error EAD Audit Extension It is prohibited that a DesignatedPoint has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DesignatedPoint </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each DesignatedPoint Found DesignatedPoint with more than one Audit extension element DesignatedPoint auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7567 Error EAD Audit Extension It is prohibited that a TaxiwayElement has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TaxiwayElement </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TaxiwayElement Found TaxiwayElement with more than one Audit extension element TaxiwayElement auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7568 Error EAD Audit Extension It is prohibited that a MissedApproachLeg has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> MissedApproachLeg </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each MissedApproachLeg Found MissedApproachLeg with more than one Audit extension element MissedApproachLeg auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7569 Error EAD Audit Extension It is prohibited that a TouchDownLiftOffSafeArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TouchDownLiftOffSafeArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TouchDownLiftOffSafeArea Found TouchDownLiftOffSafeArea with more than one Audit extension element TouchDownLiftOffSafeArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C756A Error EAD Audit Extension It is prohibited that a RadarSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RadarSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RadarSystem Found RadarSystem with more than one Audit extension element RadarSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C756B Error EAD Audit Extension It is prohibited that a AeronauticalGroundLight has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AeronauticalGroundLight </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AeronauticalGroundLight Found AeronauticalGroundLight with more than one Audit extension element AeronauticalGroundLight auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C756C Error EAD Audit Extension It is prohibited that a IntermediateLeg has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> IntermediateLeg </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each IntermediateLeg Found IntermediateLeg with more than one Audit extension element IntermediateLeg auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C756D EAD Audit Extension It is prohibited that a AerialRefuelling has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AerialRefuelling </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AerialRefuelling Found AerialRefuelling with more than one Audit extension element AerialRefuelling auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C756E Error EAD Audit Extension It is prohibited that a TACAN has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TACAN </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TACAN Found TACAN with more than one Audit extension element TACAN auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C756F Error EAD Audit Extension It is prohibited that a ArrivalLeg has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ArrivalLeg </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ArrivalLeg Found ArrivalLeg with more than one Audit extension element ArrivalLeg auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7570 Error EAD Audit Extension It is prohibited that a CirclingArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> CirclingArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each CirclingArea Found CirclingArea with more than one Audit extension element CirclingArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7571 Error EAD Audit Extension It is prohibited that a GroundTrafficControlService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> GroundTrafficControlService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each GroundTrafficControlService Found GroundTrafficControlService with more than one Audit extension element GroundTrafficControlService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7572 Error EAD Audit Extension It is prohibited that a AirportHeliportCollocation has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHeliportCollocation </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AirportHeliportCollocation Found AirportHeliportCollocation with more than one Audit extension element AirportHeliportCollocation auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7573 EAD Audit Extension It is prohibited that a SecondarySurveillanceRadar has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SecondarySurveillanceRadar </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SecondarySurveillanceRadar Found SecondarySurveillanceRadar with more than one Audit extension element SecondarySurveillanceRadar auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7574 Error EAD Audit Extension It is prohibited that a NavigationArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NavigationArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each NavigationArea Found NavigationArea with more than one Audit extension element NavigationArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7575 Error EAD Audit Extension It is prohibited that a AirportProtectionAreaMarking has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportProtectionAreaMarking </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AirportProtectionAreaMarking Found AirportProtectionAreaMarking with more than one Audit extension element AirportProtectionAreaMarking auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7576 Error EAD Audit Extension It is prohibited that a Navaid has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Navaid </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Navaid Found Navaid with more than one Audit extension element Navaid auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7577 Error EAD Audit Extension It is prohibited that a RunwayElement has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayElement </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RunwayElement Found RunwayElement with more than one Audit extension element RunwayElement auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7578 Error EAD Audit Extension It is prohibited that a SpecialNavigationStation has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SpecialNavigationStation </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SpecialNavigationStation Found SpecialNavigationStation with more than one Audit extension element SpecialNavigationStation auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7579 EAD Audit Extension It is prohibited that a SeaplaneLandingArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SeaplaneLandingArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SeaplaneLandingArea Found SeaplaneLandingArea with more than one Audit extension element SeaplaneLandingArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C757A Error EAD Audit Extension It is prohibited that a Road has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Road </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Road Found Road with more than one Audit extension element Road auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C757B Error EAD Audit Extension It is prohibited that a RunwayMarking has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayMarking </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RunwayMarking Found RunwayMarking with more than one Audit extension element RunwayMarking auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C757C Error EAD Audit Extension It is prohibited that a Unit has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Unit </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Unit Found Unit with more than one Audit extension element Unit auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C757D Error EAD Audit Extension It is prohibited that a ApronElement has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ApronElement </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ApronElement Found ApronElement with more than one Audit extension element ApronElement auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C757E Error EAD Audit Extension It is prohibited that a AirTrafficControlService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirTrafficControlService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AirTrafficControlService Found AirTrafficControlService with more than one Audit extension element AirTrafficControlService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C757F Error EAD Audit Extension It is prohibited that a CheckpointINS has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> CheckpointINS </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each CheckpointINS Found CheckpointINS with more than one Audit extension element CheckpointINS auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7580 Error EAD Audit Extension It is prohibited that a CheckpointVOR has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> CheckpointVOR </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each CheckpointVOR Found CheckpointVOR with more than one Audit extension element CheckpointVOR auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7581 Error EAD Audit Extension It is prohibited that a RunwayCentrelinePoint has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RunwayCentrelinePoint Found RunwayCentrelinePoint with more than one Audit extension element RunwayCentrelinePoint auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7582 Error EAD Audit Extension It is prohibited that a StandardInstrumentDeparture has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> StandardInstrumentDeparture </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each StandardInstrumentDeparture Found StandardInstrumentDeparture with more than one Audit extension element StandardInstrumentDeparture auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7583 Error EAD Audit Extension It is prohibited that a StandardLevelSector has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> StandardLevelSector </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each StandardLevelSector Found StandardLevelSector with more than one Audit extension element StandardLevelSector auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7584 EAD Audit Extension It is prohibited that a FlightRestriction has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> FlightRestriction </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each FlightRestriction Found FlightRestriction with more than one Audit extension element FlightRestriction auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7585 Error EAD Audit Extension It is prohibited that a GeoBorder has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> GeoBorder </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each GeoBorder Found GeoBorder with more than one Audit extension element GeoBorder auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7586 Error EAD Audit Extension It is prohibited that a Airspace has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Airspace </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Airspace Found Airspace with more than one Audit extension element Airspace auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7587 Error EAD Audit Extension It is prohibited that a GuidanceLineMarking has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> GuidanceLineMarking </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each GuidanceLineMarking Found GuidanceLineMarking with more than one Audit extension element GuidanceLineMarking auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7588 Error EAD Audit Extension It is prohibited that a SpecialDate has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SpecialDate </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SpecialDate Found SpecialDate with more than one Audit extension element SpecialDate auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7589 Error EAD Audit Extension It is prohibited that a AircraftStand has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AircraftStand </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AircraftStand Found AircraftStand with more than one Audit extension element AircraftStand auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C758A Error EAD Audit Extension It is prohibited that a ChangeOverPoint has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ChangeOverPoint </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ChangeOverPoint Found ChangeOverPoint with more than one Audit extension element ChangeOverPoint auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C758B Error EAD Audit Extension It is prohibited that a HoldingPattern has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> HoldingPattern </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each HoldingPattern Found HoldingPattern with more than one Audit extension element HoldingPattern auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C758C Error EAD Audit Extension It is prohibited that a RadioFrequencyArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RadioFrequencyArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RadioFrequencyArea Found RadioFrequencyArea with more than one Audit extension element RadioFrequencyArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C758D Error EAD Audit Extension It is prohibited that a RunwayProtectArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayProtectArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RunwayProtectArea Found RunwayProtectArea with more than one Audit extension element RunwayProtectArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C758E Error EAD Audit Extension It is prohibited that a DepartureLeg has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DepartureLeg </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each DepartureLeg Found DepartureLeg with more than one Audit extension element DepartureLeg auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C758F Error EAD Audit Extension It is prohibited that a ApronMarking has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ApronMarking </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each ApronMarking Found ApronMarking with more than one Audit extension element ApronMarking auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7590 Error EAD Audit Extension It is prohibited that a SignificantPointInAirspace has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SignificantPointInAirspace </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SignificantPointInAirspace Found SignificantPointInAirspace with more than one Audit extension element SignificantPointInAirspace auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7591 Error EAD Audit Extension It is prohibited that a AirTrafficManagementService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirTrafficManagementService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AirTrafficManagementService Found AirTrafficManagementService with more than one Audit extension element AirTrafficManagementService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7592 Error EAD Audit Extension It is prohibited that a RouteDME has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteDME </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RouteDME Found RouteDME with more than one Audit extension element RouteDME auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7593 Error EAD Audit Extension It is prohibited that a AirportHeliport has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHeliport </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AirportHeliport Found AirportHeliport with more than one Audit extension element AirportHeliport auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7594 Error EAD Audit Extension It is prohibited that a TouchDownLiftOff has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TouchDownLiftOff </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TouchDownLiftOff Found TouchDownLiftOff with more than one Audit extension element TouchDownLiftOff auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7595 Error EAD Audit Extension It is prohibited that a AltimeterSource has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AltimeterSource </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AltimeterSource Found AltimeterSource with more than one Audit extension element AltimeterSource auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7596 Error EAD Audit Extension It is prohibited that a DirectionFinder has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DirectionFinder </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each DirectionFinder Found DirectionFinder with more than one Audit extension element DirectionFinder auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7597 Error EAD Audit Extension It is prohibited that a StandMarking has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> StandMarking </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each StandMarking Found StandMarking with more than one Audit extension element StandMarking auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7598 Error EAD Audit Extension It is prohibited that a NavigationAreaRestriction has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> NavigationAreaRestriction </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each NavigationAreaRestriction Found NavigationAreaRestriction with more than one Audit extension element NavigationAreaRestriction auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C7599 Error EAD Audit Extension It is prohibited that a VOR has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VOR </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each VOR Found VOR with more than one Audit extension element VOR auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C759A Error EAD Audit Extension It is prohibited that a StandardInstrumentArrival has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> StandardInstrumentArrival </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each StandardInstrumentArrival Found StandardInstrumentArrival with more than one Audit extension element StandardInstrumentArrival auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C759B Error EAD Audit Extension It is prohibited that a TaxiHoldingPosition has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TaxiHoldingPosition </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TaxiHoldingPosition Found TaxiHoldingPosition with more than one Audit extension element TaxiHoldingPosition auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C759C Error EAD Audit Extension It is prohibited that a StandardLevelTable has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> StandardLevelTable </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each StandardLevelTable Found StandardLevelTable with more than one Audit extension element StandardLevelTable auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C759D Error EAD Audit Extension It is prohibited that a GuidanceLineLightSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> GuidanceLineLightSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each GuidanceLineLightSystem Found GuidanceLineLightSystem with more than one Audit extension element GuidanceLineLightSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C759E Error EAD Audit Extension It is prohibited that a SDF has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SDF </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SDF Found SDF with more than one Audit extension element SDF auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C759F Error EAD Audit Extension It is prohibited that a RulesProcedures has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RulesProcedures </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each RulesProcedures Found RulesProcedures with more than one Audit extension element RulesProcedures auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C75A0 Error EAD Audit Extension It is prohibited that a InformationService has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> InformationService </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each InformationService Found InformationService with more than one Audit extension element InformationService auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C75A1 Error EAD Audit Extension It is prohibited that a Taxiway has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Taxiway </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each Taxiway Found Taxiway with more than one Audit extension element Taxiway auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C75A2 Error EAD Audit Extension It is prohibited that a TerminalArrivalArea has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TerminalArrivalArea </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TerminalArrivalArea Found TerminalArrivalArea with more than one Audit extension element TerminalArrivalArea auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C75A3 Error EAD Audit Extension It is prohibited that a AirportHotSpot has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirportHotSpot </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each AirportHotSpot Found AirportHotSpot with more than one Audit extension element AirportHotSpot auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C75A4 Error EAD Audit Extension It is prohibited that a SurveyControlPoint has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> SurveyControlPoint </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each SurveyControlPoint Found SurveyControlPoint with more than one Audit extension element SurveyControlPoint auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C75A5 Error EAD Audit Extension It is prohibited that a TaxiHoldingPositionLightSystem has descendant more than one Audit <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> TaxiHoldingPositionLightSystem </noun_concept><verb_concept> has descendant </verb_concept><keyword> more than one </keyword><noun_concept> Audit </noun_concept> Not more than one Audit (extension) is allowed for each TaxiHoldingPositionLightSystem Found TaxiHoldingPositionLightSystem with more than one Audit extension element TaxiHoldingPositionLightSystem auditInformation All Standard (ICAO, industry, etc.) Audit extension occurences
AIXM-5.1_RULE-1C9081 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.Arc.pos with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.Arc.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9082 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.Arc.posList with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.Arc.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9083 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.ArcByCenterPoint.pos with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.ArcByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9084 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.ArcByCenterPoint.posList with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.ArcByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9085 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.ArcString.pos with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.ArcString.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9086 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.ArcString.posList with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.ArcString.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9087 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.Circle.pos with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.Circle.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9088 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.Circle.posList with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.Circle.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9089 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.CircleByCenterPoint.pos with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.CircleByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C908A Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.CircleByCenterPoint.posList with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.CircleByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C908B Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.Geodesic.pos with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.Geodesic.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C908C Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.Geodesic.posList with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.Geodesic.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C908D Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.GeodesicString.pos with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.GeodesicString.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C908E Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.GeodesicString.posList with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.GeodesicString.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C908F Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.LineStringSegment.pos with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.LineStringSegment.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9090 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Curve has not assigned srsName value and not Curve is-descendant-of Surface and not Curve is-descendant-of ElevatedSurface and Curve has segments.LineStringSegment.posList with not assigned srsName value and Curve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Curve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of Curve with neither its own nor inherited srsName value Curve segments.LineStringSegment.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9091 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.Arc.pos with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.Arc.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9092 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.Arc.posList with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Arc.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.Arc.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9093 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.ArcByCenterPoint.pos with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.ArcByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9094 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.ArcByCenterPoint.posList with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.ArcByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9095 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.ArcString.pos with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.ArcString.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9096 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.ArcString.posList with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.ArcString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.ArcString.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9097 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.Circle.pos with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.Circle.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9098 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.Circle.posList with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Circle.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.Circle.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C9099 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.CircleByCenterPoint.pos with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.CircleByCenterPoint.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C909A Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.CircleByCenterPoint.posList with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.CircleByCenterPoint.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.CircleByCenterPoint.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C909B Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.Geodesic.pos with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.Geodesic.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C909C Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.Geodesic.posList with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.Geodesic.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.Geodesic.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C909D Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.GeodesicString.pos with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.GeodesicString.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C909E Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.GeodesicString.posList with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.GeodesicString.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.GeodesicString.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C909F Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.LineStringSegment.pos with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.LineStringSegment.pos All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-1C90A0 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedCurve has not assigned srsName value and not ElevatedCurve is-descendant-of Surface and not ElevatedCurve is-descendant-of ElevatedSurface and ElevatedCurve has segments.LineStringSegment.posList with not assigned srsName value and ElevatedCurve is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> Surface </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> ElevatedSurface </noun_concept><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has </verb_concept><noun_concept> segments.LineStringSegment.posList </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedCurve which is not descendant of Surface or ElevatedSurface must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos or gml:posList descendant of ElevatedCurve with neither its own nor inherited srsName value ElevatedCurve segments.LineStringSegment.posList All Minimal data rule GML Profile - mandatory CRS for Curve positions (outside Surface)
AIXM-5.1_RULE-E2CE8 Warning Warning AIXM Model Each Timesheet with assigned startDate value and with not assigned endDate value shall not have startTime higher-than endTime <keyword> Each </keyword><noun_concept> Timesheet </noun_concept><keyword> with assigned </keyword><noun_concept> startDate </noun_concept><keyword> value and with not assigned </keyword><noun_concept> endDate </noun_concept><keyword> value shall </keyword><keyword> not </keyword><verb_concept> have </verb_concept><noun_concept> startTime </noun_concept><keyword> higher-than </keyword><noun_concept> endTime </noun_concept> In a Timesheet, startTime must be smaller than endTime if they occur on the same day In a Timesheet, startTime must be smaller than endTime if they occur on the same day Timesheet startDate, endDate All Data consistency rule Timesheet - startTime higher than endTime
AIXM-5.1_RULE-D6998 Error Error EAD EAD It is prohibited that an EnRouteSegmentPoint has pointChoice.SignificantPoint.navaidSystem value resolved-into isLocatedAt Navaid and Navaid has type not equal-to ('VOR', 'VOR_DME', 'DME', 'NDB', 'TACAN', 'VORTAC', 'MKR', 'NDB_DME', 'NDB_MKR') <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> EnRouteSegmentPoint </noun_concept><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.navaidSystem </noun_concept><keyword> value </keyword><keyword> resolved-into </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept><keyword> and </keyword><noun_concept> Navaid </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> not equal-to </keyword><name> ('VOR', 'VOR_DME', 'DME', 'NDB', 'TACAN', 'VORTAC', 'MKR', 'NDB_DME', 'NDB_MKR') </name> A Navaid used as pointChoiceNavaidSystem in a RouteSegment should not have a type different from VOR, VOR_DME, DME, NDB, TACAN, VORTAC, MKR, NDB_DME, NDB_MKR Found RouteSegment start or end using incorrect Navaid type EnRouteSegmentPoint Data consistency rule RouteSegment start/end Navaid type
AIXM-5.1_RULE-1B7740 Warning ICAO Annex 10 3.3.2.1 It is prohibited that a VOR has assigned frequency value higher-than 117.95 and VOR has assigned frequency.uom value equal-to 'MHZ' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword><keyword> higher-than </keyword><name> 117.95 </name><keyword> and </keyword><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><name> 'MHZ' </name> According to Point 3.3.2.1 in ICAO Annex 10, the VOR frequency shall at maximum 117.95 MHZ. Found VOR frequency value higher than 117.95 MHZ VOR frequency All Standard (ICAO, industry, etc.) VOR frequency - maximum value
AIXM-5.1_RULE-1A5E00 Error Error ICAO Annex 15 Appendix 1 It is prohibited that assigned srsName value not equal-to ('urn:ogc:def:crs:EPSG::4326', 'urn:ogc:def:crs:EPSG::4258', 'urn:ogc:def:crs:EPSG::4322', 'urn:ogc:def:crs:EPSG::4230', 'urn:ogc:def:crs:EPSG::4668', 'urn:ogc:def:crs:EPSG::4312', 'urn:ogc:def:crs:EPSG::4215', 'urn:ogc:def:crs:EPSG::4801', 'urn:ogc:def:crs:EPSG::4149', 'urn:ogc:def:crs:EPSG::4275', 'urn:ogc:def:crs:EPSG::4746', 'urn:ogc:def:crs:EPSG::4121', 'urn:ogc:def:crs:EPSG::4658', 'urn:ogc:def:crs:EPSG::4299', 'urn:ogc:def:crs:EPSG::4806', 'urn:ogc:def:crs:EPSG::4277', 'urn:ogc:def:crs:EPSG::4207', 'urn:ogc:def:crs:EPSG::4274', 'urn:ogc:def:crs:EPSG::4740', 'urn:ogc:def:crs:EPSG::4313', 'urn:ogc:def:crs:EPSG::4124', 'urn:ogc:def:crs:EPSG::4267', 'urn:ogc:def:crs:EPSG::4269', 'urn:ogc:def:crs:OGC:1.3:CRS84') <keyword> It is prohibited that assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> not </keyword><keyword> equal-to </keyword><name> ('urn:ogc:def:crs:EPSG::4326', 'urn:ogc:def:crs:EPSG::4258', 'urn:ogc:def:crs:EPSG::4322', 'urn:ogc:def:crs:EPSG::4230', 'urn:ogc:def:crs:EPSG::4668', 'urn:ogc:def:crs:EPSG::4312', 'urn:ogc:def:crs:EPSG::4215', 'urn:ogc:def:crs:EPSG::4801', 'urn:ogc:def:crs:EPSG::4149', 'urn:ogc:def:crs:EPSG::4275', 'urn:ogc:def:crs:EPSG::4746', 'urn:ogc:def:crs:EPSG::4121', 'urn:ogc:def:crs:EPSG::4658', 'urn:ogc:def:crs:EPSG::4299', 'urn:ogc:def:crs:EPSG::4806', 'urn:ogc:def:crs:EPSG::4277', 'urn:ogc:def:crs:EPSG::4207', 'urn:ogc:def:crs:EPSG::4274', 'urn:ogc:def:crs:EPSG::4740', 'urn:ogc:def:crs:EPSG::4313', 'urn:ogc:def:crs:EPSG::4124', 'urn:ogc:def:crs:EPSG::4267', 'urn:ogc:def:crs:EPSG::4269', 'urn:ogc:def:crs:OGC:1.3:CRS84') </name> Only the coordinate reference system listed in Appendix 1 of the GML Guidelines for Aviation Data shall be used. Found unsupported srsName value * * All Standard (ICAO, industry, etc.) GML Profile - Geographic Reference Systems supported
AIXM-5.1_RULE-1C5DB8 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that Route[1] has not assigned designatorPrefix and Route[1] has not assigned designatorSecondLetter and Route[1] has not assigned designatorNumber and Route[1] has not assigned multipleIdentifier and Route[1] has name equal-to Route[2].name and Route[2] has not assigned designatorPrefix and Route[2] has not assigned designatorSecondLetter and Route[2] has not assigned designatorNumber and Route[2] has not assigned multipleIdentifier and Route[1] has locationDesignator equal-to Route[2].locationDesignator <keyword> It is prohibited that </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> designatorPrefix </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> designatorSecondLetter </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> designatorNumber </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> multipleIdentifier </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> name </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].name </noun_concept><keyword> and </keyword><noun_concept> Route[2] </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> designatorPrefix </noun_concept><keyword> and </keyword><noun_concept> Route[2] </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> designatorSecondLetter </noun_concept><keyword> and </keyword><noun_concept> Route[2] </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> designatorNumber </noun_concept><keyword> and </keyword><noun_concept> Route[2] </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> multipleIdentifier </noun_concept><keyword> and </keyword><noun_concept> Route[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> locationDesignator </noun_concept><keyword> equal-to </keyword><noun_concept> Route[2].locationDesignator </noun_concept> There cannot exists two different Route that have NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and identical name and locationDesignator properties. Note: in case of non-NIL values for the designator attributes, the concatenated designator should be different - this will be tested with a separate rule. Found two different Route that have NIL values for designatorPrefix, designatorSecondLetter, designatorNumber, multipleIdentifier and also identical name and locationDesignator properties. Route designatorPrefix, designatorSecodLetter, designatorNumber, multipleIdentifie set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for Route - based on name
AIXM-5.1_RULE-1C7CF8 Error AIXM GML Profile OGC 12-028r1 It is prohibited that an AirspaceVolume.horizontalProjection.Surface has assigned patches.PolygonPatch.exterior.Ring.curveMember.href value and AirspaceVolume.horizontalProjection.Surface has next patches.PolygonPatch.exterior.Ring.curveMember with start position distance to referenced GeoBorder larger than 30 M <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember </noun_concept><noun_concept> GeoBorder </noun_concept> When GeoBorders are used in the definition of an AirspaceVolume.horizontalProjection, the position of the next gml:pos must be situated, with a tolerance of 30 M, on a segment of the related GeoBorder The position of the next AirspaceVolume.horizontalProjection.ElevatedSurface vertex is too far away (more than 30 M) from the referenced GeoBorder segments AirspaceVolume All Data consistency rule Airspace vertex (next) proximity to geoBorder
AIXM-5.1_RULE-BFA68 Error Error AIXM GML Profile OGC Document 12-128r1 It is prohibited that at least one xsi:type <keyword> It is prohibited that at least one </keyword><noun_concept> xsi:type </noun_concept> The use of dynamic type definition (with the xsi:type attribute) is forbidden. Found element with dynamic type redefinition construct by xsi:type. This is not supported. * xsi:type All Standard (ICAO, industry, etc.) GML profile - forbid use of xsi:type
AIXM-5.1_RULE-15C250 Error Error EAD EAD It is prohibited that an Airspace has more than one geometryComponent and Airspace has an empty resulting geometry <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> more than one </keyword><noun_concept> geometryComponent </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept> For an Airsapace defined as the aggregation of several AirspaceGeometryComponents, the result of the aggregation shall not be en empty geometry Found Airspace with multiple AirspaceGeometryComponent and an empty resulting geometry Airspace Minimal data rule Airspace agrregation - empty result
AIXM-5.1_RULE-38A40 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Runway has timeSlice[1].RunwayTimeSlice.type equal-to 'RWY' and has timeSlice[2].RunwayTimeSlice.type not equal-to 'RWY' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Runway </noun_concept><verb_concept> has </verb_concept><noun_concept> timeSlice[1].RunwayTimeSlice.type </noun_concept><keyword> equal-to </keyword><name> 'RWY' </name><keyword> and </keyword><verb_concept> has </verb_concept><noun_concept> timeSlice[2].RunwayTimeSlice.type </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><name> 'RWY' </name> The Runway type cannot change in EAD Found Runway with a changed type. This is not supported in EAD. Runway type baseline, snapshot, set of snapshots Data consistency rule Runway type change (in EAD)
AIXM-5.1_RULE-CB9D0 Error Error EAD EAD It is prohibited that an Airspace with more than one geometryComponent has geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.contributorAirspace.AirspaceVolumeDependency.dependency equal-to 'HORZ_PROJECTION' <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><keyword> more than one </keyword><noun_concept> geometryComponent </noun_concept><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume.contributorAirspace.AirspaceVolumeDependency.dependency </noun_concept><keyword> equal-to </keyword><name> 'HORZ_PROJECTION' </name> An Airspace that needs to be backwards mapped to AIXM 4.5 in EAD and which is composed with an aggregation of more than one AirspaceVolume, cannot use a dependency of type "horizontal projection" Found Airspace defined by the aggregation of multiple AirspaceVolume and one of these is using a dependency of type "horizontal projection", which is not supported in AIXM 4.5. Airspace Data consistency rule Airspace aggregation - not allowed to use horizontal projections
AIXM-5.1_RULE-2CEC0 Warning ICAO Annex 11 Designated Points It is prohibited that a DesignatedPoint[1] with type equal-to 'ICAO' has assigned designator value equal-to DesignatedPoint[2].designator and DesignatedPoint[2] has type equal-to 'ICAO' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DesignatedPoint[1] </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ICAO' </name><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> designator </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><noun_concept> DesignatedPoint[2].designator </noun_concept><keyword> and </keyword><noun_concept> DesignatedPoint[2] </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ICAO' </name> Designated Points of type "ICAO" should have a designator that is unique worldwide Found two different DesignatedPoint of type ICAO and having the same designator value DesignatedPoint designator, type ANY;WITH_REF Standard (ICAO, industry, etc.) Designated Point unique identifier (ICAO type)
AIXM-5.1_RULE-1B05F8 Warning Warning ICAO Annex 15 section 3.7.1.1 It is prohibited that assigned srsName value not equal-to ('urn:ogc:def:crs:EPSG::4326', 'urn:ogc:def:crs:OGC:1.3:CRS84') <keyword> It is prohibited that </keyword><keyword> assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> not equal-to </keyword><name> ('urn:ogc:def:crs:EPSG::4326', 'urn:ogc:def:crs:OGC:1.3:CRS84') </name> All geographical coordinates should be expressed in the WGS 84 system Note: complemented with the OGC 12-028 "Use of GML for aviation data" which recommends the use of the EPSG::4326 or of the OGC:1.3:CRS84 coordinate reference system. Found geographical data in a coordinate system different from WGS-84 * srsName All Standard (ICAO, industry, etc.) Geographic Reference System for aviation data - WGS 84
AIXM-5.1_RULE-1B11B0 Error Error Error ICAO Annex 11 ASE_105 It is prohibited that an Airspace with designatorICAO equal-to 'YES' has designator value not expressed with exactly 4 letters <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> designatorICAO </noun_concept><keyword> equal-to </keyword><name> 'YES' </name><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> value </keyword><keyword> not </keyword> If the Airspace designatorICAO is "YES", then the designator must be composed of exactly 4 letters Found Airspace with designatorICAO="YES" and designator not having exactly 4 letters Airspace designatorICAO Standard (ICAO, industry, etc.) Airspace ICAO designators must be 4 letters
AIXM-5.1_RULE-1CEE40 Error AIXM GML Profile OGC 12-028 It is prohibited that a AirspaceVolume.horizontalProjection.Surface has assigned patches.PolygonPatch.exterior.Ring.curveMember.href value and AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href value resolved-into exactly one ElevatedCurve and not ElevatedCurve is-descendant-of GeoBorder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> resolved-into </keyword><keyword> exactly one </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> GeoBorder </noun_concept> Surface curveMember references shall resolve into exactly one GeoBorder or one of its Curve descendants Referential integrity error: the AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember association is resolved into an ElevatedCurve that is not descendant of a GeoBorder. This is not allowed by the GML Profile. AirspaceVolume baseline outside delta, snapshot, set of snapshots Data consistency rule GML Profile - Surface to GeoBorder dependency - referential integrity
AIXM-5.1_RULE-1AFE28 NM CACD It is prohibited that an Airspace with type equal-to ('CTA','UTA', 'OCA') has geometryComponent.AirspaceGeometryComponent.operation not equal-to ('BASE', 'UNION') <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('CTA','UTA', 'OCA') </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceGeometryComponent.operation </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><name> ('BASE', 'UNION') </name> The geometry of operational airspace of type CTA, UTA and OCA shall be encoded as an aggregation of the corresponding operational SECTORS. Found Airspace of type CTA/UTA/OCA with geometry component different from aggregation (operation is not BASE/UNION) Airspace type baseline outside delta, snapshot, set of snapshots Data consistency rule CTA and similar areas shall be an aggregation of sectors - part 2
AIXM-5.1_RULE-CA648 Warning Warning AIXM 4.5 Business Rules ASE_104 Each Airspace with type equal-to ('FIR', 'UIR') shall have designatorICAO equal-to 'YES' <keyword> Each </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('FIR', 'UIR') </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> designatorICAO </noun_concept><keyword> equal-to </keyword><name> 'YES' </name> If Airspace type has the value 'FIR' or 'UIR', then designatorICAO shall be have the value 'YES' Found Airspace of type FIR/UIR and designatorICAO not equal to 'YES' Airspace type, designatorICAO BL;NO_REF Data consistency rule Airspace ICAO location indicator mandatory for FIR/UIR
AIXM-5.1_RULE-21340 Warning AIXM 4.5 Business Rules AIRSPACE Each AirspaceVolume with assigned minimumLimit value shall have minimumLimitReference equal-to 'SFC' <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> minimumLimit </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> minimumLimitReference </noun_concept><keyword> equal-to </keyword><name> 'SFC' </name> AirspaceVolume with assigned minimumLimit shall have minimumLimitreference equal to 'SFC' (height above ground) AirspaceVolume with assigned minimumLimit shall have minimumLimitreference equal to 'SFC' (height above ground) AirspaceVolume minimumLimit All Data consistency rule AirspaceVolume minimum limit shall be a height (above ground)
AIXM-5.1_RULE-F32A0 Error AIXM Model It is obligatory that each AirTrafficControlService with assigned clientProcedure value has clientProcedure value resolved-into exactly one controls Procedure specialisation StandardInstrumentDeparture or StandardInstrumentArrival or InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> AirTrafficControlService </noun_concept><keyword> with assigned </keyword><noun_concept> clientProcedure </noun_concept><keyword> value has </keyword><noun_concept> clientProcedure </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> controls </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> StandardInstrumentDeparture </noun_concept><keyword> or </keyword><noun_concept> StandardInstrumentArrival </noun_concept><keyword> or </keyword><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. Cannot resolve association from clientProcedure towards StandardInstrumentDeparture, StandardInstrumentArrival or InstrumentApproachProcedure AirTrafficControlService clientProcedure set of snapshots Minimal data rule Referential integrity towards Procedure (with specialized class)
AIXM-5.1_RULE-C96A8 Warning AIXM 4.5 Business Rules TIMESHEET It is prohibited that Timesheet with not assigned endTime has not assigned endEvent <keyword> It is prohibited that </keyword><noun_concept> Timesheet </noun_concept><keyword> with not assigned </keyword><noun_concept> endTime </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> endEvent </noun_concept> Any Timesheet should have an end time or an end event. Otherwise the end of the schedule is not precise enough. Found Timesheet with neither endTime nor endEvent specified. Timesheet endTime (1 feature + its objects) baseline outsidedelta snapshot set of snapshots Data consistency rule Timesheet needs endTime or endEvent
AIXM-5.1_RULE-639C1 Warning ICAO Annex 15 Table A7-1 It is prohibited that a SegmentPoint specialisation EnRouteSegmentPoint has pointChoice.position coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><verb_concept> has </verb_concept><noun_concept> pointChoice.position </noun_concept> Latitude and longitude of en-route points shall be published with 1 sec resolution Latitude and longitude of en-route points shall be published with 1 sec resolution EnRouteSegmentPoint pointChoice, position All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - EnRouteSegmentPoint position
AIXM-5.1_RULE-639C2 Warning ICAO Annex 15 Table A7-1 It is prohibited that a SegmentPoint specialisation TerminalSegmentPoint has pointChoice.position coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><verb_concept> has </verb_concept><noun_concept> pointChoice.position </noun_concept> Latitude and longitude of approach points shall be published with 1/10 sec resolution Latitude and longitude of approach points shall be published with 1/10 sec resolution TerminalSegmentPoint pointChoice, position All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - TerminalSegmentPoint position
AIXM-5.1_RULE-17701 Warning ICAO Annex 15 Table A7-1 It is prohibited that a RunwayCentrelinePoint with role equal-to 'THR' has location.ElevatedPoint coordinates expressed with less than 6 decimals <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'THR' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and longitude of runway THR end and holding position points shall be published with 1/100 sec resolution Latitude and longitude of runway THR end and holding position points shall be published with 1/100 sec resolution RunwayCentrelinePoint ElevatedPoint baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Runway points
AIXM-5.1_RULE-17702 Warning ICAO Annex 15 Table A7-1 It is prohibited that a RunwayCentrelinePoint with role equal-to 'LAHSO' has location.ElevatedPoint coordinates expressed with less than 6 decimals <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'LAHSO' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and longitude of runway LAHSO end and holding position points shall be published with 1/100 sec resolution Latitude and longitude of runway LAHSO end and holding position points shall be published with 1/100 sec resolution RunwayCentrelinePoint ElevatedPoint baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Runway points
AIXM-5.1_RULE-17703 Warning ICAO Annex 15 Table A7-1 It is prohibited that a RunwayCentrelinePoint with role equal-to 'END' has location.ElevatedPoint coordinates expressed with less than 6 decimals <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'END' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and longitude of runway END end and holding position points shall be published with 1/100 sec resolution Latitude and longitude of runway END end and holding position points shall be published with 1/100 sec resolution RunwayCentrelinePoint ElevatedPoint baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Runway points
AIXM-5.1_RULE-17704 Warning ICAO Annex 15 Table A7-1 It is prohibited that a RunwayCentrelinePoint with role equal-to 'DISTHR' has location.ElevatedPoint coordinates expressed with less than 6 decimals <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'DISTHR' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and longitude of runway DISTHR end and holding position points shall be published with 1/100 sec resolution Latitude and longitude of runway DISTHR end and holding position points shall be published with 1/100 sec resolution RunwayCentrelinePoint ElevatedPoint baseline outside delta, snapshot, set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Runway points
AIXM-5.1_RULE-1A42A9 Warning AIXM 4.5 Business Rules Each ElevatedSurface with assigned verticalAccuracy value shall have assigned elevation value <keyword> Each </keyword><noun_concept> ElevatedSurface </noun_concept><keyword> with assigned </keyword><noun_concept> verticalAccuracy </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> elevation </noun_concept><keyword> value </keyword> The vertical accuracy does not make sense if the elevation itself is not specified. Found elevationAccuracy while no elevation value is present ElevatedSurface verticalAccuracy All Data consistency rule Vertical accuracy only with elevation
AIXM-5.1_RULE-1A42AA Warning AIXM 4.5 Business Rules Each ElevatedCurve with assigned verticalAccuracy value shall have assigned elevation value <keyword> Each </keyword><noun_concept> ElevatedCurve </noun_concept><keyword> with assigned </keyword><noun_concept> verticalAccuracy </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> elevation </noun_concept><keyword> value </keyword> The vertical accuracy does not make sense if the elevation itself is not specified. Found elevationAccuracy while no elevation value is present ElevatedCurve verticalAccuracy All Data consistency rule Vertical accuracy only with elevation
AIXM-5.1_RULE-1A42AB Warning AIXM 4.5 Business Rules Each ElevatedPoint with assigned verticalAccuracy value shall have assigned elevation value <keyword> Each </keyword><noun_concept> ElevatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> verticalAccuracy </noun_concept><keyword> value </keyword><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> elevation </noun_concept><keyword> value </keyword> The vertical accuracy does not make sense if the elevation itself is not specified. Found elevationAccuracy while no elevation value is present ElevatedPoint verticalAccuracy All Data consistency rule Vertical accuracy only with elevation
AIXM-5.1_RULE-135151 Error EAD EAD It is prohibited that a OrganisationAuthority has assigned type value equal-to ('STATE', 'STATE_GROUP', 'INTL_ORG') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> OrganisationAuthority </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><name> ('STATE', 'STATE_GROUP', 'INTL_ORG') </name> OrganisationAuthority with type equal ('STATE', 'STATE_GROUP', 'INTL_ORG') cannot be updated by the EAD data providers. Found OrganisationAuthority type that cannot be upload in EAD OrganisationAuthority type All Data consistency rule OrganisationAuthority type upload in EAD
AIXM-5.1_RULE-135152 Error EAD EAD It is prohibited that a GeoBorder has assigned type value equal-to 'STATE' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> GeoBorder </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><name> 'STATE' </name> GeoBorder with type equal 'STATE' cannot be updated by the EAD data providers. Found GeoBorder type that cannot be upload in EAD GeoBorder type All Data consistency rule GeoBorder type upload in EAD
AIXM-5.1_RULE-135153 Error EAD EAD It is prohibited that a Airspace has assigned type value equal-to ('NAS', 'FIR', 'UIR') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> type </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><name> ('NAS', 'FIR', 'UIR') </name> Airspace with type equal ('NAS', 'FIR', 'UIR') cannot be updated by the EAD data providers. Found Airspace type that cannot be upload in EAD Airspace type All Data consistency rule Airspace type upload in EAD
AIXM-5.1_RULE-1ABBC1 Error AIXM Model It is obligatory that each DirectionFinder with assigned informationProvision value has informationProvision value resolved-into exactly one isAssociatedWith Service specialisation InformationService <keyword> It is obligatory that each </keyword><noun_concept> DirectionFinder </noun_concept><keyword> with assigned </keyword><noun_concept> informationProvision </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> informationProvision </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isAssociatedWith </verb_concept><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InformationService </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. DirectionFinder informationProvision set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the targetClass)
AIXM-5.1_RULE-EB1B9 Warning ICAO Annex 15 Table A7-1 It is prohibited that a SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice. fixDesignatedPoint isLocatedAt DesignatedPoint with assigned location. Point coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice. fixDesignatedPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept><keyword> with assigned </keyword><noun_concept> location. Point </noun_concept> Latitude and longitude of en-route intersections and waypoints, holding and STAR/SID points shall be published with 1 sec resolution Latitude and longitude of en-route intersections and waypoints, holding and STAR/SID points shall be published with 1 sec resolution EnRouteSegmentPoint fixDesignatedPoint All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - EnRouteSegmentPoint
AIXM-5.1_RULE-EB1BA Warning ICAO Annex 15 Table A7-1 It is prohibited that a SegmentPoint specialisation EnRouteSegmentPoint with assigned pointChoice. navaidSystem isLocatedAt Navaid with assigned location. ElevatedPoint coordinates expressed with less than 4 decimals <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> EnRouteSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice. navaidSystem </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> location. ElevatedPoint </noun_concept> Latitude and longitude of en-route intersections and waypoints, holding and STAR/SID points shall be published with 1 sec resolution Latitude and longitude of en-route intersections and waypoints, holding and STAR/SID points shall be published with 1 sec resolution EnRouteSegmentPoint navaidSystem All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - EnRouteSegmentPoint
AIXM-5.1_RULE-1A90C9 Warning ICAO Annex 15 Table A7-1 It is prohibited that an ObstacleArea with type equal-to ('AREA2','AREA3') hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface coordinates expressed with less than 5 decimals <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('AREA2','AREA3') </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. surfaceExtent.ElevatedSurface </noun_concept> Longitude and latitude of obstacles in Area 2 and 3 shall be published with 1/10 sec resolution Longitude and latitude of obstacles in Area 2 and 3 shall be published with 1/10 sec resolution VerticalStructure set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Obstacles in Area 2 and 3
AIXM-5.1_RULE-1A90CA Warning ICAO Annex 15 Table A7-1 It is prohibited that an ObstacleArea with type equal-to ('AREA2','AREA3') hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('AREA2','AREA3') </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. location.ElevatedPoint </noun_concept> Longitude and latitude of obstacles in Area 2 and 3 shall be published with 1/10 sec resolution Longitude and latitude of obstacles in Area 2 and 3 shall be published with 1/10 sec resolution VerticalStructure set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Obstacles in Area 2 and 3
AIXM-5.1_RULE-1A90CB Warning ICAO Annex 15 Table A7-1 It is prohibited that an ObstacleArea with type equal-to ('AREA2','AREA3') hasObstacle VerticalStructure with part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve coordinates expressed with less than 5 decimals <keyword> It is prohibited that an </keyword><noun_concept> ObstacleArea </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('AREA2','AREA3') </name><verb_concept> hasObstacle </verb_concept><noun_concept> VerticalStructure </noun_concept><keyword> with </keyword><noun_concept> part.VerticalStructurePart.horizontalProjection.VerticalStructurePartGeometry. linearExtent.ElevatedCurve </noun_concept> Longitude and latitude of obstacles in Area 2 and 3 shall be published with 1/10 sec resolution Longitude and latitude of obstacles in Area 2 and 3 shall be published with 1/10 sec resolution VerticalStructure set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Obstacles in Area 2 and 3
AIXM-5.1_RULE-1ABFA9 AIXM Model It is obligatory that each RadioFrequencyArea with assigned radar value has radar value resolved-into exactly one limits RadarEquipment specialisation SurveillanceRadar specialisation SecondarySurveillanceRadar <keyword> It is obligatory that each </keyword><noun_concept> RadioFrequencyArea </noun_concept><keyword> with assigned </keyword><noun_concept> radar </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radar </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> limits </verb_concept><noun_concept> RadarEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SurveillanceRadar </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SecondarySurveillanceRadar </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. RadioFrequencyArea radar set of snapshots Minimal data rule Referential integrity - second level of inheritance (for the targetClass)
AIXM-5.1_RULE-34FA9 Error AIXM Model It is obligatory that each VerticalStructure with assigned supportedGroundLight value has supportedGroundLight value resolved-into exactly one supports GroundLightSystem specialisation ApronLightSystem or TaxiwayLightSystem or TouchDownLiftOffLightSystem or RunwayDirectionLightSystem or VisualGlideSlopeIndicator or TaxiHoldingPositionLightSystem or RunwayProtectAreaLightSystem or GuidanceLineLightSystem <keyword> It is obligatory that each </keyword><noun_concept> VerticalStructure </noun_concept><keyword> with assigned </keyword><noun_concept> supportedGroundLight </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> supportedGroundLight </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> supports </verb_concept><noun_concept> GroundLightSystem </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApronLightSystem </noun_concept><keyword> or </keyword><noun_concept> TaxiwayLightSystem </noun_concept><keyword> or </keyword><noun_concept> TouchDownLiftOffLightSystem </noun_concept><keyword> or </keyword><noun_concept> RunwayDirectionLightSystem </noun_concept><keyword> or </keyword><noun_concept> VisualGlideSlopeIndicator </noun_concept><keyword> or </keyword><noun_concept> TaxiHoldingPositionLightSystem </noun_concept><keyword> or </keyword><noun_concept> RunwayProtectAreaLightSystem </noun_concept><keyword> or </keyword><noun_concept> GuidanceLineLightSystem </noun_concept> Referential integrity towards GroundLightSystem Referential integrity towards GroundLightSystem VerticalStructure supportedGroundLight set of snapshots Minimal data rule Referential integrity towards GroundLightSystem (EAD profile)
AIXM-5.1_RULE-1A69C0 Error AIXM Model It is obligatory that each CirclingArea with assigned approach value has approach value resolved-into exactly one isUsedOn Procedure specialisation InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> CirclingArea </noun_concept><keyword> with assigned </keyword><noun_concept> approach </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approach </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isUsedOn </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. CirclingArea approach set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the targetClass) (EAD profile)
AIXM-5.1_RULE-1A69C1 Error AIXM Model It is obligatory that each TerminalArrivalArea with assigned approachRNAV value has approachRNAV value resolved-into exactly one isFeederFor Procedure specialisation InstrumentApproachProcedure <keyword> It is obligatory that each </keyword><noun_concept> TerminalArrivalArea </noun_concept><keyword> with assigned </keyword><noun_concept> approachRNAV </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> approachRNAV </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isFeederFor </verb_concept><noun_concept> Procedure </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> InstrumentApproachProcedure </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. TerminalArrivalArea approachRNAV set of snapshots Minimal data rule Referential integrity - first level of inheritance (for the targetClass) (EAD profile)
AIXM-5.1_RULE-2E248 Warning ICAO Annex 15 Table A7-1 It is prohibited that a GuidanceLine with assigned extent value has extent.ElevatedCurve coordinates expressed with less than 6 decimals <keyword> It is prohibited that a </keyword><noun_concept> GuidanceLine </noun_concept><keyword> with assigned </keyword><noun_concept> extent </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> extent.ElevatedCurve </noun_concept> Latitude and longitude of taxiway centre line/parking guidance line points, intersection marking line and exit guidance line shall be published with 1/100 sec resolution Latitude and longitude of taxiway centre line/parking guidance line points, intersection marking line and exit guidance line shall be published with 1/100 sec resolution GuidanceLine ElevatedCurve All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Taxiway centrelines
AIXM-5.1_RULE-65901 Warning ICAO Annex 15 Table A7-5 It is prohibited that a RunwayDeclaredDistance with type equal-to 'ASDA' isValidBy RunwayDeclaredDistanceValue with assigned distance.uom value not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayDeclaredDistance </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'ASDA' </name><verb_concept> isValidBy </verb_concept><noun_concept> RunwayDeclaredDistanceValue </noun_concept><keyword> with assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value not equal-to </keyword><name> ('FT','M') </name> Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution RunwayDeclaredDistance ASDA All Recommended practice (ICAO, industry, etc.) Resolution (dimensions) - runway declared distances
AIXM-5.1_RULE-65902 Warning ICAO Annex 15 Table A7-5 It is prohibited that a RunwayDeclaredDistance with type equal-to 'TODA' isValidBy RunwayDeclaredDistanceValue with assigned distance.uom value not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayDeclaredDistance </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TODA' </name><verb_concept> isValidBy </verb_concept><noun_concept> RunwayDeclaredDistanceValue </noun_concept><keyword> with assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value not equal-to </keyword><name> ('FT','M') </name> Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution RunwayDeclaredDistance TODA All Recommended practice (ICAO, industry, etc.) Resolution (dimensions) - runway declared distances
AIXM-5.1_RULE-65903 Warning ICAO Annex 15 Table A7-5 It is prohibited that a RunwayDeclaredDistance with type equal-to 'TORA' isValidBy RunwayDeclaredDistanceValue with assigned distance.uom value not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayDeclaredDistance </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'TORA' </name><verb_concept> isValidBy </verb_concept><noun_concept> RunwayDeclaredDistanceValue </noun_concept><keyword> with assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value not equal-to </keyword><name> ('FT','M') </name> Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution RunwayDeclaredDistance TORA All Recommended practice (ICAO, industry, etc.) Resolution (dimensions) - runway declared distances
AIXM-5.1_RULE-65904 Warning ICAO Annex 15 Table A7-5 It is prohibited that a RunwayDeclaredDistance with type equal-to 'LDA' isValidBy RunwayDeclaredDistanceValue with assigned distance.uom value not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayDeclaredDistance </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'LDA' </name><verb_concept> isValidBy </verb_concept><noun_concept> RunwayDeclaredDistanceValue </noun_concept><keyword> with assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value not equal-to </keyword><name> ('FT','M') </name> Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution RunwayDeclaredDistance LDA All Recommended practice (ICAO, industry, etc.) Resolution (dimensions) - runway declared distances
AIXM-5.1_RULE-65905 Warning ICAO Annex 15 Table A7-5 It is prohibited that a RunwayDeclaredDistance with type equal-to 'DTHR' isValidBy RunwayDeclaredDistanceValue with assigned distance.uom value not equal-to ('FT','M') <keyword> It is prohibited that a </keyword><noun_concept> RunwayDeclaredDistance </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'DTHR' </name><verb_concept> isValidBy </verb_concept><noun_concept> RunwayDeclaredDistanceValue </noun_concept><keyword> with assigned </keyword><noun_concept> distance.uom </noun_concept><keyword> value not equal-to </keyword><name> ('FT','M') </name> Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution Landing distance available, take-off run available, take-off distance available, accelerate-stop and displaced threshold distance available shall be published with 1m or 1ft resolution RunwayDeclaredDistance DTHR All Recommended practice (ICAO, industry, etc.) Resolution (dimensions) - runway declared distances
AIXM-5.1_RULE-33070 Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with type equal-to 'SDF' and with assigned servedAirport value has location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'SDF' </name><keyword> and with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of Navaid of type SDF, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Latitude and Longitude of Navaid of type SDF, when used for aerodrome/heliport operations, shall be published with 1/10 sec resolution Navaid type, location (1 feature)baseline outsidedeltasnapshotset of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Navaid type SDF when used at aerodrome
AIXM-5.1_RULE-249F1 Error EAD EAD It is prohibited that at least one StandardLevelTable <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> StandardLevelTable </noun_concept> StandardLevelTable cannot be upload in EAD by data providers. Only the service provider can maintain the data. Found StandardLevelTable, which cannot be upload in EAD StandardLevelTable All Recommended practice StandardLevelTable upload in EAD
AIXM-5.1_RULE-249F2 Error EAD EAD It is prohibited that at least one StandardLevelColumn <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> StandardLevelColumn </noun_concept> StandardLevelColumn cannot be upload in EAD by data providers. Only the service provider can maintain the data. Found StandardLevelColumn, which cannot be upload in EAD StandardLevelColumn All Recommended practice StandardLevelColumn upload in EAD
AIXM-5.1_RULE-26549 Error AIXM GML Profile OGC document 12-028r1 It is prohibited that a ArcByCenterPoint has assigned endAngle.uom value not equal-to 'deg' <keyword> It is prohibited that a </keyword><noun_concept> ArcByCenterPoint </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> endAngle.uom </noun_concept><keyword> value </keyword><keyword> not equal-to </keyword><name> 'deg' </name> The symbol "deg" shall be used for the unit of measurement of endAngle Found ArcByCenterPoint with unsupported value for the endAngle unit of measurement ArcByCenterPoint endAngle All Standard (ICAO, industry, etc.) GML Profile - UCUM values for endAngle
AIXM-5.1_RULE-2654A Error AIXM GML Profile OGC document 12-028r1 It is prohibited that a ArcByCenterPoint has assigned startAngle.uom value not equal-to 'deg' <keyword> It is prohibited that a </keyword><noun_concept> ArcByCenterPoint </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> startAngle.uom </noun_concept><keyword> value </keyword><keyword> not equal-to </keyword><name> 'deg' </name> The symbol "deg" shall be used for the unit of measurement of startAngle Found ArcByCenterPoint with unsupported value for the startAngle unit of measurement ArcByCenterPoint startAngle All Standard (ICAO, industry, etc.) GML Profile - UCUM values for startAngle
AIXM-5.1_RULE-449A9 Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a Point has not assigned srsName value and Point has pos with not assigned srsName value and Point is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Point </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Point </noun_concept><verb_concept> has </verb_concept><noun_concept> pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Point </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of Point must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of Point) with neither its own nor inherited srsName value Point pos All Minimal data rule GML Profile - mandatory CRS for Point
AIXM-5.1_RULE-449AA Error AIXM GML Profile OGC Doc 12-028r1 It is prohibited that a ElevatedPoint has not assigned srsName value and ElevatedPoint has pos with not assigned srsName value and ElevatedPoint is-descendant-of a feature with not assigned boundedBy.Envelope.srsName value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedPoint </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedPoint </noun_concept><verb_concept> has </verb_concept><noun_concept> pos </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> srsName </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> ElevatedPoint </noun_concept><keyword> is-descendant-of </keyword><keyword> with </keyword><keyword> not </keyword><keyword> assigned </keyword><noun_concept> boundedBy.Envelope.srsName </noun_concept><keyword> value </keyword> The gml:pos elements that are descendants of ElevatedPoint must have either their own srsName or must be able to inherit it according to the rules states in the OGC document #12-028r1. This includes the derivation of a global srsName from the gml:Envelope element. Found gml:pos (descendant of ElevatedPoint) with neither its own nor inherited srsName value ElevatedPoint pos All Minimal data rule GML Profile - mandatory CRS for Point
AIXM-5.1_RULE-1B5BE9 Error AIXM GML Profile OGC document 12-028r1 It is prohibited that a ArcByCenterPoint has not assigned endAngle value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ArcByCenterPoint </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> endAngle </noun_concept><keyword> value </keyword> ArcByCenterPoint must have endAngle value Found ArcByCenterPoint without endAngle value. Backwards mapping to AIXM 4.5 is not possible in EAD. gml:ArcByCenterPoint endAngle All Standard (ICAO, industry, etc.) GML Profile - mandatory endAngle for arc
AIXM-5.1_RULE-1B5BEA Error AIXM GML Profile OGC document 12-028r1 It is prohibited that a ArcByCenterPoint has not assigned startAngle value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ArcByCenterPoint </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> startAngle </noun_concept><keyword> value </keyword> ArcByCenterPoint must have startAngle value Found ArcByCenterPoint without startAngle value. Backwards mapping to AIXM 4.5 is not possible in EAD. gml:ArcByCenterPoint startAngle All Standard (ICAO, industry, etc.) GML Profile - mandatory startAngle for arc
AIXM-5.1_RULE-1A65D1 Warning EAD EAD It is prohibited that a Surface has descendant ElevatedCurve <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has descendant </verb_concept><noun_concept> ElevatedCurve </noun_concept> Although it is legal from the AIXM/GML schema point of view to have ElevatedCurve as descendant element of Surface, this does not make sense from the operational point of view. The elevation information would anyhow be ignored. Found ElevatedCurve as descendant element of Surface, which is not supported. Surface All Standard (ICAO, industry, etc.) GML Profile - ElevatedCurve not allowed in Surface
AIXM-5.1_RULE-1A65D2 Warning EAD EAD It is prohibited that a ElevatedSurface has descendant ElevatedCurve <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedSurface </noun_concept><verb_concept> has descendant </verb_concept><noun_concept> ElevatedCurve </noun_concept> Although it is legal from the AIXM/GML schema point of view to have ElevatedCurve as descendant element of ElevatedSurface, this does not make sense from the operational point of view. The elevation information would anyhow be ignored. Found ElevatedCurve as descendant element of ElevatedSurface, which is not supported. ElevatedSurface All Standard (ICAO, industry, etc.) GML Profile - ElevatedCurve not allowed in ElevatedSurface
AIXM-5.1_RULE-1A65D3 Warning EAD EAD It is prohibited that a Curve has descendant ElevatedPoint <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Curve </noun_concept><verb_concept> has descendant </verb_concept><noun_concept> ElevatedPoint </noun_concept> Although it is legal from the AIXM/GML schema point of view to have ElevatedPoint as descendant element of Curve, this does not make sense from the operational point of view. The elevation information would anyhow be ignored. Found ElevatedPoint as descendant element of Curve, which is not supported. Curve All Standard (ICAO, industry, etc.) GML Profile - ElevatedPoint not allowed in Curve
AIXM-5.1_RULE-1A65D4 Warning EAD EAD It is prohibited that a ElevatedCurve has descendant ElevatedPoint <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> ElevatedCurve </noun_concept><verb_concept> has descendant </verb_concept><noun_concept> ElevatedPoint </noun_concept> Although it is legal from the AIXM/GML schema point of view to have ElevatedPoint as descendant element of ElevatedCurve, this does not make sense from the operational point of view. The elevation information would anyhow be ignored. Found ElevatedPoint as descendant element of ElevatedCurve, which is not supported. ElevatedCurve All Standard (ICAO, industry, etc.) GML Profile - ElevatedPoint not allowed in ElevatedCurve
AIXM-5.1_RULE-DAC1 Error Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a Airspace[1] has type equal-to Airspace[2].type and Airspace[1] has designator equal-to Airspace[2].designator <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Airspace[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><noun_concept> Airspace[2].type </noun_concept><keyword> and </keyword><noun_concept> Airspace[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> Airspace[2].designator </noun_concept> There cannot exists two different Airspace that have identical values for type and also for designator Found two different Airspace that have identical values for both type and designator. Backwards mapping to AIXM 4.5 is impossible. Airspace type designator All Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for Airspace - two attributes
AIXM-5.1_RULE-5340B Error EAD SDD It is prohibited that at least one FlightRestriction <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> FlightRestriction </noun_concept> FlightRestriction is not supported in EAD and cannot be upload by the data providers. Found FlightRestriction instances in the data set. This is not supported in the EAD. FlightRestriction All Recommended practice (ICAO, industry, etc.) FlightRestriction not supported in EAD
AIXM-5.1_RULE-5340D Error EAD SDD It is prohibited that at least one AirspaceBorderCrossing <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> AirspaceBorderCrossing </noun_concept> AirspaceBorderCrossing is not supported in EAD and cannot be upload by the data providers. Found AirspaceBorderCrossing instances in the data set. This is not supported in the EAD. AirspaceBorderCrossing All Recommended practice (ICAO, industry, etc.) AirspaceBorderCrossing not supported in EAD
AIXM-5.1_RULE-5341C Error EAD SDD It is prohibited that at least one AerialRefuelling <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> AerialRefuelling </noun_concept> AerialRefuelling is not supported in EAD and cannot be upload by the data providers. Found AerialRefuelling instances in the data set. This is not supported in the EAD. AerialRefuelling All Recommended practice (ICAO, industry, etc.) AerialRefuelling not supported in EAD
AIXM-5.1_RULE-5341D Error EAD SDD It is prohibited that at least one MarkingBuoy <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> MarkingBuoy </noun_concept> MarkingBuoy is not supported in EAD and cannot be upload by the data providers. Found MarkingBuoy instances in the data set. This is not supported in the EAD. MarkingBuoy All Recommended practice (ICAO, industry, etc.) MarkingBuoy not supported in EAD
AIXM-5.1_RULE-5341E Error EAD SDD It is prohibited that at least one PassengerLoadingBridge <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> PassengerLoadingBridge </noun_concept> PassengerLoadingBridge is not supported in EAD and cannot be upload by the data providers. Found PassengerLoadingBridge instances in the data set. This is not supported in the EAD. PassengerLoadingBridge All Recommended practice (ICAO, industry, etc.) PassengerLoadingBridge not supported in EAD
AIXM-5.1_RULE-5341F Error EAD SDD It is prohibited that at least one FloatingDockSite <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> FloatingDockSite </noun_concept> FloatingDockSite is not supported in EAD and cannot be upload by the data providers. Found FloatingDockSite instances in the data set. This is not supported in the EAD. FloatingDockSite All Recommended practice (ICAO, industry, etc.) FloatingDockSite not supported in EAD
AIXM-5.1_RULE-53421 Error EAD SDD It is prohibited that at least one SeaplaneLandingArea <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> SeaplaneLandingArea </noun_concept> SeaplaneLandingArea is not supported in EAD and cannot be upload by the data providers. Found SeaplaneLandingArea instances in the data set. This is not supported in the EAD. SeaplaneLandingArea All Recommended practice (ICAO, industry, etc.) SeaplaneLandingArea not supported in EAD
AIXM-5.1_RULE-53422 Error EAD SDD It is prohibited that at least one SeaplaneRampSite <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> SeaplaneRampSite </noun_concept> SeaplaneRampSite is not supported in EAD and cannot be upload by the data providers. Found SeaplaneRampSite instances in the data set. This is not supported in the EAD. SeaplaneRampSite All Recommended practice (ICAO, industry, etc.) SeaplaneRampSite not supported in EAD
AIXM-5.1_RULE-53425 Error EAD SDD It is prohibited that at least one SecondarySurveillanceRadar <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> SecondarySurveillanceRadar </noun_concept> SecondarySurveillanceRadar is not supported in EAD and cannot be upload by the data providers. Found SecondarySurveillanceRadar instances in the data set. This is not supported in the EAD. SecondarySurveillanceRadar All Recommended practice (ICAO, industry, etc.) SecondarySurveillanceRadar not supported in EAD
AIXM-5.1_RULE-53427 Error EAD SDD It is prohibited that at least one PrimarySurveillanceRadar <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> PrimarySurveillanceRadar </noun_concept> PrimarySurveillanceRadar is not supported in EAD and cannot be upload by the data providers. Found PrimarySurveillanceRadar instances in the data set. This is not supported in the EAD. PrimarySurveillanceRadar All Recommended practice (ICAO, industry, etc.) PrimarySurveillanceRadar not supported in EAD
AIXM-5.1_RULE-53429 Error EAD SDD It is prohibited that at least one UnplannedHolding <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> UnplannedHolding </noun_concept> UnplannedHolding is not supported in EAD and cannot be upload by the data providers. Found UnplannedHolding instances in the data set. This is not supported in the EAD. UnplannedHolding All Recommended practice (ICAO, industry, etc.) UnplannedHolding not supported in EAD
AIXM-5.1_RULE-5342A Error EAD SDD It is prohibited that at least one PilotControlledLighting <keyword> It is prohibited that </keyword><keyword> at least one </keyword><noun_concept> PilotControlledLighting </noun_concept> PilotControlledLighting is not supported in EAD and cannot be upload by the data providers. Found PilotControlledLighting instances in the data set. This is not supported in the EAD. PilotControlledLighting All Recommended practice (ICAO, industry, etc.) PilotControlledLighting not supported in EAD
AIXM-5.1_RULE-6979 Error Error AIXM 4.5 AIXM 4.5 It is prohibited that a RouteSegment has assigned lowerLimit.uom value equal-to assigned upperLimit.uom value and has assigned lowerLimitReference value equal-to assigned upperLimitReference value and has assigned lowerLimit value higher-than assigned upperLimit value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RouteSegment </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><keyword> assigned </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> value </keyword><keyword> and </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword><keyword> and </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> higher-than </keyword><keyword> assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword> When expressed using the same unit of measurement and the same vertical reference, the value of upperLimit must be higher than or equal to the value of lowerLimit Found RouteSegment with value of lowerLimit higher than the value of upperLimit. RouteSegment upperLimit lowerLimit All Data consistency rule RouteSegment upper limit higher than or equal to lower limit
AIXM-5.1_RULE-697A Error Error AIXM 4.5 AIXM 4.5 It is prohibited that a AirspaceLayer has assigned lowerLimit.uom value equal-to assigned upperLimit.uom value and has assigned lowerLimitReference value equal-to assigned upperLimitReference value and has assigned lowerLimit value higher-than assigned upperLimit value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceLayer </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><keyword> assigned </keyword><noun_concept> upperLimit.uom </noun_concept><keyword> value </keyword><keyword> and </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimitReference </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><keyword> assigned </keyword><noun_concept> upperLimitReference </noun_concept><keyword> value </keyword><keyword> and </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> value </keyword><keyword> higher-than </keyword><keyword> assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> value </keyword> When expressed using the same unit of measurement and the same vertical reference, the value of upperLimit must be higher than or equal to the value of lowerLimit Found AirspaceLayer with value of lowerLimit higher than the value of upperLimit. AirspaceLayer lowerLimit upperLimit All Data consistency rule AirspaceLayer upper limit higher than or equal to lower limit
AIXM-5.1_RULE-EB5A0 Digital NOTAM Event Specification RWY.CLS It is prohibited that a RunwayDirectionTimeSlice with availability.ManoeuvringAreaAvailability.operationalStatus not equal-to 'CLOSED' belongsTo Event with scenario equal-to 'RWY.CLS' and with version equal-to '2.0' <keyword> It is prohibited that a </keyword><noun_concept> RunwayDirectionTimeSlice </noun_concept><keyword> with </keyword><noun_concept> availability.ManoeuvringAreaAvailability.operationalStatus </noun_concept><keyword> not equal-to </keyword><name> 'CLOSED' </name><verb_concept> belongsTo </verb_concept><noun_concept> Event </noun_concept><keyword> with </keyword><noun_concept> scenario </noun_concept><keyword> equal-to </keyword><name> 'RWY.CLS' </name><keyword> and with </keyword><noun_concept> version </noun_concept><keyword> equal-to </keyword><name> '2.0' </name> A RWY.CLS event must have CLOSED operationalStatus A RWY.CLS event must have CLOSED operationalStatus RunwayDirection All Standard (ICAO, industry, etc.) Event - RWY.CLS - mandatory closed status
AIXM-5.1_RULE-1AA838 Warning ICAO Annex 11 Item 2.9.3.2 It is prohibited that an Airspace with type equal-to ('CTA', 'CTA_P', 'UTA', 'UTA_P', 'OCA', 'OCA_P') has geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume with lowerLimit.uom equal-to 'M' and with lowerLimit lower-than 200.0 or lowerLimit equal-to 'GND' <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('CTA', 'CTA_P', 'UTA', 'UTA_P', 'OCA', 'OCA_P') </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><keyword> and with </keyword><noun_concept> lowerLimit </noun_concept><keyword> lower-than </keyword><keyword> or </keyword><noun_concept> lowerLimit </noun_concept><keyword> equal-to </keyword><name> 'GND' </name> Airspace of type 'CTA', 'CTA_P', 'UTA', 'UTA_P', 'OCA' or 'OAC_P' should not have lower limit smaller than 200 m. Note: the check cannot detect situations where the lowerLimit is specified with reference to MSL. However, the vertical reference can be ignored in the rule check because if the value it is lower than 200 m, the rule is anyhow broken. Airspace of type 'CTA', 'CTA_P', 'UTA', 'UTA_P', 'OCA' or 'OAC_P' should not have lower limit smaller than 200 m. Note: the check cannot detect situations where the lowerLimit is specified with reference to MSL. However, the vertical reference can be ignored in the rule check because if the value it is lower than 200 m, the rule is anyhow broken. AirspaceVolume lowerLimit baseline outside delta, snapshot, set of snapshots Recommended practice Airspace CTA,UTA, etc. minimal lower limit in M
AIXM-5.1_RULE-FA00 AIXM Model It is obligatory that each AirportProtectionAreaMarking with assigned markedProtectionArea value has markedProtectionArea value resolved-into exactly one isMarkedOn AirportHeliportProtectionArea specialisation RunwayProtectArea or TouchDownLiftOffSafeArea <keyword> It is obligatory that each </keyword><noun_concept> AirportProtectionAreaMarking </noun_concept><keyword> with assigned </keyword><noun_concept> markedProtectionArea </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> markedProtectionArea </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isMarkedOn </verb_concept><noun_concept> AirportHeliportProtectionArea </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> RunwayProtectArea </noun_concept><keyword> or </keyword><noun_concept> TouchDownLiftOffSafeArea </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. AirportProtectionAreaMarking markedProtectionArea set of snapshots Minimal data rule Referential integrity towards AirportHeliportProtectionArea
AIXM-5.1_RULE-52468 Error Error AIXM 4.5 Business Rules MKR It is prohibited that a MarkerBeacon has assigned frequency value not equal-to '75' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> MarkerBeacon </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword><keyword> not </keyword><keyword> equal-to </keyword><name> '75' </name> The value of the Marker Beacon frequency must be 75 MHz. Found MarkerBeacon with frequency value different from 75. Backward mapping to AIXM 5.1 is impossible in EAD. MarkerBeacon frequency All Standard ICAO MarkerBeacon frequency value
AIXM-5.1_RULE-145AF0 Error AIXM 4.5 AIXM 4.5 It is prohibited that a VOR has timeSlice[1].VORTimeSlice.type equal-to ('VOR', 'DVOR', 'OTHER', 'OTHER:.*') and has timeSlice[2].VORTimeSlice.type not equal-to ('VOR', 'DVOR', 'OTHER', 'OTHER:.*') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><noun_concept> timeSlice[1].VORTimeSlice.type </noun_concept><keyword> equal-to </keyword><name> ('VOR', 'DVOR', 'OTHER', 'OTHER:.*') </name><keyword> and </keyword><verb_concept> has </verb_concept><noun_concept> timeSlice[2].VORTimeSlice.type </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><name> ('VOR', 'DVOR', 'OTHER', 'OTHER:.*') </name> The VOR type cannot change to a value that is not backwards mapped in EAD Found VOR with a changed type into a value that is not backwards mapped in EAD. This is not supported. VOR type baseline, snapshot, set of snapshots Data consistency rule VOR type change (in EAD)
AIXM-5.1_RULE-1A0428 Error AIXM Model Each AirspaceVolume with assigned centreline value shall have assigned width value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> centreline </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width </noun_concept><keyword> value </keyword> If AirspaceVolume has corridor shape non-zero width must be assigned Found AirspaceVolume with centreline but no width AirspaceVolume width All Data consistency rule AirspaceVolume of type corridor must have width
AIXM-5.1_RULE-1C5200 Error Error AIXM 4.5 AIXM 4.5 It is prohibited that a DesignatedPoint has timeSlice[1].DesignatedPointTimeSlice.type equal-to ('ICAO', 'COORD', 'BRG_DIST', 'TERMINAL', 'OTHER', 'OTHER:.*') and has timeSlice[2].DesignatedPointTimeSlice.type not equal-to ('ICAO', 'COORD', 'BRG_DIST', 'TERMINAL', 'OTHER', 'OTHER:.*') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DesignatedPoint </noun_concept><verb_concept> has </verb_concept><noun_concept> timeSlice[1].DesignatedPointTimeSlice.type </noun_concept><keyword> equal-to </keyword><name> ('ICAO', 'COORD', 'BRG_DIST', 'TERMINAL', 'OTHER', 'OTHER:.*') </name><keyword> and </keyword><verb_concept> has </verb_concept><noun_concept> timeSlice[2].DesignatedPointTimeSlice.type </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><name> ('ICAO', 'COORD', 'BRG_DIST', 'TERMINAL', 'OTHER', 'OTHER:.*') </name> The DesignatedPoint type cannot change to a value that is not backwards mapped in EAD Found DesignatedPoint with a changed type into a value that is not backwards mapped in EAD. This is not supported. DesignatedPoint type baseline, snapshot, set of snapshots Data consistency rule Designated Point type change (in EAD)
AIXM-5.1_RULE-58DE0 Warning ICAO Annex 14 Table A5-2 It is prohibited that a RunwayCentrelinePoint with role equal-to 'THR' and with assigned location.ElevatedPoint.horizontalAccuracy value and with location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 0.5 <keyword> It is prohibited that a </keyword><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> role </noun_concept><keyword> equal-to </keyword><name> 'THR' </name><keyword> and with assigned </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value and with </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> Runway threshold elevation for non-precision approaches shall be published with 0.5 m accuracy Runway threshold elevation for non-precision approaches shall be published with 0.5 m accuracy RunwayCentrelinePoint horizontalAccuracy All Recommended practice (ICAO, industry, etc.) Accuracy (elevation) - Runway threshold for non-precision approach
AIXM-5.1_RULE-1C908 Error EAD EAD It is prohibited that a timeslice has interpretation not equal-to 'BASELINE' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> timeslice </noun_concept><verb_concept> has </verb_concept><noun_concept> interpretation </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><name> 'BASELINE' </name> EAD does not accept on upload any other type of TimeSlice than BASELINE Found unsupported TimeSlice type * interpretation All Recommended practice (ICAO, industry, etc.) TimeSlice types in EAD
AIXM-5.1_RULE-203A0 Warning AIXM 4.5 Business Rules AIRSPACE Each AirspaceVolume with assigned maximumLimit value shall have maximumLimitReference equal-to 'SFC' <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with assigned </keyword><noun_concept> maximumLimit </noun_concept><keyword> value shall </keyword><verb_concept> have </verb_concept><noun_concept> maximumLimitReference </noun_concept><keyword> equal-to </keyword><name> 'SFC' </name> AirspaceVolume with assigned maximumLimit shall have maximumLimitReference equal to 'SFC' (distance measured from GND). AirspaceVolume with assigned maximumLimit shall have maximumLimitReference equal to 'SFC' (distance measured from GND). AirspaceVolume maximumLimit All Data consistency rule AirspaceVolume maximum limit should be a height above ground
AIXM-5.1_RULE-1A0FE0 Error Error AIXM GML Profile OGC 12-028r1 It is prohibited that an AirspaceVolume.horizontalProjection.Surface has assigned patches.PolygonPatch.exterior.Ring.curveMember.href value and AirspaceVolume.horizontalProjection.Surface has previous patches.PolygonPatch.exterior.Ring.curveMember with end position distance to referenced GeoBorder larger than 30 M <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface </noun_concept><verb_concept> has </verb_concept><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember </noun_concept><noun_concept> GeoBorder </noun_concept> When GeoBorders are used in the definition of an AirspaceVolume.horizontalProjection, the position of the previous gml:pos must be situated, with a tolerance of 30 M, on a segment of the related GeoBorder The position of the previous AirspaceVolume.horizontalProjection.ElevatedSurface vertex is too far away (more than 30 M) from the referenced GeoBorder segments AirspaceVolume All Data consistency rule Airspace vertex (previous) proximity to geoBorder
AIXM-5.1_RULE-1A8CE1 Warning ICAO Annex 15 Table A7-1 It is prohibited that a SegmentPoint specialisation TerminalSegmentPoint with assigned pointChoice. fixDesignatedPoint isLocatedAt DesignatedPoint with location. Point coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice. fixDesignatedPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept><keyword> with </keyword><noun_concept> location. Point </noun_concept> Latitude and longitude of final approach fixes/points and other essential fixes/points comprising the instrument approach procedure shall be published with 1/10 sec resolution Latitude and longitude of final approach fixes/points and other essential fixes/points comprising the instrument approach procedure shall be published with 1/10 sec resolution SegmentPoint Point, ElevatedPoint set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - TerminalSegmentPoint
AIXM-5.1_RULE-1A8CE2 Warning ICAO Annex 15 Table A7-1 It is prohibited that a SegmentPoint specialisation TerminalSegmentPoint with assigned pointChoice. runwayPoint isLocatedAt RunwayCentrelinePoint with location. ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice. runwayPoint </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> RunwayCentrelinePoint </noun_concept><keyword> with </keyword><noun_concept> location. ElevatedPoint </noun_concept> Latitude and longitude of final approach fixes/points and other essential fixes/points comprising the instrument approach procedure shall be published with 1/10 sec resolution Latitude and longitude of final approach fixes/points and other essential fixes/points comprising the instrument approach procedure shall be published with 1/10 sec resolution SegmentPoint Point, ElevatedPoint set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - TerminalSegmentPoint
AIXM-5.1_RULE-1A8CE3 Warning ICAO Annex 15 Table A7-1 It is prohibited that a SegmentPoint specialisation TerminalSegmentPoint with assigned pointChoice. navaidSystem isLocatedAt Navaid with location. ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> SegmentPoint </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> TerminalSegmentPoint </noun_concept><keyword> with assigned </keyword><noun_concept> pointChoice. navaidSystem </noun_concept><verb_concept> isLocatedAt </verb_concept><noun_concept> Navaid </noun_concept><keyword> with </keyword><noun_concept> location. ElevatedPoint </noun_concept> Latitude and longitude of final approach fixes/points and other essential fixes/points comprising the instrument approach procedure shall be published with 1/10 sec resolution Latitude and longitude of final approach fixes/points and other essential fixes/points comprising the instrument approach procedure shall be published with 1/10 sec resolution SegmentPoint Point, ElevatedPoint set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - TerminalSegmentPoint
AIXM-5.1_RULE-1AB7DA AIXM Model It is obligatory that each PilotControlledLighting with assigned activatedGroundLighting value has activatedGroundLighting value resolved-into exactly one activates GroundLightSystem specialisation ApronLightSystem or TaxiwayLightSystem or TouchDownLiftOffLightSystem or RunwayDirectionLightSystem or VisualGlideSlopeIndicator or TaxiHoldingPositionLightSystem or RunwayProtectAreaLightSystem or GuidanceLineLightSystem <keyword> It is obligatory that each </keyword><noun_concept> PilotControlledLighting </noun_concept><keyword> with assigned </keyword><noun_concept> activatedGroundLighting </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> activatedGroundLighting </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> activates </verb_concept><noun_concept> GroundLightSystem </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> ApronLightSystem </noun_concept><keyword> or </keyword><noun_concept> TaxiwayLightSystem </noun_concept><keyword> or </keyword><noun_concept> TouchDownLiftOffLightSystem </noun_concept><keyword> or </keyword><noun_concept> RunwayDirectionLightSystem </noun_concept><keyword> or </keyword><noun_concept> VisualGlideSlopeIndicator </noun_concept><keyword> or </keyword><noun_concept> TaxiHoldingPositionLightSystem </noun_concept><keyword> or </keyword><noun_concept> RunwayProtectAreaLightSystem </noun_concept><keyword> or </keyword><noun_concept> GuidanceLineLightSystem </noun_concept> Referential integrity towards GroundLightSystem Referential integrity towards GroundLightSystem PilotControlledLighting activatedGroundLighting set of snapshots Minimal data rule Referential integrity towards GroundLightSystem
AIXM-5.1_RULE-BB420 Error AIXM Model It is obligatory that each ApronElement with assigned supplyService value has supplyService value resolved-into exactly one isProvidedWith Service specialisation AirportGroundService specialisation AirportSuppliesService <keyword> It is obligatory that each </keyword><noun_concept> ApronElement </noun_concept><keyword> with assigned </keyword><noun_concept> supplyService </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> supplyService </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isProvidedWith </verb_concept><noun_concept> Service </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportGroundService </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> AirportSuppliesService </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the second level of inheritance. ApronElement supplyService set of snapshots Minimal data rule Referential integrity - second level of inheritance (for the targetClass) (EAD profile)
AIXM-5.1_RULE-DA049 AIXM 4.5 AIXM 4.5 Uid It is prohibited that a OrganisationAuthority[1] has name equal-to OrganisationAuthority[2].name <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> OrganisationAuthority[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> name </noun_concept><keyword> equal-to </keyword><noun_concept> OrganisationAuthority[2].name </noun_concept> There cannot exists two different OrganisationAuthority that have identical values for name Found two different OrganisationAuthority that have identical values for name. Backwards mapping to AIXM 4.5 is impossible. OrganisationAuthority name set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for OrganisationAuthority - attribute
AIXM-5.1_RULE-1B2538 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Runway has timeSlice[1].RunwayTimeSlice.type equal-to 'FATO' and has timeSlice[2].RunwayTimeSlice.type not equal-to 'FATO' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Runway </noun_concept><verb_concept> has </verb_concept><noun_concept> timeSlice[1].RunwayTimeSlice.type </noun_concept><keyword> equal-to </keyword><name> 'FATO' </name><keyword> and </keyword><verb_concept> has </verb_concept><noun_concept> timeSlice[2].RunwayTimeSlice.type </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><name> 'FATO' </name> The Runway type cannot change in EAD Found Runway (type FATO) with a changed type. This is not supported in EAD. Runway type baseline, snapshot, set of snapshots Data consistency rule FATO type change (in EAD)
AIXM-5.1_RULE-1C9C38 Error EAD EAD It is prohibited that a DME has not assigned channel value and DME has not assigned ghostFrequency value <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> DME </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> channel </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> DME </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> ghostFrequency </noun_concept><keyword> value </keyword> Each DME must have either channel or ghost frequency Found DME with neither channel not ghorstFrequency assigned values. Backwards mapping to AIXM 4.5 is impossible. DME channel, ghostFrequency baseline outside delta, snapshot, set of snapshots Minimal data rule Minimal feature properties for DME
AIXM-5.1_RULE-19F488 Error AIXM GML Profile AIXM It is prohibited that Airspace with more than one geometryComponent has not assigned geometryComponent.AirspaceGeometryComponent.operationSequence value <keyword> It is prohibited that </keyword><noun_concept> Airspace </noun_concept><keyword> with more than one </keyword><noun_concept> geometryComponent </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> geometryComponent.AirspaceGeometryComponent.operationSequence </noun_concept><keyword> value </keyword> If Airspace has more than one geometryComponent, then the operation seqeunce for each AirspaceGeometryComponent must be defined Found Airspace with more than one component and undefined operationSequence for AirspaceGeometryComponent Airspace All Data consistency rule Airspace aggregation - sequence mandatory
AIXM-5.1_RULE-1C88B0 Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that OrganisationAuthority[1] has name equal-to OrganisationAuthority[2].name and OrganisationAuthority[1] has type not equal-to 'OTHER:LDAP' and OrganisationAuthority[2] has type not equal-to 'OTHER:LDAP' <keyword> It is prohibited that </keyword><noun_concept> OrganisationAuthority[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> name </noun_concept><keyword> equal-to </keyword><noun_concept> OrganisationAuthority[2].name </noun_concept><keyword> and </keyword><noun_concept> OrganisationAuthority[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><name> 'OTHER:LDAP' </name><keyword> and </keyword><noun_concept> OrganisationAuthority[2] </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><name> 'OTHER:LDAP' </name> There cannot exists two different OrganisationAuthority that have identical values for name unless one of them is an LDAP Organisation Found two different non-LDAP OrganisationAuthority that have identical values for name. Backwards mapping to AIXM 4.5 is impossible. OrganisationAuthority name, type baseline outside delta, snapshot, set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for OrganisationAuthority (except LDAP Organisatons)
AIXM-5.1_RULE-26D18 Error Error AIXM 4.5 Business Rules AIRSPACE_DERIV_GEOM It is obligatory that each Airspace with more than one geometryComponent has exactly one geometryComponent.AirspaceGeometryComponent.operation equal-to 'BASE' <keyword> It is obligatory that </keyword><keyword> each </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><keyword> more than one </keyword><noun_concept> geometryComponent </noun_concept><verb_concept> has </verb_concept><keyword> exactly one </keyword><noun_concept> geometryComponent.AirspaceGeometryComponent.operation </noun_concept><keyword> equal-to </keyword><name> 'BASE' </name> If Airspace has more than one geometryComponent, then there must exist exactly one AirspacegeometryComponent with operation = 'BASE' Found Airspace with more than one geometryComponents and with either none or more than one BASE geometry component AirspaceGeometryComponent operation All Data consistency rule Airspace aggregation - one BASE component
AIXM-5.1_RULE-4BED8 Error AIXM GML Profile OGC 12-028 It is prohibited that a Surface has assigned patches.PolygonPatch.exterior.Ring.curveMember.href value and not Surface is-descendant-of AirspaceVolume <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Surface </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> and </keyword><keyword> not </keyword><noun_concept> Surface </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> AirspaceVolume </noun_concept> Surface curveMember can refer to GeoBorder only when used for AirspaceVolume Found Surface with curveMember reference (by xlink:href) and Surface does not belong to AirspaceVolume. This is not supported. AirspaceVolume All Data consistency rule GML Profile - Surface to GeoBorder dependency - only for AirspaceVolume
AIXM-5.1_RULE-1CDEA0 Error AIXM GML Profile OGC 12-028 It is prohibited that a AirspaceVolume.horizontalProjection.Surface has assigned patches.PolygonPatch.exterior.Ring.curveMember.href value and AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href value not resolved-into exactly one GeoBorder and AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href value not resolved-into exactly one Curve and AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href value not resolved-into exactly one ElevatedCurve <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> not </keyword><keyword> resolved-into </keyword><keyword> exactly one </keyword><noun_concept> GeoBorder </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> not </keyword><keyword> resolved-into </keyword><keyword> exactly one </keyword><noun_concept> Curve </noun_concept><keyword> and </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> not </keyword><keyword> resolved-into </keyword><keyword> exactly one </keyword><noun_concept> ElevatedCurve </noun_concept> Surface curveMember references shall resolve into exactly one GeoBorder or one of its Curve descendants Referential integrity error: the AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember association with GeoBorder cannot be resolved. No target GeoBorder or Curve could be found. AirspaceVolume baseline outside delta, snapshot, set of snapshots Data consistency rule GML Profile - Surface to GeoBorder dependency - referential integrity
AIXM-5.1_RULE-16760 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Airspace has timeSlice[1].AirspaceTimeSlice.type not equal-to timeSlice[2].AirspaceTimeSlice.type <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><noun_concept> timeSlice[1].AirspaceTimeSlice.type </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><noun_concept> timeSlice[2].AirspaceTimeSlice.type </noun_concept> The Airspace type cannot change in EAD Found Airspace with a changed type. This is not supported in EAD. Airspace type baseline outside delta, snapshot, set of snapshots Data consistency rule Airspace type change (in EAD)
AIXM-5.1_RULE-45D30 Warning ICAO Annex 15 Table A7-1 It is prohibited that a DeicingArea with assigned extent.ElevatedSurface value has extent.ElevatedSurface coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> DeicingArea </noun_concept><keyword> with assigned </keyword><noun_concept> extent.ElevatedSurface </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> extent.ElevatedSurface </noun_concept> Latitude and longitude of de-icing/anti-icing facility (polygon) shall be published with 1/10 sec resolution Latitude and longitude of de-icing/anti-icing facility (polygon) shall be published with 1/10 sec resolution DeicingArea All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - de-icing/anti-icing facility
AIXM-5.1_RULE-CA260 Warning AIXM 4.5 Business Rules AIRSPACE Each AirspaceVolume with not assigned lowerLimit or not assigned upperLimit shall have assigned contributorAirspace and contributorAirspace.AirspaceVolumeDependency.dependency equal-to 'FULL_GEOMETRY' <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with not assigned </keyword><noun_concept> lowerLimit </noun_concept><keyword> or not assigned </keyword><noun_concept> upperLimit </noun_concept><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> contributorAirspace </noun_concept><keyword> and </keyword><noun_concept> contributorAirspace.AirspaceVolumeDependency.dependency </noun_concept><keyword> equal-to </keyword><name> 'FULL_GEOMETRY' </name> An AirspaceVolume for which the lower or the upper limit are not specified, must be defined by aggregation (full geometry). Found AirspaceVolume with not assigned lowerLimit value or not assigned upperLimit value and which is not defined either as a dependency (of type 'FULL_GEOMETRY') on another Airspace. AirspaceVolume lowerLimit, upperLimit baseline outside delta, snapshot, set of snapshots Minimal data rule AirspaceVolume without vertical limits must be aggregation
AIXM-5.1_RULE-24220 Warning Warning AIXM 4.5 Business Rules ASE_107 Each Airspace with assigned upperLowerSeparation shall not have type not equal-to 'FIR' <keyword> Each </keyword><noun_concept> Airspace </noun_concept><keyword> with assigned </keyword><noun_concept> upperLowerSeparation </noun_concept><keyword> shall not </keyword><verb_concept> have </verb_concept><noun_concept> type </noun_concept><keyword> not equal-to </keyword><name> 'FIR' </name> The lower/upper separation value may be specified only for Airspace of type 'FIR' The lower/upper separation value may be specified only for Airspace of type 'FIR' Airspace upperLowerSeparation EXCL_DELTA;NO_REF Data consistency rule Lower/upper separation only for FIR
AIXM-5.1_RULE-1CEA58 Error AIXM GML Profile OGC 12-028 It is prohibited that a AirspaceVolume.horizontalProjection.Surface has assigned patches.PolygonPatch.exterior.Ring.curveMember.href value and AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href value resolved-into exactly one Curve and not Curve is-descendant-of GeoBorder <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember.href </noun_concept><keyword> value </keyword><keyword> resolved-into </keyword><keyword> exactly one </keyword><noun_concept> Curve </noun_concept><keyword> and </keyword><keyword> not </keyword><noun_concept> Curve </noun_concept><verb_concept> is-descendant-of </verb_concept><noun_concept> GeoBorder </noun_concept> Surface curveMember references shall resolve into exactly one GeoBorder or one of its Curve descendants Referential integrity error: the AirspaceVolume.horizontalProjection.Surface.patches.PolygonPatch.exterior.Ring.curveMember association is resolved into a Curve that is not descendant of a GeoBorder. This is not allowed by the GML Profile. AirspaceVolume baseline outside delta, snapshot, set of snapshots Data consistency rule GML Profile - Surface to GeoBorder dependency - referential integrity
AIXM-5.1_RULE-1ADEEA Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with assigned servedAirport value isComposedOf NavaidEquipment specialisation DirectionFinder with location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> DirectionFinder </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of DirectionFinder, when used for aerodrome operations, shall be published with 1/10 sec resolution Latitude and Longitude of DirectionFinder, when used for aerodrome operations, shall be published with 1/10 sec resolution Navaid set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - DirectionFinder when used at aerodrome
AIXM-5.1_RULE-1ADEED Warning ICAO Annex 15 Table A7-1 It is prohibited that a Navaid with assigned servedAirport value isComposedOf NavaidEquipment specialisation SDF with location.ElevatedPoint coordinates expressed with less than 5 decimals <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> value </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> SDF </noun_concept><keyword> with </keyword><noun_concept> location.ElevatedPoint </noun_concept> Latitude and Longitude of SDF, when used for aerodrome operations, shall be published with 1/10 sec resolution Latitude and Longitude of SDF, when used for aerodrome operations, shall be published with 1/10 sec resolution Navaid set of snapshots Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - SDF when used at aerodrome
AIXM-5.1_RULE-DC758 Warning FAA FNS-NDS Tech Spec Scenario ID: 25 It is prohibited that an AirportHeliportTimeSlice with availability.ManoeuvringAreaAvailability.operationalStatus not equal-to ('CLOSED', 'LIMITED') belongsTo Event with scenario equal-to '25' <keyword> It is prohibited that an </keyword><noun_concept> AirportHeliportTimeSlice </noun_concept><keyword> with </keyword><noun_concept> availability.ManoeuvringAreaAvailability.operationalStatus </noun_concept><keyword> not equal-to </keyword><name> ('CLOSED', 'LIMITED') </name><verb_concept> belongsTo </verb_concept><noun_concept> Event </noun_concept><keyword> with </keyword><noun_concept> scenario </noun_concept><keyword> equal-to </keyword><name> '25' </name> If the event scenario is "aerodrome closure" (id=25), then operationalStatus shall be CLOSED or LIMITED If the event scenario is "aerodrome closure" (id=25), then operationalStatus shall be CLOSED or LIMITED AirportHeliport All Standard (ICAO, industry, etc.) Event (FAA) - 25 - only CLOSED or LIMITED status
AIXM-5.1_RULE-46500 Error AIXM 4.5 GEO_BORDER It is obligatory that each GeoBorder has exactly one border.Curve.segments.GeodesicString <keyword> It is obligatory that </keyword><keyword> each </keyword><noun_concept> GeoBorder </noun_concept><verb_concept> has </verb_concept><keyword> exactly one </keyword><noun_concept> border.Curve.segments.GeodesicString </noun_concept> Each GeoBorder contains one and only one border.Curve.segments.GeodesicString Found GeoBorder with geometry defined by something else than a single geodesicString GeoBorder border All Data consistency rule GeoBorder geometry - only straight lines
AIXM-5.1_RULE-73F78 Error AIXM 4.5 Business Rules EN_ROUTE_RTE.TXT_DESIC It is prohibited that Route has not assigned designatorSecondLetter value and Route has not assigned designatorNumber value and Route has not assigned name value <keyword> It is prohibited that </keyword><noun_concept> Route </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> designatorSecondLetter </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Route </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> designatorNumber </noun_concept><keyword> value </keyword><keyword> and </keyword><noun_concept> Route </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> name </noun_concept><keyword> value </keyword> Either route designator elements or route name should be specified Found Route with unassigned values for both designatorSecondLetter, designatorNumber and name. Backwards mapping to AIXM 4.5 is impossible. Route designatorSecondLetter, designatorNumber, name All Minimal data rule Route minimal properties for AIXM 4.5 backwards compatibility
AIXM-5.1_RULE-1D4C1 Error AIXM 4.5 Business Rules AIRSPACE Each AirspaceVolume with contributorAirspace.AirspaceVolumeDependency.dependency value equal-to 'FULL_GEOMETRY' shall not have assigned upperLimit <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> contributorAirspace.AirspaceVolumeDependency.dependency </noun_concept><keyword> value equal-to </keyword><name> 'FULL_GEOMETRY' </name><keyword> shall not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> upperLimit </noun_concept> An AirspaceVolume that has a geometry defined as a full copy of the geometry of another Airspace shall not have vertical limits (because it re-uses the vertical limits of the contributor Airspace). Found AirspaceVolume defined as FULL_GEOMETRY dependency and also having upperLimit AirspaceVolume upperLimit All Data consistency rule AirspaceVolume with full geometry dependency - no vertical limits
AIXM-5.1_RULE-1D4C2 Error AIXM 4.5 Business Rules AIRSPACE Each AirspaceVolume with contributorAirspace.AirspaceVolumeDependency.dependency value equal-to 'FULL_GEOMETRY' shall not have assigned minimumLimit <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> contributorAirspace.AirspaceVolumeDependency.dependency </noun_concept><keyword> value equal-to </keyword><name> 'FULL_GEOMETRY' </name><keyword> shall not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> minimumLimit </noun_concept> An AirspaceVolume that has a geometry defined as a full copy of the geometry of another Airspace shall not have vertical limits (because it re-uses the vertical limits of the contributor Airspace). Found AirspaceVolume defined as FULL_GEOMETRY dependency and also having minimumLimit AirspaceVolume minimumLimit All Data consistency rule AirspaceVolume with full geometry dependency - no vertical limits
AIXM-5.1_RULE-1D4C3 Error AIXM 4.5 Business Rules AIRSPACE Each AirspaceVolume with contributorAirspace.AirspaceVolumeDependency.dependency value equal-to 'FULL_GEOMETRY' shall not have assigned lowerLimit <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> contributorAirspace.AirspaceVolumeDependency.dependency </noun_concept><keyword> value equal-to </keyword><name> 'FULL_GEOMETRY' </name><keyword> shall not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> lowerLimit </noun_concept> An AirspaceVolume that has a geometry defined as a full copy of the geometry of another Airspace shall not have vertical limits (because it re-uses the vertical limits of the contributor Airspace). Found AirspaceVolume defined as FULL_GEOMETRY dependency and also having lowerLimit AirspaceVolume lowerLimit All Data consistency rule AirspaceVolume with full geometry dependency - no vertical limits
AIXM-5.1_RULE-1D4C4 Error AIXM 4.5 Business Rules AIRSPACE Each AirspaceVolume with contributorAirspace.AirspaceVolumeDependency.dependency value equal-to 'FULL_GEOMETRY' shall not have assigned maximumLimit <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> contributorAirspace.AirspaceVolumeDependency.dependency </noun_concept><keyword> value equal-to </keyword><name> 'FULL_GEOMETRY' </name><keyword> shall not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> maximumLimit </noun_concept> An AirspaceVolume that has a geometry defined as a full copy of the geometry of another Airspace shall not have vertical limits (because it re-uses the vertical limits of the contributor Airspace). Found AirspaceVolume defined as FULL_GEOMETRY dependency and also having maximumLimit AirspaceVolume maximumLimit All Data consistency rule AirspaceVolume with full geometry dependency - no vertical limits
AIXM-5.1_RULE-1A5A18 Error EAD EAD Each AirspaceGeometryComponent with operation equal-to 'BASE' shall have operationSequence equal-to '1' <keyword> Each </keyword><noun_concept> AirspaceGeometryComponent </noun_concept><keyword> with </keyword><noun_concept> operation </noun_concept><keyword> equal-to </keyword><name> 'BASE' </name><keyword> shall </keyword><verb_concept> have </verb_concept><noun_concept> operationSequence </noun_concept><keyword> equal-to </keyword><name> '1' </name> An AirspaceGeometryComponent that is used as BASE for an aggregation shall have operationSequence equal to 1 Found AirspacegeometryComponent with operation='BASE' and operationSequence different from 1. AirspaceGeometryComponent operation All Data consistency rule Airspace aggregation - BASE component sequence
AIXM-5.1_RULE-1C8C98 Error EAD EAD SDD ​It is prohibited that OrganisationAuthority has type equal-to 'OTHER:LDAP' <keyword> ​It is prohibited that </keyword><noun_concept> OrganisationAuthority </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'OTHER:LDAP' </name> OrganisationAuthority OTHER:LDAP cannot be upload to EAD because of their special role in user management Found OrganisationAuthority with type equal-to OTHER:LDAP. This cannot be used in EAD uploads. OrganisationAuthority type All Standard (ICAO, industry, etc.) OrganisationAuthority OTHER:LDAP not supported in EAD
AIXM-5.1_RULE-BA090 NM CACD It is prohibited that AirspaceVolume is-property-of Airspace with type equal-to ('CTA','UTA', 'OCA') and has contributorAirspace.AirspaceVolumeDependency.dependency not equal-to 'FULL_GEOMETRY' <keyword> It is prohibited that </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('CTA','UTA', 'OCA') </name><keyword> and </keyword><verb_concept> has </verb_concept><noun_concept> contributorAirspace.AirspaceVolumeDependency.dependency </noun_concept><keyword> not equal-to </keyword><name> 'FULL_GEOMETRY' </name> The geometry of operational airspace of type CTA, UTA and OCA shall be encoded as an aggregation of the corresponding operational SECTORS. Found Airspace of type CTA/UTA/OCA that has dependency of type different from aggregation ('FULL_GEOMETRY') Airspace type All Data consistency rule CTA and similar areas shall be an aggregation of sectors - part 4
AIXM-5.1_RULE-C6F99 Error AIXM 4.5 AIXM 4.5 Uid It is prohibited that a RunwayDirection[1] has designator equal-to RunwayDirection[2]. designator and RunwayDirection[1] uses Runway and RunwayDirection[2] uses Runway <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayDirection[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> RunwayDirection[2]. designator </noun_concept><keyword> and </keyword><noun_concept> RunwayDirection[1] </noun_concept><verb_concept> uses </verb_concept><noun_concept> Runway </noun_concept><keyword> and </keyword><noun_concept> RunwayDirection[2] </noun_concept><verb_concept> uses </verb_concept><noun_concept> Runway </noun_concept> There cannot exists two different RunwayDirection that have identical values for designator and uses same Runway Found two different RunwayDirection that have identical values for designator and uses same Runway. Backwards mapping to AIXM 4.5 is impossible. RunwayDirection designator set of snapshots Standard (ICAO, industry, etc.) Unique AIXM 4.5 natural key for RunwayDirection - attribute and association
AIXM-5.1_RULE-1C7140 Warning ICAO Annex 10 3.3.2.1 It is prohibited that a VOR has assigned frequency.uom value equal-to 'MHZ' and VOR has assigned frequency value not divisible-by 0.05 <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><name> 'MHZ' </name><keyword> and </keyword><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword><keyword> not </keyword> According to ICAO Annex 10, item 3.3.2.1 each VOR frequency shall have an increment of 50 KHZ (starting from 108.0 MHZ) Found VOR frequency that is not an increment of 50 KHZ VOR frequency All Standard (ICAO, industry, etc.) VOR frequency increment
AIXM-5.1_RULE-128630 Error ICAO Annex 11 appen1 It is prohibited that a Route has assigned designatorNumber value expressed with more than 3 digits <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Route </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> designatorNumber </noun_concept><keyword> value </keyword> The route designator number must be an integer between 1 and 999 Found Route designatorNumber with more than 3 digits Route designatorNumber all Standard (ICAO, industry, etc.) Route designator number
AIXM-5.1_RULE-5B108 Warning ICAO Annex 15 Table A7-1 It is prohibited that an ApronElement has extent.ElevatedSurface coordinates expressed with less than 5 decimals <keyword> It is prohibited that an </keyword><noun_concept> ApronElement </noun_concept><verb_concept> has </verb_concept><noun_concept> extent.ElevatedSurface </noun_concept> Latitude and longitude of apron boundaries shall be published with 1/10 sec resolution Latitude and longitude of apron boundaries shall be published with 1/10 sec resolution ApronElement ElevatedSurface All Recommended practice (ICAO, industry, etc.) Resolution (horizontal) - Apron boundaries
AIXM-5.1_RULE-E8E90 Warning AIXM 4.5 Business Rules AirportHeliport It is prohibited that Runway with assigned type equal-to 'RWY' isSituatedAt AirportHeliport with assigned type equal-to 'HP' <keyword> It is prohibited that </keyword><noun_concept> Runway </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'RWY' </name><verb_concept> isSituatedAt </verb_concept><noun_concept> AirportHeliport </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'HP' </name> A Runway of type 'RWY' cannot be associated with an AirportHeliport with type 'HP' A Runway of type 'RWY' cannot be associated with an AirportHeliport with type 'HP' Runway type baseline outside delta, snapshot, set of snapshots Data consistency rule Runway cannot be associated with heliport
AIXM-5.1_RULE-D7168 Error AIXM 4.5 AIXM 4.5 It is prohibited that an Airspace has at least 100 geometryComponent <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> at least 100 </keyword><noun_concept> geometryComponent </noun_concept> An Airspace cannot have more than 99 AirspaceVolume, in order to enable the automatic creation of the Airspace PART in case of backward mapping to AIXM 4.5. Found Airspace with more than 99 AirspaceVolume. This is not allowed in EAD. Airspace All Data consistency rule Airspace aggregation - maximum volumes
AIXM-5.1_RULE-19FC58 Error Error AIXM Model AIXM Model It is prohibited that an Airspace has geometryComponent[1] and Airspace has geometryComponent[2] and geometryComponent[1].AirspaceGeometryComponent.operationSequence equal-to geometryComponent[2].AirspaceGeometryComponent.operationSequence <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><noun_concept> geometryComponent[1] </noun_concept><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><noun_concept> geometryComponent[2] </noun_concept><keyword> and </keyword><noun_concept> geometryComponent[1].AirspaceGeometryComponent.operationSequence </noun_concept><keyword> equal-to </keyword><noun_concept> geometryComponent[2].AirspaceGeometryComponent.operationSequence </noun_concept> Each AirspaceVolume associated with the same Airspace must have a unique operationSequence number Found Airspace with duplicate operationSequence value for at least two of its AirspaceVolume Airspace All Data consistency rule Airspace aggregation - unique operationSequence
AIXM-5.1_RULE-2B369 Error AIXM GML Profile OGC document 12-028r1 It is prohibited that a CircleByCenterPoint has assigned radius.uom value not equal-to ('m', 'km', '[nmi_i]') <keyword> It is prohibited that a </keyword><noun_concept> CircleByCenterPoint </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> radius.uom </noun_concept><keyword> value </keyword><keyword> not equal-to </keyword><name> ('m', 'km', '[nmi_i]') </name> UCUM values shall be used for the unit of measurement gml:radius property of CircleByCenterPoint Found CircleByCenterPoint with unsupported value for gml:radius unit of measurement CircleByCenterPoint gml:radius All Standard (ICAO, industry, etc.) GML Profile - UCUM values for gml:radius
AIXM-5.1_RULE-2B36A Error AIXM GML Profile OGC document 12-028r1 It is prohibited that a ArcByCenterPoint has assigned radius.uom value not equal-to ('m', 'km', '[nmi_i]') <keyword> It is prohibited that a </keyword><noun_concept> ArcByCenterPoint </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> radius.uom </noun_concept><keyword> value </keyword><keyword> not equal-to </keyword><name> ('m', 'km', '[nmi_i]') </name> UCUM values shall be used for the unit of measurement gml:radius property of ArcByCenterPoint Found ArcByCenterPoint with unsupported value for gml:radius unit of measurement ArcByCenterPoint gml:radius All Standard (ICAO, industry, etc.) GML Profile - UCUM values for gml:radius
AIXM-5.1_RULE-BBFD0 NM CACD It is prohibited that AirspaceVolume is-property-of Airspace with type equal-to ('CTA','UTA', 'OCA') and dependsOn Airspace with type not equal-to 'SECTOR' <keyword> It is prohibited that </keyword><noun_concept> AirspaceVolume </noun_concept><verb_concept> is-property-of </verb_concept><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('CTA','UTA', 'OCA') </name><keyword> and </keyword><verb_concept> dependsOn </verb_concept><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> not equal-to </keyword><name> 'SECTOR' </name> The geometry of operational airspace of type CTA, UTA and OCA shall be encoded as an aggregation of the corresponding operational SECTORS. Found Airspace of type CTA/UTA/OCA that depends (for aggregation) on Airspace with type other than SECTOR AirspaceVolume type set of snapshots Data consistency rule CTA and similar areas shall be an aggregation of sectors - part 3
AIXM-5.1_RULE-159371 Error AIXM GML Profile AIXM It is prohibited that a gml:pos has assigned value that includes 'NaN' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> gml:pos </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'NaN' </name> Although NaN is allowed by the GML scherma (because it is a valid double) in gml:pos, it cannot be used in AIXM because it does not make sense. Found 'NaN' (not a number) in gml:pos. This is not supported in AIXM. gml:pos Minimal data rule GML Profile - NaN not allowed in gml:pos
AIXM-5.1_RULE-159372 Error AIXM GML Profile AIXM It is prohibited that a gml:posList has assigned value that includes 'NaN' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> gml:posList </noun_concept><verb_concept> has </verb_concept><keyword> assigned value </keyword><name> 'NaN' </name> Although NaN is allowed by the GML scherma (because it is a valid double) in gml:posList, it cannot be used in AIXM because it does not make sense. Found 'NaN' (not a number) in gml:posList. This is not supported in AIXM. gml:posList Minimal data rule GML Profile - NaN not allowed in gml:posList
AIXM-5.1_RULE-4F1A1 Warning ICAO Annex 15 Table A7-4 It is prohibited that a RunwayDirection has assigned trueBearing value expressed with less than 2 decimals <keyword> It is prohibited that a </keyword><noun_concept> RunwayDirection </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> trueBearing </noun_concept><keyword> value </keyword> Runway and FATO true trueBearing shall be published with 1/100 deg resolution Runway and FATO true trueBearing shall be published with 1/100 deg resolution RunwayDirection trueBearing All Recommended practice (ICAO, industry, etc.) Resolution (bearing) - RWY and FATO
AIXM-5.1_RULE-4F1A2 Warning ICAO Annex 15 Table A7-4 It is prohibited that a RunwayDirection has assigned magneticBearing value expressed with less than 2 decimals <keyword> It is prohibited that a </keyword><noun_concept> RunwayDirection </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> magneticBearing </noun_concept><keyword> value </keyword> Runway and FATO true magneticBearing shall be published with 1/100 deg resolution Runway and FATO true magneticBearing shall be published with 1/100 deg resolution RunwayDirection trueBearing All Recommended practice (ICAO, industry, etc.) Resolution (bearing) - RWY and FATO
AIXM-5.1_RULE-DDAE0 Error AIXM 4.5 Business Rules MKR It is prohibited that a MarkerBeacon has assigned frequency.uom value not equal-to 'MHZ' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> MarkerBeacon </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword><keyword> not </keyword><keyword> equal-to </keyword><name> 'MHZ' </name> The value of the Marker Beacon frequency must be 75 MHz. Found MarkerBeacon with frequency.uom value different from MHZ. Backward mapping to AIXM 5.1 is impossible in EAD. MarkerBeacon frequency All Standard ICAO MarkerBeacon frequency uom
AIXM-5.1_RULE-255A8 Warning AIXM 4.5 Business Rules Each Navaid with assigned type equal-to ('ILS','ILS_DME','MLS','MLS_DME') shall have assigned signalPerformance value <keyword> Each </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('ILS','ILS_DME','MLS','MLS_DME') </name><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> signalPerformance </noun_concept><keyword> value </keyword> Each ILS or MLS should have a specified value for the signalPerformance Each ILS or MLS should have a specified value for the signalPerformance Navaid type All Minimal data rule ILS and MLS should have signalPerformance
AIXM-5.1_RULE-1BC560 Error EAD Rule ASE-R1 in DOC-FRRJTS It is prohibited that Airspace[1] has designator equal-to Airspace[2].designator and Airspace[1] has type equal-to ('RAS', 'ADV', 'ATZ', 'ATZ_P', 'HTZ', 'MTR', 'NAS_P', 'UADV', 'OTHER', 'OTHER:.*') and Airspace[2] has type equal-to ('RAS', 'ADV', 'ATZ', 'ATZ_P', 'HTZ', 'MTR', 'NAS_P', 'UADV', 'OTHER', 'OTHER:.*') <keyword> It is prohibited that </keyword><noun_concept> Airspace[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> equal-to </keyword><noun_concept> Airspace[2].designator </noun_concept><keyword> and </keyword><noun_concept> Airspace[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('RAS', 'ADV', 'ATZ', 'ATZ_P', 'HTZ', 'MTR', 'NAS_P', 'UADV', 'OTHER', 'OTHER:.*') </name><keyword> and </keyword><noun_concept> Airspace[2] </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('RAS', 'ADV', 'ATZ', 'ATZ_P', 'HTZ', 'MTR', 'NAS_P', 'UADV', 'OTHER', 'OTHER:.*') </name> Airspaces with type in (RAS, ADV, ATZ, ATZ_P, HTZ, MTR, NAS_P, OTHER, UADV, OTHER) cannot have the same designator value. Found more than one Airspace with the same designator and also the type equal-to one of the following: RAS, ADV, ATZ, ATZ_P, HTZ, MTR, NAS_P, OTHER, UADV, OTHER:.... Backwards mapping results in AIXM 4.5 key conflict. Airspace designator, type Standard (ICAO, industry, etc.) Unique AIXM 4.5 key for Airspace with type backwards mapped to RAS
AIXM-5.1_RULE-12B510 Error EAD EAD It is prohibited that AirspaceVolume with not assigned contributorAirspace value has not assigned horizontalProjection value and has not assigned centreline value <keyword> It is prohibited that </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with not assigned </keyword><noun_concept> contributorAirspace </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> horizontalProjection </noun_concept><keyword> value and </keyword><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> centreline </noun_concept><keyword> value </keyword> An AirspaceVolume that is not defined with a contributorAirspace must have either horizontalProjection or centreline Found AirspaceVolume without any of the following: horizontalProjection, centreline, contributorAirspace AirspaceVolume All Minimal data rule AirspaceVolume must have own or derived geometry
AIXM-5.1_RULE-1A0810 Error AIXM Model Each AirspaceVolume with not assigned centreline value shall not have assigned width value <keyword> Each </keyword><noun_concept> AirspaceVolume </noun_concept><keyword> with </keyword><keyword> not assigned </keyword><noun_concept> centreline </noun_concept><keyword> value shall not </keyword><verb_concept> have </verb_concept><keyword> assigned </keyword><noun_concept> width </noun_concept><keyword> value </keyword> If the AirspaceVolume does not have centreline (is not a corridor), then width shall not be specified Found AirspaceVolume with assigned width value, but not of type corridor (it does not have centreline as geometry) AirspaceVolume width All Data consistency rule AirspaceVolume width only for corridor
AIXM-5.1_RULE-C8320 Error AIXM Model Annex 10 It is prohibited that Navaid isComposedOf NavaidEquipment specialization VOR with type equal-to 'VOT' <keyword> It is prohibited that </keyword><noun_concept> Navaid </noun_concept><verb_concept> isComposedOf </verb_concept><noun_concept> NavaidEquipment </noun_concept><verb_concept> specialization </verb_concept><noun_concept> VOR </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'VOT' </name> A VOR Test Facility is not a real VOR, therefore it cannot be used as Navaid. Found Navaid using a VOR of type VOT (test facility) as equipment. This does not make sense. Navaid set of snapshots Data consistency rule VOT cannot be used as navaid
AIXM-5.1_RULE-A4100 Warning AIXM 4.5 Business Rules TIMESHEET It is prohibited that Timesheet with not assigned startTime has not assigned startEvent <keyword> It is prohibited that </keyword><noun_concept> Timesheet </noun_concept><keyword> with not assigned </keyword><noun_concept> startTime </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> startEvent </noun_concept> Any Timesheet should have a start time or a start event. Otherwise the start of the schedule is not precise enough. Found Timesheet with neither startTime nor startEvent specified. Timesheet startTime All Data consistency rule Timesheet needs startTime or startEvent
AIXM-5.1_RULE-EDCB0 Error AIXM 4.5 Business Rules DESIGNATED_POINT It is prohibited that DesignatedPoint[1] has type equal-to ('ICAO', 'COORD', 'OTHER' or 'OTHER:.*') and DesignatedPoint[2] has type equal-to ('ICAO', 'COORD', 'OTHER' or 'OTHER:.*') and the distance between DesignatedPoint[1].location.Point and DesignatedPoint[2].location.Point is lower-or-equal-to 1 NM <keyword> It is prohibited that </keyword><noun_concept> DesignatedPoint[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('ICAO', 'COORD', 'OTHER' or 'OTHER:.*') </name><keyword> and </keyword><noun_concept> DesignatedPoint[2] </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('ICAO', 'COORD', 'OTHER' or 'OTHER:.*') </name><keyword> and </keyword><noun_concept> DesignatedPoint[1].location.Point </noun_concept><keyword> and </keyword><noun_concept> DesignatedPoint[2].location.Point </noun_concept> There cannot exist two different DesignatedPoint with an en-route usage type ('ICAO', 'COORD', 'OTHER' or 'OTHER:.*') and located within 1 NM from each-other Found two different DesignatedPoint with type in ('ICAO', 'COORD', 'OTHER' or 'OTHER:.*') and located within 1 NM from each-other. They are very likely a duplicate. DesignatedPoint designator baseline outside delta, snapshot, set of snapshots Recommended practice DesignatedPoint for enroute use within 1NM
AIXM-5.1_RULE-1C61A0 EAD FRRJTS-1.4b, DPN-R1 It is prohibited that an EnRouteSegmentPoint has pointChoice.SignificantPoint.fixDesignatedPoint value resolved-into isLocatedAt DesignatedPoint and DesignatedPoint has type not equal-to ('ICAO', 'COORD', 'BRG_DIST', 'OTHER', 'OTHER:.*') <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> EnRouteSegmentPoint </noun_concept><verb_concept> has </verb_concept><noun_concept> pointChoice.SignificantPoint.fixDesignatedPoint </noun_concept><keyword> value </keyword><keyword> resolved-into </keyword><verb_concept> isLocatedAt </verb_concept><noun_concept> DesignatedPoint </noun_concept><keyword> and </keyword><noun_concept> DesignatedPoint </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> not equal-to </keyword><name> ('ICAO', 'COORD', 'BRG_DIST', 'OTHER', 'OTHER:.*') </name> A DesignatedPoint used as pointChoiceNavaidSystem in a RouteSegment should not have a type different from ICAO, COORD, BRG_DIST, OTHER, OTHER:... Found RouteSegment start or end using incorrect (not backwards mapped) DesignatedPoint type EnRouteSegmentPoint baseline outside delta, snapshot, set of snapshots Data consistency rule RouteSegment start/end DesignatedPoint type
AIXM-5.1_RULE-64961 Warning ICAO Annex 14 Table A5-1; V2 Table A1-1 It is prohibited that a Navaid with assigned servedAirport and location.ElevatedPoint.horizontalAccuracy.uom equal-to 'M' has location.ElevatedPoint.horizontalAccuracy value higher-than 3.0 <keyword> It is prohibited that a </keyword><noun_concept> Navaid </noun_concept><keyword> with assigned </keyword><noun_concept> servedAirport </noun_concept><keyword> and </keyword><noun_concept> location.ElevatedPoint.horizontalAccuracy.uom </noun_concept><keyword> equal-to </keyword><name> 'M' </name><verb_concept> has </verb_concept><noun_concept> location.ElevatedPoint.horizontalAccuracy </noun_concept><keyword> value higher-than </keyword> The position of Navaid located at the aerodrome should have horizontal accuracy better than 3.0 M The position of Navaid located at the aerodrome should have horizontal accuracy better than 3.0 M Navaid location set of snapshots Standard (ICAO, industry, etc.) Accuracy (horizontal) Navaid located at Aerodrome
AIXM-5.1_RULE-15BA80 Warning ICAO Annex 11 Appendix 1, section 2 It is prohibited that a Route has assigned multipleIdentifier value not equal-to ('F', 'G', 'Y' or 'Z') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Route </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> multipleIdentifier </noun_concept><keyword> value </keyword><keyword> not </keyword><keyword> equal-to </keyword><name> ('F', 'G', 'Y' or 'Z') </name> The multipleIdentifier may be 'F', 'G', 'Y' or 'Z' Found Route with multipleIdentifier value other than ('F', 'G', 'Y' or 'Z') Route multipleIdentifier All Standard (ICAO, industry, etc.) Route multiple identifier
AIXM-5.1_RULE-CF080 Error AIXM 4.5 AIXM 4.5 It is prohibited that a Route has timeSlice[1].RouteTimeSlice.type equal-to ('NAT') and has timeSlice[2].RouteTimeSlice.type not equal-to ('NAT') <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> Route </noun_concept><verb_concept> has </verb_concept><noun_concept> timeSlice[1].RouteTimeSlice.type </noun_concept><keyword> equal-to </keyword><name> ('NAT') </name><keyword> and </keyword><verb_concept> has </verb_concept><noun_concept> timeSlice[2].RouteTimeSlice.type </noun_concept><keyword> not </keyword><keyword> equal-to </keyword><name> ('NAT') </name> The Route type cannot change to a value that is not backwards mapped in EAD Found Route with a changed type into a value that is not backwards mapped in EAD. This is not supported. Route type baseline, snapshot, set of snapshots Data consistency rule Route type change (in EAD)
AIXM-5.1_RULE-1B7358 Warning ICAO Annex 10 3.3.2.1 It is prohibited that a VOR has assigned frequency value lower-than 108.0 and VOR has assigned frequency.uom value equal-to 'MHZ' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency </noun_concept><keyword> value </keyword><keyword> lower-than </keyword><name> 108.0 </name><keyword> and </keyword><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword><keyword> equal-to </keyword><name> 'MHZ' </name> According to Point 3.3.2.1 in ICAO Annex 10, the VOR frequency shall at minimum 108.0 MHZ. Found VOR frequency value lower than 108 MHZ VOR frequency All Standard (ICAO, industry, etc.) VOR frequency - minimum value
AIXM-5.1_RULE-9FAB0 Error EAD EAD It is prohibited that an Airspace[1] has geometryComponent[1].AirspaceGeometryComponent.theAirspaceVolume.contributorAirspace.AirspaceVolumeDependency.theAirspace resolves-into Airspace[2] and Airspace[1] has geometryComponent[2].AirspaceGeometryComponent.theAirspaceVolume.contributorAirspace.AirspaceVolumeDependency.theAirspace resolves-into Airspace[2] <keyword> It is prohibited that an </keyword><noun_concept> Airspace[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> geometryComponent[1].AirspaceGeometryComponent.theAirspaceVolume.contributorAirspace.AirspaceVolumeDependency.theAirspace </noun_concept><keyword> resolves-into </keyword><noun_concept> Airspace[2] </noun_concept><keyword> and </keyword><noun_concept> Airspace[1] </noun_concept><verb_concept> has </verb_concept><noun_concept> geometryComponent[2].AirspaceGeometryComponent.theAirspaceVolume.contributorAirspace.AirspaceVolumeDependency.theAirspace </noun_concept><keyword> resolves-into </keyword><noun_concept> Airspace[2] </noun_concept> An Airspace cannot be used twice for the definition (by aggregation) of the geometry of another Airspace Found Airspace that appears twice in the aggregation of the same Airspace Airspace baseline, snapshot, set of snapshots Standard (ICAO, industry, etc.) Airspace aggregation - cannot use twice the same Airspace
AIXM-5.1_RULE-877F8 Error AIXM 4.5 AIXM 4.5 It is prohibited that a RunwayDirection has designator with assigned value not matching pattern '((0[1-9])|([1-2][0-9])|(3[0-6]))([A-Z])?' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> RunwayDirection </noun_concept><verb_concept> has </verb_concept><noun_concept> designator </noun_concept><keyword> with </keyword><keyword> assigned value </keyword><keyword> not </keyword> The RunwayDirection designator 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. Found RunwayDirection.designator with assigned value different from accepted patter. Backwards mapping to AIXM 4.5 not possible in EAD. RunwayDirection designator All Coding rule RunwayDirection designator format
AIXM-5.1_RULE-F3688 Error AIXM Model It is obligatory that each RadarSystem with assigned radarEquipment.RadarComponent.theRadarEquipment value has radarEquipment.RadarComponent.theRadarEquipment value resolved-into exactly one isComposedOf RadarEquipment specialisation PrecisionApproachRadar or SurveillanceRadar specialisation PrimarySurveillanceRadar or SecondarySurveillanceRadar <keyword> It is obligatory that each </keyword><noun_concept> RadarSystem </noun_concept><keyword> with assigned </keyword><noun_concept> radarEquipment.RadarComponent.theRadarEquipment </noun_concept><keyword> value </keyword><verb_concept> has </verb_concept><noun_concept> radarEquipment.RadarComponent.theRadarEquipment </noun_concept><keyword> value resolved-into exactly one </keyword><verb_concept> isComposedOf </verb_concept><noun_concept> RadarEquipment </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> PrecisionApproachRadar </noun_concept><keyword> or </keyword><noun_concept> SurveillanceRadar </noun_concept><verb_concept> specialisation </verb_concept><noun_concept> PrimarySurveillanceRadar </noun_concept><keyword> or </keyword><noun_concept> SecondarySurveillanceRadar </noun_concept> The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. The feature instance actually targeted by an association (through its role name value) shall exist and correspond to the feature type defined by the model. This rule has to be applied to all inheritance levels - in this case is the first level of inheritance. RadarSystem radarEquipment set of snapshots Minimal data rule Referential integrity towards RadarEquipment
AIXM-5.1_RULE-1C9468 Error AIXM 4.5 AIXM 4.5 It is prohibited that an Airspace has type equal-to 'CLASS' and Airspace has not assigned class.AirspaceLayerClass.classification value <keyword> It is prohibited that </keyword><keyword> an </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> 'CLASS' </name><keyword> and </keyword><noun_concept> Airspace </noun_concept><verb_concept> has </verb_concept><keyword> not </keyword><keyword> assigned </keyword><noun_concept> class.AirspaceLayerClass.classification </noun_concept><keyword> value </keyword> Airspace of type 'CLASS' must have an assigned classification value. Found Airspace with type equal-to 'CLASS' and missing a value for its AirspaceLayerClass.classification property. Backwards mapping to AIXM 4.5 in EAD is impossible. Airspace type baseline outside delta, snapshot, set of snapshots Minimal data rule Airspace type CLASS must have classification
AIXM-5.1_RULE-19F870 Error AIXM 4.5 AIXM 4.5 It is prohibited that Airspace with more than one geometryComponent has not assigned geometryComponent.AirspaceGeometryComponent.operation value <keyword> It is prohibited that </keyword><noun_concept> Airspace </noun_concept><keyword> with more than one </keyword><noun_concept> geometryComponent </noun_concept><verb_concept> has </verb_concept><keyword> not assigned </keyword><noun_concept> geometryComponent.AirspaceGeometryComponent.operation </noun_concept><keyword> value </keyword> If Airspace has more than one geometryComponent, then the operation for each AirspaceGeometryComponent must be defined Found Airspace with more than one component and undefined operation for AirspaceGeometryComponent Airspace All Data consistency rule Airspace aggregation - operation mandatory
AIXM-5.1_RULE-104028 Warning ICAO Annex 10 3.3.2.1 It is prohibited that a VOR has assigned frequency.uom value not equal-to 'MHZ' <keyword> It is prohibited that </keyword><keyword> a </keyword><noun_concept> VOR </noun_concept><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> frequency.uom </noun_concept><keyword> value </keyword><keyword> not </keyword><keyword> equal-to </keyword><name> 'MHZ' </name> According to Point 3.3.2.1 in ICAO Annex 10, the VOR frequency shall be between 108.0 MHZ and 117.95 MHZ, both values included. The frequency is always communicated in MHZ. Found VOR frequency not expressed in MHZ VOR frequency ANY;NO_REF Standard (ICAO, industry, etc.) VOR Frequency in MHZ
AIXM-5.1_RULE-19F0A0 NM CACD Each Airspace with type equal-to ('CTA','UTA', 'OCA') shall have exactly one geometryComponent.AirspaceGeometryComponent.operation equal-to 'BASE' <keyword> Each </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('CTA','UTA', 'OCA') </name><keyword> shall </keyword><verb_concept> have </verb_concept><keyword> exactly one </keyword><noun_concept> geometryComponent.AirspaceGeometryComponent.operation </noun_concept><keyword> equal-to </keyword><name> 'BASE' </name> The geometry of operational airspace of type CTA, UTA and OCA shall be encoded as an aggregation of the corresponding operational SECTORS. Found Airspace of type CTA/UTA/OCA that is missing aggregation base (or that is not defined as aggregation) Airspace type baseline outside delta, snapshot, set of snapshots Data consistency rule CTA and similar areas shall be an aggregation of sectors - part 1
AIXM-5.1_RULE-E1578 Warning Digital NOTAM Event Specification RWY.CLS It is prohibited that a RunwayDirectionTimeSlice with assigned availability.ManoeuvringAreaAvailability.usage.ManoeuvringAreaUsage.type value not equal-to ('PERMIT', 'CONDITIONAL') belongsTo Event with scenario equal-to 'RWY.CLS' and with version equal-to '2.0' <keyword> It is prohibited that a </keyword><noun_concept> RunwayDirectionTimeSlice </noun_concept><keyword> with assigned </keyword><noun_concept> availability.ManoeuvringAreaAvailability.usage.ManoeuvringAreaUsage.type </noun_concept><keyword> value not equal-to </keyword><name> ('PERMIT', 'CONDITIONAL') </name><verb_concept> belongsTo </verb_concept><noun_concept> Event </noun_concept><keyword> with </keyword><noun_concept> scenario </noun_concept><keyword> equal-to </keyword><name> 'RWY.CLS' </name><noun_concept> version </noun_concept><keyword> equal-to </keyword><name> '2.0' </name> The ManoeuvringAreaUsage operation cannot have other value than PERMIT or CONDITIONAL The ManoeuvringAreaUsage operation cannot have other value than PERMIT or CONDITIONAL RunwayDirection operation All Standard (ICAO, industry, etc.) Event - RWY.CLS - may have excepted operations
AIXM-5.1_RULE-29FE0 Warning Digital NOTAM Event Specification Part 1, Character Set It is prohibited that an AIXMTimeSlice belongsTo Event with assigned textNOTAM value and has assigned annotation.Note.translatedNote.LinguisticNote.note value using a different character set from ('A','B','C','D','E','F','G','H','I','J','K','L','M','N','O','P','Q','R','S','T','U','V','W','X','Y','Z', 'a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z','0','1','2','3','4','5','6','7','8','9','-','?',':','(',')','.',',',"'",'=','/','+') <keyword> It is prohibited that an </keyword><noun_concept> AIXMTimeSlice </noun_concept><verb_concept> belongsTo </verb_concept><noun_concept> Event </noun_concept><keyword> with assigned </keyword><noun_concept> textNOTAM </noun_concept><keyword> value and </keyword><verb_concept> has </verb_concept><keyword> assigned </keyword><noun_concept> annotation.Note.translatedNote.LinguisticNote.note </noun_concept><keyword> value </keyword><name> ('A','B','C','D','E','F','G','H','I','J','K','L','M','N','O','P','Q','R','S','T','U','V','W','X','Y','Z', 'a','b','c','d','e','f','g','h','i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y','z','0','1','2','3','4','5','6','7','8','9','-','?',':','(',')','.',',',"'",'=','/','+') </name> Notes contained in TimeSlice(s) associated with a Digital NOTAM Event shall be limited to the character set indicated in the Digital NOTAM Event Specification, Part 1, section "Character Set" Notes contained in TimeSlice(s) associated with a Digital NOTAM Event shall be limited to the character set indicated in the Digital NOTAM Event Specification, Part 1, section "Character Set" Note isWrittenAs All Standard (ICAO, industry, etc.) Event - NOTAM character set limitation
AIXM-5.1_RULE-CB200 Warning ICAO Annex 11 Item 2.9.3.2 It is prohibited that an Airspace with type equal-to ('CTA', 'CTA_P', 'UTA', 'UTA_P', 'OCA', 'OCA_P') has geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume with lowerLimit.uom equal-to 'FT' and with lowerLimit lower-than 700.0 or lowerLimit equal-to 'GND' <keyword> It is prohibited that an </keyword><noun_concept> Airspace </noun_concept><keyword> with </keyword><noun_concept> type </noun_concept><keyword> equal-to </keyword><name> ('CTA', 'CTA_P', 'UTA', 'UTA_P', 'OCA', 'OCA_P') </name><verb_concept> has </verb_concept><noun_concept> geometryComponent.AirspaceGeometryComponent.theAirspaceVolume.AirspaceVolume </noun_concept><keyword> with </keyword><noun_concept> lowerLimit.uom </noun_concept><keyword> equal-to </keyword><name> 'FT' </name><keyword> and with </keyword><noun_concept> lowerLimit </noun_concept><keyword> lower-than </keyword><keyword> or </keyword><noun_concept> lowerLimit </noun_concept><keyword> equal-to </keyword><name> 'GND' </name> Airspace of type 'CTA', 'CTA_P', 'UTA', 'UTA_P', 'OCA' or 'OAC_P' should not have lower limit smaller than 200 M (700 FT). Note: the check cannot detect situations where the lowerLimit is specified with reference to MSL. However, the vertical reference can be ignored in the rule check because if the value it is lower than 200 m, the rule is anyhow broken. Airspace of type 'CTA', 'CTA_P', 'UTA', 'UTA_P', 'OCA' or 'OAC_P' should not have lower limit smaller than 200 M (700 FT). Note: the check cannot detect situations where the lowerLimit is specified with reference to MSL. However, the vertical reference can be ignored in the rule check because if the value it is lower than 200 m, the rule is anyhow broken. AirspaceVolume lowerLimit baseline outside delta, snapshot, set of snapshots Recommended practice Airspace CTA,UTA, etc. minimal lower limit in FT
AIXM-5.1_RULE-DCF28 Warning FAA FNS-NDS Tech Spec Scenario ID: 25 It is prohibited that an AirportHeliportTimeSlice with availability.AirportHeliportAvailability.operationalStatus equal-to 'CLOSED' and with assigned availability.AirportHeliportAvailability.usage value belongsTo Event with scenario equal-to '25' <keyword> It is prohibited that an </keyword><noun_concept> AirportHeliportTimeSlice </noun_concept><keyword> with </keyword><noun_concept> availability.AirportHeliportAvailability.operationalStatus </noun_concept><keyword> equal-to </keyword><name> 'CLOSED' </name><keyword> and with assigned </keyword><noun_concept> availability.AirportHeliportAvailability.usage </noun_concept><keyword> value </keyword><verb_concept> belongsTo </verb_concept><noun_concept> Event </noun_concept><keyword> with </keyword><noun_concept> scenario </noun_concept><keyword> equal-to </keyword><name> '25' </name> If operationalStatus is CLOSED (no restrictions or exceptions), then Usage should not be included in the Message. If operationalStatus is CLOSED (no restrictions or exceptions), then Usage should not be included in the Message. AirportHeliport All Standard (ICAO, industry, etc.) Event (FAA) - 25 - forbidden usage for CLOSED status