...
| Panel | ||
|---|---|---|
| ||
|
Introduction
The ATS unit providng providing service for an airspace is not part of the minimum AIP data set but required in ENR 3 of PANS-AIM:
an indication of the controlling unit, its operating channel and, if applicable, its logon address, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations.
Hence, in the scope of this guidelines it is considered conditional data.
The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information.
| Warning | ||
|---|---|---|
| ||
In AIXM 5.1.1, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations cannot be encoded, except by using a Note. |
Thus, it is considered conditional data.
...
Workaround for AIXM 5.1.1: Code a corresponding a Note. |
| Info | ||
|---|---|---|
| ||
Change Proposals approved by the AIXM CCB for the next version will support the coding of SATVOICE and various navigation limitations. See [AIXM-537] Add possibility to indicate SATVOICE for TelephoneContact See [AIXM-519] Add Route association with AircraftCharacteristic |
AIXM 5.1(.1) does not provide a direct relationship between Unit and RouteSegment class.
...
In addition, a Service provided by the Unit shall be encoded. The Service class has several specialised classes that have an association to a RoutePortion, i.e. as there is no direct relationship to RouteSegment . The corresponding RoutePortion has to be encoded for the Service using the clientRoute property. One or more of these services may be provided for the same RoutePortion.
...
The type of service provided may be defined by the attribute Service.type, or it may be included in the . In addition also a Service.name, or it may be included in the Unit.nameprovided.
| Info | ||||
|---|---|---|---|---|
| Which of the 3 options shall be laid down as coding rule?
| |||
A Change Proposal approved by the AIXM CCB for the next version will support the coding of direct associations from InformationService, AirTrafficControlService, AirTrafficManagementService and SearchAndRescueService towards RouteSegment. See [AIXM-532] Direct associations between certain services and RouteSegment |
The operation channel is encoded using the RadioCommunicationChannel class. The attribute frequencyTransmission and if applicable frequencyReception will carry the corresponding value and uom (see also Radio Communication Channel [RCC]).
The RadioCommunicationChannel has to be referenced by the adequate Service.
...
| Warning | ||
|---|---|---|
| ||
| Depending on the specialised Service class, different ways of encoding this information are provided by AIXM. A consolidation may be needed! |
...
The linkage and protocol attribute may then be used to define the details about the logon address.
Coding Examples
The figure below shows how the information about the controlling unit is published in an AIP:
Coding
...
Examples can be found in the AIP Data Set - Specimen (DONLON).
| No. | Description | XPath Expression |
|---|---|---|
ATC-EX-01 UNI-EX-01 RCC-EX-01 RTE-EX-02 | Controlling Unit for Route Portion | //aixm:AirTrafficControlServiceTimeSlice[@gml:id ='ATC_AMSWELL_ACC'] | //aixm:UnitTimeSlice[@gml:id ='UNI_AMSWELL_ACC'] | //aixm:RadioCommunicationChannelTimeSlice[@gml:id ='RCC_AMSWELL_ACC'] | //aixm:RouteTimeSlice[@gml:id ='RTE_UA4'] |