...
| Warning | ||
|---|---|---|
| ||
AIXM does not provide a sufficiant sufficient list of values. Workaround AIXM 5.1(.1): Use 'OTHER'. Status AIXM 5.2: CCB issue AIXM-226 contains proposal to add more values (including the above ones) to the enumeration list for activity. |
...
More details about airspace activation in regard to digital NOTAM can be found in the Digital NOTAM Event Specification
.
Schedules
For ATS airspace, Appendix 1 of PANS-AIM (Aeronautical Data Catalogue) defines the "Hours of applicability" for the airspace and in addition the "Hours of Service", which are "the operational hours of the station serving the unit".
However, in an AIP the first item is only published for ATS airspaces of section AD 2.17, whereas the latter is only published for ATS airspaces listed in section ENR 2.1.
For special activity airspaces the "Time of activity" is defined as "Time interval when the special activity takes place".
In the following, only those coding rules specific to the airspace subjects will be discussed. For the general coding guidelines for Timesheet refer to topic Common coding patterns.
Hours of Applicability
For ATS airspaces published in "AD 2.17 Air traffic services airspace" PANS-AIM requires:
6) hours of applicability;
In AIXM, this information will be provided via the Airspace.activation property. The AirspaceActivation class and its properties are used to code the detailed information, including the status and the timeInterval.
Actually, in most AIP this information is not published but rather the hours of operation of the frequency the unit is providing the service for the airspace are published. (see AIP example below).
| Tip | ||
|---|---|---|
| ||
The example below shows that in AD 2.17 the hours of applicability are not published. in AD 2.18 however, the Hours of operation of the frequency the unit is providing the service for the airspace are published.
|
Hours of Service
This information is required for ATS airspaces usually published in "ENR 2.1 FIR, UIR, TMA AND CTA":
3) call sign of aeronautical station serving the unit and language(s) used, specifying the area and conditions, when and where to be used, if applicable;
In AIXM, this information will be provided via the Service.availability. The ServiceOperationalStatus class and its properties are used to code the detailed information, including the operationalStatus and the timeInterval.
An operational status has to be coded, in order to support the AIXM Digital NOTAM Event concept
.
| Tip | ||
|---|---|---|
| ||
The example below shows the Hours of service of the unit providing the service for the airspace.
|
Time of Activity
This information is required for special activity airspace usually published section in "ENR 5":
including time of activity.
In AIXM, this information will be provided via the Airspace.activation property. The AirspaceActivation class and its properties are used to code the detailed information, including the status and the timeInterval. See also topic Restriction & Activation.
A status has to be coded, in order to support the AIXM Digital NOTAM Event concept .
| Tip | ||
|---|---|---|
| ||
The example below shows the Time of activity of a special activity airspace.
The example below shows the time Time of activity of a danger area with the note that it will be activated by NOTAM. This will be coded with corresponding Timesheet and the status 'AVBL_FOR_ACTIVATION'.
The next figure shows and example where the time of activity of a restricted area is defined by a schedule and additional hours of activity will be announced by NOTAM. In this case corresponding Timesheet will be coded and the status 'ACTIVE'. The additional activation by NOTAM will be coded as AirspaceActivation.annotation.
|
Coding Example
The figure below gives a simple example of an airspace activation for BERTRIX AREA.
...
| No. | Description | XPath Expression |
|---|---|---|
| ATC-EX-01 | AMSWELL Control providing service for AMSWELL FIR, Hours of of service: H24 | //aixm:AirspaceTimeSlice[@gml:id='ATC_AMSWELL_ACC'] |
| ASE-EX-03 | Special activity airspace, Prohibited Area, Circle, Time of activity: H24 | //aixm:AirspaceTimeSlice[@gml:id='ASE_VAARDNOR_P'] |
| ASE-EX-04 | Special activity airspace, Restricted Area, Arc segment (Arc by centrepoint) | //aixm:AirspaceTimeSlice[@gml:id='ASE_BRAVO_R'] |
| ASE-EX-05 | Special activity airspace, Restricted Area, Rectangle | //aixm:AirspaceTimeSlice[@gml:id='ASE_BURGENVALK_R'] |
| ASE-EX-06 | Special activity airspace, Restricted Area, reference to state boundary (annotation) | //aixm:AirspaceTimeSlice[@gml:id='ASE_WINSWUK_R'] |
| ASE-EX-07 | Special activity airspace, Local type, reference to state boundary (xlink:href), Time of activity: 1 OCT - 31 JUL | //aixm:AirspaceTimeSlice[@gml:id='ASE_EAMOA01_MOA'] |
| ASE-EX-08 | Special activity airspace, Danger Area, Active weekday schedulesTime of activity: MON-FRI 0700-1700 (0600-1600) | //aixm:AirspaceTimeSlice[@gml:id='ASE_HORSHAM_D'] |
| ASE-EX-09 | Special activity airspace, Danger Area, within CTR | //aixm:AirspaceTimeSlice[@gml:id='ASE_DONLON_D'] |
| ASE-EX-19 | Aerial sporting activities airspace, Time of activity: 0600-SS SUN: 0900-1600 | //aixm:AirspaceTimeSlice[@gml:id='ASE_DONBURG_PARACHUTE_JUMPING_AERA'] |
...