Confirmed Issues That May Affect Operational Versions

This page is created to document all confirmed issues which may affect operational use of approved versions of IWXXM. We hope this will not only facilitate the management of the lifecycle of these issues but raised the awareness of IWXXM users with a view to minimize the impact of incidents that cannot be prevented. One should note that these confirmed issues will only be addressed in subsequent versions of IWXXM, and for practical reasons we will not fix issues in superseded or going to be replaced versions.

IWXXM 2023-1

• Documentation of iwxxm:WAFSJetStreamWindSymbol/iwxxm:windSpeed has left out the possible use of knot as unit of measure

IWXXM 2021-2

• SIGMET.SIGMETPosition-2 and SIGMET.SIGMETEvolvingCondition-5 in iwxxm.sch will be incorrectly triggered when validating a TC SIGMET being encapsulated in a COLLECT construct (#293)
• Representation of icing phenomenon is missing in the WAFS Significant Weather Forecast Package (#294)
• The notes in the SIGMET and AIRMET schemas concerning iwxxm:directionOfMotion and iwxxm:speedOfMotion needs alignment with TAC-to-XML-Guidance.txt

IWXXM 3.0.0

• Rule COLLECT.MB1 in iwxxm.sch is overly restrictive (#162)
• Schematron rule Common.Report-4 is counting the length of extension across different reports in a bulletin (#197)
• The representation of R/SNOCLO in METAR/SPECI contradicts with Schematron rule IWXXM.nilReasonCheck (#203)
• AIRMET is unable to represent ABV in phenomenon [BKN|OVC] CLD (#206)
• Rules SIGMET.SIGMET-5 and AIRMET.AIRMET-5 incorrectly mandate the phenomenonTime of observed phenomena to be the same as the start of validTime (#208). SIGMET.SIGMET-6 is using an incorrect comparator (#212).
• Schematron rules are not able to handle namespace prefixes which are not "iwxxm" (#210)
• Schematron rule VolcanicAshSIGMET.VolcanicAshSIGMET-6 cannot handle double volcanoes (#213)
• Schematron rules erroneously mandate the structure of NON-OPERATIONAL (especially TEST) reports (#220)
• Schematron rules METAR_SPECI.MeteorologicalAerodromeObservationReport-5, 6, 7 and 8 cannot handle nilReason(s) in multiple cloud layers (#226)

IWXXM 2.1.1

• Incorrect example va-advisory-A2-1.xml (#94)
• Incorrect description in TAC-to-XML Guidance on representing 'NO VA EXP' in SIGMET (#128)
• Inability to use xlink in iwxxm:geometry of SIGMET to represent the entire FIR (#129)
• Deficiency in representing a volcano in a Volcanic Ash Advisory (#153)