...
Warning | ||
---|---|---|
| ||
In AIXM 5.1.1, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations cannot be encoded, Workaround for AIXM 5.1.1: Code a corresponding a Note.Status: for SATVOICE see CCB AIXM-189. For RCP/RSP issue has to be reported to CCB. |
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.
...
Info | ||
---|---|---|
| ||
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 [Lot 5] [AIXM-532] Direct associations between certain services and RouteSegment |
...
The linkage and protocol attribute may then be used to define the details about the logon address.All RouteSegment of a Route should have a related a Service provided by a Unit with the name attribute encoded.
Coding Examples
The figure below shows how the information about the controlling unit is published in an AIP:
...