For ATS and special activity airspaces, PANS-AIM requires its lateral limits to be provided as part of the minimum AIP data set.
The diagram below shows the AIXM classes that may be used to encode that information:
There are two main ways to describe the geometry of airspace volumes in AIXM:
- by providing a horizontal border and vertical limits;
- Vertical limits defined in AirspaceVolume class
- Horizontal Border
- described as horizontalProjection (Surface)
- described by a AirspaceVolume.width and a centreline (Curve), for airspace corridors
- by providing a composition rule by which the airspace is defined as a series of unions, intersections, subtractions of other Airspace (aggregation) using the AirspaceComponentGeometry operation attributes and/or the AirspaceVolumeDependency association classes.
The model gives the possibility for using several approaches for the encoding of airspace aggregations/dependencies. The use of a method from the ones described further down in this section, depends on the intended use of the data. Examples of the application of such airspace aggregations are:
- Airspace of type CTR defined as a “circle of 50 NM from which the portion of airspace situated in a neighbouring FIR is subtracted”;
- Airspace of type UIR that has “the same horizontal projection as an FIR”, but different vertical limits;
- Airspace of type CTA which is the result of aggregating some Airspace of type SECTOR;
- etc.
Detailed encoding descriptions of the GML elements used by AIXM 5 can be found in OGC® document: 12-028r1 "Use of Geography Markup Language (GML) for Aviation Data".
This document can be found in the file list Supporting Documents. An overview of the encoding of geometries in AIXM 5 is can also be found in the Geometry topic of this documentation.
The attributes of the AirspaceVolume class are used to define the vertical limits of the airspace (see also Vertical Limits of Airspace). In addition, a horizontalProjection (lateral limits) will be encoded using the Surface class.
In case of an airspace corridor, a centreline will be defined using the Curve class.
The Surface of the airspace may use SignificantPoint and/or GeoBorder for its definition (see also the topics Significant Point for Airspace Border and GeoBorder).
The example below shows the Special Rule Airspace (SRA) WIEN IV with the vertical limits from 4500 FT AMSL up to FL 195.
The lateral limits are defined by several points and types of path between them. Between P1 and P2 the state border between Austria and the Czech Republic is referenced. Between P2 and P3 it is the state border between Austria and Slovakia. From P3 to P4 a DME Arc based on the VOR/DME "FMD" is used to define the airspace border. From P4 to P5 a geodesic line defines the lateral limits. P5 to P6 is again defined by an DME arc. From P6 to P7 again a geodesic line is used. Finally, the airspace border is closed by a geodesic line between P7 and P1.
Coding Rules for Geometry of Airspace
Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
---|---|---|---|---|
ASE-410 | Airspace geometry may be defined either by by providing a horizontal border and vertical limits (one airspace volume) or by an airspace aggregation (i.e. more than one airspace volume). | Data consistency | TBD | |
ASE-411 | An Airspace instance shall have lateral & vertical limits (i.e. each Airspace shall have assigned geometryComponent and and each AirspaceGeometryComponent shall have assigned theAirspaceVolume value). | Minimum AIP data set | AIXM-5.1_RULE-1A33E0, AIXM-5.1_RULE-1A33E1 | In case of an airspace geometry defined by airspace aggregation it has to be ensured that the child airspace has consistent and complete vertical limits (e.g. closed shape). |
ASE-412 | Airspace.type equal-to 'PART', shall only be coded when it is used as parent within an airspace aggregation. | Data consistency | TBD | |
ASE-413 | An AirspaceVolume that is not defined with a contributorAirspace must have either horizontalProjection or centreline. | EAD / Minimal data rule | AIXM-5.1_RULE-12B510 | |
ASE-414 | An Airspace cannot be used twice for the definition (by aggregation) of the geometry of another Airspace. | EAD / Minimal data rule | AIXM-5.1_RULE-9FAB0 | |
ASE-415 | If Airspace has more than one geometryComponent, then the operationSequence for each AirspaceGeometryComponent must be defined | AIXM Model / Data consistency rule | AIXM-5.1_RULE-19F488 | |
ASE-415 | Each AirspaceVolume with assigned centreline value shall have assigned width value. | AIXM Model / Data consistency rule | AIXM-5.1_RULE-1A0428 | |
ASE-416 | Coordinates of ('FIR','FIR_P','UIR','UIR_P') boundary points shall be published with at least 2 decimals resolution. | PANS-AIM | AIXM-5.1_RULE-D5611 | PANS-AIM requires a publication resolution of 1 minute, which can be achieved by minimum 2 decimal of a degree. |
ASE-417 | Coordinates of boundary points of 'CTA','CTA_P','CTR','CTR_P','TMA','TMA_P' shall be published with at least 4 decimals resolution. | PANS-AIM | AIXM-5.1_RULE-D5612 (No rule defined for TMA and TMA-P) | PANS-AIM requires a publication resolution of 1 second, which can be achieved by minimum 4 decimal of a degree. |
ASE-418 | Coordinates of ('P','R','D') boundary points shall be published with at least 2 decimals resolution if located outside CTA/CTR. | PANS-AIM | AIXM-5.1_RULE-D5613 (Rule does not take into account "outside CTA/CTR") | |
ASE-419 | Coordinates of ('P','R','D') boundary points shall be published with at least 4 decimals resolution if located inside CTA/CTR. | PANS-AIM | TBD | |
ASE-420 | If AirspaceGeometryComponent.operation is equal-to 'BASE', then AirspaceGeometryComponent.operationSequence must be 1 (first). | AIXM 4.5 Business Rules / Data consistency rule | AIXM-5.1_RULE-1A5A18 | |
ASE-421 | If the AirspaceVolume does not have centreline (is not a corridor), then width shall not be specified | AIXM Model / Data consistency rule | AIXM-5.1_RULE-1A0810 | |
ASE-422 | For an Airspace defined as the aggregation of several AirspaceGeometryComponent, the result of the aggregation shall not be en empty geometry | EAD / Minimal data rule | AIXM-5.1_RULE-15C250 | |
ASE-423 | The horizontalAccuracy of ('CTA','CTA_P','CTR','CTR_P','TMA','TMA_P') boundary points shall be equal-to or lower than '100' 'M' (or equal-to or lower than '300' 'FT)'. | PANS-AIM | AIXM-5.1_RULE-57E41, AIXM-5.1_RULE-57E42, AIXM-5.1_RULE-57E43, AIXM-5.1_RULE-57E44, AIXM-5.1_RULE-57E45, AIXM-5.1_RULE-57E46, AIXM-5.1_RULE-57E47, AIXM-5.1_RULE-57E48 (No rule defined for TMA and TMA-P) | |
ASE-424 | The horizontalAccuracy of ('FIR','FIR_P','UIR','UIR_P') boundary points shall be equal-to or lower than '2' 'KM'. | PANS-AIM | AIXM-5.1_RULE-57E4A, AIXM-5.1_RULE-57E4B, AIXM-5.1_RULE-57E4E, AIXM-5.1_RULE-57E4F | |
ASE-425 | The horizontalAccuracy of ('P','R','D') boundary points shall be equal-to or lower than '2' 'KM' if located outside CTA/CTR. | PANS-AIM | AIXM-5.1_RULE-57E49, AIXM-5.1_RULE-57E4C, AIXM-5.1_RULE-57E4D (Rules do not take into account "Outside CTA/CTR") | |
ASE-426 | The horizontalAccuracy of ('P','R','D') boundary points shall be equal-to or lower than '100' 'M' if located inside CTA/CTR. | PANS-AIM | TBD | |
ASE-427 | An AirspaceVolume cannot have at the same time a horizontalProjection and a contributorAirspace. | AIXM 4.5 Business Rules / Data consistency rule | AIXM-5.1_RULE-1A0BFA | |
ASE-428 | An AirspaceVolume cannot have at the same time a centreline and a contributorAirspace. | AIXM 4.5 Business Rules / Data consistency rule | AIXM-5.1_RULE-1A0BF9 | |
ASE-429 | An AirspaceVolume cannot have at the same time a horizontalProjection and a centreline. | AIXM 4.5 Business Rules / Data consistency rule | AIXM-5.1_RULE-1A0BFB | |
ASE-431 | An AirspaceVolume that has a geometry defined as a full copy of the geometry of another Airspace (AirspaceVolumeDependency.dependency value equal-to 'FULL_GEOMETRY'), shall not have vertical limits (because it re-uses the vertical limits of the contributorAirspace). | AIXM 4.5 Business Rules / Data consistency rule | AIXM-5.1_RULE-1D4C1, AIXM-5.1_RULE-1D4C2, AIXM-5.1_RULE-1D4C3, AIXM-5.1_RULE-1D4C4 | |
ASE-432 | An AirspaceVolume for which the lowerLimit and upperLimit are not specified, must have the geometry defined as a full copy of the geometry of another Airspace (AirspaceVolumeDependency.dependency value equal-to 'FULL_GEOMETRY'). | AIXM 4.5 Business Rules / Data consistency rule | AIXM-5.1_RULE-CA260 | |
ASE-433 | The value 'OTHER' shall not be used for AirspaceGeometryComponent.operation. | AIXM 4.5 / Data consistency rule | AIXM-5.1_RULE-C2D32 | |
ASE-434 | The value 'OTHER' shall not be used for AirspaceVolume.width.uom | AIXM 4.5 / Data consistency rule | AIXM-5.1_RULE-C2D40 | |
ASE-435 | Coordinates of (''P','R','D'') boundary points shall be aggregated with Airspace that have boundary points published with at least 2 decimals resolution, if outside CTA/CTR. | PANS-AIM | AIXM-5.1_RULE-1AA069 (Rule does not take into account "outside CTA/CTR) | |
ASE-436 | Coordinates of (''P','R','D'') boundary points shall be aggregated with Airspace that have boundary points published with at least 4 decimals resolution, if inside CTA/CTR. | PANS-AIM | TBD | |
ASE-437 | Coordinates of (''CTA','CTA-P','CTR','CTR-P', TMA, TMA-P') boundary points shall be aggregated with Airspace that have boundary points published with at least 4 decimals resolution | PANS-AIM | AIXM-5.1_RULE-1AA06A (Rule does not take into account TMA and TMA-P) | |
ASE-438 | Coordinates 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 | PANS-AIM | AIXM-5.1_RULE-1AA06B | |
ASE-439 | Each AirspaceVolumeDependency shall have assigned theAirspace value | AIXM4.5 / Minimal data rule | AIXM-5.1_RULE-1A33E2 | |
ASE-440 | Each AirspaceVolumeDependency shall have assigned dependency value | AIXM4.5 / Minimal data rule | AIXM-5.1_RULE-1A33E3 | |
ASE-441 | If Airspace has more than one geometryComponent, then the operation for each AirspaceGeometryComponent must be defined | AIXM Model / Data consistency | AIXM-5.1_RULE-19F870 | |
ASE-442 | If Airspace has more than one geometryComponent, then there must exist exactly one with operation is equal-to 'BASE'. | AIXM 4.5 Business Rules / Data consistency rule | AIXM-5.1_RULE-26D18 | |
ASE-443 | Child Airspace in airspace aggregation cannot have duplicate AirspaceGeometryComponent.operationSequence. | EAD Rule | TBD | |
ASE-444 | If there is an AirspaceVolumeDependency coded for an Airspace the Surface and Curve shall not be encoded for that child airspace. | Data consistency | TBD |
Coding Examples
See child pages.
References
Child Pages
Children Display |
---|