ID: | AIXM-574 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 10 AUG 2022 |
status: | APPROVED |
Description
Missing types are added to CodeAirspaceBaseType in order to support various existing airspace types.
Rationale for change
See https://aixmccb.atlassian.net/browse/AIXM-536
It was identified that some of the existing airspace types do not have corresponding CodeAirspaceBaseType values. The proposed additions aim for alignment with ICAO/EU/EUROCONTROL provisions.
Stemming from the ICAO provisions for civil aircraft operations over or near conflict zones and based on civil-military cooperation two airspace types are proposed: MOA (Military Operations Area) and RCZ (Remote Conflict Zone).
The missing airspace types related to the provision of aerodrome flight information service and alerting service for aerodrome traffic or areas where specific equipment is mandatory stemming from, inter alia, EU regulations are: FIZ (Flight Information Zone), RMZ (Radio Mandatory Zone) and TMZ (Transponder Mandatory Zone).
The proposed airspace types based on the (European) Free Route Airspace concept and Flexible Use of Airspace/Airspace Management principles are: FRA (Free Route Airspace), FBZ (Flight Plan Buffer Zone) and NPZ (No Planning Zone).
Impact assessment
[FWD_MAP_1:1] “Data mapping is possible and no data loss occurs when data is exchanged from a system (A) that uses AIXM 5.1.1 for output towards a system (B) that uses AIXM 5.2 for input.”
[BWD_MAP_1:1] “Data mapping is possible and no data loss occurs when data is exchanged from a system (B) that uses AIXM 5.2 for output towards a system (A) that uses AIXM 5.1.1 for input”
Change Proposal details
In the UML model:
- In CodeAirspaceBaseType add:
- FBZ , type = string, definition = “Flight Plan Buffer Zone.”
- FIZ, type = string, definition = “Flight Information Zone.”
- FRA, type = string, definition = “Free Route Airspace.”
- MOA, type = string, definition = “Military Operations Area.”
- NPZ, type = string, definition = “No Planning Zone.”
- RCZ, type = string, definition = “Remote Conflict Zone.”
- RMZ, type = string, definition = “Radio Mandatory Zone.”
- TMZ, type = string, definition = “Transponder Mandatory Zone.”
- In CodeAirspaceBaseType delete:
- HTZ
The UML class diagram to the right indicates the new/changed elements:
Mapping AIXM 5.1.1 to AIXM 5.2 (forward)
[MAPC-00] The following data conversion algorithm is proposed for:
- For each Airspace that has one of the type values:
- ‘OTHER:TIA’
- ‘OTHER:TIZ’
- ‘HTZ’
copy value from Airspace.type in Airspace.localType, except for “OTHER:”
- Replace type as follows::
- ‘OTHER:TIA’ with ‘FIZ’
- ‘OTHER:TIZ’ with ‘FIZ’
- ‘HTZ’ with ‘FIZ
[MAPC-01] The following data conversion algorithm is proposed for:
- For each Airspace that has one of the type values:
- Replace ‘OTHER:FBZ’ with ‘FBZ’
- Replace ‘OTHER:FIZ’ with ‘FIZ’
- Replace ‘OTHER:FRA’ with ‘FRA’
- Replace ‘OTHER:MOA’ with ‘MOA’
- Replace ‘OTHER:NPZ’ with ‘NPZ’
- Replace ‘OTHER:RCZ’ with ‘RCZ’
- Replace ‘OTHER:RMZ’ with ‘RMZ’
- Replace ‘OTHER:TMZ’ with ‘TMZ’
Mapping AIXM 5.2 to AIXM 5.1.1 (backward)
[MAPC-01] The following data conversion algorithm is proposed for:
- For each Airspace that has one of the type values:
- Replace ‘FBZ’ with ‘OTHER:FBZ’
- Replace ‘FIZ’ with ‘OTHER:FIZ’
- Replace ‘FRA’ with ‘OTHER:FRA’
- Replace ‘MOA’ with ‘OTHER:MOA’
- Replace ‘NPZ’ with ‘OTHER:NPZ’
- Replace ‘RCZ’ with ‘OTHER:RCZ’
- Replace ‘RMZ’ with ‘OTHER:RMZ’
- Replace ‘TMZ’ with ‘OTHER:TMZ’
Mapping example
(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx)
| AIXM 5.2 | AIXM 5.1(.1) |
|---|---|
... | ... |