AIXM 5.1 Business Rules - version 0.9.0
Version 0.9.0 is applied in EAD starting with Release 15.1 and comprises the following updates to the rules of the EAD profile:
|
Rule ID |
Change type |
Issue |
Change description |
|
1C7CF8, 1A0FE0 |
correction |
discrepancy SDD-SDO |
The EAD profile currently includes rules regarding the maximum allowed gap to a referenced GeoBorder. The gap should be increased from 30 m to 32 m because the gap tolerated in SDO is in fact 32 m. |
|
1F3831, 1F3832, 1F3833, 1F3834 |
new |
missing rule |
Added rules to prevent that a RouteSegment is coded as both A-to-B and B-to-A. |
|
4269, 426A, 1B1599, 1B159A |
correction |
too strict rule |
RULE-4269 and RULE-426A should only count the geometryComponent associations that resolve to an AirspaceVolume that has the horizontalProjection attribute populated. The 4 rules will keep their existing UIDs. |
|
DA435 |
profile |
rule becomes warning |
RULE-DA435 can also be triggered for non-BWM DesignatedPoint types. However, this is acceptable and the rule can be downgraded to WARNING in particular cases as needed. |
|
1F3C19 |
new |
complement existing rule |
This rule complements the downgrading of DA435 to "warning". It is restricted only to DesignatedPoints of type 'ICAO', 'COORD', 'OTHER' or 'OTHER:.*', which are actually backwards mapped to SDO in EAD. |
|
D5229 |
profile |
rule becomes warning |
On request of a migrating client, the rule was downgraded in EAD because DME are used systematically as navigable location in that country data. |
|
1A33DF |
removed |
Not justified for MKR |
Each MarkerBeacon shall have assigned designator value. |
The following items are provided:
- an XML version of the rules, which preserves the information about templates used in the definition of many rules;
- a tabular version, extracted from the XML version, in both HTML and Excel format