Page tree
Skip to end of metadata
Go to start of metadata

Note

This page contains a temporary copy of the AIXM Business Rules version 0.8, with the objective to facilitate collecting eventual comments/suggestions on these rules. As much as possible, please use the inline comment, by selecting the UID of the rule.


UID

Comments

AIXM Class

AIXM Attributes

AIXM Associations

AIXM-5.1_RULE-1A5E00

Only the coordinate reference system listed in Appendix 1 of the GML Guidelines for Aviation Data shall be used.

*

*

 

AIXM-5.1_RULE-1C908

EAD does not accept on upload any other type of TimeSlice than BASELINE

*

interpretation

 

AIXM-5.1_RULE-1B05F8

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.

*

srsName

 

AIXM-5.1_RULE-BFA68

The use of dynamic type definition (with the xsi:type attribute) is forbidden.

*

xsi:type

 

AIXM-5.1_RULE-C2561

For each instance of a feature/object, some properties are mandatory for the data to make sense

AerialRefuelling

designatorNumber

 

AIXM-5.1_RULE-C2562

For each instance of a feature/object, some properties are mandatory for the data to make sense

AerialRefuelling

designatorPrefix

 

AIXM-5.1_RULE-1AB009

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

 

AIXM-5.1_RULE-1AB00B

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

 

AIXM-5.1_RULE-1AB00A

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

 

AIXM-5.1_RULE-1A2F22

The propertyName of any Note should refer to an existing property.

AerialRefuelling

 

 

AIXM-5.1_RULE-5341C

AerialRefuelling is not supported in EAD and cannot be upload by the data providers.

AerialRefuelling

 

 

AIXM-5.1_RULE-D8CC3

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AerialRefuellingAnchor

legLength

 

AIXM-5.1_RULE-D8CC2

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AerialRefuellingAnchor

legSeparation

 

AIXM-5.1_RULE-D8CC4

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AerialRefuellingAnchor

refuellingBaseLevel

 

AIXM-5.1_RULE-1AE2D8

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

AerialRefuellingAnchor

refuellingBaseLevel

 

AIXM-5.1_RULE-D8CC1

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AerialRefuellingAnchor

speedLimit

 

AIXM-5.1_RULE-1AC391

The propertyName of any Note should refer to an existing property.

AerialRefuellingAnchor

 

 

AIXM-5.1_RULE-1AC392

The propertyName of any Note should refer to an existing property.

AerialRefuellingPoint

 

 

AIXM-5.1_RULE-1AC393

The propertyName of any Note should refer to an existing property.

AerialRefuellingTrack

 

 

AIXM-5.1_RULE-1A8512

The 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

 

AIXM-5.1_RULE-1A33B6

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AeronauticalGroundLight

location.ElevatedPoint.pos

 

AIXM-5.1_RULE-1A339B

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AeronauticalGroundLight

name

 

AIXM-5.1_RULE-1A8511

The 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

 

AIXM-5.1_RULE-1A3372

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AeronauticalGroundLight

type

 

AIXM-5.1_RULE-1A2F23

The propertyName of any Note should refer to an existing property.

AeronauticalGroundLight

 

 

AIXM-5.1_RULE-D8CC7

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AircraftCharacteristic

speed

 

AIXM-5.1_RULE-D8CC6

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AircraftCharacteristic

weight

 

AIXM-5.1_RULE-D8CC5

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AircraftCharacteristic

wingSpan

 

AIXM-5.1_RULE-1A2F24

The propertyName of any Note should refer to an existing property.

AircraftCharacteristic

 

 

AIXM-5.1_RULE-1A338C

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AircraftGroundService

airportHeliport

 

AIXM-5.1_RULE-1A52AF

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1028C5

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1028BD

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F25

The propertyName of any Note should refer to an existing property.

AircraftGroundService

 

 

AIXM-5.1_RULE-1A330D

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AircraftStand

apronLocation

 

AIXM-5.1_RULE-1A8513

The 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

 

AIXM-5.1_RULE-1DC94

AircraftStand. contaminant is not supported in EAD and cannot be upload by the data providers

AircraftStand

contaminant

 

AIXM-5.1_RULE-1A3320

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AircraftStand

designator

 

AIXM-5.1_RULE-5C493

Latitude and longitude of AircraftStand location shall be published with at least 6 decimals resolution

AircraftStand

ElevatedPoint

 

AIXM-5.1_RULE-E680

The horizontal accuracy of the AircraftStand location shall be better than 0.5 M

AircraftStand

location

 

AIXM-5.1_RULE-E683

The horizontal accuracy of the AircraftStand location shall be better than 1.5 FT

AircraftStand

location

 

AIXM-5.1_RULE-1A333F

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AircraftStand

location.ElevatedPoint.pos

 

AIXM-5.1_RULE-1A33CE

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AircraftStand

type

 

AIXM-5.1_RULE-1A2F26

The propertyName of any Note should refer to an existing property.

AircraftStand

 

 

AIXM-5.1_RULE-1AC394

The propertyName of any Note should refer to an existing property.

AircraftStandContamination

 

 

AIXM-5.1_RULE-1A33DC

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportClearanceService

airportHeliport

 

AIXM-5.1_RULE-1A52B0

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1028C8

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1028C0

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F27

The propertyName of any Note should refer to an existing property.

AirportClearanceService

 

 

AIXM-5.1_RULE-1B5801

AirportHeliport type cannot change between "aerodrome" and "heliport" in EAD

AirportHeliport

type

 

AIXM-5.1_RULE-1B5802

AirportHeliport type cannot change between "aerodrome" and "heliport" in EAD

AirportHeliport

type

 

AIXM-5.1_RULE-DAC00

If the event scenario is "aerodrome closure" (id=25), there should be a single availability

AirportHeliport

 

 

AIXM-5.1_RULE-DC758

If the event scenario is "aerodrome closure" (id=25), then operationalStatus shall be CLOSED or LIMITED

AirportHeliport

 

 

AIXM-5.1_RULE-DCF28

If operationalStatus is CLOSED (no restrictions or exceptions), then Usage should not be included in the Message.

AirportHeliport

 

 

AIXM-5.1_RULE-1AB00C

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

 

AIXM-5.1_RULE-E679

The horizontal accuracy of the AirportHeliport ARP shall be better than 30 M

AirportHeliport

ARP

 

AIXM-5.1_RULE-E67F

The horizontal accuracy of the AirportHeliport ARP shall be better than 100 FT

AirportHeliport

ARP

 

AIXM-5.1_RULE-D4A6D

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

 

AIXM-5.1_RULE-D4A66

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

 

AIXM-5.1_RULE-D4A6F

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

 

AIXM-5.1_RULE-D4A5E

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

 

AIXM-5.1_RULE-D4A59

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

 

AIXM-5.1_RULE-1A33A3

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliport

ARP.ElevatedPoint.pos

 

AIXM-5.1_RULE-D6D81

The accuracy of the AirportHeliport ARP.ElevatedPoint.verticalAccuracy shall be not less than 0.5

AirportHeliport

ARP.ElevatedPoint.verticalAccuracy

 

AIXM-5.1_RULE-D4A60

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

 

AIXM-5.1_RULE-D4A73

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

 

AIXM-5.1_RULE-D4A70

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

 

AIXM-5.1_RULE-1DC93

AirportHeliport.contaminant is not supported in EAD and cannot be upload by the data providers

AirportHeliport

contaminant

 

AIXM-5.1_RULE-1A3367

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliport

designator

 

AIXM-5.1_RULE-DA04B

There cannot exists two different AirportHeliport that have identical values for designator

AirportHeliport

designator

 

AIXM-5.1_RULE-5C492

Latitude and longitude of AirportHeliport ARP shall be published with at least 4 decimals resolution

AirportHeliport

ElevatedPoint

 

AIXM-5.1_RULE-D8CC8

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirportHeliport

fieldElevation

 

AIXM-5.1_RULE-F07AF

AirportHeliport cannot use coded values as fieldElevation limits

AirportHeliport

fieldElevation

 

AIXM-5.1_RULE-1B0DC9

The unit of measurement for AirportHeliport.fieldElevation cannot take the values ('FL', 'SM'), because they cannot be mapped to AIXM 4.5

AirportHeliport

fieldElevation

 

AIXM-5.1_RULE-D4A5F

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

 

AIXM-5.1_RULE-C2D3A

The values OTHER and OTHER:.. in AirportHeliport.fieldElevation.uom are not supported for mapping to 4.5

AirportHeliport

fieldElevation.uom

 

AIXM-5.1_RULE-D8CC9

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirportHeliport

fieldElevationAccuracy

 

AIXM-5.1_RULE-D4A69

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

 

AIXM-5.1_RULE-46119

WGS-84 geoid undulation at AirportHeliport ARP shall be published with 1m or 1ft resolution

AirportHeliport

geoidUndulation

 

AIXM-5.1_RULE-D8CCD

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirportHeliport

lowestTemperature

 

AIXM-5.1_RULE-1A333C

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliport

name

 

AIXM-5.1_RULE-D8CCA

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirportHeliport

referenceTemperature

 

AIXM-5.1_RULE-1A33C5

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliport

responsibleOrganisation

 

AIXM-5.1_RULE-1A8514

The 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

 

AIXM-5.1_RULE-D8CCB

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirportHeliport

transitionAltitude

 

AIXM-5.1_RULE-D8CCC

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirportHeliport

transitionLevel

 

AIXM-5.1_RULE-1A3322

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliport

type

 

AIXM-5.1_RULE-1A2FD7

The propertyName of any Note should refer to an existing property.

AirportHeliport

 

 

AIXM-5.1_RULE-1A5285

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A3309

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliportAvailability

usage

 

AIXM-5.1_RULE-1A2F29

The propertyName of any Note should refer to an existing property.

AirportHeliportAvailability

 

 

AIXM-5.1_RULE-1A336D

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliportCollocation

dependentAirport

 

AIXM-5.1_RULE-1A8517

The 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

 

AIXM-5.1_RULE-1A3394

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliportCollocation

hostAirport

 

AIXM-5.1_RULE-1A8516

The 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

 

AIXM-5.1_RULE-1A3379

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliportCollocation

type

 

AIXM-5.1_RULE-1A2F2A

The propertyName of any Note should refer to an existing property.

AirportHeliportCollocation

 

 

AIXM-5.1_RULE-1AC395

The propertyName of any Note should refer to an existing property.

AirportHeliportContamination

 

 

AIXM-5.1_RULE-D8CCF

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirportHeliportProtectionArea

length

 

AIXM-5.1_RULE-D8CCE

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirportHeliportProtectionArea

width

 

AIXM-5.1_RULE-1A5286

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A33E4

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportHeliportResponsibilityOrganisation

theOrganisationAuthority

 

AIXM-5.1_RULE-1A2F2B

The propertyName of any Note should refer to an existing property.

AirportHeliportResponsibilityOrganisation

 

 

AIXM-5.1_RULE-1A2F2C

The propertyName of any Note should refer to an existing property.

AirportHeliportUsage

 

 

AIXM-5.1_RULE-1A8518

The 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

 

AIXM-5.1_RULE-1A2F2D

The propertyName of any Note should refer to an existing property.

AirportHotSpot

 

 

AIXM-5.1_RULE-FA00

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1AC396

The propertyName of any Note should refer to an existing property.

AirportProtectionAreaMarking

 

 

AIXM-5.1_RULE-1A334E

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirportSuppliesService

airportHeliport

 

AIXM-5.1_RULE-1A52AE

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1028C7

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1028BF

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F2E

The propertyName of any Note should refer to an existing property.

AirportSuppliesService

 

 

AIXM-5.1_RULE-4269

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.

Airspace

designator

 

AIXM-5.1_RULE-426A

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.

Airspace

designator

 

AIXM-5.1_RULE-1B11B0

If the Airspace designatorICAO is "YES", then the designator must be composed of exactly 4 letters

Airspace

designatorICAO

 

AIXM-5.1_RULE-57E41

The horizontal accuracy of CTA boundary points shall be better than 300.0 FT

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E42

The horizontal accuracy of CTA boundary points shall be better than 100.0 M

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E43

The horizontal accuracy of CTA_P boundary points shall be better than 300.0 FT

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E44

The horizontal accuracy of CTA_P boundary points shall be better than 100.0 M

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E45

The horizontal accuracy of CTR boundary points shall be better than 300.0 FT

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E46

The horizontal accuracy of CTR boundary points shall be better than 100.0 M

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E47

The horizontal accuracy of CTR_P boundary points shall be better than 300.0 FT

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E48

The horizontal accuracy of CTR_P boundary points shall be better than 100.0 M

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E49

The horizontal accuracy of D boundary points shall be better than 2.0 KM

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E4A

The horizontal accuracy of FIR boundary points shall be better than 2.0 KM

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E4B

The horizontal accuracy of FIR_P boundary points shall be better than 2.0 KM

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E4C

The horizontal accuracy of P boundary points shall be better than 2.0 KM

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E4D

The horizontal accuracy of R boundary points shall be better than 2.0 KM

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E4E

The horizontal accuracy of UIR boundary points shall be better than 2.0 KM

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-57E4F

The horizontal accuracy of UIR_P boundary points shall be better than 2.0 KM

Airspace

horizontalAccuracy

 

AIXM-5.1_RULE-1B1599

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.

Airspace

operationSequence

 

AIXM-5.1_RULE-1B159A

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.

Airspace

operationSequence

 

AIXM-5.1_RULE-BA090

The geometry of operational airspace of type CTA, UTA and OCA shall be encoded as an aggregation of the corresponding operational SECTORS.

Airspace

type

 

AIXM-5.1_RULE-16760

The Airspace type cannot change in EAD

Airspace

type

 

AIXM-5.1_RULE-1AFE28

The geometry of operational airspace of type CTA, UTA and OCA shall be encoded as an aggregation of the corresponding operational SECTORS.

Airspace

type

 

AIXM-5.1_RULE-19F0A0

The geometry of operational airspace of type CTA, UTA and OCA shall be encoded as an aggregation of the corresponding operational SECTORS.

Airspace

type

 

AIXM-5.1_RULE-CA648

If Airspace type has the value 'FIR' or 'UIR', then designatorICAO shall be have the value 'YES'

Airspace

type, designatorICAO

 

AIXM-5.1_RULE-24220

The lower/upper separation value may be specified only for Airspace of type 'FIR'

Airspace

upperLowerSeparation

 

AIXM-5.1_RULE-19FC58

Each AirspaceVolume associated with the same Airspace must have a unique operationSequence number

Airspace

 

 

AIXM-5.1_RULE-CB9D0

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"

Airspace

 

 

AIXM-5.1_RULE-15C250

For an Airsapace defined as the aggregation of several AirspaceGeometryComponents, the result of the aggregation shall not be en empty geometry

Airspace

 

 

AIXM-5.1_RULE-19F488

If Airspace has more than one geometryComponent, then the operation seqeunce for each AirspaceGeometryComponent must be defined

Airspace

 

 

AIXM-5.1_RULE-D7168

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.

Airspace

 

 

AIXM-5.1_RULE-9FAB0

An Airspace cannot be used twice for the definition (by aggregation) of the geometry of another Airspace

Airspace

 

 

AIXM-5.1_RULE-19F870

If Airspace has more than one geometryComponent, then the operation for each AirspaceGeometryComponent must be defined

Airspace

 

 

AIXM-5.1_RULE-1A33A9

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Airspace

designator

 

AIXM-5.1_RULE-1A33E0

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Airspace

geometryComponent

 

AIXM-5.1_RULE-1A8519

The 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

 

AIXM-5.1_RULE-1A3336

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Airspace

type

 

AIXM-5.1_RULE-135153

Airspace with type equal ('NAS', 'FIR', 'UIR') cannot be updated by the EAD data providers.

Airspace

type

 

AIXM-5.1_RULE-DAC1

There cannot exists two different Airspace that have identical values for type and also for designator

Airspace

type designator

 

AIXM-5.1_RULE-D8CD0

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

Airspace

upperLowerSeparation

 

AIXM-5.1_RULE-1A2F2F

The propertyName of any Note should refer to an existing property.

Airspace

 

 

AIXM-5.1_RULE-1A5287

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A85AC

The 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

 

AIXM-5.1_RULE-1A2F30

The propertyName of any Note should refer to an existing property.

AirspaceActivation

 

 

AIXM-5.1_RULE-1AB00E

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

 

AIXM-5.1_RULE-1A3365

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirspaceBorderCrossing

enteredAirspace

 

AIXM-5.1_RULE-1AB00F

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

 

AIXM-5.1_RULE-1A337A

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirspaceBorderCrossing

exitedAirspace

 

AIXM-5.1_RULE-1AC397

The propertyName of any Note should refer to an existing property.

AirspaceBorderCrossing

 

 

AIXM-5.1_RULE-5340D

AirspaceBorderCrossing is not supported in EAD and cannot be upload by the data providers.

AirspaceBorderCrossing

 

 

AIXM-5.1_RULE-1A5A18

An AirspaceGeometryComponent that is used as BASE for an aggregation shall have operationSequence equal to 1

AirspaceGeometryComponent

operation

 

AIXM-5.1_RULE-26D18

If Airspace has more than one geometryComponent, then there must exist exactly one AirspacegeometryComponent with operation = 'BASE'

AirspaceGeometryComponent

operation

 

AIXM-5.1_RULE-C2D32

The values OTHER and OTHER:.. in AirspaceGeometryComponent.operation are not supported for mapping to 4.5

AirspaceGeometryComponent

operation

 

AIXM-5.1_RULE-1A33E1

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirspaceGeometryComponent

theAirspaceVolume

 

AIXM-5.1_RULE-1A2F31

The propertyName of any Note should refer to an existing property.

AirspaceGeometryComponent

 

 

AIXM-5.1_RULE-1A851A

The 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

 

AIXM-5.1_RULE-1A4E7B

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

 

AIXM-5.1_RULE-D8CD2

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirspaceLayer

lowerLimit

 

AIXM-5.1_RULE-1A4A79

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

AirspaceLayer

lowerLimit

 

AIXM-5.1_RULE-1A13CA

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

AirspaceLayer

lowerLimit

 

AIXM-5.1_RULE-697A

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

Airspacelayer

lowerLimit upperLimit

 

AIXM-5.1_RULE-1A4E64

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

 

AIXM-5.1_RULE-D8CD1

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirspaceLayer

upperLimit

 

AIXM-5.1_RULE-1A4A7B

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

AirspaceLayer

upperLimit

 

AIXM-5.1_RULE-1A13C9

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

AirspaceLayer

upperLimit

 

AIXM-5.1_RULE-1A2F32

The propertyName of any Note should refer to an existing property.

AirspaceLayer

 

 

AIXM-5.1_RULE-1A5288

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F33

The propertyName of any Note should refer to an existing property.

AirspaceLayerClass

 

 

AIXM-5.1_RULE-1AA838

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

 

AIXM-5.1_RULE-CB200

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

 

AIXM-5.1_RULE-1D4C3

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).

AirspaceVolume

lowerLimit

 

AIXM-5.1_RULE-CA260

An AirspaceVolume for which the lower and upper limit are not specified, must be defined by aggregation (full geometry).

AirspaceVolume

lowerLimit, upperLimit

 

AIXM-5.1_RULE-203A0

AirspaceVolume with assigned maximumLimit shall have maximumLimitReference equal to 'SFC' (distance measured from GND).

AirspaceVolume

maximumLimit

 

AIXM-5.1_RULE-1D4C4

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).

AirspaceVolume

maximumLimit

 

AIXM-5.1_RULE-1E84C

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 the value of the upper limit (or maximum limit).

AirspaceVolume

maximumLimit lowerLimit

 

AIXM-5.1_RULE-1E84B

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 the value of the upper limit (or maximum limit).

AirspaceVolume

maximumLimit minimumLimit

 

AIXM-5.1_RULE-21340

AirspaceVolume with assigned minimumLimit shall have minimumLimitreference equal to 'SFC' (height above ground)

AirspaceVolume

minimumLimit

 

AIXM-5.1_RULE-1D4C2

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).

AirspaceVolume

minimumLimit

 

AIXM-5.1_RULE-D5611

Longitude and Latitude of ('FIR','UIR','FIR-P','UIR-P') boundary points shall be published with at least 2 decimals resolution.

AirspaceVolume

Surface

 

AIXM-5.1_RULE-D5612

Longitude and Latitude of ('CTA','CTA-P','CTR','CTR-P') boundary points shall be published with at least 4 decimals resolution.

AirspaceVolume

Surface

 

AIXM-5.1_RULE-D5613

Longitude and Latitude of ('P','R','D') boundary points shall be published with at least 2 decimals resolution.

AirspaceVolume

Surface

 

AIXM-5.1_RULE-BBFD0

The geometry of operational airspace of type CTA, UTA and OCA shall be encoded as an aggregation of the corresponding operational SECTORS.

AirspaceVolume

type

 

AIXM-5.1_RULE-1D4C1

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).

AirspaceVolume

upperLimit

 

AIXM-5.1_RULE-1E84A

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 the value of the upper limit (or maximum limit).

AirspaceVolume

upperLimit lowerLimit

 

AIXM-5.1_RULE-1E849

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 the value of the upper limit (or maximum limit).

AirspaceVolume

upperLimit minimumLimit

 

AIXM-5.1_RULE-1A0810

If the AirspaceVolume does not have centreline (is not a corridor), then width shall not be specified

AirspaceVolume

width

 

AIXM-5.1_RULE-1AA069

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

 

 

AIXM-5.1_RULE-1AA06A

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

 

 

AIXM-5.1_RULE-1AA06B

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

 

 

AIXM-5.1_RULE-1A0BF9

An AirspaceVolume cannot have in the same time horizontalProjection, centreline and contributorAirspace

AirspaceVolume

 

 

AIXM-5.1_RULE-1A0BFA

An AirspaceVolume cannot have in the same time horizontalProjection, centreline and contributorAirspace

AirspaceVolume

 

 

AIXM-5.1_RULE-1A0BFB

An AirspaceVolume cannot have in the same time horizontalProjection, centreline and contributorAirspace

AirspaceVolume

 

 

AIXM-5.1_RULE-1AC778

Surface curveMember references shall resolve into exactly one GeoBorder

AirspaceVolume

 

 

AIXM-5.1_RULE-12B510

An AirspaceVolume that is not defined with a contributorAirspace must have either horizontalProjection or centreline

AirspaceVolume

 

 

AIXM-5.1_RULE-4BED8

Surface curveMember can refer to GeoBorder only when used for AirspaceVolume

AirspaceVolume

 

 

AIXM-5.1_RULE-1A85B6

The 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

 

AIXM-5.1_RULE-1A4E61

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

 

AIXM-5.1_RULE-D8CD5

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirspaceVolume

lowerLimit

 

AIXM-5.1_RULE-1A4A7E

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

AirspaceVolume

lowerLimit

 

AIXM-5.1_RULE-1A13CD

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

AirspaceVolume

lowerLimit

 

AIXM-5.1_RULE-F07AD

AirspaceVolume cannot use coded values as lowerLimit limits

AirspaceVolume

lowerLimit

 

AIXM-5.1_RULE-C2D3C

The values OTHER and OTHER:.. in AirspaceVolume. lowerLimit.uom are not supported for mapping to 4.5

AirspaceVolume

lowerLimit.uom

 

AIXM-5.1_RULE-1A4E76

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

 

AIXM-5.1_RULE-D8CD4

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirspaceVolume

maximumLimit

 

AIXM-5.1_RULE-1A4A7D

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

AirspaceVolume

maximumLimit

 

AIXM-5.1_RULE-1A13CC

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

AirspaceVolume

maximumLimit

 

AIXM-5.1_RULE-F07B0

AirspaceVolume cannot use coded values as maximumLimit limits

AirspaceVolume

maximumLimit

 

AIXM-5.1_RULE-C2D37

The values OTHER and OTHER:.. in AirspaceVolume. maximumLimit.uom are not supported for mapping to 4.5

AirspaceVolume

maximumLimit.uom

 

AIXM-5.1_RULE-1A4E73

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

 

AIXM-5.1_RULE-D8CD6

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirspaceVolume

minimumLimit

 

AIXM-5.1_RULE-1A4A7F

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

AirspaceVolume

minimumLimit

 

AIXM-5.1_RULE-1A13CE

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

AirspaceVolume

minimumLimit

 

AIXM-5.1_RULE-F07B1

AirspaceVolume cannot use coded values as minimumLimit limits

AirspaceVolume

minimumLimit

 

AIXM-5.1_RULE-C2D36

The values OTHER and OTHER:.. in AirspaceVolume. minimumLimit.uom are not supported for mapping to 4.5

AirspaceVolume

minimumLimit.uom

 

AIXM-5.1_RULE-1A4E7A

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

 

AIXM-5.1_RULE-D8CD3

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirspaceVolume

upperLimit

 

AIXM-5.1_RULE-1A4A7C

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

AirspaceVolume

upperLimit

 

AIXM-5.1_RULE-1A13CB

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

AirspaceVolume

upperLimit

 

AIXM-5.1_RULE-F07AE

AirspaceVolume cannot use coded values as upperLimit limits

AirspaceVolume

upperLimit

 

AIXM-5.1_RULE-C2D3B

The values OTHER and OTHER:.. in AirspaceVolume.upperLimit.uom are not supported for mapping to 4.5

AirspaceVolume

upperLimit.uom

 

AIXM-5.1_RULE-D8CD7

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AirspaceVolume

width

 

AIXM-5.1_RULE-1B0DCD

The unit of measurement for AirspaceVolume.width cannot take the values ('MI', 'CM'), because they cannot be mapped to AIXM 4.5

AirspaceVolume

width

 

AIXM-5.1_RULE-1A0428

If AirspaceVolume has corridor shape non-zero width must be assigned

AirspaceVolume

width

 

AIXM-5.1_RULE-C2D40

The values OTHER and OTHER:.. in AirspaceVolume.width.uom are not supported for mapping to 4.5

AirspaceVolume

width.uom

 

AIXM-5.1_RULE-1A2F34

The propertyName of any Note should refer to an existing property.

AirspaceVolume

 

 

AIXM-5.1_RULE-1A0FE0

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

AirspaceVolume

 

 

AIXM-5.1_RULE-1B4478

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

AirspaceVolume

 

 

AIXM-5.1_RULE-1A33E3

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirspaceVolumeDependency

dependency

 

AIXM-5.1_RULE-1A33E2

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AirspaceVolumeDependency

theAirspace

 

AIXM-5.1_RULE-1A2F35

The propertyName of any Note should refer to an existing property.

AirspaceVolumeDependency

 

 

AIXM-5.1_RULE-F32A0

The feature instance actually targeted by an association (through its role name value) shall exist and 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.

AirTrafficControlService

clientProcedure

 

AIXM-5.1_RULE-1AB030

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

 

AIXM-5.1_RULE-1AB02F

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

 

AIXM-5.1_RULE-1A85A0

The 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

 

AIXM-5.1_RULE-1A85A2

The 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

 

AIXM-5.1_RULE-1A85A3

The 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

 

AIXM-5.1_RULE-1028C3

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1028BA

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F36

The propertyName of any Note should refer to an existing property.

AirTrafficControlService

 

 

AIXM-5.1_RULE-1A851B

The 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

 

AIXM-5.1_RULE-1A524E

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A524B

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F37

The propertyName of any Note should refer to an existing property.

AirTrafficManagementService

 

 

AIXM-5.1_RULE-1AB010

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

AirTrafficManagementServices

clientAerialRefuelling

 

AIXM-5.1_RULE-1AC398

The propertyName of any Note should refer to an existing property.

AltimeterSource

 

 

AIXM-5.1_RULE-53423

AltimeterSource is not supported in EAD and cannot be upload by the data providers.

AltimeterSource

 

 

AIXM-5.1_RULE-1AB3F8

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1AC399

The propertyName of any Note should refer to an existing property.

AltimeterSourceStatus

 

 

AIXM-5.1_RULE-D8CD8

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AltitudeAdjustment

altitudeAdjustment

 

AIXM-5.1_RULE-1A2F38

The propertyName of any Note should refer to an existing property.

AltitudeAdjustment

 

 

AIXM-5.1_RULE-1A33B9

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AngleIndication

angle

 

AIXM-5.1_RULE-1A851C

The 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

 

AIXM-5.1_RULE-D8CD9

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

AngleIndication

minimumReceptionAltitude

 

AIXM-5.1_RULE-1A851D

The 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

 

AIXM-5.1_RULE-1A851E

The 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

 

AIXM-5.1_RULE-1A2F39

The propertyName of any Note should refer to an existing property.

AngleIndication

 

 

AIXM-5.1_RULE-1A33E7

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AngleUse

theAngleIndication

 

AIXM-5.1_RULE-1A2F3A

The propertyName of any Note should refer to an existing property.

AngleUse

 

 

AIXM-5.1_RULE-1A4E75

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

 

AIXM-5.1_RULE-D8CDA

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ApproachAltitudeTable

altitude

 

AIXM-5.1_RULE-1A4A80

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

ApproachAltitudeTable

altitude

 

AIXM-5.1_RULE-1A13CF

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

ApproachAltitudeTable

altitude

 

AIXM-5.1_RULE-1A2F3B

The propertyName of any Note should refer to an existing property.

ApproachAltitudeTable

 

 

AIXM-5.1_RULE-1AB011

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

 

AIXM-5.1_RULE-1A2F3C

The propertyName of any Note should refer to an existing property.

ApproachCondition

 

 

AIXM-5.1_RULE-D8CDC

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ApproachDistanceTable

distance

 

AIXM-5.1_RULE-D8CDB

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ApproachDistanceTable

valueHAT

 

AIXM-5.1_RULE-1A2F3D

The propertyName of any Note should refer to an existing property.

ApproachDistanceTable

 

 

AIXM-5.1_RULE-D8CDD

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ApproachLightingSystem

length

 

AIXM-5.1_RULE-1A33CC

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

ApproachLightingSystem

servedRunwayDirection

 

AIXM-5.1_RULE-1A851F

The 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

 

AIXM-5.1_RULE-1A333D

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

ApproachLightingSystem

type

 

AIXM-5.1_RULE-1A2F3E

The propertyName of any Note should refer to an existing property.

ApproachLightingSystem

 

 

AIXM-5.1_RULE-D8CDF

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ApproachTimingTable

speed

 

AIXM-5.1_RULE-D8CDE

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ApproachTimingTable

time

 

AIXM-5.1_RULE-1A2F3F

The propertyName of any Note should refer to an existing property.

ApproachTimingTable

 

 

AIXM-5.1_RULE-1A33C2

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Apron

associatedAirportHeliport

 

AIXM-5.1_RULE-1A8520

The 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

 

AIXM-5.1_RULE-1DC95

Apron.contaminant is not supported in EAD and cannot be upload by the data providers

Apron

contaminant

 

AIXM-5.1_RULE-1A3323

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Apron

name

 

AIXM-5.1_RULE-1A3346

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Apron

surfaceProperties

 

AIXM-5.1_RULE-1A2F40

The propertyName of any Note should refer to an existing property.

Apron

 

 

AIXM-5.1_RULE-1A528A

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F41

The propertyName of any Note should refer to an existing property.

ApronAreaAvailability

 

 

AIXM-5.1_RULE-1A2F42

The propertyName of any Note should refer to an existing property.

ApronAreaUsage

 

 

AIXM-5.1_RULE-1AC39A

The propertyName of any Note should refer to an existing property.

ApronContamination

 

 

AIXM-5.1_RULE-5B108

Latitude and longitude of apron boundaries shall be published with 1/10 sec resolution

ApronElement

ElevatedSurface

 

AIXM-5.1_RULE-1A8522

The 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

 

AIXM-5.1_RULE-DE699

The accuracy of the ApronElement extent shall be better than 1.0 M

ApronElement

ElevatedSurface extent

 

AIXM-5.1_RULE-D8CE0

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ApronElement

length

 

AIXM-5.1_RULE-1A8521

The 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

 

AIXM-5.1_RULE-BB420

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-D8CE1

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ApronElement

width

 

AIXM-5.1_RULE-1A2F43

The propertyName of any Note should refer to an existing property.

ApronElement

 

 

AIXM-5.1_RULE-1A3315

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

ApronLightSystem

lightedApron

 

AIXM-5.1_RULE-1A85AA

The 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

 

AIXM-5.1_RULE-1A2F44

The propertyName of any Note should refer to an existing property.

ApronLightSystem

 

 

AIXM-5.1_RULE-1AB012

The 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

 

AIXM-5.1_RULE-1AC39B

The propertyName of any Note should refer to an existing property.

ApronMarking

 

 

AIXM-5.1_RULE-26549

The symbol "deg" shall be used for the unit of measurement of endAngle

ArcByCenterPoint

endAngle

 

AIXM-5.1_RULE-2654A

The symbol "deg" shall be used for the unit of measurement of startAngle

ArcByCenterPoint

startAngle

 

AIXM-5.1_RULE-2B36A

UCUM values shall be used for the unit of measurement gml:radius property of ArcByCenterPoint

ArcByCenterPoint

gml:radius

 

AIXM-5.1_RULE-D8CE2

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ArrestingGear

length

 

AIXM-5.1_RULE-D8CE4

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ArrestingGear

location

 

AIXM-5.1_RULE-1A8523

The 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

 

AIXM-5.1_RULE-D8CE3

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ArrestingGear

width

 

AIXM-5.1_RULE-1A2F45

The propertyName of any Note should refer to an existing property.

ArrestingGear

 

 

AIXM-5.1_RULE-1A4E7E

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

 

AIXM-5.1_RULE-1A4A99

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

ArrivalFeederLeg

altitudeOverrideATC

 

AIXM-5.1_RULE-1A13E4

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

ArrivalFeederLeg

altitudeOverrideATC

 

AIXM-5.1_RULE-1028DC

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-BB804

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1028E1

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1028D7

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A4E7D

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

 

AIXM-5.1_RULE-1A4A98

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

ArrivalFeederLeg

lowerLimitAltitude

 

AIXM-5.1_RULE-1A13E5

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

ArrivalFeederLeg

lowerLimitAltitude

 

AIXM-5.1_RULE-1A4E7C

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

 

AIXM-5.1_RULE-1A4A97

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

ArrivalFeederLeg

upperLimitAltitude

 

AIXM-5.1_RULE-1A13E6

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

ArrivalFeederLeg

upperLimitAltitude

 

AIXM-5.1_RULE-1A2F46

The propertyName of any Note should refer to an existing property.

ArrivalFeederLeg

 

 

AIXM-5.1_RULE-1A4E8D

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

 

AIXM-5.1_RULE-1A4AA8

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

ArrivalLeg

altitudeOverrideATC

 

AIXM-5.1_RULE-1A13E1

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

ArrivalLeg

altitudeOverrideATC

 

AIXM-5.1_RULE-1A5262

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-BB038

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A5264

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A5260

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A4E8C

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

 

AIXM-5.1_RULE-1A4AA7

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

ArrivalLeg

lowerLimitAltitude

 

AIXM-5.1_RULE-1A13E2

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

ArrivalLeg

lowerLimitAltitude

 

AIXM-5.1_RULE-1A4E8B

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

 

AIXM-5.1_RULE-1A4AA6

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

ArrivalLeg

upperLimitAltitude

 

AIXM-5.1_RULE-1A13E3

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

ArrivalLeg

upperLimitAltitude

 

AIXM-5.1_RULE-1A2F47

The propertyName of any Note should refer to an existing property.

ArrivalLeg

 

 

AIXM-5.1_RULE-C2563

For each instance of a feature/object, some properties are mandatory for the data to make sense

AuthorityForAerialRefuelling

theOrganisationAuthority

 

AIXM-5.1_RULE-1AC39C

The propertyName of any Note should refer to an existing property.

AuthorityForAerialRefuelling

 

 

AIXM-5.1_RULE-1A8524

The 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

 

AIXM-5.1_RULE-1A33A6

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AuthorityForAirspace

assignedAirspace

 

AIXM-5.1_RULE-1A8525

The 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

 

AIXM-5.1_RULE-1A33B0

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AuthorityForAirspace

responsibleOrganisation

 

AIXM-5.1_RULE-1B5031

There cannot exists two different AuthorityForAirspace that have identical values for type and isResponsibleFor the same Airspace and is the same OrganisationAuthority

AuthorityForAirspace

type

 

AIXM-5.1_RULE-1A2F48

The propertyName of any Note should refer to an existing property.

AuthorityForAirspace

 

 

AIXM-5.1_RULE-1A33EC

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AuthorityForNavaidEquipment

theOrganisationAuthority

 

AIXM-5.1_RULE-1A2F49

The propertyName of any Note should refer to an existing property.

AuthorityForNavaidEquipment

 

 

AIXM-5.1_RULE-1A33E9

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

AuthorityForSpecialNavigationStation

theOrganisationAuthority

 

AIXM-5.1_RULE-1AC39D

The propertyName of any Note should refer to an existing property.

AuthorityForSpecialNavigationStation

 

 

AIXM-5.1_RULE-1AC39E

The propertyName of any Note should refer to an existing property.

AuthorityForSpecialNavigationSystem

 

 

AIXM-5.1_RULE-1A526F

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A332D

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Azimuth

channel

 

AIXM-5.1_RULE-1A331C

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Azimuth

designator

 

AIXM-5.1_RULE-26164

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

 

AIXM-5.1_RULE-5B4F1

The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 3.0 M

Azimuth

location

 

AIXM-5.1_RULE-5B4F7

The location of ILS/MLS components (as navaids located at aerodrome) shall have horizontal accuracy better than 10.0 FT

Azimuth

location

 

AIXM-5.1_RULE-16B59

Latitude and Longitude of Azimuth shall be published with 1/10 sec resolution (aerodrome navaid equipment)

Azimuth

location

 

AIXM-5.1_RULE-1A3332

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Azimuth

location.ElevatedPoint.pos

 

AIXM-5.1_RULE-1A3373

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

Azimuth

type

 

AIXM-5.1_RULE-1A2F4A

The propertyName of any Note should refer to an existing property.

Azimuth

 

 

AIXM-5.1_RULE-1A33CA

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

CallsignDetail

callSign

 

AIXM-5.1_RULE-1A33D3

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

CallsignDetail

language

 

AIXM-5.1_RULE-1A2F4B

The propertyName of any Note should refer to an existing property.

CallsignDetail

 

 

AIXM-5.1_RULE-D8CE5

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ChangeOverPoint

distance

 

AIXM-5.1_RULE-1A8529

The 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

 

AIXM-5.1_RULE-1A8528

The 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

 

AIXM-5.1_RULE-1A852A

The 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

 

AIXM-5.1_RULE-1A8526

The 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

 

AIXM-5.1_RULE-1A8527

The 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

 

AIXM-5.1_RULE-1A2F4C

The propertyName of any Note should refer to an existing property.

ChangeOverPoint

 

 

AIXM-5.1_RULE-1A5271

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-5C491

Latitude and longitude of CheckpointINS position shall be published with at least 6 decimals resolution

CheckpointINS

ElevatedPoint

 

AIXM-5.1_RULE-DE69E

The accuracy of the CheckpointINS position shall be better than 0.5 M

CheckpointINS

ElevatedPoint position

 

AIXM-5.1_RULE-1A4E92

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

 

AIXM-5.1_RULE-1A4AAD

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

CheckpointINS

lowerLimit

 

AIXM-5.1_RULE-1A13F4

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

CheckpointINS

lowerLimit

 

AIXM-5.1_RULE-1A4E91

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

 

AIXM-5.1_RULE-1A4AAC

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

CheckpointINS

upperLimit

 

AIXM-5.1_RULE-1A13F3

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

CheckpointINS

upperLimit

 

AIXM-5.1_RULE-1A2F4D

The propertyName of any Note should refer to an existing property.

CheckpointINS

 

 

AIXM-5.1_RULE-1A5270

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-BB039

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A4E94

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

 

AIXM-5.1_RULE-1A4AAF

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

CheckpointVOR

lowerLimit

 

AIXM-5.1_RULE-1A13F6

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

CheckpointVOR

lowerLimit

 

AIXM-5.1_RULE-1A4E93

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

 

AIXM-5.1_RULE-1A4AAE

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

CheckpointVOR

upperLimit

 

AIXM-5.1_RULE-1A13F5

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

CheckpointVOR

upperLimit

 

AIXM-5.1_RULE-1A2F4E

The propertyName of any Note should refer to an existing property.

CheckpointVOR

 

 

AIXM-5.1_RULE-2B369

UCUM values shall be used for the unit of measurement gml:radius property of CircleByCenterPoint

CircleByCenterPoint

gml:radius

 

AIXM-5.1_RULE-D8CE6

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

CircleSector

innerDistance

 

AIXM-5.1_RULE-1A4E6D

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

 

AIXM-5.1_RULE-D8CE9

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

CircleSector

lowerLimit

 

AIXM-5.1_RULE-1A4A82

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

CircleSector

lowerLimit

 

AIXM-5.1_RULE-1A13D1

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

CircleSector

lowerLimit

 

AIXM-5.1_RULE-D8CE7

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

CircleSector

outerDistance

 

AIXM-5.1_RULE-1A4E77

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

 

AIXM-5.1_RULE-D8CE8

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

CircleSector

upperLimit

 

AIXM-5.1_RULE-1A4A81

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

CircleSector

upperLimit

 

AIXM-5.1_RULE-1A13D0

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

CircleSector

upperLimit

 

AIXM-5.1_RULE-1A2F4F

The propertyName of any Note should refer to an existing property.

CircleSector

 

 

AIXM-5.1_RULE-1A852B

The 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

 

AIXM-5.1_RULE-1A69C0

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F50

The propertyName of any Note should refer to an existing property.

CirclingArea

 

 

AIXM-5.1_RULE-1A528B

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F51

The propertyName of any Note should refer to an existing property.

CirclingRestriction

 

 

AIXM-5.1_RULE-1A2F52

The propertyName of any Note should refer to an existing property.

City

 

 

AIXM-5.1_RULE-1A528C

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A2F53

The propertyName of any Note should refer to an existing property.

ConditionCombination

 

 

AIXM-5.1_RULE-1A2F54

The propertyName of any Note should refer to an existing property.

ContactInformation

 

 

AIXM-5.1_RULE-1A3EC2

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.

Curve

ArcByBulge

 

AIXM-5.1_RULE-1A3EC3

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.

Curve

ArcString

 

AIXM-5.1_RULE-1A3EC1

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.

Curve

ArcStringByBulge

 

AIXM-5.1_RULE-1A3EC5

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.

Curve

Bezier

 

AIXM-5.1_RULE-1A3EC4

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.

Curve

BSplineCurve

 

AIXM-5.1_RULE-1A3EC7

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.

Curve

Clothoid

 

AIXM-5.1_RULE-1A3EC6

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.

Curve

CubicSpline

 

AIXM-5.1_RULE-D8CEA

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

Curve

horizontalAccuracy

 

AIXM-5.1_RULE-1A3EC8

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.

Curve

OffsetCurve

 

AIXM-5.1_RULE-1B2D14

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.

Curve

segments.Arc.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B292C

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.

Curve

segments.Arc.pos

 

AIXM-5.1_RULE-1B2930

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.

Curve

segments.Arc.posList

 

AIXM-5.1_RULE-1B2D1F

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.

Curve

segments.ArcByCenterPoint.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2921

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.

Curve

segments.ArcByCenterPoint.pos

 

AIXM-5.1_RULE-1B2926

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.

Curve

segments.ArcByCenterPoint.posList

 

AIXM-5.1_RULE-1B2D28

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.

Curve

segments.ArcString.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2937

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.

Curve

segments.ArcString.pos

 

AIXM-5.1_RULE-1B293B

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.

Curve

segments.ArcString.posList

 

AIXM-5.1_RULE-1B2D27

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.

Curve

segments.Circle.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B292F

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.

Curve

segments.Circle.pos

 

AIXM-5.1_RULE-1B292E

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.

Curve

segments.Circle.posList

 

AIXM-5.1_RULE-1B2D1B

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.

Curve

segments.CircleByCenterPoint.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2923

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.

Curve

segments.CircleByCenterPoint.pos

 

AIXM-5.1_RULE-1B2925

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.

Curve

segments.CircleByCenterPoint.posList

 

AIXM-5.1_RULE-1B2D0B

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.

Curve

segments.Geodesic.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2940

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.

Curve

segments.Geodesic.pos

 

AIXM-5.1_RULE-1B293E

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.

Curve

segments.Geodesic.posList

 

AIXM-5.1_RULE-1B2D16

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.

Curve

segments.GeodesicString.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B293C

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.

Curve

segments.GeodesicString.pos

 

AIXM-5.1_RULE-1B2932

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.

Curve

segments.GeodesicString.posList

 

AIXM-5.1_RULE-1B2D19

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.

Curve

segments.LineStringSegment.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2935

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.

Curve

segments.LineStringSegment.pos

 

AIXM-5.1_RULE-1B293A

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.

Curve

segments.LineStringSegment.posList

 

AIXM-5.1_RULE-1A2F55

The propertyName of any Note should refer to an existing property.

Curve

 

 

AIXM-5.1_RULE-1A65D3

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.

Curve

 

 

AIXM-5.1_RULE-45D30

Latitude and longitude of de-icing/anti-icing facility (polygon) shall be published with 1/10 sec resolution

DeicingArea

 

 

AIXM-5.1_RULE-1AB014

The 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

 

AIXM-5.1_RULE-DE69D

The accuracy of the DeicingArea extent shall be better than 1.0 M

DeicingArea

ElevatedSurface extent

 

AIXM-5.1_RULE-1AB013

The 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

 

AIXM-5.1_RULE-1AB015

The 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

 

AIXM-5.1_RULE-1AC39F

The propertyName of any Note should refer to an existing property.

DeicingArea

 

 

AIXM-5.1_RULE-1AB00D

The 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

 

AIXM-5.1_RULE-1AC3A0

The propertyName of any Note should refer to an existing property.

DeicingAreaMarking

 

 

AIXM-5.1_RULE-1A4E6A

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

 

AIXM-5.1_RULE-D8CED

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

DepartureArrivalCondition

maximumCrossingAtEnd

 

AIXM-5.1_RULE-1A4A84

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

DepartureArrivalCondition

maximumCrossingAtEnd

 

AIXM-5.1_RULE-1A13D3

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

DepartureArrivalCondition

maximumCrossingAtEnd

 

AIXM-5.1_RULE-1A4E79

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

 

AIXM-5.1_RULE-D8CEC

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

DepartureArrivalCondition

minimumCrossingAtEnd

 

AIXM-5.1_RULE-1A4A83

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

DepartureArrivalCondition

minimumCrossingAtEnd

 

AIXM-5.1_RULE-1A13D2

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

DepartureArrivalCondition

minimumCrossingAtEnd

 

AIXM-5.1_RULE-D8CEB

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

DepartureArrivalCondition

minimumEnrouteAltitude

 

AIXM-5.1_RULE-1A2F56

The propertyName of any Note should refer to an existing property.

DepartureArrivalCondition

 

 

AIXM-5.1_RULE-1A4E90

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

 

AIXM-5.1_RULE-1A4AAB

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

DepartureLeg

altitudeOverrideATC

 

AIXM-5.1_RULE-1A13E0

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

DepartureLeg

altitudeOverrideATC

 

AIXM-5.1_RULE-1A5261

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-BB037

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A5263

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A525F

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A4E8F

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

 

AIXM-5.1_RULE-1A4AAA

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

DepartureLeg

lowerLimitAltitude

 

AIXM-5.1_RULE-1A13DF

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

DepartureLeg

lowerLimitAltitude

 

AIXM-5.1_RULE-D8CEE

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

DepartureLeg

minimumObstacleClearanceAltitude

 

AIXM-5.1_RULE-1A4E8E

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

 

AIXM-5.1_RULE-1A4AA9

If the unit of measurement for an altitude is 'FL' (flight level) then the value should have 2 or 3 digits

DepartureLeg

upperLimitAltitude

 

AIXM-5.1_RULE-1A13DE

For each feature that has a vertical limit attribute, the vertical reference of that limit shall be also specified.

DepartureLeg

upperLimitAltitude

 

AIXM-5.1_RULE-1A2F57

The propertyName of any Note should refer to an existing property.

DepartureLeg

 

 

AIXM-5.1_RULE-2CEC0

Designated Points of type "ICAO" should have a designator that is unique worldwide

DesignatedPoint

designator, type

 

AIXM-5.1_RULE-1A7570

The DesignatedPoint type cannot change to a value that is not backwards mapped in EAD

DesignatedPoint

type

 

AIXM-5.1_RULE-1A852D

The 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

 

AIXM-5.1_RULE-1A852C

The 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

 

AIXM-5.1_RULE-1A3368

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DesignatedPoint

designator

 

AIXM-5.1_RULE-DA435

There cannot exists two different DesignatedPoint that have identical values for designator and also for their position (within a tolerance of 1 second)

DesignatedPoint

designator

 

AIXM-5.1_RULE-1A3384

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DesignatedPoint

location.Point.pos

 

AIXM-5.1_RULE-1A852E

The 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

 

AIXM-5.1_RULE-1A3371

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DesignatedPoint

type

 

AIXM-5.1_RULE-1A2F58

The propertyName of any Note should refer to an existing property.

DesignatedPoint

 

 

AIXM-5.1_RULE-D8CEF

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

DirectFlightClass

exceedLength

 

AIXM-5.1_RULE-1A33C1

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DirectFlightClass

exceedLength

 

AIXM-5.1_RULE-1AC3A1

The propertyName of any Note should refer to an existing property.

DirectFlightClass

 

 

AIXM-5.1_RULE-1A3392

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DirectFlightSegment

end

 

AIXM-5.1_RULE-1AB033

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

 

AIXM-5.1_RULE-1AB035

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

 

AIXM-5.1_RULE-1AB031

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

 

AIXM-5.1_RULE-1AB032

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

 

AIXM-5.1_RULE-1AB034

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

 

AIXM-5.1_RULE-1A335B

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DirectFlightSegment

start

 

AIXM-5.1_RULE-1AB038

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

 

AIXM-5.1_RULE-1AB03A

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

 

AIXM-5.1_RULE-1AB036

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

 

AIXM-5.1_RULE-1AB037

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

 

AIXM-5.1_RULE-1AB039

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

 

AIXM-5.1_RULE-1AC3CE

The propertyName of any Note should refer to an existing property.

DirectFlightSegment

 

 

AIXM-5.1_RULE-1AB3F4

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1ABBC1

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1ADB05

Latitude and Longitude of DirectionFinder shall be published with 1 sec resolution (aerodrome navaid equipment)

DirectionFinder

location

 

AIXM-5.1_RULE-1AC3A2

The propertyName of any Note should refer to an existing property.

DirectionFinder

 

 

AIXM-5.1_RULE-53424

DirectionFinder is not supported in EAD and cannot be upload by the data providers.

DirectionFinder

 

 

AIXM-5.1_RULE-1A3342

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DistanceIndication

distance

 

AIXM-5.1_RULE-D8CF0

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

DistanceIndication

distance

 

AIXM-5.1_RULE-1A852F

The 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

 

AIXM-5.1_RULE-D8CF1

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

DistanceIndication

minimumReceptionAltitude

 

AIXM-5.1_RULE-1A8531

The 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

 

AIXM-5.1_RULE-1A8530

The 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

 

AIXM-5.1_RULE-1A2F59

The propertyName of any Note should refer to an existing property.

DistanceIndication

 

 

AIXM-5.1_RULE-DC371

DME/P elevation accuracy shall be equal or better than 3 m or 10 ft

DME

verticalAccuracy

 

AIXM-5.1_RULE-DC372

DME/P elevation accuracy shall be equal or better than 3 m or 10 ft

DME

verticalAccuracy

 

AIXM-5.1_RULE-1A33AB

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DME

authority

 

AIXM-5.1_RULE-1A5269

The feature instance actually targeted by an association (through its role name value) shall exist and 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

 

AIXM-5.1_RULE-1A33F0

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DME

channel

 

AIXM-5.1_RULE-1A3350

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DME

designator

 

AIXM-5.1_RULE-DA436

There cannot exists two different DME that have identical values for designator and also for their position (within a tolerance of 1 second)

DME

designator

 

AIXM-5.1_RULE-D8CF3

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

DME

displace

 

AIXM-5.1_RULE-D8CF2

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

DME

ghostFrequency

 

AIXM-5.1_RULE-16B52

Latitude and Longitude of DME shall be published with 1 sec resolution (aerodrome navaid equipment)

DME

location

 

AIXM-5.1_RULE-D9C61

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

 

AIXM-5.1_RULE-1A3321

For each instance of a feature/object, some properties are mandatory for backwards compatibility reasons with the previous AIXM 4.5 version.

DME

location.ElevatedPoint.pos

 

AIXM-5.1_RULE-D6D8B

The accuracy of the DME location.ElevatedPoint.verticalAccuracy shall be not less than 30

DME

location.ElevatedPoint.verticalAccuracy

 

AIXM-5.1_RULE-D6D8D

The accuracy of the DME location.ElevatedPoint.verticalAccuracy shall be not less than 100

DME

location.ElevatedPoint.verticalAccuracy

 

AIXM-5.1_RULE-1A2F5A

The propertyName of any Note should refer to an existing property.

DME

 

 

AIXM-5.1_RULE-1B1D6D

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.

DME

 

 

AIXM-5.1_RULE-1A3ECA

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.

ElevatedCurve

ArcByBulge

 

AIXM-5.1_RULE-1A3ECB

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.

ElevatedCurve

ArcString

 

AIXM-5.1_RULE-1A3EC9

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.

ElevatedCurve

ArcStringByBulge

 

AIXM-5.1_RULE-1A3ECD

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.

ElevatedCurve

Bezier

 

AIXM-5.1_RULE-1A3ECC

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.

ElevatedCurve

BSplineCurve

 

AIXM-5.1_RULE-1A3ECF

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.

ElevatedCurve

Clothoid

 

AIXM-5.1_RULE-1A3ECE

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.

ElevatedCurve

CubicSpline

 

AIXM-5.1_RULE-D8CF4

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ElevatedCurve

elevation

 

AIXM-5.1_RULE-D8CF5

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ElevatedCurve

geoidUndulation

 

AIXM-5.1_RULE-1A3ED0

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.

ElevatedCurve

OffsetCurve

 

AIXM-5.1_RULE-1B2D0F

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.

ElevatedCurve

segments.Arc.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2929

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.

ElevatedCurve

segments.Arc.pos

 

AIXM-5.1_RULE-1B292B

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.

ElevatedCurve

segments.Arc.posList

 

AIXM-5.1_RULE-1B2D24

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.

ElevatedCurve

segments.ArcByCenterPoint.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2922

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.

ElevatedCurve

segments.ArcByCenterPoint.pos

 

AIXM-5.1_RULE-1B2924

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.

ElevatedCurve

segments.ArcByCenterPoint.posList

 

AIXM-5.1_RULE-1B2D1A

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.

ElevatedCurve

segments.ArcString.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2931

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.

ElevatedCurve

segments.ArcString.pos

 

AIXM-5.1_RULE-1B293F

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.

ElevatedCurve

segments.ArcString.posList

 

AIXM-5.1_RULE-1B2D1C

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.

ElevatedCurve

segments.Circle.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B292D

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.

ElevatedCurve

segments.Circle.pos

 

AIXM-5.1_RULE-1B292A

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.

ElevatedCurve

segments.Circle.posList

 

AIXM-5.1_RULE-1B2D0C

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.

ElevatedCurve

segments.CircleByCenterPoint.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2927

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.

ElevatedCurve

segments.CircleByCenterPoint.pos

 

AIXM-5.1_RULE-1B2928

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.

ElevatedCurve

segments.CircleByCenterPoint.posList

 

AIXM-5.1_RULE-1B2D15

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.

ElevatedCurve

segments.Geodesic.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2936

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.

ElevatedCurve

segments.Geodesic.pos

 

AIXM-5.1_RULE-1B2934

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.

ElevatedCurve

segments.Geodesic.posList

 

AIXM-5.1_RULE-1B2D0A

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.

ElevatedCurve

segments.GeodesicString.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2933

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.

ElevatedCurve

segments.GeodesicString.pos

 

AIXM-5.1_RULE-1B293D

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.

ElevatedCurve

segments.GeodesicString.posList

 

AIXM-5.1_RULE-1B2D26

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.

ElevatedCurve

segments.LineStringSegment.pointProperty.Point.pos

 

AIXM-5.1_RULE-1B2939

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.

ElevatedCurve

segments.LineStringSegment.pos

 

AIXM-5.1_RULE-1B2938

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.

ElevatedCurve

segments.LineStringSegment.posList

 

AIXM-5.1_RULE-1A42AA

The vertical accuracy does not make sense if the elevation itself is not specified.

ElevatedCurve

verticalAccuracy

 

AIXM-5.1_RULE-D8CF6

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ElevatedCurve

verticalAccuracy

 

AIXM-5.1_RULE-1A2F5B

The propertyName of any Note should refer to an existing property.

ElevatedCurve

 

 

AIXM-5.1_RULE-1A65D4

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.

ElevatedCurve

 

 

AIXM-5.1_RULE-D8CF7

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ElevatedPoint

elevation

 

AIXM-5.1_RULE-D4A5B

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

 

AIXM-5.1_RULE-D8CF8

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ElevatedPoint

geoidUndulation

 

AIXM-5.1_RULE-D4A67

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

 

AIXM-5.1_RULE-449AA

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.

ElevatedPoint

pos

 

AIXM-5.1_RULE-1A42AB

The vertical accuracy does not make sense if the elevation itself is not specified.

ElevatedPoint

verticalAccuracy

 

AIXM-5.1_RULE-D8CF9

The Unit of measurement shall be specified if a value is specified for a property with uom attribute.

ElevatedPoint

verticalAccuracy

 

AIXM-5.1_RULE-D4A5A

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