From 780aed9d345fedf8b15ef9c8d16a2fe524efea32 Mon Sep 17 00:00:00 2001 From: markh Date: Mon, 11 Feb 2019 13:47:58 +0000 Subject: [PATCH] include 2.1.0 --- IWXXM/ReleaseNotes-IWXXM.txt | 28 + IWXXM/TAC-to-XML-Guidance.txt | 114 ++-- IWXXM/airmet.xsd | 72 +- IWXXM/common.xsd | 53 +- IWXXM/examples/airmet-A6-1a-TS.xml | 106 +-- IWXXM/examples/airmet-translation-failed.xml | 8 +- IWXXM/examples/metar-A3-1.xml | 14 +- IWXXM/examples/metar-EDDF-runwaystate.xml | 18 +- IWXXM/examples/metar-LKKV.xml | 28 +- IWXXM/examples/metar-NIL.xml | 8 +- IWXXM/examples/metar-translation-failed.xml | 68 ++ IWXXM/examples/sigmet-A6-1a-TS.xml | 67 +- IWXXM/examples/sigmet-A6-1b-CNL.xml | 12 +- IWXXM/examples/sigmet-A6-2-TC.xml | 90 +-- IWXXM/examples/sigmet-VA-EGGX.xml | 105 +-- IWXXM/examples/sigmet-multi-location.xml | 230 +++++++ IWXXM/examples/sigmet-translation-failed.xml | 67 ++ IWXXM/examples/speci-A3-2.xml | 12 +- IWXXM/examples/taf-A5-1.xml | 14 +- IWXXM/examples/taf-A5-2.xml | 6 +- IWXXM/examples/taf-NIL.xml | 8 +- IWXXM/examples/taf-translation-failed.xml | 42 ++ IWXXM/examples/tc-advisory-A2-2.xml | 9 +- .../tc-advisory-translation-failed.xml | 71 ++ IWXXM/examples/va-advisory-A2-1.xml | 8 +- .../va-advisory-translation-failed.xml | 84 +++ IWXXM/iwxxm-collect.xsd | 2 +- IWXXM/iwxxm.xsd | 2 +- IWXXM/measures.xsd | 2 +- IWXXM/metarSpeci.xsd | 131 ++-- IWXXM/rule/iwxxm-collect.sch | 636 +++++++++++++++++- IWXXM/rule/iwxxm.sch | 146 ++-- IWXXM/sigmet.xsd | 100 +-- IWXXM/taf.xsd | 19 +- IWXXM/tropicalCycloneAdvisory.xsd | 10 +- IWXXM/volcanicAshAdvisory.xsd | 10 +- 36 files changed, 1853 insertions(+), 547 deletions(-) create mode 100644 IWXXM/examples/metar-translation-failed.xml create mode 100644 IWXXM/examples/sigmet-multi-location.xml create mode 100644 IWXXM/examples/sigmet-translation-failed.xml create mode 100644 IWXXM/examples/taf-translation-failed.xml create mode 100644 IWXXM/examples/tc-advisory-translation-failed.xml create mode 100644 IWXXM/examples/va-advisory-translation-failed.xml diff --git a/IWXXM/ReleaseNotes-IWXXM.txt b/IWXXM/ReleaseNotes-IWXXM.txt index b2bab6b9..9aba770f 100644 --- a/IWXXM/ReleaseNotes-IWXXM.txt +++ b/IWXXM/ReleaseNotes-IWXXM.txt @@ -1,3 +1,31 @@ +==================================== +2.1 - March 2017 +==================================== +* Modified AIRMET and SIGMET to correctly handle complex cases where there are multiple OBS/FCST elements and forecast + position elements. See http://bit.ly/2lZroAM for more information. + * AIRMET and SIGMET analysis results are now Collection types which may include up to two sets of conditions as + allowed by ICAO Annex 3 Amendment 77 Table A6-1A Note 27 on "AND" elements. AIRMET and SIGMET XML elements were + renamed to be more consistent. The OBS/FCST time indicator was moved to the Collection types, and all other + information may be repeated on EvolvingCondition types. EvolvingCondition types may now only have a single geometry + + New elements: SIGMETEvolvingConditionCollection and AIRMETEvolvingConditionCollection + * Renamed elements: (SIGMET) EvolvingMeteorologicalCondition -> SIGMETEvolvingCondition, + AIRMETEvolvingMeteorologicalCondition -> AIRMETEvolvingCondition, SIGMET MeteorologicalPosition -> SIGMETPosition, + SIGMET MeteorologicalPositionCollection -> SIGMETPositionCollection + * AIRMET and SIGMET analysis elements are now 0..1 and there must now be exactly one geometry element per member + element. Multiple polygons for an OBS or FCST are represented as multiple member elements in the result +* No significant change (NSC) is now represented on TAFs as a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance". + The TAF ForecastChangeIndicator "NO_SIGNIFICANT_CHANGES" has been removed and "changeForecast" references are now nillable +* The TAC to XML Guidance document has been updated to be more internally consistent and readable +* Added translation failed examples for each product and slightly improved SIGMET Schematron rules to properly support + these types of messages +* Per AIXM developer feedback, all AIXM snippets now use the correct "SNAPSHOT" terminology for time slices instead of + "BASELINE". This required changes to a number of examples +* The METAR LKKV example has been updated to include a wind shear section +* Made relevant elements mentioned in TAC-to-XML-Guidance.txt nillable to allow the inclusion of nilReason as indicated + in the text +* Corrected syntax errors in contraints METAR_SPECI.ASW6 and COMMON.ACF2 +* Fixed issues with regard to the placement and associated constraints of extension blocks + ==================================== 2.0 - August 2016 ==================================== diff --git a/IWXXM/TAC-to-XML-Guidance.txt b/IWXXM/TAC-to-XML-Guidance.txt index 5998bb6f..7364c2cc 100644 --- a/IWXXM/TAC-to-XML-Guidance.txt +++ b/IWXXM/TAC-to-XML-Guidance.txt @@ -1,159 +1,127 @@ -========================== +========================== Introduction ========================== -This document provides guidance on how abbreviations and codes from the Traditional Alphanumeric Codes (TAC) -are represented in XML (IWXXM). +This document provides guidance on how abbreviations and codes from the Traditional Alphanumeric Codes (TAC) are represented in XML (IWXXM). ========================== METAR/SPECI ========================== -NIL (report) - (Represented as a status of "MISSING" on METAR/SPECI and TAF reports) +NIL report + NIL reports shall be represented as a status of "MISSING" on METAR/SPECI and TAF reports CAVOK - Cloud and visibility OK - When CAVOK conditions apply, the appropriate Record type shall have "cloudAndVisibilityOK" set to true and visibility, - runway visual range, weather, and cloud information shall be missing. + When CAVOK conditions apply, the appropriate Record type shall have "cloudAndVisibilityOK" set to true and visibility, runway visual range, weather, and cloud information shall be missing CLRD - Runway contamination is cleared When runway contamination has been cleared, AerodromeRunwayState shall have "cleared" set to true NSC - No clouds of operational significance - When no cloud of operational significance is observed/forecast, and no restriction on vertical - visibility and 'CAVOK' is not appropriate, the cloud group shall be missing with a nil reason of - http://codes.wmo.int/common/nil/nothingOfOperationalSignificance + When no cloud of operational significance is observed/forecast, and no restriction on vertical visibility and 'CAVOK' is not appropriate, "cloud" shall be nil with a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" NCD - No clouds detected (by auto system) - When no clouds are detected by the automatic observing system, it shall be indicated by a - missing cloud group with a nil reason of http://codes.wmo.int/common/nil/notDetectedByAutoSystem + When no clouds are detected by an automatic observing system, this shall be indicated by a nil "cloud" with a nil reason of "http://codes.wmo.int/common/nil/notDetectedByAutoSystem" NOSIG - No significant changes are forecast - When no change is expected to occur, this shall be indicated by a single missing trend forecast with a nil - reason of http://codes.wmo.int/common/nil/noSignificantChange + When no change is expected to occur, this shall be indicated by a single nil "trendForecast" with a nil reason of "http://codes.wmo.int/common/nil/noSignificantChange" NSW - No weather of operational significance - The expected end of occurrence of weather phenomena shall be indicated by a change forecast with a missing weather - group with a nil reason of http://codes.wmo.int/common/nil/nothingOfOperationalSignificance - + The expected end of occurrence of weather phenomena shall be indicated by a nil "forecastWeather" with a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" + R88 (runway designator for runway state) When all runways are being indicated, the AerodromeRunwayState shall have "allRunways" set to true R99 (runway designator for runway state) - When a new runway state report is not available in time for dissemination of the METAR message, the - previous runway state report will be repeated + When a new runway state report is not available in time for dissemination of the METAR message, the previous runway state report will be repeated SNOCLO - Runway closed due to snow When a runway is closed due to snow, AerodromeRunwayState shall have "snowClosure" set to true Present weather "//" - When present weather cannot be observed by the automatic observing system due to a temporary failure of the - system/sensor, the present weather shall be missing with a nil reason of - http://codes.wmo.int/common/nil/notObservable + When present weather cannot be observed by the automatic observing system due to a temporary failure of the system/sensor, "presentWeather" shall be nil with a nil reason of "http://codes.wmo.int/common/nil/notObservable" Vertical visibility "VV///" (METAR/SPECI observations) - When the sky is obscured and the value of the vertical visibility cannot be determined by the automatic observing - system due to a temporary failure of the system/sensor, the vertical visibility shall be missing with a nil reason of - http://codes.wmo.int/common/nil/notObservable + When the sky is obscured and the value of the vertical visibility cannot be determined by the automatic observing system due to a temporary failure of the system/sensor, the "verticalVisibility shall be nil with a nil reason of "http://codes.wmo.int/common/nil/notObservable" Cloud amount and base "//////" - When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the - cloud amount and the height of cloud base cannot be observed, this shall be indicated by a missing cloud layer - with a nil reason of either http://codes.wmo.int/common/nil/notObservable if the value could not be observed due to - a sensor or system failure, or http://codes.wmo.int/common/nil/notDetectedByAutoSystem if the automated system is - working properly but did not observe any values + When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the cloud amount and the height of cloud base cannot be observed, this shall be indicated by a nil cloud "layer" with a nil reason of either "http://codes.wmo.int/common/nil/notObservable" if the value could not be observed due to a sensor or system failure, or "http://codes.wmo.int/common/nil/notDetectedByAutoSystem" if the automated system is working properly but did not observe any values Cloud amount "///015" - When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the - cloud amount cannot be observed, this shall be indicated by a CloudLayer with a missing "amount" with a nil reason - of either http://codes.wmo.int/common/nil/notObservable if the value could not be observed due to - a sensor or system failure, or http://codes.wmo.int/common/nil/notDetectedByAutoSystem if the automated system is - working properly but did not observe any values + When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the cloud amount cannot be observed, this shall be indicated by a cloud "layer" with a nil "amount" and a nil reason of either "http://codes.wmo.int/common/nil/notObservable" if the value could not be observed due to a sensor or system failure, or "http://codes.wmo.int/common/nil/notDetectedByAutoSystem" if the automated system is working properly but did not observe any values Cloud base "BKN///" - When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the height of - cloud base cannot be observed, this shall be indicated by a CloudLayer with a missing "base" with a nil reason - of either http://codes.wmo.int/common/nil/notObservable if the value could not be observed due to - a sensor or system failure, or http://codes.wmo.int/common/nil/notDetectedByAutoSystem if the automated system is - working properly but did not observe any values + When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the height of cloud base cannot be observed, this shall be indicated by a cloud "layer" with a nil "base" and a nil reason of either "http://codes.wmo.int/common/nil/notObservable" if the value could not be observed due to a sensor or system failure, or "http://codes.wmo.int/common/nil/notDetectedByAutoSystem" if the automated system is working properly but did not observe any values Cloud type "///" - When cloud type cannot be observed by an auto system due to sensor limitations this shall be indicated by - http://codes.wmo.int/common/nil/notObservable. + When cloud type cannot be observed by an auto system due to sensor limitations "cloudType" shall be nil with a nil reason of "http://codes.wmo.int/common/nil/notObservable" Runway depth of deposit "//" - When the runway depth of deposits is operationally insignificant or is not measurable this shall be indicated by - a missing depthOfDeposits and a nilReason of either http://codes.wmo.int/common/nil/notObservable or - http://codes.wmo.int/common/nil/nothingOfOperationalSignificance. + When the runway depth of deposits is operationally insignificant or is not measurable this shall be indicated by a nil "depthOfDeposits" and a nil reason of either "http://codes.wmo.int/common/nil/notObservable" or "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" Runway depth of deposit "99" (value from WMO code table 1079) - When the runway depth of deposits is not reported due to runway or runways non-operational due to snow, slush, ice, - large drifts or runway clearance this shall be indicated by a missing depthOfDeposits and a nilReason of - http://www.opengis.net/def/nil/OGC/0/unknown. + When the runway depth of deposits is not reported due to runway or runways non-operational due to snow, slush, ice, large drifts or runway clearance this shall be indicated by a nil "depthOfDeposits" and a nil reason of "http://www.opengis.net/def/nil/OGC/0/unknown" - - ========================== TAF ========================== -NIL (report) - (Represented as a status of "MISSING" on METAR/SPECI and TAF reports) +NIL report + NIL reports shall be represented as a status of "MISSING" on METAR/SPECI and TAF reports CAVOK - Cloud and visibility OK - When CAVOK conditions apply, the appropriate Record type shall have "cloudAndVisibilityOK" set to true and visibility, - runway visual range, weather, and cloud information shall be missing. + When CAVOK conditions apply, the appropriate Record type shall have "cloudAndVisibilityOK" set to true and visibility, runway visual range, weather, and cloud information shall be missing NSC - No clouds of operational significance - When no cloud of operational significance is observed/forecast, and 'CAVOK' is not appropriate, the cloud group shall be missing with a nil reason of - http://codes.wmo.int/common/nil/nothingOfOperationalSignificance + When no cloud of operational significance is observed/forecast, and 'CAVOK' is not appropriate, "cloud" shall be nil with a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" NSW - No weather of operational significance - The expected end of occurrence of weather phenomena shall be indicated by a change forecast with a missing weather - group with a nil reason of http://codes.wmo.int/common/nil/nothingOfOperationalSignificance + The expected end of occurrence of weather phenomena shall be indicated by a nil "weather" with a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" Vertical visibility "VV///" - When the vertical visibility is not available for any reason, vertical visibility shall be missing with no nil reason. + When the vertical visibility is not available for any reason, "verticalVisibility" shall be missing with no nil reason ========================== SIGMET ========================== NO VA EXP - No volcanic ash expected - The expected end of occurrence of volcanic ash shall be indicated with a missing VolcanicAshSIGMET "phenomenon" with a - nil reason of http://codes.wmo.int/common/nil/nothingOfOperationalSignificance + The expected end of occurrence of volcanic ash shall be indicated with a nil "VolcanicAshSIGMET/phenomenon" and a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" ========================== Volcanic Ash Advisory ========================== 'UNKNOWN' volcano name - An unknown volcano name shall be indicated with an EruptingVolcano name of "UNKNOWN" + An unknown volcano name shall be indicated with an "EruptingVolcano/name" of "UNKNOWN" 'UNNAMED' volcano name - An unnamed volcano shall be indicated with an EruptingVolcano name of "UNNAMED" + An unnamed volcano shall be indicated with an "EruptingVolcano/name" of "UNNAMED" 'UNKNOWN' volcano location - An unknown volcano location shall be indicated with a missing EruptingVolcano position with a nilReason of "unknown" + An unknown volcano location shall be indicated with a nil "EruptingVolcano/position" and a nil reason of "unknown" 'UNKNOWN' aviation colour code - An unknown aviation colour code shall be indicated with a missing colourCode with a nilReason of "unknown" + An unknown aviation colour code shall be indicated with a nil "colourCode" and a nil reason of "unknown" 'NOT GIVEN' aviation colour code - An aviation colour code that is not given shall be indicated with a missing colourCode with a nilReason of "withheld" + An aviation colour code that is not given shall be indicated with a nil "colourCode" and a nil reason of "withheld" 'NIL' aviation colour code - A NIL aviation colour code shall be indicated with a missing colourCode with a nilReason of "missing" + A NIL aviation colour code shall be indicated with a nil "colourCode" with a nil reason of "missing" 'VA NOT IDENTIFIABLE FM SATELLITE DATA' - Unidentifiable volcanic ash from satellite data shall be indicated with a nil ashCloudExtent with a nilReason of "unknown" + Unidentifiable volcanic ash from satellite data shall be indicated with a nil "ashCloudExtent" and a nil reason of "unknown" 'NO VA EXP' - When no volcanic ash is expected it shall be indicated with a nil ashCloudExtent with a nilReason of - http://codes.wmo.int/common/nil/nothingOfOperationalSignificance + When no volcanic ash is expected it shall be indicated with a nil "ashCloudExtent" and a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" 'NOT AVBL' - When volcanic ash is not available it shall be indicated with a nil ashCloudExtent with a nilReason of 'missing' + When volcanic ash is not available it shall be indicated with a nil "ashCloudExtent" and a nil reason of "missing" 'NOT PROVIDED' - When volcanic ash is not provided it shall be indicated with a nil ashCloudExtent with a nilReason of 'withheld' + When volcanic ash is not provided it shall be indicated with a nil "ashCloudExtent" and a nil reason of "withheld" ========================== Tropical Cyclone Advisory ========================== -' \ No newline at end of file +'UNNAMED' volcano name + An unnamed tropical cyclone shall be indicated with a "tropicalCycloneName" of "UNNAMED" + +'NIL' remarks + NIL remarks shall be indicated with an missing "remarks" element diff --git a/IWXXM/airmet.xsd b/IWXXM/airmet.xsd index fac88d15..b13e3880 100644 --- a/IWXXM/airmet.xsd +++ b/IWXXM/airmet.xsd @@ -1,5 +1,5 @@ - + @@ -11,9 +11,40 @@ AIRMETs report the occurrence and/or expected occurrence of specified en-route w References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. + + + A collection of AIRMETEvolvingConditions, each representing a location where AIRMET observed or forecast conditions exist. All members of this collection are of type AIRMETEvolvingCondition. + + + + + + + + + + Extension block for optional and/or additional parameters for element AIRMETEvolvingConditionCollection + + + + + + Indication whether the information is observed and expected to continue, or forecast + + + + + + + + + + + + - An AIRMET (significant meteorological) report. AIRMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena over time. + An AIRMET (significant meteorological) report. AIRMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena over time. The AIRMET report class represents the base AIRMET types that may be reported such as squall lines, thunderstorms, dust storms, turbulence, etc. AIRMETs may report either observed or forecast hazardous conditions. @@ -61,16 +92,14 @@ YUDD AIRMET A3 VALID ... The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, etc. - + - AIRMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, as well as observed and forecast conditions for each of these reported areas. All combinations of observations and forecasts of meteorological conditions, including changing conditions, are represented by their own AIRMETEvolvingMeteorologicalCondition. - -Each analysis has a single EvolvingMeteorologicalCondition as its result. + AIRMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, as well as observed and forecast conditions for each of these reported areas. AIRMETs may include a single set of observed and/or forecast conditions at a particular time, which is represented as a single analysis with a single AIRMETEvolvingConditionCollection as its result. - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element AIRMET @@ -89,14 +118,14 @@ Each analysis has a single EvolvingMeteorologicalCondition as its result. - + - Conditions that indicate the presence of a specific AIRMET phenomenon such as volcanic ash or a thunderstorm, along with expected changes to the phenomenon such as intensity, speed, and direction. These conditions are reported with OBS/FCST conditions on all SIGMET types. + Conditions that indicate the presence of a specific AIRMET phenomenon such as mountain obscuration or a thunderstorm, along with expected changes to the phenomenon such as intensity, speed, and direction. These conditions are reported with OBS/FCST conditions on all AIRMET types. TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. - + @@ -105,21 +134,21 @@ TC TOP (ABV and BLW) conditions are represented by the vertical component of the The expected direction of movement of a meteorological condition. When no movement is expected, this is a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason and the speedOfMotion will be 0. Direction of motion to shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". - + The expected geographic region(s) affected by the reported phenomenon at a particular time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of phenomenon historically reported in ICAO Annex 3 / WMO No. 49-2: a boundary with a base and top, a TC centre position, and a VA line with a width - The reported relational operator for the airspace geometry lower limit. When reported, this operator is reported in conjunction with the airspace geometry's lower limit. + The reported relational operator for the airspace geometry lower limit. When reported, this operator is reported in conjunction with the airspace geometry's lower limit. To report an airspace lower limit of below FL 300, airspace lower limit is reported as FL 300 and the operator is reported as "below". When no operator is reported, the airspace lower limit represents an exact value with identical semantics to other measured quantities - The reported relational operator for the airspace geometry upper limit. When reported, this operator is reported in conjunction with the airspace geometry's upper limit. + The reported relational operator for the airspace geometry upper limit. When reported, this operator is reported in conjunction with the airspace geometry's upper limit. To report an airspace upper limit of above FL 300, airspace upper limit is reported as FL 300 and the operator is reported as "above". When no operator is reported, the airspace upper limit represents an exact value with identical semantics to other measured quantities @@ -143,7 +172,7 @@ Cloud base and top may differ from but should be within the AIRMET base and top - The cloud top of reported clouds. Only used with an AIRMET reporting cloud phenomenon. Height of cloud top shall be given in either "m" (metres) or "[ft_i]" (feet). + The cloud top of reported clouds. Only used with an AIRMET reporting cloud phenomenon. Height of cloud top shall be given in either "m" (metres) or "[ft_i]" (feet). Cloud base and top may differ from but should be within the AIRMET base and top which are reported in airspace upper and lower limits. @@ -178,7 +207,7 @@ Appendix 6 Section 2.1 - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element AIRMETEvolvingCondition @@ -187,11 +216,6 @@ Appendix 6 Section 2.1 The expected change in intensity for the reported meteorological condition (e.g., intensifying, weakening, or no change) determined at the time of AIRMET analysis based on the current state of the meteorological condition - - - Indication whether the information is observed and expected to continue, or forecast - - Indicator of whether the location of phenomena is approximate. If not reported locations are not approximate @@ -200,9 +224,9 @@ Appendix 6 Section 2.1 - + - + @@ -226,9 +250,7 @@ Appendix 6 Section 2.1 - Expected change in intensity for (significant) meteorological phenomena. - -This is a copy of the ExpectedIntensityChange enumeration found in IWXXM 1.0. This copy removes the need for a dependency on IWXXM. + Expected change in intensity for AIRMET phenomena. See WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 20 028 'Expected change in intensity'. diff --git a/IWXXM/common.xsd b/IWXXM/common.xsd index bfe3164f..33e04617 100644 --- a/IWXXM/common.xsd +++ b/IWXXM/common.xsd @@ -1,6 +1,5 @@ - - + @@ -16,13 +15,7 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - - - - Extension block for optional and/or additional parameters - - - + The permissible usage of this report (operational or non-operational) @@ -80,7 +73,7 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - Forecast cloud conditions, including predicted vertical visibility and cloud layers. + Forecast cloud conditions, including predicted vertical visibility and cloud layers. A single vertical visibility may be reported, but cannot be reported with cloud layers. @@ -99,10 +92,18 @@ Vertical visibility shall be reported either in meters ("m") or feet ("[ft_i]"). - + + + + + + + + + - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element AerodromeCloudForecast @@ -118,7 +119,7 @@ Vertical visibility shall be reported either in meters ("m") or feet ("[ft_i]"). - A forecast of wind conditions at an aerodrome. + A forecast of wind conditions at an aerodrome. Wind direction shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". A true north wind is indicated with a direction of 360. Calm wind is indicated with a direction of 0. Wind speeds and gusts, if present, shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). @@ -128,13 +129,7 @@ This extends AerodromeSurfaceWindTrendForecast to allow for a variable wind dire - - - - Extension block for optional and/or additional parameters - - - + Indicates variable wind direction. Cannot be reported with a mean wind direction @@ -179,7 +174,7 @@ Wind speeds shall be provided in either two units of measures: "m/s" or "[kn_i]" - Indication that the mean wind speed is above or below the reported value. To report a wind speed of at least 49 meters per second, wind speed is reported as 49 meters per second and the operator is reported as "above". + Indication that the mean wind speed is above or below the reported value. To report a wind speed of at least 49 meters per second, wind speed is reported as 49 meters per second and the operator is reported as "above". When no operator is reported, wind speed is an exact value with identical semantics to other measured quantities. @@ -196,11 +191,16 @@ Wind gusts shall be provided in either two units of measures: "m/s" or "[kn_i]" - Indication that the wind gust speed is above or below the reported value. To report a wind gust speed of at least 49 meters per second, wind gust speed is reported as 49 meters per second and the operator is reported as "above". + Indication that the wind gust speed is above or below the reported value. To report a wind gust speed of at least 49 meters per second, wind gust speed is reported as 49 meters per second and the operator is reported as "above". When no operator is reported, wind gust speed is an exact value with identical semantics to other measured quantities. + + + Extension block for optional and/or additional parameters for element AerodromeSurfaceWindTrendForecast + + @@ -216,7 +216,7 @@ When no operator is reported, wind gust speed is an exact value with identical s - + The observed cloud amount @@ -231,11 +231,16 @@ Measured cloud bases shall be reported in meters ("m") or feet ("[ft_i]"). - + The observed significant cloud types: cumulonimbus or towering cumulus + + + Extension block for optional and/or additional parameters for element CloudLayer + + diff --git a/IWXXM/examples/airmet-A6-1a-TS.xml b/IWXXM/examples/airmet-A6-1a-TS.xml index a42df42f..e12dd429 100644 --- a/IWXXM/examples/airmet-A6-1a-TS.xml +++ b/IWXXM/examples/airmet-A6-1a-TS.xml @@ -6,13 +6,13 @@ YUDD SHANLON FIR ISOL TS OBS N OF S50 TOP ABV FL100 STNR WKN --> @@ -22,7 +22,7 @@ - BASELINE + SNAPSHOT YUDD FIC FIC YUDD @@ -35,7 +35,7 @@ - BASELINE + SNAPSHOT YUDD MWO MWO YUDD @@ -55,15 +55,13 @@ + - + - - - 2014-05-15T15:00:00Z - - + + @@ -87,36 +85,10 @@ - BASELINE + SNAPSHOT FIR YUCC AMSWELL FIR - - - - - 600 - SFC - GND - SFC - - - - - - - - 60.0 -30.0 60.0 -10.0 54.0 -10.0 53.0 -15.0 51.0 -15.0 51.0 -8.0 45.0 -8.0 45.0 -30.0 60.0 - - - - - - - - - - @@ -126,40 +98,36 @@ - - - 315 - - + + + + + + - 500 - - - - - - - - - - - 27.1 -73.1 - 150 - - - - - - - - - - + 100 + STD + + + + + + + + -50.0 50.0 -50.0 70.0 -40.0 70.0 -40.0 50.0 -50.0 50.0 + + + + + + - - 10 - + + ABOVE + 0 + + + diff --git a/IWXXM/examples/airmet-translation-failed.xml b/IWXXM/examples/airmet-translation-failed.xml index 7cc40c35..36e999ad 100644 --- a/IWXXM/examples/airmet-translation-failed.xml +++ b/IWXXM/examples/airmet-translation-failed.xml @@ -7,13 +7,13 @@ YUDD SHANLON FIR INVALID TS OBS N OF S50 TOP ABV FL100 STNR WKN --> - BASELINE + SNAPSHOT YUDD FIC FIC YUDD @@ -45,7 +45,7 @@ - BASELINE + SNAPSHOT YUDD MWO MWO YUDD diff --git a/IWXXM/examples/metar-A3-1.xml b/IWXXM/examples/metar-A3-1.xml index 09008626..f93fb447 100644 --- a/IWXXM/examples/metar-A3-1.xml +++ b/IWXXM/examples/metar-A3-1.xml @@ -5,14 +5,14 @@ METAR YUDO 221630Z 24004MPS 0600 R12/1000U DZ FG SCT010 OVC020 17/16 Q1018 BECMG TL1700 0800 FG BECMG AT1800 9999 NSW --> - - + @@ -52,7 +52,7 @@ - BASELINE + SNAPSHOT YUDO DONLON/INTERNATIONAL YUDO @@ -92,7 +92,7 @@ - BASELINE + SNAPSHOT 12 @@ -125,7 +125,7 @@ - + @@ -148,7 +148,7 @@ - + diff --git a/IWXXM/examples/metar-EDDF-runwaystate.xml b/IWXXM/examples/metar-EDDF-runwaystate.xml index 045862fb..69751790 100644 --- a/IWXXM/examples/metar-EDDF-runwaystate.xml +++ b/IWXXM/examples/metar-EDDF-runwaystate.xml @@ -4,7 +4,7 @@ resulting METAR (FM 15): METAR EDDF 120550Z 03015KT 1400 R07R/P2000N R07C/P2000N R07L/1900U SN DRSN BR VV/// M04/M04 Q1000 R07R/11//90 R07C/15//90 R07L/15//90 BECMG 4000 NSW --> - - + 2013-03-12T05:50:00Z @@ -41,7 +41,7 @@ - BASELINE + SNAPSHOT EDDF FRANKFURT AM MAIN INTERNATIONAL EDDF @@ -116,7 +116,7 @@ - BASELINE + SNAPSHOT 07R 70 @@ -124,7 +124,7 @@ - + @@ -135,7 +135,7 @@ - BASELINE + SNAPSHOT 07C 70 @@ -154,7 +154,7 @@ - BASELINE + SNAPSHOT 07L 70 @@ -173,7 +173,7 @@ - + diff --git a/IWXXM/examples/metar-LKKV.xml b/IWXXM/examples/metar-LKKV.xml index 8826489f..3ccab6d7 100644 --- a/IWXXM/examples/metar-LKKV.xml +++ b/IWXXM/examples/metar-LKKV.xml @@ -1,5 +1,5 @@ - - + 2007-07-25T12:00:00Z @@ -35,7 +35,7 @@ - BASELINE + SNAPSHOT LKKV KARLOVY VARY INTERNATIONAL LKKV @@ -63,14 +63,30 @@ - + + + + + + + + + SNAPSHOT + 18C + + + + + + + - BASELINE + SNAPSHOT 11 diff --git a/IWXXM/examples/metar-NIL.xml b/IWXXM/examples/metar-NIL.xml index d3160ad0..b981f35c 100644 --- a/IWXXM/examples/metar-NIL.xml +++ b/IWXXM/examples/metar-NIL.xml @@ -3,14 +3,14 @@ An example of a NIL METAR: METAR YUDO 221630Z NIL --> - - + @@ -50,7 +50,7 @@ - BASELINE + SNAPSHOT YUDO DONLON/INTERNATIONAL YUDO diff --git a/IWXXM/examples/metar-translation-failed.xml b/IWXXM/examples/metar-translation-failed.xml new file mode 100644 index 00000000..27693215 --- /dev/null +++ b/IWXXM/examples/metar-translation-failed.xml @@ -0,0 +1,68 @@ + + + + + + + + + + 2012-08-22T16:30:00Z + + + + + 2012-08-22T16:40:00Z + + + + + WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 3 TECHNICAL SPECIFICATIONS RELATED TO METEOROLOGICAL OBSERVATIONS AND REPORTS + + + + + + + + + + + + SNAPSHOT + YUDO + DONLON/INTERNATIONAL + YUDO + + + + + + + + + + + + diff --git a/IWXXM/examples/sigmet-A6-1a-TS.xml b/IWXXM/examples/sigmet-A6-1a-TS.xml index 1bc279ee..e2ba66f5 100644 --- a/IWXXM/examples/sigmet-A6-1a-TS.xml +++ b/IWXXM/examples/sigmet-A6-1a-TS.xml @@ -5,13 +5,13 @@ YUDD SIGMET 2 VALID 101200/101600 YUSO – YUDD SHANLON FIR/UIR OBSC TS FCST S OF N54 AND E OF W012 TOP FL390 MOV E 20KT WKN --> - - BASELINE + SNAPSHOT YUDD FIC FIC YUDD @@ -37,7 +37,7 @@ - BASELINE + SNAPSHOT YUSO MWO MWO YUSO @@ -62,7 +62,7 @@ - + @@ -89,7 +89,7 @@ - BASELINE + SNAPSHOT OTHER:FIR_UIR YUDD SHANLON FIR/UIR @@ -102,34 +102,37 @@ - - 90 - - + + + + 90 + + - 390 - STD - - - - - - - - - 54.0 -12.0 54.0 -8.0 50.0 -8.0 50.0 -12.0 54.0 -12.0 - - - - - - - + 390 + STD + + + + + + + + + 54.0 -12.0 54.0 -8.0 50.0 -8.0 50.0 -12.0 54.0 -12.0 + + + + + + + - - 20 - + + 20 + + + diff --git a/IWXXM/examples/sigmet-A6-1b-CNL.xml b/IWXXM/examples/sigmet-A6-1b-CNL.xml index e5fa52a6..9baee979 100644 --- a/IWXXM/examples/sigmet-A6-1b-CNL.xml +++ b/IWXXM/examples/sigmet-A6-1b-CNL.xml @@ -5,13 +5,13 @@ YUDD SIGMET 3 VALID 101345/101600 YUSO YUDD SHANLON FIR/UIR CNL SIGMET 2 101200/101600 --> - - BASELINE + SNAPSHOT YUDD FIC FIC YUDD @@ -38,7 +38,7 @@ - BASELINE + SNAPSHOT YUSO MWO MWO YUSO @@ -70,7 +70,7 @@ - + @@ -92,7 +92,7 @@ - BASELINE + SNAPSHOT OTHER:FIR_UIR YUDD SHANLON FIR/UIR diff --git a/IWXXM/examples/sigmet-A6-2-TC.xml b/IWXXM/examples/sigmet-A6-2-TC.xml index 25ace2e0..b7c86244 100644 --- a/IWXXM/examples/sigmet-A6-2-TC.xml +++ b/IWXXM/examples/sigmet-A6-2-TC.xml @@ -6,13 +6,13 @@ YUCC AMSWELL FIR TC GLORIA PSN N2706 W07306 CB OBS AT 1600Z WI 250NM OF TC CENTRE TOP FL500 NC FCST AT 2200Z TC CENTRE PSN N2740 W07345 --> - - BASELINE + SNAPSHOT YUCC FIC FIC YUCC @@ -38,7 +38,7 @@ - BASELINE + SNAPSHOT YUDO MWO MWO YUDO @@ -63,7 +63,7 @@ - + @@ -93,7 +93,7 @@ - BASELINE + SNAPSHOT FIR YUCC AMSWELL FIR @@ -107,38 +107,42 @@ - - - - - 500 - STD - - - - - - - - - - - 27.10 -73.10 - 250 - - - - - - - - - - - - - + + + + + + + 500 + STD + + + + + + + + + + + 27.10 -73.10 + 250 + + + + + + + + + + + + + + + @@ -146,7 +150,7 @@ - + @@ -165,10 +169,10 @@ - + - + @@ -195,9 +199,9 @@ - + - + diff --git a/IWXXM/examples/sigmet-VA-EGGX.xml b/IWXXM/examples/sigmet-VA-EGGX.xml index 7deb0fce..bffb79fb 100644 --- a/IWXXM/examples/sigmet-VA-EGGX.xml +++ b/IWXXM/examples/sigmet-VA-EGGX.xml @@ -1,12 +1,10 @@ - - BASELINE + SNAPSHOT SHANWICK OCEANIC AREA CONTROL CENTRE ATCC EGGX @@ -40,7 +38,7 @@ FCST 2200Z SFC/FL550 N OF N6100 W01100 – N5800 W01400 – N6100 W01600= - BASELINE + SNAPSHOT UK METEOROLOGICAL OFFICE - EXETER MWO EGRR @@ -58,15 +56,19 @@ FCST 2200Z SFC/FL550 N OF N6100 W01100 – N5800 W01400 – N6100 W01600= - + YYYY-MM-25T16:00:00Z - - + + + + WMO No. 49 Volume 2 Meteorological Service for International Air Navigation [C.3.1.]7 SIGMET AND AIRMET INFORMATION, AERODROME WARNINGS AND WIND SHEAR WARNINGS AND ALERTS + + @@ -76,7 +78,7 @@ FCST 2200Z SFC/FL550 N OF N6100 W01100 – N5800 W01400 – N6100 W01600= - BASELINE + SNAPSHOT FIR EGGX SHANWICK OCEANIC FIR @@ -89,44 +91,50 @@ FCST 2200Z SFC/FL550 N OF N6100 W01100 – N5800 W01400 – N6100 W01600= - - + + + + 180 + - - 550 - STD - - - - - - - - - 60.0 -11.5 - 59.0 -13.0 - 60.0 -16.0 - 60.0 -11.5 - - - - - - - + + 550 + STD + + + + + + + + + 60.0 -11.5 + 59.0 -13.0 + 60.0 -16.0 + 60.0 -11.5 + + + + + + + - - + + 60 + + + - + YYYY-MM-25T22:00:00Z @@ -138,14 +146,11 @@ FCST 2200Z SFC/FL550 N OF N6100 W01100 – N5800 W01400 – N6100 W01600= - + - + - - 550 - STD @@ -167,9 +172,9 @@ FCST 2200Z SFC/FL550 N OF N6100 W01100 – N5800 W01400 – N6100 W01600= - + - + diff --git a/IWXXM/examples/sigmet-multi-location.xml b/IWXXM/examples/sigmet-multi-location.xml new file mode 100644 index 00000000..67a1f2fb --- /dev/null +++ b/IWXXM/examples/sigmet-multi-location.xml @@ -0,0 +1,230 @@ + + + + + + + + + SNAPSHOT + SHANWICK OCEANIC AREA CONTROL CENTRE + ATCC + YUDD + + + + + + + + + + SNAPSHOT + UK METEOROLOGICAL OFFICE - EXETER + MWO + YUSO + + + + + 2 + + + YYYY-MM-10T12:00:00Z + YYYY-MM-10T18:00:00Z + + + + + + + + + + YYYY-MM-10T12:00:00Z + + + + + + + + + + + + + + + SNAPSHOT + OTHER:FIR_UIR + YUDD + SHANLON FIR/UIR + + + + + + + + + + + + + + + + + 370 + STD + 250 + STD + + + + + + + 43.15 21.15 43.45 21.45 43.30 22.15 42.45 22.30 42.30 21.45 43.15 21.15 + + + + + + + + + + + + + + + + + 300 + STD + 150 + STD + + + + + + + 42.00 21.15 42.17 21.30 41.45 22.00 41.30 21.30 42.00 21.15 + + + + + + + + + + + + + + + + + + + + YYYY-MM-10T18:00:00Z + + + + + + + + + + + + + + + + + + + + + 43.30 22.15 43.15 23.45 41.45 23.15 42.30 22.00 43.30 22.15 + + + + + + + + + + + + + + + + + + + + + + 42.00 21.45 41.45 22.15 41.00 22.15 41.30 21.30 42.00 21.45 + + + + + + + + + + + + + + + + + MT ASHVAL + + + 43.15 21.15 + + + + + \ No newline at end of file diff --git a/IWXXM/examples/sigmet-translation-failed.xml b/IWXXM/examples/sigmet-translation-failed.xml new file mode 100644 index 00000000..f83ea581 --- /dev/null +++ b/IWXXM/examples/sigmet-translation-failed.xml @@ -0,0 +1,67 @@ + + + + + + + + + + SNAPSHOT + YUCC FIC + FIC + YUCC + + + + + + + + + + SNAPSHOT + YUDO MWO + MWO + YUDO + + + + + + 3 + + + + 2014-05-25T16:00:00 + 2014-05-25T22:00:00 + + + + + + + + \ No newline at end of file diff --git a/IWXXM/examples/speci-A3-2.xml b/IWXXM/examples/speci-A3-2.xml index 9f292739..3e7b14d9 100644 --- a/IWXXM/examples/speci-A3-2.xml +++ b/IWXXM/examples/speci-A3-2.xml @@ -5,14 +5,14 @@ SPECI YUDO 151115Z 05025G37KT 3000 1200NE+TSRA BKN005CB 25/22 Q1008 TEMPO TL1200 0600 BECMG AT1200 8000 NSW NSC --> - - + @@ -52,7 +52,7 @@ - BASELINE + SNAPSHOT YUDO DONLON/INTERNATIONAL YUDO @@ -106,7 +106,7 @@ - + @@ -128,7 +128,7 @@ - + diff --git a/IWXXM/examples/taf-A5-1.xml b/IWXXM/examples/taf-A5-1.xml index cef9abb6..0efd870c 100644 --- a/IWXXM/examples/taf-A5-1.xml +++ b/IWXXM/examples/taf-A5-1.xml @@ -4,12 +4,12 @@ TAF YUDO 151800Z 1600/1618 13005MPS 9000 BKN020 BECMG 1606/1608 SCT015CB BKN020 TEMPO 1608/1612 17006G12MPS 1000 TSRA SCT010CB BKN020 FM161230 15004MPS 9999 BKN020 --> - - + @@ -56,7 +56,7 @@ - BASELINE + SNAPSHOT YUDO DONLON/INTERNATIONAL YUDO @@ -99,7 +99,7 @@ - + 2012-08-16T06:00:00Z @@ -139,7 +139,7 @@ - + 2012-08-16T08:00:00Z @@ -191,7 +191,7 @@ - + 2012-08-16T12:30:00Z diff --git a/IWXXM/examples/taf-A5-2.xml b/IWXXM/examples/taf-A5-2.xml index 7764d96e..7f508819 100644 --- a/IWXXM/examples/taf-A5-2.xml +++ b/IWXXM/examples/taf-A5-2.xml @@ -4,11 +4,11 @@ TAF AMD YUDO 161500Z 1600/1618 CNL --> - - BASELINE + SNAPSHOT YUDO DONLON/INTERNATIONAL YUDO diff --git a/IWXXM/examples/taf-NIL.xml b/IWXXM/examples/taf-NIL.xml index 22f7e669..bb60c662 100644 --- a/IWXXM/examples/taf-NIL.xml +++ b/IWXXM/examples/taf-NIL.xml @@ -3,14 +3,14 @@ An example of a NIL TAF: TAF YUDO 160000Z NIL --> - - + @@ -47,7 +47,7 @@ - BASELINE + SNAPSHOT YUDO DONLON/INTERNATIONAL YUDO diff --git a/IWXXM/examples/taf-translation-failed.xml b/IWXXM/examples/taf-translation-failed.xml new file mode 100644 index 00000000..27d4324f --- /dev/null +++ b/IWXXM/examples/taf-translation-failed.xml @@ -0,0 +1,42 @@ + + + + + + + + 2012-08-15T18:00:00Z + + + + + + + 2012-08-16T00:00:00Z + 2012-08-16T18:00:00Z + + + + + diff --git a/IWXXM/examples/tc-advisory-A2-2.xml b/IWXXM/examples/tc-advisory-A2-2.xml index d8b5e354..132baddb 100644 --- a/IWXXM/examples/tc-advisory-A2-2.xml +++ b/IWXXM/examples/tc-advisory-A2-2.xml @@ -24,12 +24,12 @@ NXT MSG: 20040925/2000Z --> @@ -48,7 +48,7 @@ NXT MSG: 20040925/2000Z - BASELINE + SNAPSHOT 2004-01-01T00:00:00Z @@ -232,9 +232,6 @@ NXT MSG: 20040925/2000Z - - - 2004-09-25T20:00:00Z diff --git a/IWXXM/examples/tc-advisory-translation-failed.xml b/IWXXM/examples/tc-advisory-translation-failed.xml new file mode 100644 index 00000000..f9bcf8ed --- /dev/null +++ b/IWXXM/examples/tc-advisory-translation-failed.xml @@ -0,0 +1,71 @@ + + + + + + + 2004-09-25T16:00:00Z + + + + + + + + + + 2004-01-01T00:00:00Z + + + + SNAPSHOT + + + 2004-01-01T00:00:00Z + + + + OTHER:TCAC + YUFO + + + + + + GLORIA + 0 + + + + + + + + + \ No newline at end of file diff --git a/IWXXM/examples/va-advisory-A2-1.xml b/IWXXM/examples/va-advisory-A2-1.xml index 533b32f3..7c829757 100644 --- a/IWXXM/examples/va-advisory-A2-1.xml +++ b/IWXXM/examples/va-advisory-A2-1.xml @@ -30,12 +30,12 @@ NXT ADVISORY: 20080923/0730Z --> @@ -54,7 +54,7 @@ NXT ADVISORY: 20080923/0730Z - BASELINE + SNAPSHOT 2008-01-01T00:00:00Z @@ -74,7 +74,7 @@ NXT ADVISORY: 20080923/0730Z KARYMSKY 1000-13 - 54.03 159.27 1536 + 54.03 159.27 1536 2008-09-23T01:30:00Z diff --git a/IWXXM/examples/va-advisory-translation-failed.xml b/IWXXM/examples/va-advisory-translation-failed.xml new file mode 100644 index 00000000..699fde81 --- /dev/null +++ b/IWXXM/examples/va-advisory-translation-failed.xml @@ -0,0 +1,84 @@ + + + + + + + 2008-09-23T01:30:00Z + + + + + + + + + + 2008-01-01T00:00:00Z + + + + SNAPSHOT + + + 2008-01-01T00:00:00Z + + + + TOKYO + OTHER:VACC + + + + + + + + FL300 REPORTED + KARYMSKY 1000-13 + + + 54.03 159.27 1536 + + + 2008-09-23T01:30:00Z + + + + + + + + + \ No newline at end of file diff --git a/IWXXM/iwxxm-collect.xsd b/IWXXM/iwxxm-collect.xsd index a5b3591a..c4058d48 100644 --- a/IWXXM/iwxxm-collect.xsd +++ b/IWXXM/iwxxm-collect.xsd @@ -1,6 +1,6 @@ - + A convenience schema file for validating against IWXXM and WMO Collect. This is useful for XML validators (such as libxml2) that allow only a single schema location. diff --git a/IWXXM/iwxxm.xsd b/IWXXM/iwxxm.xsd index 6bed9d75..83a091ca 100644 --- a/IWXXM/iwxxm.xsd +++ b/IWXXM/iwxxm.xsd @@ -1,5 +1,5 @@ - + diff --git a/IWXXM/measures.xsd b/IWXXM/measures.xsd index 24cba262..4e3e8227 100644 --- a/IWXXM/measures.xsd +++ b/IWXXM/measures.xsd @@ -1,5 +1,5 @@ - + Common measured quantities used across multiple packages. diff --git a/IWXXM/metarSpeci.xsd b/IWXXM/metarSpeci.xsd index a697ee7b..d4b93b06 100644 --- a/IWXXM/metarSpeci.xsd +++ b/IWXXM/metarSpeci.xsd @@ -1,6 +1,5 @@ - - + @@ -9,9 +8,9 @@ METAR and SPECI reports include identical information but are issued for different purposes. -METAR reports are routine observations made at an aerodrome throughout the day. METAR observations are made (and distributed) at intervals of one hour or, if so determined by regional air navigation agreement, at intervals of one half-hour. +METAR reports are routine observations made at an aerodrome throughout the day. METAR observations are made (and distributed) at intervals of one hour or, if so determined by regional air navigation agreement, at intervals of one half-hour. -SPECI reports are special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations are made (and distributed) in accordance with criteria established by the meteorological authority, in consultation with the appropriate ATS authority, operators and others concerned. +SPECI reports are special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations are made (and distributed) in accordance with criteria established by the meteorological authority, in consultation with the appropriate ATS authority, operators and others concerned. References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. @@ -29,16 +28,11 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha The observation which resulted in the current meteorological conditions at an aerodrome - + The process that results in a trend forecast. When no change is expected to occur during a forecast period ("NOSIG") this is indicated by a single missing trend forecast with a nil reason of noSignificantChange - - - Extension block for optional and/or additional parameters - - @@ -62,7 +56,7 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - A special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations are made (and distributed) in accordance with criteria established by the meteorological authority, in consultation with the appropriate ATS authority, operators and others concerned. + A special (i.e., non-routine) observation made at an aerodrome as needed. SPECI observations are made (and distributed) in accordance with criteria established by the meteorological authority, in consultation with the appropriate ATS authority, operators and others concerned. The information contained in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine report on conditions at an aerodrome. @@ -76,7 +70,13 @@ See ICAO Annex 3 / WMO No. 49-2 Table A3-2 - + + + + Extension block for optional and/or additional parameters for element SPECI + + + @@ -89,7 +89,7 @@ See ICAO Annex 3 / WMO No. 49-2 Table A3-2 - A routine observation made at an aerodrome throughout the day. METAR observations are made (and distributed) at intervals of one hour or, if so determined by regional air navigation agreement, at intervals of one half-hour. + A routine observation made at an aerodrome throughout the day. METAR observations are made (and distributed) at intervals of one hour or, if so determined by regional air navigation agreement, at intervals of one half-hour. The information contained in METAR and SPECI is identical. SPECI is issued when conditions merit a non-routine report on conditions at an aerodrome. @@ -101,7 +101,13 @@ See ICAO Annex 3 / WMO No. 49-2 Table A3-2 - + + + + Extension block for optional and/or additional parameters for element METAR + + + @@ -137,17 +143,17 @@ Prevailing horizontal visibility shall be reported in meters ("m"). The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility. -To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities - - + + - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element MeteorologicalAerodromeTrendForecastRecord @@ -175,7 +181,7 @@ When CAVOK conditions are observed, no other information on visibility, runway v - A specialized Record type containing meteorological conditions observed at an aerodrome. + A specialized Record type containing meteorological conditions observed at an aerodrome. When no clouds of operational significance or no weather of operational significance is observed, the NothingOfOperationalSignificance nilReason is used for the cloud or presentWeather association. When no clouds were detected by the automatic observing system, the NotDetectedByAutoSystem nilReason is used for the cloud association. @@ -219,15 +225,23 @@ Measured altimeter setting shall be given in hectoPascals ("hPa"). - - + + + + + + + + + + - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element MeteorologicalAerodromeObservationRecord @@ -276,7 +290,7 @@ WMO reporting procedures require that contamination is reported in the following - less than 10%; - between 11% and 25%; - between 26% and 50%; and -- more than 50%. +- more than 50%. See WMO No. 306: - WMO Code table 0519 @@ -306,6 +320,11 @@ WMO 306: Table 0366 + + + Extension block for optional and/or additional parameters for element AerodromeRunwayState + + @@ -367,11 +386,16 @@ Section 4.3.6.6 - The reported relational operator for the mean RVR. When reported, this operator is reported in conjunction with mean RVR. + The reported relational operator for the mean RVR. When reported, this operator is reported in conjunction with mean RVR. To report a mean RVR of at least 2000 metres, mean RVR is reported as 2000 metres and the operator is reported as "above". To report a mean RVR of less than 50 metres, mean RVR is reported as 50 metres and the operator is reported as "below". When no operator is reported, mean RVR represents an exact value with identical semantics to other measured quantities + + + Extension block for optional and/or additional parameters for element AerodromeRunwayVisualRange + + @@ -431,6 +455,11 @@ WMO 306: Table 3700 + + + Extension block for optional and/or additional parameters for element AerodromeSeaState + + @@ -451,6 +480,11 @@ Table 3700 The specific runway(s) affected by wind shear at this aerodrome. No specific runways are reported when all runways are affected by wind shear + + + Extension block for optional and/or additional parameters for element AerodromeWindShear + + @@ -485,7 +519,20 @@ When the sky is obscured and the value of the vertical visibility cannot be dete - + + + + + + + + + + + + Extension block for optional and/or additional parameters for element AerodromeObservedClouds + + @@ -496,7 +543,7 @@ When the sky is obscured and the value of the vertical visibility cannot be dete - An aggregation of surface wind conditions typically reported together at an aerodrome, including wind direction information, wind speed, and wind gusts. + An aggregation of surface wind conditions typically reported together at an aerodrome, including wind direction information, wind speed, and wind gusts. Wind direction is reported according to ICAO Annex 3 / WMO No. 49-2 Section 4.1.5.2b: "variations from the mean wind direction during the past 10 minutes is reported as follows, if the total variation is 60 or more: @@ -534,7 +581,7 @@ Wind speeds shall be provided in either two units of measures: "m/s" or "[kn_i]" - Indication that the mean wind speed is above or below the reported value. To report a wind speed of at least 49 meters per second, wind speed is reported as 49 meters per second and the operator is reported as "above". + Indication that the mean wind speed is above or below the reported value. To report a wind speed of at least 49 meters per second, wind speed is reported as 49 meters per second and the operator is reported as "above". When no operator is reported, wind speed is an exact value with identical semantics to other measured quantities. @@ -554,7 +601,7 @@ Wind gusts shall be provided in either two units of measures: "m/s" or "[kn_i]" - Indication that the wind gust speed is above or below the reported value. To report a wind gust speed of at least 49 meters per second, wind gust speed is reported as 49 meters per second and the operator is reported as "above". + Indication that the wind gust speed is above or below the reported value. To report a wind gust speed of at least 49 meters per second, wind gust speed is reported as 49 meters per second and the operator is reported as "above". When no operator is reported, wind gust speed is an exact value with identical semantics to other measured quantities. @@ -581,6 +628,11 @@ Section 4.1.5.2b + + + Extension block for optional and/or additional parameters for element AerodromeSurfaceWind + + @@ -596,7 +648,7 @@ Section 4.1.5.2b - An aggregation of horizontal visibility conditions typically reported together at an aerodrome, including the prevailing visibility and minimum visibility. + An aggregation of horizontal visibility conditions typically reported together at an aerodrome, including the prevailing visibility and minimum visibility. Direction of minimum visibility shall be given in degrees from true North. Plane angle unit of measure (uom) is "deg". Measured prevailing and minimum horizontal visibility, if present, shall be reported in meters ("m") only. @@ -628,7 +680,7 @@ Section 4.2.4.4b The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility. -To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities @@ -641,11 +693,9 @@ Measured minimum visibility shall be reported in meters ("m") only. ICAO Annex 3 / WMO No. 49-2 Section 4.2.4.4a: "When the visibility is not the same in different directions and -a) when the lowest visibility is different from the prevailing visibility, and - 1) less than 1 500 m or - 2) less than 50 percent of the prevailing visibility and less than 5000 m; the lowest visibility observed should also be reported and,when possible, its general direction in relation to the aerodrome reference point indicated by reference to one of the -eight points of the compass. If the lowest visibility is observed in more than one direction, then the most -operationally significant direction should be reported; and +a) when the lowest visibility is different from the prevailing visibility, and + 1) less than 1500 m or + 2) less than 50 percent of the prevailing visibility and less than 5000 m; the lowest visibility observed should also be reported and,when possible, its general direction in relation to the aerodrome reference point indicated by reference to one of the eight points of the compass. If the lowest visibility is observed in more than one direction, then the most operationally significant direction should be reported; and b) when the visibility is fluctuating rapidly, and the prevailing visibility cannot be determined, only the lowest visibility should be reported, with no indication of direction." @@ -663,6 +713,11 @@ Direction of minimum visibility shall be given in degrees from true North. Plane + + + Extension block for optional and/or additional parameters for element AerodromeHorizontalVisibility + + @@ -680,11 +735,6 @@ Defined in WMO No. 306 Vol I.1; FM-15 METAR, FM-16 SPECI and FM-51 TAF. Also see WMO No. 306 Vol I.2 Part B FM 94 BUFR code-table 0 08 016 'Change qualifier of a trend forecast or an aerodrome forecast'. - - - No significant changes are forecast (NOSIG) - - When the change is forecast to commence at the beginning of the forecast period and be completed by the end of that period, or when the change is forecast to occur within the forecast period but the time of the change is uncertain (possibly shortly after the beginning of the forecast period, or midway or near the end of that period), the change is indicated by only the change indicator BECMG. @@ -818,7 +868,6 @@ See WMO No. 306 Vol I.1 code table 0919 and WMO No. 306 Vol I.2 FM 94 BUFR code - Extent of runway surface that is contaminated (covered) diff --git a/IWXXM/rule/iwxxm-collect.sch b/IWXXM/rule/iwxxm-collect.sch index 397d0ab2..edff4d75 100644 --- a/IWXXM/rule/iwxxm-collect.sch +++ b/IWXXM/rule/iwxxm-collect.sch @@ -1,6 +1,638 @@ Schematron validation - - + + + + + + + + + + + + COLLECT.MB1: All meteorologicalInformation instances in MeteorologicalBulletin must be of the same type + + + + + METAR_SPECI.ARS1: When all runways are being reported upon, no specific Runway should be reported + + + + + METAR_SPECI.ARS2: When a single Runway is reported upon, the allRunways flag should be missing or false + + + + + METAR_SPECI.ARVR1: meanRVR shall be reported in metres (m). + + + + + METAR_SPECI.MAORep2: When no clouds are detected by the auto system, this report must be an auto report + + + + + METAR_SPECI.MAORep1: Missing reports only include identifying information (time, aerodrome) and no other information + + + + + METAR_SPECI.MAORep6: The sampled feature should be equal in observation and trendForecast + + + + + METAR_SPECI.MAORep3: The sampled feature for a METAR/SPECI observation is an aerodrome + + + + + METAR_SPECI.MAORep7: The procedure of a METAR/SPECI observation should be a metce:Process + + + + + METAR_SPECI.MAORep4: The result of a METAR/SPECI observation should be a MeteorologicalAerodromeObservationRecord + + + + + METAR_SPECI.MAORep5: The result of a METAR/SPECI trendForecast should be a MeteorologicalAerodromeTrendForecastRecord + + + + + METAR_SPECI.ASS1: If the sea state is set, significantWaveHeight is not reported (one or the other) + + + + + METAR_SPECI.ASS3: Either seaState or significantWaveHeight must be present + + + + + METAR_SPECI.ASS4: seaSurfaceTemperature shall be reported in degrees Celsius (Cel). + + + + + METAR_SPECI.ASS2: If the significantWaveHeight is set, seaState is not reported (one or the other) + + + + + METAR_SPECI.ASS5: significantWaveHeight shall be reported in metres (m). + + + + + METAR_SPECI.AWS1: When all runways are affected by wind shear, no specific runways should be reported + + + + + METAR_SPECI.MATFR5: prevailingVisibility, prevailingVisibilityOperator, clouds, forecastWeather and cloudAndVisibilityOK should be absent when changeIndicator equals 'NO_SIGNIFICANT_CHANGES' + + + + + METAR_SPECI.MATFR1: clouds should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MATFR2: forecastWeather should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MATFR4: prevailingVisibility and prevailingVisibilityOperator should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MATFR3: prevailingVisibility shall be reported in metres (m). + + + + + METAR_SPECI.MAORec6: airTemperature shall be reported in degrees Celsius (Cel). + + + + + METAR_SPECI.MAORec4: clouds should be absent when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec3: presentWeather should not be reported when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec2: rvr should not be reported when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec1: visibility should not be reported when cloudAndVisibilityOK is true + + + + + METAR_SPECI.MAORec7: dewpointTemperature shall be reported in degrees Celsius (Cel). + + + + + METAR_SPECI.MAORec8: qnh shall be reported in hectopascals (hPa). + + + + + METAR_SPECI.MAORec5: Table A3-2 Note 7 states: "To be included if visibility or RVR < 1500 m; for up to a maximum of four runways". This is interpreted to mean that if the prevailing visibility is below 1500 meters, RVR should always be included + + + + + METAR_SPECI.AOC1: Vertical visibility cannot be reported with cloud layers + + + + + METAR_SPECI.AOC2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). + + + + + METAR_SPECI.ASW3: extremeClockwiseWindDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.ASW4: extremeCounterClockwiseWindDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.ASW5: meanWindDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.ASW6: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + METAR_SPECI.ASW2: Wind direction is not reported when variable winds are indicated + + + + + METAR_SPECI.ASW7: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + METAR_SPECI.ASW1: All wind UOMs must be the same + + + + + METAR_SPECI.AHV1: minimumVisibility shall be reported in metres (m). + + + + + METAR_SPECI.AHV2: minimumVisibilityDirection shall be reported in degrees (deg). + + + + + METAR_SPECI.AHV3: prevailingVisibility shall be reported in metres (m). + + + + + TAF.MAFR2: cloud should not be reported when cloudAndVisibilityOK is true + + + + + TAF.MAFR1: prevailingVisibility should not be reported when cloudAndVisibilityOK is true + + + + + TAF.MAFR3: weather should not be reported when cloudAndVisibilityOK is true + + + + + TAF.MAFR4: prevailingVisibility shall be reported in metres (m). + + + + + TAF.AATF1: maximumTemperature shall be reported in degrees Celsius (Cel). + + + + + TAF.AATF2: minimumTemperature shall be reported in degrees Celsius (Cel). + + + + + TAF.TAF1: Forecast conditions cannot include temperature information. They are otherwise identical to the prevailing conditions + + + + + TAF.TAF18: surfaceWind and cloud are mandatory in a non-empty baseForecast + + + + + TAF.TAF3: An amended report must also include the valid time of the amended report + + + + + TAF.TAF4: A cancelled report must also include the valid time of the cancelled report + + + + + TAF.TAF5: A corrected report must reference + + + + + TAF.TAF9: Missing TAF reports only include aerodrome information and issue time information + + + + + TAF.TAF2: previousReportValidPeriod must be null unless this cancels, corrects or amends a previous report + + + + + TAF.TAF11: Non-missing TAF reports must contains validTime + + + + + TAF.TAF8: Base conditions may not have a change indicator + + + + + TAF.TAF14: The sampled feature of baseForecast is always an aerodrome + + + + + TAF.TAF16: The procedure of a TAF baseForecast should be a metce:Process + + + + + TAF.TAF12: The O&M validTime of baseForecast must be a time period for TAF forecasts + + + + + TAF.TAF15: The sampled feature of changeForecast is always an aerodrome + + + + + TAF.TAF17: The procedure of a TAF changeForecast should be a metce:Process + + + + + TAF.TAF13: The O&M validTime of changeForecast must be a time period for TAF forecasts + + + + + TAF.TAF6: resultTime for the baseForecast and the changeForecasts must match + + + + + SIGMET.SIGMET9: SIGMET can not have both a forecastPositionAnalysis and expected speed and/or direction of motion + + + + + SIGMET.SIGMET1: A cancelled SIGMET should only include identifying information (time and airspace) and no other information + + + + + SIGMET.SIGMET2: There must be at least one analysis when a SIGMET does not have canceled status + + + + + SIGMET.SIGMET10: SIGMET must have a cancelled status if reporting volcanicAshMovedToFIR + + + + + SIGMET.SIGMET4: Sampled feature in analysis and forecastPositionAnalysis must be an FIR, UIR, or CTA + + + + + SIGMET.SIGMET7: The procedure of a SIGMET analysis should be a metce:Process + + + + + SIGMET.SIGMET3: OBS and FCST analyses must have a result type of SIGMETEvolvingConditionCollection + + + + + SIGMET.SIGMET8: The procedure of a SIGMET forecastPositionAnalysis should be a metce:Process + + + + + SIGMET.SIGMET5: The result of a forecastPositionAnalysis should be a SIGMETPositionCollection + + + + + SIGMET.SEC1: directionOfMotion shall be reported in degrees (deg). + + + + + SIGMET.SEC3: geometryLowerLimitOperator can either be NULL or BELOW. + + + + + SIGMET.SEC4: geometryUpperLimitOperator can either be NULL or ABOVE + + + + + SIGMET.SEC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + SIGMET.SECC3: The number of SIGMETEvolvingConditionCollection member should be 1 for non-Tropical Cyclone/Volcanic Ash SIGMETs + + + + + SIGMET.SECC2: When SIGMETEvolvingConditionCollection timeIndicator is a forecast, the phenomenonTime must be later than or equal to the beginning of the validPeriod of the report. + + + + + SIGMET.SECC1: When SIGMETEvolvingConditionCollection timeIndicator is an observation, the phenomenonTime must be earlier than or equal to the beginning of the validPeriod of the report. + + + + + SIGMET.SPC1: The number of SIGMETPositionCollection member should be 1 for non-Tropical Cyclone/Volcanic Ash SIGMETs + + + + + AIRMET.AECC2: When AIRMETEvolvingConditionCollection timeIndicator is a forecast, the phenomenonTime must be later than or equal to the beginning of the validPeriod of the report. + + + + + AIRMET.AECC1: When AIRMETEvolvingConditionCollection timeIndicator is an observation, the phenomenonTime must be earlier than or equal to the beginning of the validPeriod of the report. + + + + + AIRMET.AEC1: cloudBase shall be reported in metres (m) or feet ([ft_i]). + + + + + AIRMET.AEC2: cloudTop shall be reported in metres (m) or feet ([ft_i]). + + + + + AIRMET.AEC3: directionOfMotion shall be reported in degrees (deg). + + + + + AIRMET.AEC9: geometryLowerLimitOperator can either be NULL or BELOW. + + + + + AIRMET.AEC10: geometryUpperLimitOperator can either be NULL or ABOVE + + + + + AIRMET.AEC4: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + AIRMET.AEC5: surfaceVisibility shall be reported in metres (m). + + + + + AIRMET.AEC7: surfaceWindDirection shall be reported in the degrees unit of measure ('deg'). + + + + + AIRMET.AEC6: surfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + AIRMET.AEC8: surfaceWindDirection and surfaceWindSpeed must be reported together + + + + + AIRMET.AIRMET5: AIRMET can not have both a forecastPositionAnalysis and expected speed and/or direction of motion + + + + + AIRMET.AIRMET2: A canceled AIRMET only include identifying information (time and airspace) and no other information + + + + + AIRMET.AIRMET3: There must be at least one analysis when a AIRMET does not have canceled status + + + + + AIRMET.AIRMET4: The procedure of an AIRMET analysis should be a metce:Process + + + + + AIRMET.AIRMET1: OBS and FCST classifications must have a result type of AIRMETEvolvingConditionCollection + + + + + TCA.TCFC1: maximumSurfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + TCA.TCA4: The procedure of a TCA forecast should be a metce:Process + + + + + TCA.TCA2: The result of a TCA forecast should be a TropicalCycloneForecastConditions + + + + + TCA.TCA3: The procedure of a TCA observation should be a metce:Process + + + + + TCA.TCA1: The result of a TCA observation should be a TropicalCycloneObservedConditions + + + + + TCA.TCOC1: centralPressure shall be reported in hectopascals (hPa). + + + + + TCA.TCOC2: meanMaxSurfaceWind shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + TCA.TCOC3: movementDirection shall be reported in degrees (deg). + + + + + TCA.TCOC4: movementSpeed shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + VAA.VAC1: directionOfMotion shall be reported in degrees (deg). + + + + + VAA.VAC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + + + VAA.VAC3: windDirection shall be reported in degrees (deg). + + + + + VAA.VAC4: windSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + VAA.VAA2: The procedure of a VAA analysis should be a metce:Process + + + + + VAA.VAA1: The result of a VAA analysis should be a VolcanicAshConditions + + + + + COMMON.CL1: base shall be reported in metres (m) or feet ([ft_i]). + + + + + COMMON.Report4: Total size of extension content must not exceed 5000 characters per report + + + + + COMMON.Report2: Operational reports should not include a permissibleUsageReason + + + + + COMMON.Report1: Non-operational reports must include a permissibleUsageReason + + + + + COMMON.Report3: Translated reports must include translatedBulletinID, translatedBulletinReceptionTime, translationCentreDesignator, translationCentreName, translationTime and optionally translationFailedTAC if translation failed + + + + + COMMON.ACF1: Vertical visibility cannot be reported together with cloud layers + + + + + COMMON.ACF2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). + + + + + COMMON.ASWF1: Wind direction is not reported when variable winds are indicated + + + + + COMMON.ASWTF1: meanWindDirection shall be reported in degrees (deg). + + + + + COMMON.ASWTF2: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + COMMON.ASWTF3: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + IWXXM.ExtensionAlwaysLast: Extension elements should be the last elements in their parents + + diff --git a/IWXXM/rule/iwxxm.sch b/IWXXM/rule/iwxxm.sch index e8ef82b0..924fb01c 100644 --- a/IWXXM/rule/iwxxm.sch +++ b/IWXXM/rule/iwxxm.sch @@ -1,7 +1,7 @@ Schematron validation - + @@ -36,7 +36,7 @@ - METAR_SPECI.MAORep6: The sampled feature should be equal in observation and trendForecast + METAR_SPECI.MAORep6: The sampled feature should be equal in observation and trendForecast @@ -121,7 +121,7 @@ - METAR_SPECI.MAORec4: clouds should be absent when cloudAndVisibilityOK is true + METAR_SPECI.MAORec4: clouds should be absent when cloudAndVisibilityOK is true @@ -181,7 +181,7 @@ - METAR_SPECI.ASW6: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kt_i]). + METAR_SPECI.ASW6: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). @@ -249,6 +249,11 @@ TAF.TAF1: Forecast conditions cannot include temperature information. They are otherwise identical to the prevailing conditions + + + TAF.TAF18: surfaceWind and cloud are mandatory in a non-empty baseForecast + + TAF.TAF3: An amended report must also include the valid time of the amended report @@ -341,7 +346,7 @@ - SIGMET.SIGMET4: Sampled feature in analysis and forecastPositionAnalysis must be an FIR, UIR, or CTA + SIGMET.SIGMET4: Sampled feature in analysis and forecastPositionAnalysis must be an FIR, UIR, or CTA @@ -351,7 +356,7 @@ - SIGMET.SIGMET3: OBS and FCST analyses must have a result type of EvolvingMeteorologicalCondition + SIGMET.SIGMET3: OBS and FCST analyses must have a result type of SIGMETEvolvingConditionCollection @@ -361,97 +366,107 @@ - SIGMET.SIGMET5: The result of a forecastPositionAnalysis should be a MeteorologicalPositionCollection + SIGMET.SIGMET5: The result of a forecastPositionAnalysis should be a SIGMETPositionCollection + + + + + SIGMET.SEC1: directionOfMotion shall be reported in degrees (deg). - - - SIGMET.EMC1: directionOfMotion shall be reported in degrees (deg). + + + SIGMET.SEC3: geometryLowerLimitOperator can either be NULL or BELOW. - - - SIGMET.EMC5: geometryLowerLimitOperator can either be NULL or BELOW. + + + SIGMET.SEC4: geometryUpperLimitOperator can either be NULL or ABOVE - - - SIGMET.EMC6: geometryUpperLimitOperator can either be NULL or ABOVE + + + SIGMET.SEC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). - - - SIGMET.EMC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + SIGMET.SECC3: The number of SIGMETEvolvingConditionCollection member should be 1 for non-Tropical Cyclone/Volcanic Ash SIGMETs - - - SIGMET.EMC4: When SIGMET EvolvingMeteorologicalCondition timeIndicator is a forecast, the phenomenonTime must be later than or equal to the beginning of the validPeriod of the report. + + + SIGMET.SECC2: When SIGMETEvolvingConditionCollection timeIndicator is a forecast, the phenomenonTime must be later than or equal to the beginning of the validPeriod of the report. - - - SIGMET.EMC3: When SIGMET EvolvingMeteorologicalCondition timeIndicator is an observation, the phenomenonTime must be earlier than or equal to the beginning of the validPeriod of the report. + + + SIGMET.SECC1: When SIGMETEvolvingConditionCollection timeIndicator is an observation, the phenomenonTime must be earlier than or equal to the beginning of the validPeriod of the report. - - - AIRMET.AEMC1: cloudBase shall be reported in metres (m) or feet ([ft_i]). + + + SIGMET.SPC1: The number of SIGMETPositionCollection member should be 1 for non-Tropical Cyclone/Volcanic Ash SIGMETs - - - AIRMET.AEMC2: cloudTop shall be reported in metres (m) or feet ([ft_i]). + + + AIRMET.AECC2: When AIRMETEvolvingConditionCollection timeIndicator is a forecast, the phenomenonTime must be later than or equal to the beginning of the validPeriod of the report. - - - AIRMET.AEMC3: directionOfMotion shall be reported in degrees (deg). + + + AIRMET.AECC1: When AIRMETEvolvingConditionCollection timeIndicator is an observation, the phenomenonTime must be earlier than or equal to the beginning of the validPeriod of the report. - - - AIRMET.AEMC11: geometryLowerLimitOperator can either be NULL or BELOW. + + + AIRMET.AEC1: cloudBase shall be reported in metres (m) or feet ([ft_i]). - - - AIRMET.AEMC12: geometryUpperLimitOperator can either be NULL or ABOVE + + + AIRMET.AEC2: cloudTop shall be reported in metres (m) or feet ([ft_i]). - - - AIRMET.AEMC4: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + + + AIRMET.AEC3: directionOfMotion shall be reported in degrees (deg). - - - AIRMET.AEMC5: surfaceVisibility shall be reported in metres (m). + + + AIRMET.AEC9: geometryLowerLimitOperator can either be NULL or BELOW. - - - AIRMET.AEMC9: surfaceWindDirection shall be reported in the degrees unit of measure ('deg'). + + + AIRMET.AEC10: geometryUpperLimitOperator can either be NULL or ABOVE - - - AIRMET.AEMC6: surfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + AIRMET.AEC4: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). - - - AIRMET.AEMC10: surfaceWindDirection and surfaceWindSpeed must be reported together + + + AIRMET.AEC5: surfaceVisibility shall be reported in metres (m). - - - AIRMET.AEMC8: When AIRMETEvolvingMeteorologicalCondition timeIndicator is a forecast, the phenomenonTime must be later than or equal to the beginning of the validPeriod of the report. + + + AIRMET.AEC7: surfaceWindDirection shall be reported in the degrees unit of measure ('deg'). - - - AIRMET.AEMC7: When AIRMETEvolvingMeteorologicalCondition timeIndicator is an observation, the phenomenonTime must be earlier than or equal to the beginning of the validPeriod of the report. + + + AIRMET.AEC6: surfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + + + AIRMET.AEC8: surfaceWindDirection and surfaceWindSpeed must be reported together @@ -476,7 +491,7 @@ - AIRMET.AIRMET1: OBS and FCST classifications must have a result type of AIRMETEvolvingMeteorologicalCondition + AIRMET.AIRMET1: OBS and FCST classifications must have a result type of AIRMETEvolvingConditionCollection @@ -586,7 +601,7 @@ - COMMON.ACF2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). + COMMON.ACF2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). @@ -609,4 +624,9 @@ COMMON.ASWTF3: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + + + IWXXM.ExtensionAlwaysLast: Extension elements should be the last elements in their parents + + diff --git a/IWXXM/sigmet.xsd b/IWXXM/sigmet.xsd index e4826bf8..54bbc4a0 100644 --- a/IWXXM/sigmet.xsd +++ b/IWXXM/sigmet.xsd @@ -1,5 +1,5 @@ - + @@ -12,16 +12,47 @@ SIGMETs report the occurrence and/or expected occurrence of specified en-route w References to WMO and ICAO Technical Regulations within this XML schema shall have no formal status and are for information purposes only. Where there are differences between the Technical Regulations and the schema, the Technical Regulations shall take precedence. Technical Regulations may impose requirements that are not described in this schema. - + + + A collection of SIGMETEvolvingConditions, each representing a location where SIGMET observed or forecast conditions exist. All members of this collection are of type SIGMETEvolvingCondition. + + + + + + + + + + Extension block for optional and/or additional parameters for element SIGMETEvolvingConditionCollection + + + + + + Indication whether the information is observed and expected to continue, or forecast + + + + + + + + + + + + + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic ash or a thunderstorm. Used to represent the forecast positions of SIGMET phenomena. -TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. +TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. In cases where the position covers an entire FIR or CTA, ("ENTIRE CTA or ENTIRE FIR" from ICAO Annex 3 / WMO No. 49-2) the geometry should be an xlink to the sampled feature for this SIGMET. - + @@ -32,7 +63,7 @@ In cases where the position covers an entire FIR or CTA, ("ENTIRE CTA or ENTIRE - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element SIGMETPosition @@ -44,16 +75,16 @@ In cases where the position covers an entire FIR or CTA, ("ENTIRE CTA or ENTIRE - + - + - A SIGMET (significant meteorological) report. SIGMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena over time. + A SIGMET (significant meteorological) report. SIGMETs report the occurrence and/or expected occurrence of specified en-route weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena over time. The SIGMET report class represents the base SIGMET types that may be reported such as squall lines, thunderstorms, dust storms, turbulence, etc. Tropical cyclone and volcanic ash SIGMET reports are subclasses of SIGMET due to their ability to report additional information, including volcano/tropical cyclone identification and forecast position(s). @@ -103,14 +134,14 @@ YUDD SIGMET A3 VALID ... The valid period of a previous SIGMET that is cancelled by this SIGMET. Mandatory when this is a cancellation report, must be missing otherwise - + The reported phenomenon, such as thunderstorm, tropical cyclone, icing, mountain wave, etc. The expected end of occurrence of volcanic ash ("NO VA EXP") is indicated with a missing SIGMET phenomenon with a nil reason of nothingOfOperationalSignificance - + SIGMETs may include the same phenomenon covering more than one area within the FIR/UIR/CTA, as well as observed and forecast conditions for each of these reported areas. All combinations of observations and forecasts of meteorological conditions, including changing conditions, are represented by their own SIGMETEvolvingMeteorologicalCondition. @@ -129,7 +160,7 @@ Each analysis has a single EvolvingMeteorologicalCondition as its result. - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element SIGMET @@ -148,18 +179,14 @@ Each analysis has a single EvolvingMeteorologicalCondition as its result. - + Conditions that indicate the presence of a specific SIGMET phenomenon such as volcanic ash or a thunderstorm, along with expected changes to the phenomenon such as intensity, speed, and direction. These conditions are reported with OBS/FCST conditions on all SIGMET types. -TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. - -directionOfMotion element refers to the direction which the phenomenon is moving towards, .e.g, "moving to the east". directionOfMotion is given in degrees from true North. Plane angle unit of measure (uom) is "deg". - -speedOfMotion can be provided in either two units of measures: "km/h" or "kn_i" (knots). +TC TOP (ABV and BLW) conditions are represented by the vertical component of the geometry. For example: CB TOP FL500 is represented as a missing lowerLimit and an upperLimit of 500FL. - + @@ -170,21 +197,21 @@ speedOfMotion can be provided in either two units of measures: "km/h" or "kn_i" This element value is given in degrees from true North. Plane angle unit of measure (uom) is "deg". - + The expected geographic region(s) affected by the reported phenomenon at a particular time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of phenomenon historically reported in ICAO Annex 3 / WMO No. 49-2: a boundary with a base and top, a TC centre position, and a VA line with a width - The reported relational operator for the airspace geometry lower limit. When reported, this operator is reported in conjunction with the airspace geometry's lower limit. + The reported relational operator for the airspace geometry lower limit. When reported, this operator is reported in conjunction with the airspace geometry's lower limit. To report an airspace lower limit of below FL 300, airspace lower limit is reported as FL 300 and the operator is reported as "below". When no operator is reported, the airspace lower limit represents an exact value with identical semantics to other measured quantities - The reported relational operator for the airspace geometry upper limit. When reported, this operator is reported in conjunction with the airspace geometry's upper limit. + The reported relational operator for the airspace geometry upper limit. When reported, this operator is reported in conjunction with the airspace geometry's upper limit. To report an airspace upper limit of above FL 300, airspace upper limit is reported as FL 300 and the operator is reported as "above". When no operator is reported, the airspace upper limit represents an exact value with identical semantics to other measured quantities @@ -198,7 +225,7 @@ speedOfMotion can be provided in either two units of measures: "km/h" or "[kn_i] - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element SIGMETEvolvingCondition @@ -207,11 +234,6 @@ speedOfMotion can be provided in either two units of measures: "km/h" or "[kn_i] The expected change in intensity for the reported meteorological condition (e.g., intensifying, weakening, or no change) determined at the time of SIGMET analysis based on the current state of the meteorological condition - - - Indication whether the information is observed and expected to continue, or forecast - - Indicator of whether the location of phenomena is approximate. If not reported locations are not approximate @@ -220,9 +242,9 @@ speedOfMotion can be provided in either two units of measures: "km/h" or "[kn_i] - + - + @@ -238,14 +260,14 @@ speedOfMotion can be provided in either two units of measures: "km/h" or "[kn_i] - The tropical cyclone being reported in this SIGMET. + The tropical cyclone being reported in this SIGMET. When reporting the tropical cyclone name, 'NN' may be used if the tropical cyclone is unnamed - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element TropicalCycloneSIGMET @@ -275,7 +297,7 @@ When reporting the tropical cyclone name, 'NN' may be used if the tropical cyclo - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element VolcanicAshSIGMET @@ -289,28 +311,28 @@ When reporting the tropical cyclone name, 'NN' may be used if the tropical cyclo - + - A collection of MeteorologicalPositions, each representing a location where meteorological conditions exist. All members of this collection are of type MeteorologicalPosition. + A collection of SIGMETPositions, each representing a location where meteorological conditions exist. All members of this collection are of type SIGMETPosition. - + - + - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element SIGMETPositionCollection - + - + diff --git a/IWXXM/taf.xsd b/IWXXM/taf.xsd index 816adb63..655d309f 100644 --- a/IWXXM/taf.xsd +++ b/IWXXM/taf.xsd @@ -1,10 +1,10 @@ - + - TAF reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + TAF reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. An Aerodrome Forecast (TAF) report is a routine forecast of meteorological conditions at an aerodrome intended for distribution. TAF reports include base forecast conditions, and modifications to those conditions throughout the valid period. @@ -59,13 +59,13 @@ Prevailing conditions and forecast changes differ in that the prevailing conditi - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element TAF - The status of this report, including amended, cancelled, normal, or corrected. + The status of this report, including amended, cancelled, normal, or corrected. Missing reports indicate that a report was not issued from the responsible reporting party as expected. Missing reports are typically issued by third parties that were expecting a report. @@ -84,7 +84,7 @@ Missing reports indicate that a report was not issued from the responsible repor A specialized Record type containing meteorological conditions forecast at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeTrendForecastRecord, which is reported on a METAR/SPECI - conditions reported in trend forecasts in METAR/SPECI differ from forecast groups in a TAF. -When no clouds of operational significance or no weather of operational significance is predicted, the nothingOfOperationalSignificance nilReason should be used for the cloud or presentWeather association. +When no clouds of operational significance or no weather of operational significance is predicted, the nothingOfOperationalSignificance nilReason should be used for the cloud or presentWeather association. Note that the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast (MeteorologicalAerodromeForecast): FM and TL - a phenomenonTime with a TimePeriod (start is FM and end is TL) @@ -111,7 +111,7 @@ Prevailing horizontal visibility shall be reported in meters ("m"). The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility. -To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". +To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities @@ -122,7 +122,7 @@ When no operator is reported, prevailing visibility represents an exact value wi - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element MeteorologicalAerodromeForecastRecord @@ -197,6 +197,11 @@ ICAO Annex 3 / WMO No. 49-2: "TN" + + + Extension block for optional and/or additional parameters for element AerodromeAirTemperatureForecast + + diff --git a/IWXXM/tropicalCycloneAdvisory.xsd b/IWXXM/tropicalCycloneAdvisory.xsd index 6c2686a8..ff65994b 100644 --- a/IWXXM/tropicalCycloneAdvisory.xsd +++ b/IWXXM/tropicalCycloneAdvisory.xsd @@ -1,5 +1,5 @@ - + @@ -56,14 +56,14 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - The time at which the next advisory is expected to be issued. + The time at which the next advisory is expected to be issued. When no subsequent advisory is expected to be issued it should be indicated by a missing expected advisory time with a nil reason of 'inapplicable' - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element TropicalCycloneAdvisory @@ -113,7 +113,7 @@ When no subsequent advisory is expected to be issued it should be indicated by a - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element TropicalCycloneObservedConditions @@ -143,7 +143,7 @@ When no subsequent advisory is expected to be issued it should be indicated by a - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element TropicalCycloneForecastConditions diff --git a/IWXXM/volcanicAshAdvisory.xsd b/IWXXM/volcanicAshAdvisory.xsd index a5818f1b..646c2aca 100644 --- a/IWXXM/volcanicAshAdvisory.xsd +++ b/IWXXM/volcanicAshAdvisory.xsd @@ -1,5 +1,5 @@ - + @@ -42,7 +42,7 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha Information source - described in free text - + The aviation colour code @@ -69,7 +69,7 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element VolcanicAshAdvisory @@ -95,7 +95,7 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element VolcanicAshConditions @@ -165,7 +165,7 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - Extension block for optional and/or additional parameters + Extension block for optional and/or additional parameters for element VolcanicAshCloud