Date: Thu, 28 Mar 2024 18:32:27 +0000 (UTC) Message-ID: <934175292.16686.1711650747869@pmtpub41.ops.cfmu.eurocontrol.be> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16685_1195223621.1711650747867" ------=_Part_16685_1195223621.1711650747867 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
ID: |
AIXM-467 |
target version: |
AIXM 5.2 |
version: |
1.0 |
last updated: |
27 SEP 2021 |
status: |
PROPOSED |
|
---|
Additional classes, associations and data types are added in the model r= epresenting elements of the Global Navigation Satellite System (GNSS) and t= heir augmentation systems (SBAS/GBAS). Some properties and associations are= added or modified in existing AIXM classes, such as RadioFrequencyArea and= GuidanceService, in order to support the coding of data related to the new= satellite navigation system model.
See https://aixmccb.atlassi= an.net/browse/AIXM-206, = https://aixmccb.atlassian.net/browse/AIXM-186, <= a href=3D"https://aixmccb.atlassian.net/browse/AIXM-350" class=3D"external-= link" rel=3D"nofollow">https://aixmccb.atlassian.net/browse/AIXM-350<= /p>
The current model is lacking the capability to represent the information= about satellite navigation systems, augmentation systems and their use for= air navigation. Although the list of values for the SpecialNavigationSyste= m.type attribute includes =E2=80=9CGNSS=E2=80=9D, the properties of the Spe= cialNavigationSystem and its associated classes are far from a complete GNS= S aeronautical data model for AIS. The current model is also missing the ca= pability to define service coverage and limitations in relation with a runw= ay direction, which may be necessary for certain GBAS configurations.
Therefore, a dedicated set of classes and properties need to be added in= the model in order to support the coding of satellite navigation systems i= nformation, as relevant for aviation use. The proposed model is based on th= e ICAO requirements and guidelines for the use of satellite navigation syst= ems, as contained in the ICAO Annex 10, Vol I, 6th Edition and in the ICAO = PANS-OPS document. It also takes into consideration the AIS data provision = requirements for such systems. The proposed model can be summarised as foll= ows:
The existing RadioFrequencyArea model is used, with some improvements, i= n order to support the coding of the GBAS service volumes. This requires an= additional =E2=80=9Czero axis rotation=E2=80=9D property in the CircleSect= or class, in order to indicate that the angles are measured from the runway= centreline.
An additional correction concerns the =E2=80=9CWAASreliable=E2=80=9D att= ribute of the InstrumentApproachProcedure. Its name was initially derived f= rom the =E2=80=9CWide Area Augmentation System (WAAS)=E2=80=9D, which is an= FAA-specific implementation of Satellite Based Augmentation System (SBAS).= It does not seem to be still necessary, since the SatelliteService class c= an be used to indicate the local unavailability of an SBAS system.
= p>
[FWD_MAP_1:1] Data mapping is possi= ble and no data loss occurs when data is exchanged from a system (A) that u= ses AIXM 5.1.1 for output towards a system (B) that uses AIXM 5.2 for input= .
[BWD_MAP_LOSS] Data mapping = is possible, but some data would be lost (or converted into Notes) when dat= a is exchanged from a system (B) that uses AIXM 5.2 for output towards a sy= stem (A) that uses AIXM 5.1.1 for input.
In the UML model, create a new package =E2=80=9CSatellite Na= vigation Systems=E2=80=9D under Navaids and Points:
Note: the new CodeSatelliteApproachType data type is defined in AIXM-473= Change Proposal.
The resulting model for Satellite Navigation systems is shown in the fol= lowing UML class diagram, with the new classes and properties highlighted i= n blue.
The resulting GBAS model is shown in the following UM= L class diagram, with the new classes and associations = highlighted in blue:
The resulting GuidanceFacility model is shown in the following UML class= diagram, with the new classes and associations highlighted (Note: the = multiplicity of the GuidanceService class in the association to Procedure i= s 0..1 on this diagram. This takes into consideration the Change Proposal <= a href=3D"/aixm_confluence/display/AIXM52CP/%5BAIXM-419%5D+Correct+multipli= city+of+multi-occurring+%3C%3Cchoice%3E%3E+classes">AIXM-419):
[MAPC-99] No mapping is possible or justified. This is a completely new = model for GNSS elements.
[MAPC-02] Applied only for Procedure specialisations that have the new a= ssociations for GuidanceService. From the three backward mapping options di= scussed for this case, the first two (discard the value or use an extension= ) are straightforward and do not need any further details. The 3rd option (backward mapping into a Note) is detailed in order to provide a = complete description of this case and its conversion option:
[MAPC-99] No mapping possible for the rest of the data. The only other o= ption in the previous version is the use of an extension, for those systems= that are interested to use the new capability without a complete transitio= n to the new version. Therefore, the following elements shall be removed fr= om the file in order to ensure a valid AIXM 5.1.1 output:
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) |
---|---|
... |
... |