[Lot 6][AIXM-427] Additional values in CodeProcedureFixRoleType

Description

Additional values for CodeProcedureFixRoleBaseType are added and the definition of FAF and FROP are updated based on the ICAO provisions.

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-113, https://aixmccb.atlassian.net/browse/AIXM-108, https://aixmccb.atlassian.net/browse/AIXM-476

ICAO PANS-OPS Volume II, Sixth Edition, incl Amdt 9 contains various waypoint/fix types used for the design, publication and down-stream usage of flight procedures. Several types are missing from the AIXM 5.1.1 CodeProcedureFixRoleBaseType enumeration and are proposed to be introduced for AIXM 5.2, incl. FAP, PFAF, MATF etc.

It was also identified that the definitions for FAF and FROP are outdated and the proposed change is introduced..

Impact assessment

[FWD_MAP_1:1] Data mapping is possible and no data loss occurs when data is exchanged from a system (A) that uses AIXM 5.1.1 for output towards a system (B) that uses AIXM 5.2 for input.

[BWD_MAP_1:1] Data mapping is possible and no data loss occurs when data is exchanged from a system (B) that uses AIXM 5.2 for output towards a system (A) that uses AIXM 5.1.1 for input.

Change Proposal details

In the UML model, in the CodeProcedureFixRoleBaseType:

• Add value FEEDER_FIX = “The fix depicted on Instrument Approach Procedure Charts which establishes the starting point of the feeder route.”
• Add value PFAF = "Precision Final Approach Fix - An RNP final approach is 3-D. The final approach fix for all 3-D approach procedures is the point that the glidepath intercepts the intermediate segment minimum altitude."
• Add value FAP = "Final Approach Point - the position where the precision segment starts, that is, the intersection of the nominal glide path and the minimum altitude specified for the preceding segment."
• Add value DP = "Descent point - A point defined by track and distance from the MAPt to identify the point at which the helicopter may descend below the OCA/H on a visual descent to the heliport/landing location."
• Add value FHP = "Fictitious heliport point - is a point over which the PinS final approach segment path passes at a relative height defined as the fictitious heliport point crossing height (FHPCH). It is defined by the WGS-84 latitude, longitude and ellipsoid height. The FHP replaces the FTP for PinS approaches. The FHP elevation is the same as the actual landing heliport elevation."
• Add value IDF = "Initial departure fix - The terminal fix for the visual segment and the fix where the instrument phase of the PinS departure begins."
• Add value MATF = "Missed approach turning fix (MATF) is a fix different from MAPt that marks a turn in the missed approach segment."
• Add value PRP = "Point-in-space reference point for the point-in-space approach as identified by the latitude and longitude of the MAPt."
• Change the definition of the existing value FAF into “Final approach fix for non-precision approach.”

Change the definition of the existing value FROP into “Final Rollout Point - Where a course change is required within the Final Approach Segment (FAS), the point that the aircraft rolls to a wings-level attitude aligned with the runway centreline extended is considered the FROP. FROP is used in an RNP AR procedure when a turn is required in the final between the FAF and the threshold.”

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

[MAPC-01] The following data conversion algorithm is proposed:

• For each TerminalSegmentPoint.role that has values of ”OTHER:FEEDER_FIX”
  • Replace the value with “FEEDER_FIX”
• For each TerminalSegmentPoint.role that has values of ”OTHER:PFAF”
  • Replace the value with “PFAF”
• For each TerminalSegmentPoint.role that has values of ”OTHER:FAP”
  • Replace the value with “FAP”
• For each TerminalSegmentPoint.role that has values of ”OTHER:DP”
  • Replace the value with “DP”
• For each TerminalSegmentPoint.role that has values of ”OTHER:FHP”
  • Replace the value with “FHP”
• For each TerminalSegmentPoint.role that has values of ”OTHER:IDF”
  • Replace the value with “IDF”
• For each TerminalSegmentPoint.role that has values of ”OTHER:MATF”
  • Replace the value with “MATF”
• For each TerminalSegmentPoint.role that has values of ”OTHER:PRP”
  • Replace the value with “PRP”

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-01] The following data conversion algorithm is proposed:

• For each TerminalSegmentPoint.role that has values of ”FEEDER_FIX”
  • Replace the value with “OTHER:FEEDER_FIX”
• For each TerminalSegmentPoint.role that has values of ”PFAF”
  • Replace the value with “OTHER:PFAF”
• For each TerminalSegmentPoint.role that has values of ”FAP”
  • Replace the value with “OTHER:FAP”
• For each TerminalSegmentPoint.role that has values of ”DP”
  • Replace the value with “OTHER:DP”
• For each TerminalSegmentPoint.role that has values of ”FHP”
  • Replace the value with “OTHER:FHP”
• For each TerminalSegmentPoint.role that has values of ”IDF”
  • Replace the value with “OTHER:IDF”
• For each TerminalSegmentPoint.role that has values of ”MATF”
  • Replace the value with “OTHER:MATF”
• For each TerminalSegmentPoint.role that has values of ”PRP”
  • Replace the value with “OTHER:PRP”

Mapping example

(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx) 

  ...

...