...
Data item | Description | AIXM mapping |
|---|---|---|
type | The type of airspace concerned. Typical examples are CTR and TMA. | Airspace.type Not to be encoded, just used to identify the airspace concerned. To be consistent with the scenario scope and purpose, only the following types shall be used: CTR, CTR_P, CLASS, ATZ, ATZ_P, HTZ, ADIZ, CTA, CTA_P, UTA, UTA_P, OCA, OCA_P, OTA, SECTOR, SECTOR_C, RAS, TMA, TMA_P, ADV, UADV, FIR, FIR_P, OTHER:TMZ, OTHER:RMZ. |
name | The published name of the area. | Airspace.name. Not to be encoded, just used to identify the airspace concerned. |
designator | The published designator of the airspace concerned. If not provided, then the airspace is identified by its name. | Airspace.designator. Not to be encoded, just used to identify the airspace concerned. |
activation status | The activation/de-activation status. | Airspace/AirspaceActivation.status with the list of values CodeStatusAirspaceType. Note: only the values 'ACTIVE' or 'INACTIVE' can be used in this scenario. |
start time | The effective date & time when the activation/de-activation starts. This might be further detailed in a "schedule". | Airspace/AirspaceTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/beginPosition |
end time | The end date & time when the activation/de-activation ends. It might be an estimated value, if the exact end of activation is unknown. | Airspace/AirspaceTimeSlice/TimePeriod.endPosition, Event/EventTimeSlice.validTime/timePosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for Events with estimated termination |
schedule | A schedule might be provided, in case the area is only active according to a regular timetable, within the period between the start time and the end time. | Airspace/AirspaceActivation/Timesheet/... according to the rules for Schedules |
note | A free text note that provides further instructions concerning the area activation, such as the authority to be contacted for further information, the possibility of crossing at ATC discretion, etc. | Airspace/AirspaceActivation.annotation with purpose=”REMARK” |
| affected aerodrome | A reference (name, designator) to one or more airports/heliports for which the establishment of the area has an operational relevance and needs to be notified to the users thereof (if such information is known to the data originator) Note: a default list of 'affected airports' might need to be maintained in the application used for the Digital NOTAM coding. | Event.concernedAirportHeliport |
| affected FIR | A reference (type, designator) to one or more neighboring airspace of type FIR, for which the establishment of the area has an operational relevance and needs to be notified (if such information is known to the data originator). Note: the FIR(s) within which the area is physically situated do not need to be provided by the data originator. They will be automatically identified by the application that enables the coding of the Event. | Event.concernedAirspace |
...