diff --git a/IWXXM/ReleaseNotes-IWXXM.txt b/IWXXM/ReleaseNotes-IWXXM.txt index 87b9305e..d0973165 100644 --- a/IWXXM/ReleaseNotes-IWXXM.txt +++ b/IWXXM/ReleaseNotes-IWXXM.txt @@ -1,3 +1,31 @@ +==================================== +3.0.0RC1 - July 2018 +==================================== +* Restructured and simplified to remove the Observations and Measurements model (O&M) (issue #27) +* Incorporated ICAO Annex 3 / WMO No. 49 changes (issue #49): + + Space Weather Advisory has been added as a new product + * Tropical Cyclone Advisory (TCA) sequence numbers are now of the form "2004/13" instead of simple numbers + - TCA observed movement speed can no longer be reported as "moving slowly", per the Annex change +* Updated AIR/SIGMET structure to support TC and VA SIGMETs with multiple TCs/volcanoes, and to support the Amd 78 + provisions for reporting both a TC location along with CB location and movement (#49) +* All METAR/SPECI fields are now nillable in support of cases of observing system failures, such as a broken rain + gauge (issue #16) +* All gml:ids are now UUIDs, and this is supported by Schematron rules. This allows IWXXM message intermediaries to + re-assemble COLLECT advisories freely without requiring IWXXM message modifications en route (issue #31) +* SIGMET sub-types (VA and TC) elements are now optional to allow cancellations to be reported along with the SIGMET + type (issue #18) +* All Schematron files were combined into iwxxm.sch, including the WMO Codes Registry validation which were formerly in + iwxxm-collect-codelists.sch (issue #60) +* Made a number of fields nillable to support the minimum set of required information for failed translation cases (issue #41) ++ Added issue times onto IWXXM messages in support of standalone IWXXM messages (without WMO or Collect headers) (issue #47) +* Snow closure of all runways is now properly indicated, rather than being a snowClosure boolean on a single runway state. + The snowClosure boolean was removed, and full aerodrome/all runways snow closure is now indicated with a nilReason of + "http://codes.wmo.int/bufr4/codeflag/0-20-085/1" with a single runwayState element (issue #48) +* AerodromeObservedClouds was renamed to AerodromeCloud for consistency with other portions of IWXXM (issue #81) +* Added an iwxxm:AirspaceVolumePropertyType to allow for http://... nilReasons to be used with AirspaceVolume references (issue #94) ++ METAR/SPECI now have an optional timeIndicator which may be used to indicate FM/TL/AT explicitly (issue #7). +* Enhanced documentation on TAF phenomenonTime to clarify the meaning with timeIndicators of BECOMING (issue #13). + ==================================== 2.1.1 - November 2017 ==================================== @@ -9,7 +37,6 @@ * Fixed minor issues in the examples and added bulletin examples with COLLECT * Added a new schematron file iwxxm-collect-codelist.sch for offline checking of codelist items for pre-implementation testing -* Entered into force 15 May 2018. ==================================== 2.1 - March 2017 diff --git a/IWXXM/TAC-to-XML-Guidance.txt b/IWXXM/TAC-to-XML-Guidance.txt index 6e813249..b8e00b54 100644 --- a/IWXXM/TAC-to-XML-Guidance.txt +++ b/IWXXM/TAC-to-XML-Guidance.txt @@ -16,16 +16,16 @@ 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, "cloud" shall be nil 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 reported with a nilReason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" NCD - No clouds detected (by auto system) - 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" + When no clouds are detected by an automatic observing system, this shall be indicated by a "cloud" with a nilReason 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 nil "trendForecast" 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 "trendForecast" with a nilReason 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 nil "forecastWeather" 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 "forecastWeather" with a nilReason 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 @@ -33,32 +33,41 @@ R88 (runway designator for runway state) 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 -SNOCLO - Runway closed due to snow - When a runway is closed due to snow, AerodromeRunwayState shall have "snowClosure" set to true +SNOCLO - Runways closed due to snow + When all runways are closed due to snow, this shall be indicated with a "runwayState" with a nilReason of "http://codes.wmo.int/bufr4/codeflag/0-20-085/1" Present weather "//" - 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" + When present weather cannot be observed by the automatic observing system due to a temporary failure of the system/sensor, "presentWeather" shall be reported 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 "verticalVisibility shall be nil 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 nilReason 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 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 + 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 cloud "layer" with a nilReason 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 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 + 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 an "amount" with a nilReason 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 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 + 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 "base" and a nilReason 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 "cloudType" shall be nil with a nil reason of "http://codes.wmo.int/common/nil/notObservable" + When cloud type cannot be observed by an auto system due to sensor limitations "cloudType" shall be reported with a nilReason 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 nil "depthOfDeposits" and a nil reason 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 "depthOfDeposits" with a nilReason 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 nil "depthOfDeposits" and a nil reason 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 "depthOfDeposits" with a nilReason of "http://www.opengis.net/def/nil/OGC/0/unknown" + +Trend forecast BECMG without a specified time (TL, AT, FM) + When a trend forecast is reported with a BECMG block without a specified time and the period commences at the beginning of the trend forecast period and ceases by the end of the trend forecast period this should be represented as a phenomenonTime with a nilReason of "missing". Otherwise if the BECMG time is uncertain within the trend forecast period this should be represented as a phenomenonTime with a nilReason of "unknown" + +Trend forecast TEMPO without a specified time (TL, AT, FM) + When a trend forecast is reported with a TEMPO block without a specified time and the period commences at the beginning of the trend forecast period and ceases by the end of the trend forecast period this should be represented as a phenomenonTime with a nilReason of "missing" + +Observed quantities with a nil reason + When observed measures or quantities (such as air temperature or prevailing visibility) can not be reported due to sensor failures, the XML element should have xsi:nil set to "true", the uom set to "N/A", and the nilReason set to "http://codes.wmo.int/common/nil/notObservable" ========================== TAF @@ -70,13 +79,13 @@ 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 NSC - No clouds of operational significance - 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" + When no cloud of operational significance is observed/forecast, and 'CAVOK' is not appropriate, "cloud" shall be reported with a nilReason 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 nil "weather" 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 "weather" with a nilReason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" Vertical visibility "VV///" - When the vertical visibility is not available for any reason, "verticalVisibility" shall be missing with no nil reason + When the vertical visibility is not available for any reason, "verticalVisibility" shall be missing with no nilReason ========================== AIRMET and SIGMET @@ -85,13 +94,13 @@ FLnnn, nnnnM, nnnnFT When a single altitude for AIR/SIGMET conditions are specified, this shall be indicated with the same altitude value in both aixm:lowerLimit and aixm:upperLimit TOP [ABV or BLW] FLnnn - When an AIR/SIGMET top is specified without a lower limit, this shall be indicated with a nil aixm:lowerLimit with a nilReason of "missing" + When an AIR/SIGMET top is specified without a lower limit, this shall be indicated with a aixm:lowerLimit with a nilReason of "missing" Nnn[nn] Wnnn[nn] or Nnn[nn] Ennn[nn] or Snn[nn] Wnnn[nn] or Snn[nn] Ennn[nn] When an AIR/SIGMET position is reported at a single point the location shall be indicated as a gml:CircleByCenterPoint with a gml:radius of 0 NO VA EXP - No volcanic ash expected - 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" + The expected end of occurrence of volcanic ash shall be indicated with a "VolcanicAshSIGMET/phenomenon" with a nilReason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" ========================== Volcanic Ash Advisory @@ -103,29 +112,35 @@ Volcanic Ash Advisory An unnamed volcano shall be indicated with an "EruptingVolcano/name" of "UNNAMED" 'UNKNOWN' volcano location - An unknown volcano location shall be indicated with a nil "EruptingVolcano/position" and a nil reason of "unknown" + An unknown volcano location shall be indicated with a "EruptingVolcano/position" with a nilReason of "unknown" 'UNKNOWN' aviation colour code - An unknown aviation colour code shall be indicated with a nil "colourCode" and a nil reason of "unknown" + An unknown aviation colour code shall be indicated with a "colourCode" with a nilReason of "unknown" 'NOT GIVEN' aviation colour code - An aviation colour code that is not given shall be indicated with a nil "colourCode" and a nil reason of "withheld" + An aviation colour code that is not given shall be indicated with a "colourCode" with a nilReason of "withheld" 'NIL' aviation colour code - A NIL aviation colour code shall be indicated with a nil "colourCode" with a nil reason of "missing" + A NIL aviation colour code shall be indicated with a "colourCode" with a nilReason of "missing" 'VA NOT IDENTIFIABLE FM SATELLITE DATA' - Unidentifiable volcanic ash from satellite data shall be indicated with a nil "ashCloudExtent" and a nil reason of "unknown" + Unidentifiable volcanic ash from satellite data shall be indicated with a "ashCloudExtent" with a nilReason of "unknown" 'NO VA EXP' - 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" + When no volcanic ash is expected it shall be indicated with a "ashCloudExtent" with a nilReason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance" 'NOT AVBL' - When volcanic ash is not available it shall be indicated with a nil "ashCloudExtent" and a nil reason of "missing" + When volcanic ash is not available it shall be indicated with a "ashCloudExtent" with a nilReason of "missing" 'NOT PROVIDED' - When volcanic ash is not provided it shall be indicated with a nil "ashCloudExtent" and a nil reason of "withheld" + When volcanic ash is not provided it shall be indicated with a "ashCloudExtent" with a nilReason of "withheld" + +'NIL' remarks + NIL remarks shall be indicated with an missing "remarks" element +'NO FURTHER ADVISORIES' + A NIL shall be indicated with "nextAdvisoryTime" with a nilReason of "Inapplicable" + ========================== Tropical Cyclone Advisory ========================== @@ -134,3 +149,15 @@ Tropical Cyclone Advisory 'NIL' remarks NIL remarks shall be indicated with an missing "remarks" element + +'NO MSG EXP' + A NIL shall be indicated with "expectedNextAdvisoryTime" with a nilReason of "Inapplicable" + +========================== +Space Weather Advisory +========================== +'NIL' remarks + NIL remarks shall be indicated with an missing "remarks" element + +'NO FURTHER ADVISORIES' + A NIL shall be indicated with "nextAdvisoryTime" with a nilReason of "Inapplicable" diff --git a/IWXXM/airmet.xsd b/IWXXM/airmet.xsd index 47f56c39..41b3ab0c 100644 --- a/IWXXM/airmet.xsd +++ b/IWXXM/airmet.xsd @@ -1,8 +1,7 @@ - + - AIRMET reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. @@ -20,8 +19,17 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - - + + + The time at which meteorological phenomena occur + + + + + The members of this collection + + + Extension block for optional and/or additional parameters for element AIRMETEvolvingConditionCollection @@ -53,17 +61,27 @@ The AIRMET report class represents the base AIRMET types that may be reported su + + + The time at which this report was issued + + The ATS unit serving the FIR or CTA to which the AIRMET refers. ICAO Annex 3 / WMO No. 49-2: A6-1: "Location indicator of FIR/CTA" - + MWO originating this report - + + + The ATS region (FIR, UIR, CTA, or FIR/UIR) + + + The sequence number of this message. For example: "5", "A3", or "2" @@ -87,17 +105,17 @@ YUDD AIRMET A3 VALID ... The valid period of a previous AIRMET that is cancelled by this AIRMET. Mandatory when this is a cancellation report, must be missing otherwise - + 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. 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 for element AIRMET @@ -129,12 +147,7 @@ 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 @@ -153,6 +166,11 @@ To report an airspace lower limit of below FL 300, airspace lower limit is repor 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 + + + 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 speed of movement of a meteorological condition. When no movement is expected, this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason. Speed of movement shall be given in either "km/h" or "[kn_i]" (knot). @@ -217,7 +235,7 @@ Appendix 6 Section 2.1 - + Extension block for optional and/or additional parameters for element AIRMETEvolvingCondition diff --git a/IWXXM/common.xsd b/IWXXM/common.xsd index ec8540cb..c6a543d6 100644 --- a/IWXXM/common.xsd +++ b/IWXXM/common.xsd @@ -1,5 +1,5 @@ - + @@ -92,16 +92,8 @@ Vertical visibility shall be reported either in meters ("m") or feet ("[ft_i]"). - - - - - - - - - - + + Extension block for optional and/or additional parameters for element AerodromeCloudForecast @@ -145,6 +137,18 @@ This extends AerodromeSurfaceWindTrendForecast to allow for a variable wind dire + + + A nillable string quantity. References to this type may be nil and may include a nilReason + + + + + + + + + A trend forecast of surface wind conditions at an aerodrome. @@ -196,7 +200,7 @@ Wind gusts shall be provided in either two units of measures: "m/s" or "[kn_i]" 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 @@ -236,7 +240,7 @@ 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 @@ -318,6 +322,13 @@ For example, the "above" operator in conjunction with the reported quantity 10.6 + + + + + + + @@ -339,6 +350,17 @@ For example, the "above" operator in conjunction with the reported quantity 10.6 + + + + + + + + + + + Whether the information is observed and expected to continue, or forecast diff --git a/IWXXM/examples/airmet-A6-1a-TS.txt b/IWXXM/examples/airmet-A6-1a-TS.txt deleted file mode 100644 index 34381e58..00000000 --- a/IWXXM/examples/airmet-A6-1a-TS.txt +++ /dev/null @@ -1,12 +0,0 @@ -YUDD AIRMET 1 VALID 151520/151800 YUSO -YUDD SHANLON FIR ISOL TS OBS -N OF S50 TOP ABV FL100 STNR WKN - -The first AIRMET message issued by a fictitious YUDD flight information -region by the fictitious YUSO meteorological watch office since 0001 UTC; -the message is valid from 1520 UTC to 1800 UTC on the 15th of the month; -isolated thunderstorm with a top above 100FL is expected north of 50 latitude -remaining stationary and weakening - -(not an official interpretation from ICAO Annex 3 - created by -Aaron Braeckel on October 7, 2012) \ No newline at end of file diff --git a/IWXXM/examples/airmet-A6-1a-TS.xml b/IWXXM/examples/airmet-A6-1a-TS.xml index 05c1170f..26c9bb07 100644 --- a/IWXXM/examples/airmet-A6-1a-TS.xml +++ b/IWXXM/examples/airmet-A6-1a-TS.xml @@ -6,48 +6,67 @@ YUDD SHANLON FIR ISOL TS OBS N OF S50 TOP ABV FL100 STNR WKN --> + gml:id="uuid.69a2497b-193c-47bf-a6bd-1cc71acbc8e5" status="NORMAL"> + + + + 2014-05-15T15:20:00Z + + - - - - - SNAPSHOT - YUDD FIC - FIC - YUDD + + + + + SNAPSHOT + YUDD FIC + FIC + YUDD - + + - - - - - SNAPSHOT - YUDD MWO - MWO - YUDD - + + + + + SNAPSHOT + YUDD MWO + MWO + YUDD + - + + + + + + + SNAPSHOT + FIR + YUCC + AMSWELL FIR + + + + + + 1 - + - + 2014-05-15T15:20:00 2014-05-15T18:00:00 @@ -57,78 +76,36 @@ - - - - - - - - - 2014-05-15T15:20:00Z - - - - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 6-1 TECHNICAL SPECIFICATIONS RELATED TO AIRMET INFORMATION - - - - - - - - - - - - - SNAPSHOT - FIR - YUCC - AMSWELL FIR - - - - - - - - - - - - - - - - - 100 - STD - - - - - - - - -50.0 50.0 -50.0 70.0 -40.0 70.0 -40.0 50.0 -50.0 50.0 - - - - - - + + + + + + + + 100 + STD + + + + + + + + -50.0 50.0 -50.0 70.0 -40.0 70.0 -40.0 50.0 -50.0 50.0 + + + + + + - - ABOVE - 0 - - - - - + + ABOVE + + 0 + + + diff --git a/IWXXM/examples/airmet-translation-failed.xml b/IWXXM/examples/airmet-translation-failed.xml index f1c5b87b..eef297be 100644 --- a/IWXXM/examples/airmet-translation-failed.xml +++ b/IWXXM/examples/airmet-translation-failed.xml @@ -1,21 +1,18 @@ + + + 2014-05-10T15:00:00 + + + - + - + SNAPSHOT YUDD FIC @@ -40,31 +43,22 @@ - - - - - - SNAPSHOT - YUDD MWO - MWO - YUDD - - - - - 1 + + + + + - + 2014-05-15T15:20:00 2014-05-15T18:00:00 - + - + diff --git a/IWXXM/examples/metar-A3-1.tac b/IWXXM/examples/metar-A3-1.tac deleted file mode 100644 index 4bb68080..00000000 --- a/IWXXM/examples/metar-A3-1.tac +++ /dev/null @@ -1 +0,0 @@ -METAR YUDO 221630Z 24004MPS 0600 R12/1000U DZ FG SCT010 OVC020 17/16 Q1018 BECMG TL1700 0800 FG BECMG AT1800 9999 NSW \ No newline at end of file diff --git a/IWXXM/examples/metar-A3-1.txt b/IWXXM/examples/metar-A3-1.txt deleted file mode 100644 index b81425fe..00000000 --- a/IWXXM/examples/metar-A3-1.txt +++ /dev/null @@ -1,18 +0,0 @@ -METAR YUDO 221630Z 24004MPS 0600 R12/1000U DZ FG SCT010 OVC020 17/16 Q1018 BECMG TL1700 0800 FG BECMG AT1800 9999 NSW - - -Routine report for Donlon/International* issued on the 22nd of the month at 1630 UTC; surface wind direction -240 degrees; wind speed 4 metres per second; visibility (along the runway(s) in the local routine report; prevailing -visibility in METAR) 600 metres; runway visual range representative of the touchdown zone for runway 12 is -1 000 metres and the runway visual range values have shown an upward tendency during previous 10 minutes -(RVR tendency to be included in METAR only); and moderate drizzle and fog; scattered cloud at 300 metres; -overcast at 600 metres; air temperature 17 degrees Celsius; dew-point temperature 16 degrees Celsius; QNH -1 018 hectopascals; trend during next 2 hours, visibility (along the runway(s) in the local routine report; prevailing -visibility in METAR) becoming 800 metres in fog by 1700 UTC; at 1800 UTC visibility (along the runway(s) in -the local routine report; prevailing visibility in METAR) becoming 10 kilometres or more and nil significant -weather. - -* Fictitious location - -Note. In this example, the primary units metre per second and metre were used for wind speed and height of cloud base, respectively. -However, in accordance with Annex 5, the corresponding non-SI alternative units knot and foot may be used instead. diff --git a/IWXXM/examples/metar-A3-1.xml b/IWXXM/examples/metar-A3-1.xml index 87a27b23..bf67885f 100644 --- a/IWXXM/examples/metar-A3-1.xml +++ b/IWXXM/examples/metar-A3-1.xml @@ -1,169 +1,136 @@ - + + + + 2012-08-22T16:30:00Z + + + + + + + + + + SNAPSHOT + YUDO + DONLON/INTERNATIONAL + YUDO + + + 12.34 -12.34 + + + + + + + + + + + 2012-08-22T16:30:00Z + + + - - - - - - 2012-08-22T16:30: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 - - - - - - - - 12.34 -12.34 - - - - - - - - 17.0 - 16.0 - 1018 - - - 240 - 4.0 - - - - - 600 - - - - - - - - - - SNAPSHOT - 12 - - - - - 1000 - - - - - - - - - - 1000 - - - - - - 2000 - - - - - - - + + 17.0 + 16.0 + 1018 + + + 240 + 4.0 + + + + + 600 + + + + + + + + + + SNAPSHOT + 12 + + + + + 1000 + + + + + + + + + + 1000 + + + + + + 2000 + + + + + + - - + - - + + 2012-08-22T16:30:00Z 2012-08-22T17:00:00Z - - - - - - - - - 800 - - - - + + UNTIL + 800 + + + - - + - - + + 2012-08-22T18:00:00Z 2012-08-22T18:00:00Z - - - - - - - - - 10000 - ABOVE - - - - + + AT + 10000 + ABOVE + + + diff --git a/IWXXM/examples/metar-EDDF-runwaystate.tac b/IWXXM/examples/metar-EDDF-runwaystate.tac deleted file mode 100644 index 1788626f..00000000 --- a/IWXXM/examples/metar-EDDF-runwaystate.tac +++ /dev/null @@ -1 +0,0 @@ -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 \ No newline at end of file diff --git a/IWXXM/examples/metar-EDDF-runwaystate.xml b/IWXXM/examples/metar-EDDF-runwaystate.xml index 5b62bbe9..7badf224 100644 --- a/IWXXM/examples/metar-EDDF-runwaystate.xml +++ b/IWXXM/examples/metar-EDDF-runwaystate.xml @@ -4,187 +4,159 @@ 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 --> - + xsi:schemaLocation="http://icao.int/iwxxm/3.0 http://schemas.wmo.int/iwxxm/3.0.0RC1/iwxxm.xsd" + gml:id="uuid.96a5ba6a-47ce-4c10-bc56-355a32dcf22c" status="NORMAL" automatedStation="false" permissibleUsage="OPERATIONAL"> + + + + + 2013-03-12T05:50:00Z + + + + + + + + + + SNAPSHOT + EDDF + FRANKFURT AM MAIN INTERNATIONAL + EDDF + + + 50.0464 8.5986 112 + + + + + + + + + + 2013-03-12T05:50:00Z + + + - - - - - 2013-03-12T05:50:00Z - - - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 3 TECHNICAL SPECIFICATIONS RELATED TO METEOROLOGICAL OBSERVATIONS AND REPORTS - - - - - - - - - + + -4 + -4 + 1000 + + + 30 + 15 + + + + + 1400 + + + + + + 2000 + ABOVE + + + + + + 2000 + ABOVE + + + + + + 1900 + + + + + + + + + + + + + + - + SNAPSHOT - EDDF - FRANKFURT AM MAIN INTERNATIONAL - EDDF - + 07R + 70 + - - - - - 50.0464 8.5986 112 - - - - - - - - -4 - -4 - 1000 - - - 30 - 15 - - - - - 1400 - - - - - - - 2000 - ABOVE - - - - - - 2000 - ABOVE - - - - - - 1900 - - - - - - - - - - - - - - - - - - - - SNAPSHOT - 07R - 70 - - - - - - - - - - - - - - - - - SNAPSHOT - 07C - 70 - - - - - - - - - - - - - - - - - SNAPSHOT - 07L - 70 - - - - - - - - - - - - - + + + + + + + + + + + + + + + SNAPSHOT + 07C + 70 + + + + + + + + + + + + + + + + + SNAPSHOT + 07L + 70 + + + + + + + + + + + - - - - - - - - - - 4000 - - - - + + + 4000 + + + diff --git a/IWXXM/examples/metar-LKKV.tac b/IWXXM/examples/metar-LKKV.tac deleted file mode 100644 index ee7eb769..00000000 --- a/IWXXM/examples/metar-LKKV.tac +++ /dev/null @@ -1 +0,0 @@ -METAR LKKV 251200Z 21003MPS VCSH 27/10 Q1010 RETS R11/1///// \ No newline at end of file diff --git a/IWXXM/examples/metar-LKKV.xml b/IWXXM/examples/metar-LKKV.xml index 9fba6a20..5d30f2b1 100644 --- a/IWXXM/examples/metar-LKKV.xml +++ b/IWXXM/examples/metar-LKKV.xml @@ -1,102 +1,88 @@ - + xsi:schemaLocation="http://icao.int/iwxxm/3.0 http://schemas.wmo.int/iwxxm/3.0.0RC1/iwxxm.xsd" + gml:id="uuid.ce3b61b9-d360-4da1-83b9-67e668406869" status="NORMAL" automatedStation="false" permissibleUsage="OPERATIONAL"> + + + + + 2007-07-25T12:00:00Z + + + + + + + + + + SNAPSHOT + LKKV + KARLOVY VARY INTERNATIONAL + LKKV + + + + + + + + + 2007-07-25T12:00:00Z + + + - - - - - 2007-07-25T12:00:00Z - - - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 3 TECHNICAL SPECIFICATIONS RELATED TO METEOROLOGICAL OBSERVATIONS AND REPORTS - - - - - - - - - - - - SNAPSHOT - LKKV - KARLOVY VARY INTERNATIONAL - LKKV - - - - - - - 50.20 12.92 606 - - - - - - - 27 - 10 - 1010 - - - 210 - 2.6 - - - - - - - - - - - - - SNAPSHOT - 18C + + 27 + 10 + 1010 + + + 210 + 2.6 + + + + + + + + + + + + + SNAPSHOT + 18C + + + + + + + + + + + + + + SNAPSHOT + 11 - - - - - - - - - - - - - SNAPSHOT - 11 - - - - - - - - - - + + + + + + + + diff --git a/IWXXM/examples/metar-NIL-collect.xml b/IWXXM/examples/metar-NIL-collect.xml index 3201f07c..ea47ad60 100644 --- a/IWXXM/examples/metar-NIL-collect.xml +++ b/IWXXM/examples/metar-NIL-collect.xml @@ -6,77 +6,57 @@ METAR YUDO 221630Z NIL --> + xmlns:collect="http://def.wmo.int/collect/2014" + xmlns:gml="http://www.opengis.net/gml/3.2" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://def.wmo.int/collect/2014 http://schemas.wmo.int/collect/1.2/collect.xsd" + gml:id="uuid.6f353602-12a1-40a7-b6b5-3edb14c6241e"> - - - - - - - - - 2012-08-22T16:30: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 - - - - - - - - 12.34 -12.34 - - - - - - - - + + + + + 2012-08-22T16:30:00Z + + + + + + + + + + SNAPSHOT + YUDO + DONLON/INTERNATIONAL + YUDO + + + + + + + + + 2012-08-22T16:30:00Z + + + + + + diff --git a/IWXXM/examples/metar-NIL.tac b/IWXXM/examples/metar-NIL.tac deleted file mode 100644 index 45bd5a02..00000000 --- a/IWXXM/examples/metar-NIL.tac +++ /dev/null @@ -1 +0,0 @@ -METAR YUDO 221630Z NIL \ No newline at end of file diff --git a/IWXXM/examples/metar-translation-failed.xml b/IWXXM/examples/metar-translation-failed.xml index 98db5b0c..3ba4055c 100644 --- a/IWXXM/examples/metar-translation-failed.xml +++ b/IWXXM/examples/metar-translation-failed.xml @@ -4,16 +4,13 @@ METAR YUDO 221630Z INVALID --> - - - - - - - - 2012-08-22T16:30:00Z - - - - - 2012-08-22T16:40:00Z + + + + + 2012-08-22T16:30: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 + + + + + + + + + SNAPSHOT + YUDO + DONLON/INTERNATIONAL + YUDO - - - - - - - - - + + + + + + + 2012-08-22T16:30:00Z + + + + diff --git a/IWXXM/examples/sigmet-A6-1a-TS.tac b/IWXXM/examples/sigmet-A6-1a-TS.tac deleted file mode 100644 index 0f2e8046..00000000 --- a/IWXXM/examples/sigmet-A6-1a-TS.tac +++ /dev/null @@ -1 +0,0 @@ -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 WKN FCST 1600Z S OF N54 AND E OF W010 diff --git a/IWXXM/examples/sigmet-A6-1a-TS.xml b/IWXXM/examples/sigmet-A6-1a-TS.xml index 1e615e4f..0e16d866 100644 --- a/IWXXM/examples/sigmet-A6-1a-TS.xml +++ b/IWXXM/examples/sigmet-A6-1a-TS.xml @@ -1,28 +1,31 @@ - + + + + 2012-08-10T12:00:00Z + + + - + - + SNAPSHOT YUDD FIC @@ -32,10 +35,11 @@ + - + - + SNAPSHOT YUSO MWO @@ -46,11 +50,26 @@ + + + + + + SNAPSHOT + OTHER:FIR_UIR + YUDD + SHANLON FIR/UIR + + + + + + 2 - + 2012-08-10T12:00:00Z 2012-08-10T16:00:00Z @@ -61,80 +80,39 @@ - - + - - - - - - 2012-08-10T12:00:00Z - - - - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 6-1 TECHNICAL SPECIFICATIONS RELATED TO SIGMET INFORMATION - - - - - - - - - - - - - SNAPSHOT - OTHER:FIR_UIR - YUDD - SHANLON FIR/UIR - - - - - - - - - - - - - 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 - - - - - + + 90 + 20 + + + diff --git a/IWXXM/examples/sigmet-A6-1b-CNL.tac b/IWXXM/examples/sigmet-A6-1b-CNL.tac deleted file mode 100644 index a5119565..00000000 --- a/IWXXM/examples/sigmet-A6-1b-CNL.tac +++ /dev/null @@ -1 +0,0 @@ -YUDD SIGMET 3 VALID 101345/101600 YUSO - YUDD SHANLON FIR/UIR CNL SIGMET 2 101200/101600 \ No newline at end of file diff --git a/IWXXM/examples/sigmet-A6-1b-CNL.txt b/IWXXM/examples/sigmet-A6-1b-CNL.txt deleted file mode 100644 index 6189c0c9..00000000 --- a/IWXXM/examples/sigmet-A6-1b-CNL.txt +++ /dev/null @@ -1,11 +0,0 @@ -YUDD SIGMET 3 VALID 101345/101600 YUSO -YUDD SHANLON FIR/UIR CNL SIGMET 2 101200/101600 - - -The third SIGMET message issued by a fictitious YUDD flight information -region by the fictitious YUSO meteorological watch office since 0001 UTC; -the message is valid from 1345 UTC to 1600 UTC on the 10th of the month; -this cancels the second SIGMET message valid from 1200 UTC to 1600 UTC -on the 10th of the month - -(not an official interpretation from ICAO Annex 3 - Aaron Braeckel May 25, 2012) diff --git a/IWXXM/examples/sigmet-A6-1b-CNL.xml b/IWXXM/examples/sigmet-A6-1b-CNL.xml index da14bed8..e35a663d 100644 --- a/IWXXM/examples/sigmet-A6-1b-CNL.xml +++ b/IWXXM/examples/sigmet-A6-1b-CNL.xml @@ -1,28 +1,31 @@ - + + + + 2012-08-10T13:45:00Z + + + - + - + SNAPSHOT YUDD FIC @@ -34,9 +37,9 @@ - + - + SNAPSHOT YUSO MWO @@ -46,12 +49,26 @@ + + + + + + + SNAPSHOT + OTHER:FIR_UIR + YUDD + SHANLON FIR/UIR + + + + 3 - + - + 2012-08-10T13:45:00Z 2012-08-10T16:00:00Z @@ -60,52 +77,13 @@ 2 - + 2012-08-10T12:00:00Z 2012-08-10T16:00:00Z - - - - - - - - - 2012-08-10T13:45:00Z - - - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 6-1 TECHNICAL SPECIFICATIONS RELATED TO SIGMET INFORMATION - - - - - - - - - - - - SNAPSHOT - OTHER:FIR_UIR - YUDD - SHANLON FIR/UIR - - - - - - - - - - - + + diff --git a/IWXXM/examples/sigmet-A6-2-TC.tac b/IWXXM/examples/sigmet-A6-2-TC.tac deleted file mode 100644 index 0f20487b..00000000 --- a/IWXXM/examples/sigmet-A6-2-TC.tac +++ /dev/null @@ -1 +0,0 @@ -YUCC SIGMET 3 VALID 251600/252200 YUDO - YUCC AMSWELL FIR TC GLORIA OBS AT 1600Z N2706 W07306 CB TOP FL500 WI 150NM OF CENTRE MOV NW 10KT NC FCST 2200Z TC CENTRE N2740 W07345 \ No newline at end of file diff --git a/IWXXM/examples/sigmet-A6-2-TC.txt b/IWXXM/examples/sigmet-A6-2-TC.txt deleted file mode 100644 index 88401bf8..00000000 --- a/IWXXM/examples/sigmet-A6-2-TC.txt +++ /dev/null @@ -1,14 +0,0 @@ -YUCC SIGMET 3 VALID 251600/252200 YUDO -YUCC AMSWELL FIR TC GLORIA OBS AT 1600Z N2706 W07306 CB TOP FL500 WI 150NM OF CENTRE -MOV NW 10KT NC FCST 2200Z TC CENTRE N2740 W07345 - - -The third SIGMET message issued for the AMSWELL* flight information region (identified by YUCC Amswell -area control centre) by the Donlon/International* meteorological watch office (YUDO) since 0001 UTC; the -message is valid from 1600 UTC to 2200 UTC on the 25th of the month; tropical cyclone Gloria was observed at -1600 UTC at 27 degrees 6 minutes north and 73 degrees 6 minutes west with cumulonimbus top at flight level 500 -within 150 nautical miles of the centre; the tropical cyclone is expected to move northwestwards at 10 knots and -not to undergo any changes in intensity; the forecast position of the centre of the tropical cyclone at 2200 UTC is -expected to be at 27 degrees 40 minutes north and 73 degrees 45 minutes west. - -* Fictitious location \ No newline at end of file diff --git a/IWXXM/examples/sigmet-A6-2-TC.xml b/IWXXM/examples/sigmet-A6-2-TC.xml index 3bb9aca0..1f3b1649 100644 --- a/IWXXM/examples/sigmet-A6-2-TC.xml +++ b/IWXXM/examples/sigmet-A6-2-TC.xml @@ -1,29 +1,29 @@ - + xsi:schemaLocation="http://icao.int/iwxxm/3.0 http://schemas.wmo.int/iwxxm/3.0.0RC1/iwxxm.xsd" + gml:id="uuid.f12194be-0d82-49ad-ad97-41e46f724dec" permissibleUsage="OPERATIONAL" status="NORMAL"> + + + + 2012-08-25T16:00:00Z + + + - + - + SNAPSHOT YUCC FIC @@ -33,10 +33,11 @@ + - + - + SNAPSHOT YUDO MWO @@ -47,11 +48,26 @@ + + + + + + SNAPSHOT + FIR + YUCC + AMSWELL FIR + + + + + + 3 - + 2012-08-25T16:00:00Z 2012-08-25T22:00:00Z @@ -62,152 +78,81 @@ - - + + - - - 2012-08-25T16:00:00Z - - - - - + + 2012-08-25T16:00:00Z - - - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 6-1 TECHNICAL SPECIFICATIONS RELATED TO SIGMET INFORMATION - - - - - - - - - - - - - SNAPSHOT - FIR - YUCC - AMSWELL FIR - - - - - - - - - - - - - - - - - 500 - STD - - - - - - - - - - - 27.10 -73.10 - 250 - - - - - - - - - - - - - - - - - + + + + + + + 500 + STD + + + + + + + + + + + 27.10 -73.10 + 250 + + + + + + + + + + + + + + + + + 27.10 -73.10 + + + - - + - - + + 2012-08-25T22:00:00Z - - - - - 2012-08-25T16:00:00Z - - - - - - - - - - - - - - - - - - - - - - - - - 27.6667 -73.75 - 0 - - - - - - - - - - - - - - - - - + + + + + + + + + + 27.6667 -73.75 + + + - + Gloria diff --git a/IWXXM/examples/sigmet-VA-EGGX.tac b/IWXXM/examples/sigmet-VA-EGGX.tac deleted file mode 100644 index 34c3aba7..00000000 --- a/IWXXM/examples/sigmet-VA-EGGX.tac +++ /dev/null @@ -1 +0,0 @@ -EGGX SIGMET 4 VALID 251600/252200 EGRR - EGGX SHANWICK OCEANIC FIR VA ERUPTION MT HEKLA PSN N6359 W01940 VA CLD OBS AT 1600Z SFC/FL550 N6000 W01150 - N5900 W01300 - N6000 W01600 - N6000 W01150 MOV S 60KT NC FCST 2200Z SFC/FL550 N6000 W01200 - N5800 W01400 - N6000 W01535 - N6000 W01200 \ No newline at end of file diff --git a/IWXXM/examples/sigmet-VA-EGGX.xml b/IWXXM/examples/sigmet-VA-EGGX.xml index da02f578..51c4b8ce 100644 --- a/IWXXM/examples/sigmet-VA-EGGX.xml +++ b/IWXXM/examples/sigmet-VA-EGGX.xml @@ -1,29 +1,30 @@ - - + + + + + YYYY-MM-25T16:00:00Z + + + - + - + SNAPSHOT SHANWICK OCEANIC AREA CONTROL CENTRE @@ -33,10 +34,11 @@ EGGX SHANWICK OCEANIC FIR VA ERUPTION MT HEKLA PSN N6359 W01940 VA CLD OBS AT 16 + - + - + SNAPSHOT UK METEOROLOGICAL OFFICE - EXETER @@ -46,146 +48,123 @@ EGGX SHANWICK OCEANIC FIR VA ERUPTION MT HEKLA PSN N6359 W01940 VA CLD OBS AT 16 + + + + + + + SNAPSHOT + FIR + EGGX + SHANWICK OCEANIC FIR + + + + + + 4 + - - YYYY-MM-25T16:00:00Z - YYYY-MM-25T22:00:00Z + + 2018-07-25T16:00:00Z + 2018-07-25T22:00:00Z + + - - - - - YYYY-MM-25T16:00:00Z + + + + 2018-07-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 - - - - - - - - - - - - SNAPSHOT - FIR - EGGX - SHANWICK OCEANIC FIR - - - - - - - - - - - - - 180 - - - - 550 - STD - - - - - - - - - 60.0 -11.5 - 59.0 -13.0 - 60.0 -16.0 - 60.0 -11.5 - - - - - - - - - - 60 - - - - - + + + + + + + 550 + STD + + + + + + + + + 60.0 -11.5 + 59.0 -13.0 + 60.0 -16.0 + 60.0 -11.5 + + + + + + + + + + + + + - - - - - YYYY-MM-25T22:00:00Z + + + + 2018-07-25T22:00:00Z - - - - - - - - - - - - - - - - - - - - - 60.0 -12.0 - 58.0 -14.0 - 60.0 -15.35 - 60.0 -12.0 - - - - - - - - - - - - - - + + + + + + + + + + + + + + 60.0 -12.0 + 58.0 -14.0 + 60.0 -15.35 + 60.0 -12.0 + + + + + + + + + + + + + - + MT HEKLA - + 63.98 -19.67 + diff --git a/IWXXM/examples/sigmet-multi-location-VA.xml b/IWXXM/examples/sigmet-multi-location-VA.xml new file mode 100644 index 00000000..aea466cd --- /dev/null +++ b/IWXXM/examples/sigmet-multi-location-VA.xml @@ -0,0 +1,216 @@ + + + + + + + 2018-07-10T12:00:00Z + + + + + + + + + SNAPSHOT + SHANWICK OCEANIC AREA CONTROL CENTRE + ATCC + YUDD + + + + + + + + + + + SNAPSHOT + UK METEOROLOGICAL OFFICE - EXETER + MWO + YUSO + + + + + + + + + + + SNAPSHOT + OTHER:FIR_UIR + YUDD + SHANLON FIR/UIR + + + + + + + 2 + + + + 2018-07-10T12:00:00Z + 2018-07-10T18:00:00Z + + + + + + + + + + + 2018-07-10T12:00:00Z + + + + + + + + + 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 + + + + + + + + + + + + + + + + + + 2018-07-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 + + + + + + diff --git a/IWXXM/examples/sigmet-multi-location.xml b/IWXXM/examples/sigmet-multi-location.xml deleted file mode 100644 index a8d5eede..00000000 --- a/IWXXM/examples/sigmet-multi-location.xml +++ /dev/null @@ -1,234 +0,0 @@ - - - - - - - - - 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 - - - - - - - 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 - - - - - - - - - - - - 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 - - - - - diff --git a/IWXXM/examples/sigmet-translation-failed-collect.xml b/IWXXM/examples/sigmet-translation-failed-collect.xml index c63e0b51..57632447 100644 --- a/IWXXM/examples/sigmet-translation-failed-collect.xml +++ b/IWXXM/examples/sigmet-translation-failed-collect.xml @@ -8,25 +8,19 @@ --> + xsi:schemaLocation="http://def.wmo.int/collect/2014 http://schemas.wmo.int/collect/1.2/collect.xsd" + gml:id="uuid.fee171e9-1aec-4815-bcca-9e3c467388c6"> - + + + 2012-08-10T12:00:00Z + + + - + - + SNAPSHOT YUDD FIC @@ -50,32 +50,23 @@ - - - - - - SNAPSHOT - YUSO MWO - MWO - YUSO - - - - + + + + + + - 2 - - + 2012-08-10T12:00:00Z 2012-08-10T16:00:00Z - + - + diff --git a/IWXXM/examples/spacewx-A2-3.xml b/IWXXM/examples/spacewx-A2-3.xml new file mode 100644 index 00000000..7baaf5ae --- /dev/null +++ b/IWXXM/examples/spacewx-A2-3.xml @@ -0,0 +1,167 @@ + + + + + + + 2016-11-08T01:00:00Z + + + + + + + + + SNAPSHOT + DONLON + OTHER:SWXC + + + + + + 2016/2 + 2016/1 + + + + + + + + + + 2016-11-08T01:00:00Z + + + + + + + + + + + + + + -180 90 -180 60 180 60 180 90 -180 90 + + + + + + + + + + + + + + + + + + + + + + + -180 -90 -180 -60 180 -60 180 -90 -180 -90 + + + + + + + + + + + + + + + + + + + + 2016-11-08T07:00:00Z + + + + + + + + + + + + + + + 2016-11-08T13:00:00Z + + + + + + + + + + + + + + + 2016-11-08T19:00:00Z + + + + + + + + + + + + + + + 2016-11-09T01:00:00Z + + + + + + + + LOW LVL GEOMAGNETIC STORMING CAUSING INCREASED AURORAL ACT AND SUBSEQUENT MOD DEGRADATION OF GNSS AND HF COM AVBL IN THE AURORAL ZONE. THIS STORMING EXP TO SUBSIDE IN THE FCST PERIOD. SEE WWW.SPACEWEATHERPROVIDER.WEB + + + + diff --git a/IWXXM/examples/spacewx-A2-4.xml b/IWXXM/examples/spacewx-A2-4.xml new file mode 100644 index 00000000..dc3db09e --- /dev/null +++ b/IWXXM/examples/spacewx-A2-4.xml @@ -0,0 +1,173 @@ + + + + + + + 2016-11-08T00:00:00Z + + + + + + + + + SNAPSHOT + DONLON + OTHER:SWXC + + + + + + 2016/2 + 2016/1 + + + + + + + + + 2016-11-08T01:00:00Z + + + + + + + + 350 + STD + + + + + + + -180 90 -180 60 180 60 180 90 -180 90 + + + + + + + + + ABOVE + + + + + + + + + 350 + STD + + + + + + + -180 -90 -180 -60 180 -60 180 -90 -180 -90 + + + + + + + + + ABOVE + + + + + + + + + + + + 2016-11-08T07:00:00Z + + + + + + + + + + + + + + + 2016-11-08T13:00:00Z + + + + + + + + + + + + + + + 2016-11-08T19:00:00Z + + + + + + + + + + + + + + + 2016-11-09T01:00:00Z + + + + + + + + RADIATION LVL EXCEEDED 100 PCT OF BACKGROUND LVL AT FL350 AND ABV. THE CURRENT EVENT HAS PEAKED AND LVL SLW RTN TO BACKGROUND LVL. SEE WWW.SPACEWEATHERPROVIDER.WEB + + + + diff --git a/IWXXM/examples/spacewx-A2-5.xml b/IWXXM/examples/spacewx-A2-5.xml new file mode 100644 index 00000000..340dc051 --- /dev/null +++ b/IWXXM/examples/spacewx-A2-5.xml @@ -0,0 +1,272 @@ + + + + + + + 2016-11-08T00:00:00Z + + + + + + + + + SNAPSHOT + DONLON + OTHER:SWXC + + + + + + 2016/2 + 2016/1 + + + + + + + + + 2016-11-08T01:00:00Z + + + + + + + + + + + + + + + + + + -16.6392 160.9368 + + 5409.75 + + + + + + + + + + + + + + + + + + + + + + + + 2016-11-08T07:00:00Z + + + + + + + + + + + + + + + + + + -16.7114 70.9413 + 5409.75 + + + + + + + + + + + + + + + + + + + + + + + + 2016-11-08T13:00:00Z + + + + + + + + + + + + + + + + + + -16.7832 -19.0539 + 5409.75 + + + + + + + + + + + + + + + + + + + + + + + + 2016-11-08T19:00:00Z + + + + + + + + + + + + + + + + + + -16.8548 -109.0489 + 5409.75 + + + + + + + + + + + + + + + + + + + + + + + + 2016-11-09T01:00:00Z + + + + + + + + + + + + + + + + + + -16.9261 160.9563 + 5409.75 + + + + + + + + + + + + + + + + + + + + PERIODIC HF COM ABSORPTION OBS AND LIKELY TO CONT IN THE NEAR TERM. CMPL AND PERIODIC LOSS OF HF ON THE SUNLIT SIDE OF THE EARTH EXP. CONT HF COM DEGRADATION LIKELY OVER THE NXT 7 DAYS. SEE WWW.SPACEWEATHERPROVIDER.WEB + + + + 2016-11-08T07:00:00Z + + + + diff --git a/IWXXM/examples/spacewx-translation-failed.xml b/IWXXM/examples/spacewx-translation-failed.xml new file mode 100644 index 00000000..0488289a --- /dev/null +++ b/IWXXM/examples/spacewx-translation-failed.xml @@ -0,0 +1,56 @@ + + + + + + + 2016-11-08T00:00:00Z + + + + + + + + + SNAPSHOT + DONLON + OTHER:SWXC + + + + + + + + + + + + + + + + diff --git a/IWXXM/examples/speci-A3-2.tac b/IWXXM/examples/speci-A3-2.tac deleted file mode 100644 index 93832035..00000000 --- a/IWXXM/examples/speci-A3-2.tac +++ /dev/null @@ -1 +0,0 @@ -SPECI YUDO 151115Z 05025G37KT 3000 1200NE +TSRA BKN005CB 25/22 Q1008 TEMPO TL1200 0600 BECMG AT1200 8000 NSW NSC \ No newline at end of file diff --git a/IWXXM/examples/speci-A3-2.txt b/IWXXM/examples/speci-A3-2.txt deleted file mode 100644 index ccfddbcb..00000000 --- a/IWXXM/examples/speci-A3-2.txt +++ /dev/null @@ -1,28 +0,0 @@ -SPECI YUDO 151115Z 05025G37KT 3000 1200NE+TSRA BKN005CB 25/22 Q1008 TEMPO TL1200 0600 -BECMG AT1200 8000 NSW NSC - - -Special report for Donlon/International* issued on the 15th of the month at 1115 UTC; - surface wind direction 050 degrees; - wind speed 25 knots, gusting 37 knots; - prevailing visibility 3000 metres; - minimum visibility 1200 metres to north east; - thunderstorm with heavy rain; - broken cumulonimbus cloud at 500 feet; - air temperature 25 degrees Celsius; - dew-point temperature 22 degrees Celsius; - QNH 1008 hectopascals; - -temporarily from 1115 to 1200 - prevailing visibility 600 metres; - -becoming at 1200 UTC - prevailing visibility 8 kilometres; - (thunderstorm ceases) - nil significant weather; - nil significant cloud; - -* Fictitious location - -Note. In this example, the non-SI alternative units knot and foot were used for wind speed and height of cloud base, respectively. -However, in accordance with Annex 5, the corresponding primary units metres per second and metre may be used instead. \ No newline at end of file diff --git a/IWXXM/examples/speci-A3-2.xml b/IWXXM/examples/speci-A3-2.xml index 503205c1..ee0dcd36 100644 --- a/IWXXM/examples/speci-A3-2.xml +++ b/IWXXM/examples/speci-A3-2.xml @@ -1,152 +1,113 @@ - - - - - - - - - 2012-08-15T11:15:00Z - - - - - - 2012-08-15T11:25: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 - - - - - - - + + + + + 2012-08-15T11:15:00Z + + + + + + + + + + SNAPSHOT + YUDO + DONLON/INTERNATIONAL + YUDO + + 12.34 -12.34 - - - - - - - - 25.0 - 22.0 - 1008 - - - 50 - 25.0 - 37 - - - - - 3000 - 1200 - 45 - - - - - - - - - 500 - - - - - - - - + + + + + + + + + + 2012-08-15T11:15:00Z + + + + + + 25.0 + 22.0 + 1008 + + + 50 + 25.0 + 37 + + + + + 3000 + 1200 + 45 + + + + + + + + + 500 + + + + + + + - - - - - + + + 2012-08-15T11:15:00Z 2012-08-15T12:00:00Z - - - - - - - - - 600 - - - + + 600 + + - - + - - + + 2012-08-15T12:00:00Z - - - - - - - - - 8000 - - - - - + + 8000 + + + + diff --git a/IWXXM/examples/taf-A5-1.tac b/IWXXM/examples/taf-A5-1.tac deleted file mode 100644 index 2b05d758..00000000 --- a/IWXXM/examples/taf-A5-1.tac +++ /dev/null @@ -1 +0,0 @@ -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 diff --git a/IWXXM/examples/taf-A5-1.txt b/IWXXM/examples/taf-A5-1.txt deleted file mode 100644 index b5bac3e2..00000000 --- a/IWXXM/examples/taf-A5-1.txt +++ /dev/null @@ -1,19 +0,0 @@ -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 - - -TAF for Donlon/International* issued on the 15th of the month at 1800 UTC valid from 0000 UTC to 1800 UTC -on the 16th of the month; surface wind direction 130 degrees; wind speed 5 metres per second; visibility -9 kilometres, broken cloud at 600 metres; becoming between 0600 UTC and 0800 UTC on the 16th of the month, -scattered cumulonimbus cloud at 450 metres and broken cloud at 600 metres; temporarily between 0800 UTC and -1200 UTC on the 16th of the month surface wind direction 170 degrees; wind speed 6 metres per second gusting to -12 metres per second; visibility 1 000 metres in a thunderstorm with moderate rain, scattered cumulonimbus cloud -at 300 metres and broken cloud at 600 metres; from 1230 UTC on the 16th of the month surface wind direction -150 degrees; wind speed 4 metres per second; visibility 10 kilometres or more; and broken cloud at 600 metres. - -* Fictitious location - -Note. In this example, the primary units metre per second and metre were used for wind speed and height of cloud base, respectively. -However, in accordance with Annex 5, the corresponding non-SI alternative units knot and foot may be used instead. diff --git a/IWXXM/examples/taf-A5-1.xml b/IWXXM/examples/taf-A5-1.xml index d9055395..afd71e3e 100644 --- a/IWXXM/examples/taf-A5-1.xml +++ b/IWXXM/examples/taf-A5-1.xml @@ -1,233 +1,178 @@ - + - + 2012-08-15T18:00:00Z + + + + + + + SNAPSHOT + YUDO + DONLON/INTERNATIONAL + YUDO + + + 12.34 -12.34 + + + + + + + - + 2012-08-16T00:00:00Z 2012-08-16T18:00:00Z + - - + + - - - + - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 5 TECHNICAL SPECIFICATIONS RELATED TO FORECASTS - - - - - - - - - - - - - - SNAPSHOT - YUDO - DONLON/INTERNATIONAL - YUDO - - - - - - - - 12.34 -12.34 - - - - - - - - 9000 - - - 130 - 5.0 - - - - - - - - 2000 - - - - - - - + 9000 + + + 130 + 5.0 + + + + + + + + 2000 + + + + + + - - - - + + + 2012-08-16T06:00:00Z 2012-08-16T08:00:00Z - - - - - - - - - - - - - - - - 1500 - - - - - - - 2000 - - - - - - - + + + + + + + 1500 + + + + + + + 2000 + + + + + + - - - - + + + 2012-08-16T08:00:00Z 2012-08-16T12:00:00Z - - - - - - - - - - - 1000 - - - - 170 - 6 - 12 - - - - - - - - - - - 1000 - - - - - - - 2000 - - - - - - - + + 1000 + + + + 170 + 6 + 12 + + + + + + + + + + + 1000 + + + + + + + 2000 + + + + + + - - - - + + + 2012-08-16T12:30:00Z - 2012-08-17T00:00:00Z + 2012-08-16T18:00:00Z - - - - - - - - - - - 10000 - ABOVE - - - 150 - 4 - - - - - - - - 2000 - - - - - - - + + 10000 + ABOVE + + + 150 + 4 + + + + + + + + 2000 + + + + + diff --git a/IWXXM/examples/taf-A5-2.tac b/IWXXM/examples/taf-A5-2.tac deleted file mode 100644 index ea9abf1c..00000000 --- a/IWXXM/examples/taf-A5-2.tac +++ /dev/null @@ -1 +0,0 @@ -TAF AMD YUDO 161500Z 1600/1618 CNL diff --git a/IWXXM/examples/taf-A5-2.txt b/IWXXM/examples/taf-A5-2.txt deleted file mode 100644 index 7b3ca842..00000000 --- a/IWXXM/examples/taf-A5-2.txt +++ /dev/null @@ -1,7 +0,0 @@ -TAF AMD YUDO 161500Z 1606/1624 CNL - - -Amended TAF for Donlon/International* issued on the 16th of the month at 1500 UTC cancelling the -previously issued TAF valid from 0000 UTC to 1800 UTC on the 16th of the month. - -* Fictitious location diff --git a/IWXXM/examples/taf-A5-2.xml b/IWXXM/examples/taf-A5-2.xml index 60b3315f..1a0acadd 100644 --- a/IWXXM/examples/taf-A5-2.xml +++ b/IWXXM/examples/taf-A5-2.xml @@ -1,38 +1,29 @@ - - + 2012-08-16T15:00:00Z - - - - - 2012-08-16T15:00:00Z - 2012-08-17T00:00:00Z - - - - - - + + + - + SNAPSHOT YUDO @@ -41,11 +32,22 @@ - + + + + + + 2012-08-16T15:00:00Z + 2012-08-17T00:00:00Z + + + + + - + 2012-08-16T00:00:00Z 2012-08-16T18:00:00Z diff --git a/IWXXM/examples/taf-NIL-collect.xml b/IWXXM/examples/taf-NIL-collect.xml index dfb5781d..3d42183f 100644 --- a/IWXXM/examples/taf-NIL-collect.xml +++ b/IWXXM/examples/taf-NIL-collect.xml @@ -7,77 +7,43 @@ --> + xsi:schemaLocation="http://def.wmo.int/collect/2014 http://schemas.wmo.int/collect/1.2/collect.xsd" + gml:id="uuid.507b41d4-2656-4f93-a1d7-2d01bd8e4c50"> - - + - + 2012-08-16T00:00:00Z + + + + + + + SNAPSHOT + YUDO + DONLON/INTERNATIONAL + YUDO + + + + - - - - - - - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 5 TECHNICAL SPECIFICATIONS RELATED TO FORECASTS - - - - - - - - - - - - - - SNAPSHOT - YUDO - DONLON/INTERNATIONAL - YUDO - - - - - - - - 12.34 -12.34 - - - - - - - - + diff --git a/IWXXM/examples/taf-NIL.tac b/IWXXM/examples/taf-NIL.tac deleted file mode 100644 index 58280b2f..00000000 --- a/IWXXM/examples/taf-NIL.tac +++ /dev/null @@ -1 +0,0 @@ -TAF YUDO 160000Z NIL \ No newline at end of file diff --git a/IWXXM/examples/taf-translation-failed.xml b/IWXXM/examples/taf-translation-failed.xml index 56e8dc40..613c8798 100644 --- a/IWXXM/examples/taf-translation-failed.xml +++ b/IWXXM/examples/taf-translation-failed.xml @@ -4,16 +4,12 @@ TAF YUDO 151800Z 1600/1618 INVALID --> - - + 2012-08-15T18:00:00Z + + + + + + + SNAPSHOT + YUDO + DONLON/INTERNATIONAL + YUDO + + + + + - + 2012-08-16T00:00:00Z 2012-08-16T18:00:00Z - + + diff --git a/IWXXM/examples/tc-advisory-A2-2.txt b/IWXXM/examples/tc-advisory-A2-2.txt deleted file mode 100644 index 8164db78..00000000 --- a/IWXXM/examples/tc-advisory-A2-2.txt +++ /dev/null @@ -1,20 +0,0 @@ -TC ADVISORY - -DTG: 20040925/1600Z -TCAC: YUFO -TC: GLORIA -NR: 01 -PSN: N2706 W07306 -MOV: NW 20KMH -C: 965HPA -MAX WIND: 22MPS -FCST PSN +6 HR: 25/2200Z N2748 W07350 -FCST MAX WIND +6 HR: 22MPS -FCST PSN +12 HR: 26/0400Z N2830 W07430 -FCST MAX WIND +12 HR: 22MPS -FCST PSN +18 HR: 26/1000Z N2852 W07500 -FCST MAX WIND +18 HR: 21MPS -FCST PSN +24 HR: 26/1600Z N2912 W07530 -FCST MAX WIND +24 HR: 20MPS -RMK: NIL -NXT MSG: 20040925/2000Z \ No newline at end of file diff --git a/IWXXM/examples/tc-advisory-A2-2.xml b/IWXXM/examples/tc-advisory-A2-2.xml index 5702e7da..df16ae60 100644 --- a/IWXXM/examples/tc-advisory-A2-2.xml +++ b/IWXXM/examples/tc-advisory-A2-2.xml @@ -1,13 +1,14 @@ - - + - - - 2004-09-25T16:00:00Z - - + + + 2004-09-25T16:00:00Z + + - - - - - - SNAPSHOT - OTHER:TCAC - YUFO - - - - + + + + + + SNAPSHOT + OTHER:TCAC + YUFO + + + + - GLORIA - 01 + GLORIA + 01 - - - - - 2004-09-25T16:00:00Z - - - - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 2 Tropical cyclone advisory information - - - - - - - - - - - 27.1 -73.1 - - - - - - + + + + + 2004-09-25T16:00:00Z + + + + + 27.1 -73.1 + + + + + + + + + + + + + + + 27.1 -73.1 + 250 + + + + + + + + + + + + MOVING 315 20 965 22 - - - + - - - - - - 2004-09-25T22:00:00Z - - - - - - - - - - - - - - 27.8 -73.83333 - - - - - - + + + + + + 2004-09-25T22:00:00Z + + + + + 27.8 -73.83333 + + + 22 + + + + + + + + + 2004-09-26T04:00:00Z + + + + + 28.5 -74.5 + + 22 - - - + - - - - - - 2004-09-26T04:00:00Z - - - - - - - - - - - - - - 28.5 -74.5 - - - - - - - 22 - - - - + + + + + + 2004-09-26T10:00:00Z + + + + + 28.86667 -75.00 + + + 21 + + - - - - - - 2004-09-26T10:00:00Z - - - - - - - - - - - - - - 28.86667 -75.00 - - - - - - - 21 - - - - + + + + + + 2004-09-26T16:00:00Z + + + + + 29.2 -75.5 + + + 20 + + - - - - - - 2004-09-26T16:00:00Z - - - - - - - - - - - - - - 29.2 -75.5 - - - - - - - 20 - - - - + - - - 2004-09-25T20:00:00Z - - + + + 2004-09-25T20:00:00Z + + diff --git a/IWXXM/examples/tc-advisory-translation-failed.xml b/IWXXM/examples/tc-advisory-translation-failed.xml index 938e5972..56768f02 100644 --- a/IWXXM/examples/tc-advisory-translation-failed.xml +++ b/IWXXM/examples/tc-advisory-translation-failed.xml @@ -9,63 +9,58 @@ TC: GLORIA INVALID INVALID INVALID --> + xmlns:iwxxm="http://icao.int/iwxxm/3.0" xmlns:metce="http://def.wmo.int/metce/2013" + xmlns:aixm="http://www.aixm.aero/schema/5.1.1" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://icao.int/iwxxm/3.0 http://schemas.wmo.int/iwxxm/3.0.0RC1/iwxxm.xsd" + gml:id="uuid.4a954e38-b132-4d3c-aaba-90dbd056d497" permissibleUsage="OPERATIONAL" + translatedBulletinID="TTAAiiCCCYYGGgg" + translatedBulletinReceptionTime="2014-05-15T15:29:00Z" + translationCentreDesignator="YUZZ" + translationCentreName="Fictional translation centre" + translationTime="2014-05-15T15:30:00Z" + translationFailedTAC="TC ADVISORY + + DTG: 20040925/1600Z + TCAC: YUFO + TC: GLORIA + INVALID INVALID INVALID"> + + + + 2004-09-25T16:00:00Z + + + + + + + + + SNAPSHOT + OTHER:TCAC + YUFO + + + + + + + + + + + + + + - - - 2004-09-25T16:00:00Z - - + - - - - - - - 2004-01-01T00:00:00Z - - - - SNAPSHOT - - - 2004-01-01T00:00:00Z - - - - OTHER:TCAC - YUFO - - - - + - GLORIA - 0 + - - - - - - + diff --git a/IWXXM/examples/va-advisory-A2-1.txt b/IWXXM/examples/va-advisory-A2-1.txt deleted file mode 100644 index a5a758b7..00000000 --- a/IWXXM/examples/va-advisory-A2-1.txt +++ /dev/null @@ -1,29 +0,0 @@ -FVFE01 RJTD 230130 -VA ADVISORY - -DTG: 20080923/0130Z -VAAC: TOKYO -VOLCANO: KARYMSKY 1000-13 -PSN: N5403 E15927 -AREA: RUSSIA -SUMMIT ELEV: 1536M -ADVISORY NR: 2008/4 -INFO SOURCE: MTSAT-1R KVERT KEMSD -AVIATION COLOUR CODE: RED -ERUPTION DETAILS: ERUPTION AT 20080923/0000Z FL300 REPORTED -OBS VA DTG: 23/0100Z -OBS VA CLD: FL250/300 N5400 E15930 N5400 E16100 N5300 E15945 MOV SE 20KT - SFC/FL200 N5130 E16130 N5130 E16230 N5230 E16230 N5230 E16130 - MOV SE 15KT -FCST VA CLD +6 HR: 23/0700Z FL250/350 N5130 E16030 N5130 E16230 N5330 E16230 N5330 - E16030 SFC/FL180 N4830 E16330 N4830 E16630 N5130 E16630 N5130 - E16330 -FCST VA CLD +12 HR: 23/1300Z SFC/FL270 N4830 E16130 N4830 E16600 N5300 E16600 N5300 - E16130 -FCST VA CLD +18 HR: 23/1900Z NO VA EXP -RMK: LATEST REP FM KVERT (0120Z) INDICATES ERUPTION HAS CEASED. - TWO DISPERSING VA CLD ARE EVIDENT ON SATELLITE IMAGERY -NXT ADVISORY: 20080923/0730Z - - -(Example A2-1 from ICAO Annex 3 Amd 76) \ 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 753fc750..4071c565 100644 --- a/IWXXM/examples/va-advisory-A2-1.xml +++ b/IWXXM/examples/va-advisory-A2-1.xml @@ -1,5 +1,5 @@ - + xmlns:iwxxm="http://icao.int/iwxxm/3.0" xmlns:metce="http://def.wmo.int/metce/2013" + xmlns:aixm="http://www.aixm.aero/schema/5.1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://icao.int/iwxxm/3.0 http://schemas.wmo.int/iwxxm/3.0.0RC1/iwxxm.xsd" + gml:id="uuid.fb4861a8-0438-4f17-b8a7-efc13de58dec" permissibleUsage="OPERATIONAL"> - - - 2008-09-23T01:30:00Z - - + + + 2008-09-23T01:30:00Z + + - - - - - - SNAPSHOT - TOKYO - OTHER:VACC - - - - + + + + + + SNAPSHOT + TOKYO + OTHER:VACC + + + + - - - FL300 REPORTED - KARYMSKY 1000-13 - - - 54.03 159.27 1536 - - - 2008-09-23T01:30:00Z - - + + + FL300 REPORTED + KARYMSKY 1000-13 + + + 54.03 159.27 1536 + + + 2008-09-23T01:30:00Z + + - 2008/4 - MTSAT-1R KVERT KEMSD - + 2008/4 + MTSAT-1R KVERT KEMSD + - - - - - 2008-09-23T01:00:00Z - - - - - - 2008-09-23T00:00:00Z - - - - - WMO No. 49 Volume 2 Meteorological Service for International Air Navigation APPENDIX 2 Volcanic ash advisory information - - - - - - - - - - - - - - - - - - - 300 - STD - 250 - STD - - - - - - - 54.00 159.50 54.00 161.00 53.00 159.75 54.00 159.50 - - - - - - - - - 135 - 20 - - - - - - - - 200 - STD - GND - SFC - - - - - - - 51.50 161.50 51.50 162.50 52.50 162.50 52.50 161.50 51.50 161.50 - - - - - - - - - 135 - 15 - - + + + + + 2008-09-23T01:00:00Z + + + + + + + + 300 + STD + 250 + STD + + + + + + + 54.00 159.50 54.00 161.00 53.00 159.75 54.00 159.50 + + + + + + + + + 135 + 20 + + + + + + + + 200 + STD + GND + SFC + + + + + + + 51.50 161.50 51.50 162.50 52.50 162.50 52.50 161.50 51.50 161.50 + + + + + + + + + 135 + 15 + + - - - + - - - - - - 2008-09-23T07:00:00Z - - - - - - - - - - - - - - - 350 - STD - 250 - STD - - - - - - - 51.50 160.50 51.50 162.50 53.50 162.50 53.50 160.50 51.50 160.50 - - - - - - - - - - - - - - - - 180 - STD - GND - SFC - - - - - - - 48.50 163.50 48.50 166.50 51.50 166.50 51.50 163.50 48.50 163.50 - - - - - - - - - - + + + + + + + 2008-09-23T07:00:00Z + + + + + + + 350 + STD + 250 + STD + + + + + + + 51.50 160.50 51.50 162.50 53.50 162.50 53.50 160.50 51.50 160.50 + + + + + + + + + + + + + + + + 180 + STD + GND + SFC + + + + + + + 48.50 163.50 48.50 166.50 51.50 166.50 51.50 163.50 48.50 163.50 + + + + + + + + + + - - - + - - - - - - 2008-09-23T13:00:00Z - - - - - - - - - - - - - - - 270 - STD - GND - SFC - - - - - - - 48.50 161.50 48.50 166.00 53.00 166.00 53.00 161.50 48.50 161.50 - - - - - - - - - - + + + + + + + 2008-09-23T13:00:00Z + + + + + + + 270 + STD + GND + SFC + + + + + + + 48.50 161.50 48.50 166.00 53.00 166.00 53.00 161.50 48.50 161.50 + + + + + + + + + + - - - + - - - - - - 2008-09-23T19:00:00Z - - - - - - - - - + + + + + + 2008-09-23T19:00:00Z + + + + + - - LATEST REP FM KVERT (0120Z) INDICATES ERUPTION HAS CEASED. TWO DISPERSING VA CLD ARE EVIDENT ON SATELLITE IMAGERY + + LATEST REP FM KVERT (0120Z) INDICATES ERUPTION HAS CEASED. TWO DISPERSING VA CLD ARE EVIDENT ON SATELLITE IMAGERY - - - 2008-09-23T07:30:00Z - - - + + + 2008-09-23T07:30:00Z + + diff --git a/IWXXM/examples/va-advisory-translation-failed.xml b/IWXXM/examples/va-advisory-translation-failed.xml index 08f2d594..29b04d9d 100644 --- a/IWXXM/examples/va-advisory-translation-failed.xml +++ b/IWXXM/examples/va-advisory-translation-failed.xml @@ -12,73 +12,54 @@ INVALID INVALID INVALID --> +DTG: 20080923/0130Z +VAAC: TOKYO +VOLCANO: KARYMSKY 1000-13 +PSN: N5403 E15927 +INVALID INVALID INVALID"> + + + + 2008-09-23T01:30:00Z + + + + + + + + + SNAPSHOT + TOKYO + OTHER:VACC + + + + + + + + - - - 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 - - + - - - - + diff --git a/IWXXM/gmliwxxm.xsd b/IWXXM/gmliwxxm.xsd index 88bce367..9b9e0320 100644 --- a/IWXXM/gmliwxxm.xsd +++ b/IWXXM/gmliwxxm.xsd @@ -8,7 +8,7 @@ elementFormDefault="qualified" version="3.2.1.2"> - GML Subset schema for gml:AbstractFeature,gml:AbstractFeatureType,gml:AngleType,gml:SpeedType,gml:LengthType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup,gml:ReferenceType,gml:TimePeriodPropertyType,gml:AbstractGML,gml:AbstractGMLType,gml:AbstractObject,gml:NilReasonType,gml:MeasureType,gml:ScaleType,gml:TimeInstantPropertyType, written by gmlSubset.xslt. + GML Subset schema for gml:AbstractFeature,gml:AbstractFeatureType,gml:AssociationAttributeGroup,gml:OwnershipAttributeGroup,gml:TimeInstantPropertyType,gml:TimePeriodPropertyType,gml:SpeedType,gml:LengthType,gml:AngleType,gml:ReferenceType,gml:AbstractGML,gml:AbstractGMLType,gml:NilReasonType,gml:AbstractObject,gml:AbstractTimeObject,gml:MeasureType,gml:AbstractMemberType,gml:PointPropertyType, written by gmlSubset.xslt. @@ -41,7 +41,7 @@ The value of the gml:location property describes the extent, position or relativ - + @@ -427,94 +427,28 @@ The following rules shall be adhered to: deprecated - - - - - - - - gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units Of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. - - - - - - - - - - The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. - - - - - - This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. -It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. - - - - - - - - This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . -NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). -In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either -- a conventional unit of measure symbol, -- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. - - - - - - - - - - - - - This is a prototypical definition for a specific measure type defined as a vacuous extension (i.e. aliases) of gml:MeasureType. In this case, the content model supports the description of a length (or distance) quantity, with its units. The unit of measure referenced by uom shall be suitable for a length, such as metres or feet. - - - - - - + - gml:TimePeriodPropertyType provides for associating a gml:TimePeriod with an object. + gml:TimeInstantPropertyType provides for associating a gml:TimeInstant with an object. - + - - gml:TimePeriod acts as a one-dimensional geometric primitive that represents an identifiable extent in time. -The location in of a gml:TimePeriod is described by the temporal positions of the instants at which it begins and ends. The length of the period is equal to the temporal distance between the two bounding temporal positions. -Both beginning and end may be described in terms of their direct position using gml:TimePositionType which is an XML Schema simple content type, or by reference to an indentifiable time instant using gml:TimeInstantPropertyType. -Alternatively a limit of a gml:TimePeriod may use the conventional GML property model to make a reference to a time instant described elsewhere, or a limit may be indicated as a direct position. + gml:TimeInstant acts as a zero-dimensional geometric primitive that represents an identifiable position in time. - + - - - - - - - - - + @@ -597,6 +531,11 @@ Alternatively a limit of a gml:TimePeriod may use the conventional GML property gml:AbstractTimeObject acts as the head of a substitution group for all temporal primitives and complexes. + + + This element is used directly as a property of gml:TimeInstant (see 15.2.2.3), and may also be used in application schemas. + + The method for identifying a temporal position is specific to each temporal reference system. gml:TimePositionType supports the description of temporal position according to the subtypes described in ISO 19108. @@ -650,47 +589,53 @@ A value for indeterminatePosition may - + - gml:TimeInstantPropertyType provides for associating a gml:TimeInstant with an object. + gml:TimeGeometricPrimitive acts as the head of a substitution group for geometric temporal primitives. +A temporal geometry shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. The GPS calendar is an alternative reference systems in common use. +The two geometric primitives in the temporal dimension are the instant and the period. GML components are defined to support these as follows. + + + + + gml:TimePeriodPropertyType provides for associating a gml:TimePeriod with an object. - + - - gml:TimeInstant acts as a zero-dimensional geometric primitive that represents an identifiable position in time. + gml:TimePeriod acts as a one-dimensional geometric primitive that represents an identifiable extent in time. +The location in of a gml:TimePeriod is described by the temporal positions of the instants at which it begins and ends. The length of the period is equal to the temporal distance between the two bounding temporal positions. +Both beginning and end may be described in terms of their direct position using gml:TimePositionType which is an XML Schema simple content type, or by reference to an indentifiable time instant using gml:TimeInstantPropertyType. +Alternatively a limit of a gml:TimePeriod may use the conventional GML property model to make a reference to a time instant described elsewhere, or a limit may be indicated as a direct position. - + - + + + + + + + + + - - - This element is used directly as a property of gml:TimeInstant (see 15.2.2.3), and may also be used in application schemas. - - - - - gml:TimeGeometricPrimitive acts as the head of a substitution group for geometric temporal primitives. -A temporal geometry shall be associated with a temporal reference system through the frame attribute that provides a URI reference that identifies a description of the reference system. Following ISO 19108, the Gregorian calendar with UTC is the default reference system, but others may also be used. The GPS calendar is an alternative reference systems in common use. -The two geometric primitives in the temporal dimension are the instant and the period. GML components are defined to support these as follows. - - The length of a time period. @@ -740,9 +685,114 @@ The value of the unit is either selected from the units for time intervals from - + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units Of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + The simple type gml:UomIdentifer defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + This is a prototypical definition for a specific measure type defined as a vacuous extension (i.e. aliases) of gml:MeasureType. In this case, the content model supports the description of a length (or distance) quantity, with its units. The unit of measure referenced by uom shall be suitable for a length, such as metres or feet. + + + + + + + + + + + + + To create a collection of GML Objects that are not all features, a property type shall be derived by extension from gml:AbstractMemberType. +This abstract property type is intended to be used only in object types where software shall be able to identify that an instance of such an object type is to be interpreted as a collection of objects. +By default, this abstract property type does not imply any ownership of the objects in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of an object in the collection. A collection shall not own an object already owned by another object. + + + + + + + + A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. + + + + + + + + + + + + + + + + + gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. + + + + + + + + The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. + + diff --git a/IWXXM/iwxxm-collect.xsd b/IWXXM/iwxxm-collect.xsd index c4058d48..f5371d3a 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 c1f17691..55b24fed 100644 --- a/IWXXM/iwxxm.xsd +++ b/IWXXM/iwxxm.xsd @@ -1,19 +1,19 @@ - + + - - The ICAO Meteorological Information Exchange Model (IWXXM) package, including METAR, SPECI, TAF, and other reports as defined in ICAO Annex 3, Amendment 76. IWXXM reports are essential operational meteorology products used to enable safe and efficient air travel worldwide. + The ICAO Meteorological Information Exchange Model (IWXXM) package, including METAR, SPECI, TAF, and other reports as defined in ICAO Annex 3. IWXXM reports are essential operational meteorology products used to enable safe and efficient air travel worldwide. -The report types in this package include METAR, SPECI, TAF, SIGMET, AIRMET, Volcanic Ash Advisory (VAA), and Tropical Cyclone Advisory (TCA). +The report types in this package include METAR, SPECI, TAF, SIGMET, AIRMET, Volcanic Ash Advisory (VAA), Tropical Cyclone Advisory (TCA), and Space Weather Advisory. This package builds upon the ISO 19100 family (ISO TC211) and WMO standard meteorological modeling constructs. Additionally, the constructs in this application schema refer to a number of aviation constructs such Runway and Airspace from AIXM. The full relationship of this package with external dependencies are shown in the 'Package Dependencies' diagram. diff --git a/IWXXM/measures.xsd b/IWXXM/measures.xsd index 742408fe..25495a4d 100644 --- a/IWXXM/measures.xsd +++ b/IWXXM/measures.xsd @@ -1,5 +1,5 @@ - + Common measured quantities used across multiple packages. @@ -42,4 +42,28 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha + + + A nillable Measure quantity. Unlike the base measure, references to this type may be nil and may include a nilReason + + + + + + + + + + + + A nillable Velocity quantity. Unlike the base Velocity measure, references to this type may be nil and may include a nilReason + + + + + + + + + diff --git a/IWXXM/metarSpeci.xsd b/IWXXM/metarSpeci.xsd index 18bda897..51ffb38a 100644 --- a/IWXXM/metarSpeci.xsd +++ b/IWXXM/metarSpeci.xsd @@ -1,7 +1,7 @@ - + + - METAR and SPECI reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. @@ -23,12 +23,27 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - + + + The time at which this report was issued + + + + + The aerodrome location for this report + + + + + The time at which phenomena were observed. This may differ from the times reported for forecast conditions + + + 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 @@ -71,7 +86,7 @@ See ICAO Annex 3 / WMO No. 49-2 Table A3-2 - + Extension block for optional and/or additional parameters for element SPECI @@ -102,7 +117,7 @@ See ICAO Annex 3 / WMO No. 49-2 Table A3-2 - + Extension block for optional and/or additional parameters for element METAR @@ -118,17 +133,27 @@ See ICAO Annex 3 / WMO No. 49-2 Table A3-2 - + - A specialized Record type containing meteorological conditions for trend forecasting at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeForecastRecord which is reported on a TAF - conditions reported in trend forecasts in METAR/SPECI differ from forecast groups in a TAF. + Meteorological conditions for trend forecasting at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeForecast which is reported on a TAF - 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 were detected by the automatic observing system, the NotDetectedByAutoSystem nilReason should be used for the cloud association. - + + + + The time at which meteorological phenomena occur + + + + + The human-readable time indicator for this trend forecast. This should match the time period or time instant reported in the phenomenon time + + The prevailing horizontal visibility reported in a trend forecast. @@ -149,11 +174,11 @@ When no operator is reported, prevailing visibility represents an exact value wi - + - + - Extension block for optional and/or additional parameters for element MeteorologicalAerodromeTrendForecastRecord + Extension block for optional and/or additional parameters for element MeteorologicalAerodromeTrendForecast @@ -172,25 +197,25 @@ When CAVOK conditions are observed, no other information on visibility, runway v - + - + - + - A specialized Record type containing meteorological conditions observed at an aerodrome. + 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. - + - + The observed air temperature. This is the temperature indicated by a thermometer exposed to the air in a place sheltered from direct solar radiation. @@ -200,7 +225,7 @@ Measured air temperature shall be given in degrees Celsius ("Cel"). - + The observed dew point temperature. This is the temperature to which a given air parcel must be cooled at constant pressure and constant water vapor content in order for saturation to occur. @@ -210,7 +235,7 @@ Measured dew-point temperature shall be given in degrees Celsius ("Cel"). - + The observed QNH altimeter setting. @@ -222,26 +247,74 @@ Measured altimeter setting shall be given in hectoPascals ("hPa"). - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + - + - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - Extension block for optional and/or additional parameters for element MeteorologicalAerodromeObservationRecord + Extension block for optional and/or additional parameters for element MeteorologicalAerodromeObservation @@ -255,9 +328,9 @@ When CAVOK conditions are observed, no other information on visibility, runway v - + - + @@ -269,12 +342,12 @@ When CAVOK conditions are observed, no other information on visibility, runway v - + The runway to which the conditions apply. The runway may be missing in cases where all runways are closed due to snow - + The type of runway deposit, such as damp conditions, wet snow, or ice. @@ -282,7 +355,7 @@ WMO 306: Table 0919 - + Proportion of runway surface that is contaminated - usually expressed as a percentage of the total runway area. @@ -312,7 +385,7 @@ See WMO No. 306 WMO Code table 1079. - + The estimated surface friction or braking action for the affected runway. When braking conditions are not reported and/or the runway is not operational estimatedSurfaceFrictionOrBrakingAction will not be reported. @@ -320,7 +393,7 @@ WMO 306: Table 0366 - + Extension block for optional and/or additional parameters for element AerodromeRunwayState @@ -341,14 +414,6 @@ ICAO Annex 3 / WMO No. 49-2: Section 4.8.1.5, Table A3-2 "State of the runway" - - - Indicates whether the aerodrome is closed due to an extreme deposit of snow. This affects all runways -<b> -</b>WMO 306: -Section 15.13.6.1 - - @@ -363,12 +428,12 @@ Section 15.13.6.1 - + The runway to which reported runway visual range information applies - + The mean recent runway visual range value observed. This mean represents the 10 minute average for observed RVR except when the 10-minute period immediately preceding the observation includes a marked discontinuity in runway visual range values, only those values occurring after the discontinuity is used for obtaining mean values. @@ -384,14 +449,14 @@ Section 4.3.6.6 - + 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 @@ -422,7 +487,7 @@ Section 4.3.6.6a - + The sea-surface temperature observed by aeronautical meteorological stations established on offshore structures in support of helicopter operations. @@ -437,14 +502,14 @@ Section 4.8.1.5a - + The significant wave height observed. Significant wave height shall be reported in meters ("m"). - + The state of the sea observed by aeronautical meteorological stations established on offshore structures in support of helicopter operations @@ -455,7 +520,7 @@ WMO 306: Table 3700 - + Extension block for optional and/or additional parameters for element AerodromeSeaState @@ -475,12 +540,12 @@ 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 @@ -498,12 +563,12 @@ Table 3700 - + An aggregation of observed cloud conditions typically reported together at an aerodrome, including cloud types, cloud layers, and vertical visibility. - + @@ -528,16 +593,16 @@ 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 + Extension block for optional and/or additional parameters for element AerodromeCloud - + - + @@ -556,7 +621,7 @@ Wind direction shall be given in degrees from true North. Plane angle unit of me - + The observed average wind direction from which the wind is blowing over the past ten minutes. Not reported when winds are variable. @@ -566,7 +631,7 @@ Wind direction shall be given in degrees from true North. Plane angle unit of me - + The average observed wind speed over the past ten minutes @@ -579,14 +644,14 @@ 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". When no operator is reported, wind speed is an exact value with identical semantics to other measured quantities. - + The maximum wind speed observed over the past ten minutes @@ -599,14 +664,14 @@ 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". When no operator is reported, wind gust speed is an exact value with identical semantics to other measured quantities. - + The extreme clockwise direction from which the wind is blowing, inclusive. @@ -617,7 +682,7 @@ Section 4.1.5.2b - + The extreme counter-clockwise direction from which the wind is blowing, inclusive. @@ -628,7 +693,7 @@ Section 4.1.5.2b - + Extension block for optional and/or additional parameters for element AerodromeSurfaceWind @@ -656,7 +721,7 @@ Measured prevailing and minimum horizontal visibility, if present, shall be repo - + The reported prevailing horizontal visibility at the surface that is representative of the aerodrome. @@ -676,7 +741,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. @@ -685,7 +750,7 @@ To report a prevailing visibility of at least 10000 meters, prevailing visibilit When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities - + The minimum observed visibility. @@ -703,7 +768,7 @@ should be reported, with no indication of direction." - + The direction of the minimum visibility relative to the reporting station. This is optional in cases where minimum visibility is reported but the visibility is fluctuating rapidly. Minimum visibility is reported in cardinal and inter-cardinal directions (N, NE, E, SE, S, SW, W, and NW) @@ -713,7 +778,7 @@ Direction of minimum visibility shall be given in degrees from true North. Plane - + Extension block for optional and/or additional parameters for element AerodromeHorizontalVisibility @@ -780,7 +845,7 @@ See WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 018 "Tendency of runway visua - The status of a MeteorologicalAerodromeObservationReport (e.g., a normal issuance, correction of an earlier report, etc.) + The report issuance status (e.g., a normal issuance, correction of an earlier report, etc.) @@ -800,6 +865,33 @@ See WMO No. 306 Vol I.2 FM 94 BUFR code-table 0 20 018 "Tendency of runway visua + + + Time indicators for trend forecast conditions. These are equivalent to the traditional FM, TL, and AT codes + + + + + This trend forecast specifies a time instant at which time conditions occur (AT) + + + + + This trend forecast specifies a time period which commences at the beginning of the trend forecast period and is completed by a specified time (TL) + + + + + This trend forecast specifies a time period which commences at a specified time and is completed by the end of the trend forecast period (FM) + + + + + This trend forecast specifies a time period which commences at a specified time and is completed by another specified time (FM and TL) + + + + Weather phenomenon of operational significance to aviation observed during the period since the last routine report, or last hour, whichever is shorter, but not at the time of observation. diff --git a/IWXXM/rule/codes.wmo.int-49-2-AerodromeRecentWeather.rdf b/IWXXM/rule/codes.wmo.int-49-2-AerodromeRecentWeather.rdf index 3c187e66..2ea59e66 100644 --- a/IWXXM/rule/codes.wmo.int-49-2-AerodromeRecentWeather.rdf +++ b/IWXXM/rule/codes.wmo.int-49-2-AerodromeRecentWeather.rdf @@ -65,11 +65,6 @@ Volcanic ash - - - Thunderstorm with precipitation of hail - - Precipitation of freezng rain @@ -83,6 +78,11 @@ + + + Thunderstorm with precipitation of hail + + Showery precipitation of snow @@ -98,8 +98,6 @@ Precipitation of rain - 2018-04-04T15:53:40.229Z Precipitation of ice pellets @@ -110,21 +108,20 @@ Precipitation of snow grains + 2014-09-03T09:52:41.1Z Thunderstorm with precipitation of snow pellets/small hail - - - Precipitation of rain and snow - - Precipitation of freezing drizzle + 2 Thunderstorm with precipitation of rain @@ -173,7 +170,5 @@ - 3 diff --git a/IWXXM/rule/codes.wmo.int-49-2-SpaceWxLocation.rdf b/IWXXM/rule/codes.wmo.int-49-2-SpaceWxLocation.rdf new file mode 100644 index 00000000..70634634 --- /dev/null +++ b/IWXXM/rule/codes.wmo.int-49-2-SpaceWxLocation.rdf @@ -0,0 +1,93 @@ + + + + + Equatorial latitudes northern hemisphere + Equatorial latitudes northern hemisphere + EQN + + + + + Middle northern hemisphere + Middle northern hemisphere + MNH + + + The items within this code table are the locations of space weather phenomena of significance to aeronautical operations + + + Daylight Side + Daylight Side + DAYLIGHT_SIDE + + + Space Wx Location + + + Equatorial latitudes southern hemisphere + Equatorial latitudes southern hemisphere + EQS + + + + + Middle latitudes southern hemisphere + Middle latitudes southern hemisphere + MSH + + + + 2018-07-05T08:00:33.421Z + + + 1 + + + High latitudes southern hemisphere + High latitudes southern hemisphere + HSH + + + + + High northern hemisphere + High northern hemisphere + HNH + + + + diff --git a/IWXXM/rule/codes.wmo.int-49-2-SpaceWxPhenomena.rdf b/IWXXM/rule/codes.wmo.int-49-2-SpaceWxPhenomena.rdf new file mode 100644 index 00000000..880f7b98 --- /dev/null +++ b/IWXXM/rule/codes.wmo.int-49-2-SpaceWxPhenomena.rdf @@ -0,0 +1,100 @@ + + + + + GNSS-based navigation and surveillance (degradation) - severe + GNSS-based navigation and surveillance (degradation) - severe + GNSS_SEV + + + + + HF communications (propagation, absorption) - moderate + HF communications (propagation, absorption) - moderate + HF_COM_MOD + + + + + Radiation at flight levels (increased exposure) - moderate + Radiation at flight levels (increased exposure) - moderate + RADIATION_MOD + + + The items within this code table are the types of space weather phenomena of significance to aeronautical operations + + + Communications via satellite (propagation, absorption) - moderate + Communications via satellite (propagation, absorption) - moderate + SATCOM_MOD + + + + + GNSS-based navigation and surveillance (degradation) - moderate + GNSS-based navigation and surveillance (degradation) - moderate + GNSS_MOD + + + + + Communications via satellite (propagation, absorption) - severe + Communications via satellite (propagation, absorption) - severe + SATCOM_SEV + + + + Space Wx Phenomena + 2018-08-22T14:48:20.308Z + 1 + + + Radiation at flight levels (increased exposure) - severe + Radiation at flight levels (increased exposure) - severe + RADIATION_SEV + + + + + HF communications (propagation, absorption) - severe + HF communications (propagation, absorption) - severe + HF_COM_SEV + + + + + + diff --git a/IWXXM/rule/iwxxm-collect-codelists.sch b/IWXXM/rule/iwxxm-collect-codelists.sch deleted file mode 100644 index c4d6ab71..00000000 --- a/IWXXM/rule/iwxxm-collect-codelists.sch +++ /dev/null @@ -1,735 +0,0 @@ - - - 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 &lt; 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.TAF19: cloud is mandatory in a non-empty baseForecast when cloudAndVisibilityOK is false - - - - - TAF.TAF18: surfaceWind is 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&amp;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&amp;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.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.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 - - - - - - - - - - - - - - - - - - - - - - - - SIGMET iwxxm:phenomenon elements should be a member of http://codes.wmo.int/49-2/SigWxPhenomena - - - - - - - AIRMETEvolvingCondition iwxxm:surfaceVisibilityCause elements should be a member of http://codes.wmo.int/49-2/WeatherCausingVisibilityReduction - - - - - - - MeteorologicalAerodromeTrendForecastRecord iwxxm:forecastWeather elements should be a member of http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather - - - - - - - MeteorologicalAerodromeForecastRecord iwxxm:weather elements should be a member of http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather - - - - - - - AerodromeRunwayState iwxxm:estimatedSurfaceFrictionOrBrakingAction elements should be a member of http://codes.wmo.int/bufr4/codeflag/0-20-089 - - - - - - - MeteorologicalAerodromeObservationRecord iwxxm:recentWeather elements should be a member of http://codes.wmo.int/49-2/AerodromeRecentWeather - - - - - - - CloudLayer iwxxm:amount elements should be a member of http://codes.wmo.int/49-2/CloudAmountReportedAtAerodrome - - - - - - - AerodromeRunwayState iwxxm:depositType elements should be a member of http://codes.wmo.int/bufr4/codeflag/0-20-086 - - - - - - - VolcanicAshAdvisory iwxxm:colourCode elements should be a member of http://codes.wmo.int/49-2/AviationColourCode - - - - - - - CloudLayer iwxxm:cloudType elements should be a member of http://codes.wmo.int/49-2/SigConvectiveCloudType - - - - - - - AerodromeRunwayState iwxxm:contamination elements should be a member of http://codes.wmo.int/bufr4/codeflag/0-20-087 - - - - - - - MeteorologicalAerodromeObservationRecord iwxxm:presentWeather elements should be a member of http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather - - - - - - - AIRMET iwxxm:phenomenon elements should be a member of http://codes.wmo.int/49-2/AirWxPhenomena - - - - - - - AerodromeSeaState iwxxm:seaState elements should be a member of http://codes.wmo.int/bufr4/codeflag/0-22-061 - - - - - diff --git a/IWXXM/rule/iwxxm-collect.sch b/IWXXM/rule/iwxxm-collect.sch deleted file mode 100644 index 322d1d28..00000000 --- a/IWXXM/rule/iwxxm-collect.sch +++ /dev/null @@ -1,618 +0,0 @@ - - - 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 &lt; 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.TAF19: cloud is mandatory in a non-empty baseForecast when cloudAndVisibilityOK is false - - - - - TAF.TAF18: surfaceWind is 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&amp;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&amp;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.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.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 cbae2ba4..bfff9918 100644 --- a/IWXXM/rule/iwxxm.sch +++ b/IWXXM/rule/iwxxm.sch @@ -1,607 +1,618 @@ 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.AerodromeRunwayState-1: 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.AerodromeRunwayState-2: 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.AerodromeRunwayVisualRange-1: 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 + + + MeteorologicalAerodromeObservation iwxxm:recentWeather elements should be a member of http://codes.wmo.int/49-2/AerodromeRecentWeather - + - METAR_SPECI.MAORep1: Missing reports only include identifying information (time, aerodrome) and no other information + METAR_SPECI.MeteorologicalAerodromeObservationReport-6: When cloud amount is not detected by an automated station, this report must be an automated station report - + - METAR_SPECI.MAORep6: The sampled feature should be equal in observation and trendForecast + METAR_SPECI.MeteorologicalAerodromeObservationReport-7: When cloud base is not detected by an automated station, this report must be an automated station report - + - METAR_SPECI.MAORep3: The sampled feature for a METAR/SPECI observation is an aerodrome + METAR_SPECI.MeteorologicalAerodromeObservationReport-4: When no clouds are detected by an automated station, this report must be an automated station report - + - METAR_SPECI.MAORep7: The procedure of a METAR/SPECI observation should be a metce:Process + METAR_SPECI.MeteorologicalAerodromeObservationReport-5: When both cloud amount and base are not detected by an automated station, this report must be an automated station report - + - METAR_SPECI.MAORep4: The result of a METAR/SPECI observation should be a MeteorologicalAerodromeObservationRecord + METAR_SPECI.MeteorologicalAerodromeObservationReport-2: A 'Nil' report should have appropriately filled elements including Iwxxm:issueTime, iwxxm:aerodrome, iwxxm:observationTime, iwxxm:observation (empty with nilReason) and iwxxm:trendForecast (missing) - + - METAR_SPECI.MAORep5: The result of a METAR/SPECI trendForecast should be a MeteorologicalAerodromeTrendForecastRecord + METAR_SPECI.MeteorologicalAerodromeObservationReport-3: A NORMAL or CORRECTION report should have appropriately filled elements including Iwxxm:issueTime, iwxxm:aerodrome, iwxxm:observationTime and iwxxm:observation - - - METAR_SPECI.ASS1: If the sea state is set, significantWaveHeight is not reported (one or the other) + + + METAR_SPECI.MeteorologicalAerodromeObservationReport-1: A report that failed translation should have as a minimum appropriately filled elements including Iwxxm:issueTime, iwxxm:aerodrome and iwxxm:observationTime - - - METAR_SPECI.ASS3: Either seaState or significantWaveHeight must be present + + + AerodromeSeaState iwxxm:seaState elements should be a member of http://codes.wmo.int/bufr4/codeflag/0-22-061 - - - METAR_SPECI.ASS4: seaSurfaceTemperature shall be reported in degrees Celsius (Cel). + + + AerodromeRunwayState iwxxm:depositType elements should be a member of http://codes.wmo.int/bufr4/codeflag/0-20-086 - + - METAR_SPECI.ASS2: If the significantWaveHeight is set, seaState is not reported (one or the other) + METAR_SPECI.AerodromeSeaState-1: If the sea state is set, significantWaveHeight is not reported - + - 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.AerodromeSeaState-2: If significantWaveHeight is reported, seaState should not be set - - - METAR_SPECI.MATFR5: prevailingVisibility, prevailingVisibilityOperator, clouds, forecastWeather and cloudAndVisibilityOK should be absent when changeIndicator equals 'NO_SIGNIFICANT_CHANGES' + + + METAR_SPECI.AerodromeSeaState-3: seaSurfaceTemperature shall be reported in degrees Celsius (Cel) - - - METAR_SPECI.MATFR1: clouds should be absent when cloudAndVisibilityOK is true + + + METAR_SPECI.AerodromeSeaState-4: significantWaveHeight shall be reported in metres (m) - - - METAR_SPECI.MATFR2: forecastWeather should be absent when cloudAndVisibilityOK is true + + + METAR_SPECI.AerodromeWindShear-1: When all runways are affected by wind shear, no specific runways should be reported - - - METAR_SPECI.MATFR4: prevailingVisibility and prevailingVisibilityOperator should be absent when cloudAndVisibilityOK is true + + + METAR_SPECI.AerodromeWindShear-2: When a single Runway is reported upon, the allRunways flag should be missing or false - - - METAR_SPECI.MATFR3: prevailingVisibility shall be reported in metres (m). + + + AerodromeRunwayState iwxxm:contamination elements should be a member of http://codes.wmo.int/bufr4/codeflag/0-20-087 - - - METAR_SPECI.MAORec6: airTemperature shall be reported in degrees Celsius (Cel). + + + METAR_SPECI.MeteorologicalAerodromeTrendForecast-1: When cloudAndVisibilityOK is true cloud, weather, prevailingVisibility and prevailingVisibilityOperator should be missing - - - METAR_SPECI.MAORec4: clouds should be absent when cloudAndVisibilityOK is true + + + METAR_SPECI.MeteorologicalAerodromeTrendForecast-2: prevailingVisibility shall be reported in metres (m) - - - METAR_SPECI.MAORec3: presentWeather should not be reported when cloudAndVisibilityOK is true + + + METAR_SPECI.MeteorologicalAerodromeObservation-3: airTemperature shall be reported in degrees Celsius (Cel) - - - METAR_SPECI.MAORec2: rvr should not be reported when cloudAndVisibilityOK is true + + + METAR_SPECI.MeteorologicalAerodromeObservation-4: dewpointTemperature shall be reported in degrees Celsius (Cel) - - - METAR_SPECI.MAORec1: visibility should not be reported when cloudAndVisibilityOK is true + + + METAR_SPECI.MeteorologicalAerodromeObservation-1: When cloudAndVisibilityOK is true, visibility, rvr, presentWeather and cloud should be missing - - - METAR_SPECI.MAORec7: dewpointTemperature shall be reported in degrees Celsius (Cel). + + + METAR_SPECI.MeteorologicalAerodromeObservation-2: RVR should always be included if prevailing visibility is below 1500 meters, - - - METAR_SPECI.MAORec8: qnh shall be reported in hectopascals (hPa). + + + METAR_SPECI.MeteorologicalAerodromeObservation-5: qnh shall be reported in hectopascals (hPa) - - - METAR_SPECI.MAORec5: Table A3-2 Note 7 states: "To be included if visibility or RVR &lt; 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.AerodromeCloud-2: When cloud layers are reported vertical visibility should be empty - - - METAR_SPECI.AOC1: Vertical visibility cannot be reported with cloud layers + + + METAR_SPECI.AerodromeCloud-1: When vertical visibility is reported cloud layers should be empty - - - METAR_SPECI.AOC2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). + + + METAR_SPECI.AerodromeCloud-3: verticalVisibility shall be reported in metres (m) or feet ([ft_i]) - + - METAR_SPECI.ASW3: extremeClockwiseWindDirection shall be reported in degrees (deg). + METAR_SPECI.AerodromeSurfaceWind-3: extremeClockwiseWindDirection shall be reported in degrees (deg) - + - METAR_SPECI.ASW4: extremeCounterClockwiseWindDirection shall be reported in degrees (deg). + METAR_SPECI.AerodromeSurfaceWind-4: extremeCounterClockwiseWindDirection shall be reported in degrees (deg) - + - METAR_SPECI.ASW5: meanWindDirection shall be reported in degrees (deg). + METAR_SPECI.AerodromeSurfaceWind-2: Wind direction is not reported when variable winds are indicated - + - METAR_SPECI.ASW6: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + METAR_SPECI.AerodromeSurfaceWind-5: meanWindDirection shall be reported in degrees (deg) - + - METAR_SPECI.ASW2: Wind direction is not reported when variable winds are indicated + METAR_SPECI.AerodromeSurfaceWind-1: All wind UOMs must be the same - + - METAR_SPECI.ASW7: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + METAR_SPECI.AerodromeSurfaceWind-6: meanWindSpeed 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.AerodromeSurfaceWind-7: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]) - - - METAR_SPECI.AHV1: minimumVisibility shall be reported in metres (m). + + + MeteorologicalAerodromeObservation iwxxm:presentWeather elements should be a member of http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather - - - METAR_SPECI.AHV2: minimumVisibilityDirection shall be reported in degrees (deg). + + + AerodromeRunwayState iwxxm:estimatedSurfaceFrictionOrBrakingAction elements should be a member of http://codes.wmo.int/bufr4/codeflag/0-20-089 - + - METAR_SPECI.AHV3: prevailingVisibility shall be reported in metres (m). + METAR_SPECI.AerodromeHorizontalVisibility-1: minimumVisibility shall be reported in metres (m) - - - TAF.MAFR2: cloud should not be reported when cloudAndVisibilityOK is true + + + METAR_SPECI.AerodromeHorizontalVisibility-2: minimumVisibilityDirection shall be reported in degrees (deg) - - - TAF.MAFR1: prevailingVisibility should not be reported when cloudAndVisibilityOK is true + + + METAR_SPECI.AerodromeHorizontalVisibility-3: prevailingVisibility shall be reported in metres (m) - - - TAF.MAFR3: weather should not be reported when cloudAndVisibilityOK is true + + + TAF.MeteorologicalAerodromeForecast-1: When cloudAndVisibilityOK is true, prevailingVisibility, rvr, weather and cloud should be missing - - - TAF.MAFR4: prevailingVisibility shall be reported in metres (m). + + + TAF.MeteorologicalAerodromeForecast-2: prevailingVisibility shall be reported in metres (m) - + - TAF.AATF1: maximumTemperature shall be reported in degrees Celsius (Cel). + TAF.AerodromeAirTemperatureForecast-1: maximumTemperature shall be reported in degrees Celsius (Cel) - + - TAF.AATF2: minimumTemperature shall be reported in degrees Celsius (Cel). - - - - - TAF.TAF19: cloud is mandatory in a non-empty baseForecast when cloudAndVisibilityOK is false - - - - - TAF.TAF18: surfaceWind is mandatory in a non-empty baseForecast + TAF.AerodromeAirTemperatureForecast-2: minimumTemperature shall be reported in degrees Celsius (Cel) - + - TAF.TAF3: An amended report must also include the valid time of the amended report + TAF.TAF-5: A non-empty iwxxm:baseForecast should not have @changeIndicator - + - TAF.TAF4: A cancelled report must also include the valid time of the cancelled report + TAF.TAF-6: in a non-empty iwxxm:baseForecast wxxm:surfaceWind is mandatory - + - TAF.TAF5: A corrected report must reference + TAF.TAF-7: In a non-empty iwxxm:baseForecast when @cloudAndVisibilityOK is false iwxxm:prevailingVisibility and iwxxm:cloud are mandatory - + - TAF.TAF9: Missing TAF reports only include aerodrome information and issue time information + TAF.TAF-2: A 'Nil' report should have appropriately filled elements including iwxxm:issueTime, iwxxm:aerodrome, iwxxm:validTime (missing), iwxxm:baseForecast (empty with nilReason), iwxxm:changeForecast (missing), iwxxm:previousReportAerodrome (missing) and iwxxm:previousReportValidPeriod (missing) - + - TAF.TAF2: previousReportValidPeriod must be null unless this cancels, corrects or amends a previous report + TAF.TAF-3: A NORMAL report should have appropriately filled elements including iwxxm:issueTime, iwxxm:aerodrome, iwxxm:validTime, iwxxm:baseForecast, iwxxm:previousReportAerodrome (missing) and iwxxm:previousReportValidPeriod (missing) - + - TAF.TAF11: Non-missing TAF reports must contains validTime + TAF.TAF-1: A report that failed translation should have as a minimum appropriately filled elements including iwxxm:issueTime, iwxxm:aerodrome and iwxxm:validTime - + - TAF.TAF8: Base conditions may not have a change indicator + TAF.TAF-4: An AMENDMENT, CANCELLATION or CORRECTION report should have the appropriate elements filled including iwxxm:issueTime, iwxxm:aerodrome, iwxxm:validTime, iwxxm:previousReportAerodrome and iwxxm:previousReportValidPeriod should be non-empty - - - 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&amp;M validTime of baseForecast must be a time period for TAF forecasts - - - - - TAF.TAF15: The sampled feature of changeForecast is always an aerodrome + + + SIGMET.SIGMET-4: iwxxm:analysis//iwxxm:phenomenonTime must be equal to iwxxm:validPeriod//gml:beginPosition - - - TAF.TAF17: The procedure of a TAF changeForecast should be a metce:Process + + + SIGMET.SIGMET-6: A report cannot have both iwxxm:forecastPositionAnalysis and iwxxm:analysis//iwxxm:directionOfMotion (with or without iwxxm:analysis//iwxxm:speedOfMotion) at the same time - - - TAF.TAF13: The O&amp;M validTime of changeForecast must be a time period for TAF forecasts + + + SIGMET.SIGMET-5: iwxxm:forecastPositionAnalysis//iwxxm:phenomenonTime must be less than or equal to iwxxm:validPeriod//endPosition - - - TAF.TAF6: resultTime for the baseForecast and the changeForecasts must match + + + SIGMET.SIGMET-8: In a SIGMET report the child element of iwxxm:analysis should be SIGMETEvolvingConditionCollection - + - SIGMET.SIGMET9: SIGMET can not have both a forecastPositionAnalysis and expected speed and/or direction of motion + SIGMET.SIGMET-9: In a SIGMET report the child element of iwxxm:forecastPositionAnalysis should be SIGMETPositionCollection - + - SIGMET.SIGMET1: A cancelled SIGMET should only include identifying information (time and airspace) and no other information + SIGMET.SIGMET-10: In a SIGMET report there should be one iwxxm:analysis at most - + - SIGMET.SIGMET2: There must be at least one analysis when a SIGMET does not have canceled status + SIGMET.SIGMET-11: In a SIGMET report there should be one iwxxm:forecastPositionAnalysis at most - + - SIGMET.SIGMET10: SIGMET must have a cancelled status if reporting volcanicAshMovedToFIR + SIGMET.SIGMET-2: A 'CANCELLATION' report should have appropriately filled elements including Iwxxm:issueTime, iwxxm:issuingAirTrafficServicesUnit, iwxxm:originatingMeteorologicalWatchOffice, iwxxm:issuingAirTrafficServicesRegion, iwxxm:sequenceNumber, iwxxm:validPeriod, iwxxm:cancelledSequenceNumber, iwxxm:cancelledValidPeriod, iwxxm:phenomenon (inapplicable) and iwxxm:analysis (inapplicable) - + - SIGMET.SIGMET4: Sampled feature in analysis and forecastPositionAnalysis must be an FIR, UIR, or CTA + SIGMET.SIGMET-3: A 'NORMAL' report should have appropriately filled elements including Iwxxm:issueTime, iwxxm:issuingAirTrafficServicesUnit, iwxxm:originatingMeteorologicalWatchOffice, iwxxm:issuingAirTrafficServicesRegion, iwxxm:sequenceNumber, iwxxm:validPeriod, iwxxm:phenomenon, iwxxm:analysis, iwxxm:forecastPositionAnalysis (optional) - + - SIGMET.SIGMET7: The procedure of a SIGMET analysis should be a metce:Process + SIGMET.SIGMET-1: A report that failed translation should have as a minimum appropriately filled elements including Iwxxm:issueTime, iwxxm:issuingAirTrafficServicesUnit and iwxxm:validPeriod - + - SIGMET.SIGMET3: OBS and FCST analyses must have a result type of SIGMETEvolvingConditionCollection + SIGMET.SIGMET-7: iwxxm:volcanicAshMovedToFIR can only be used in a VolcanicAshSIGMET 'CANCELLATION' report - - - SIGMET.SIGMET8: The procedure of a SIGMET forecastPositionAnalysis should be a metce:Process + + + SIGMET iwxxm:phenomenon elements should be a member of http://codes.wmo.int/49-2/SigWxPhenomena - - - SIGMET.SIGMET5: The result of a forecastPositionAnalysis should be a SIGMETPositionCollection + + + SIGMET.SIGMETEvolvingCondition-2: directionOfMotion shall be reported in degrees (deg) - + - SIGMET.SEC1: directionOfMotion shall be reported in degrees (deg). + SIGMET.SIGMETEvolvingCondition-1: iwxxm:speedOfMotion cannot be given without having iwxxm:directionOfMotion - + - SIGMET.SEC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + SIGMET.SIGMETEvolvingCondition-3: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]) + + + + + TropicalCycloneSIGMET.TropicalCycloneSIGMET-1: A 'NORMAL' report should also have iwxxm:TropicalCyclone - - - SIGMET.SECC3: The number of SIGMETEvolvingConditionCollection member should be 1 for non-Tropical Cyclone/Volcanic Ash SIGMETs + + + TropicalCycloneSIGMET.TropicalCycloneSIGMET-2: In a TC SIGMET report the child elements of iwxxm:analysis should be TropicalCycloneSIGMETEvolvingConditionCollection and TropicalCycloneSIGMETEvolvingCondition - - - 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. + + + TropicalCycloneSIGMET.TropicalCycloneSIGMET-3: In a TC SIGMET report the child elements of iwxxm:forecastPositionAnalysis should be TropicalCycloneSIGMETPositionCollection and TropicalCycloneSIGMETPosition - - - 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. + + + VolcanicAshSIGMET.VolcanicAshSIGMET-1: A 'NORMAL' report should also have iwxxm:eruptingVolcano - - - SIGMET.SPC1: The number of SIGMETPositionCollection member should be 1 for non-Tropical Cyclone/Volcanic Ash SIGMETs + + + VolcanicAshSIGMET.VolcanicAshSIGMET-2: In a VA SIGMET report the child elements of iwxxm:analysis should be VolcanicAshSIGMETEvolvingConditionCollection - - - 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. + + + VolcanicAshSIGMET.VolcanicAshSIGMET-3: In a VA SIGMET report the child elements of iwxxm:forecastPositionAnalysis should be VolcanicAshSIGMETPositionCollection - - - 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. + + + AIRMETEvolvingCondition iwxxm:surfaceVisibilityCause elements should be a member of http://codes.wmo.int/49-2/WeatherCausingVisibilityReduction - + - AIRMET.AEC1: cloudBase shall be reported in metres (m) or feet ([ft_i]). + AIRMET.AIRMETEvolvingCondition-1: 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.AIRMETEvolvingCondition-2: cloudTop shall be reported in metres (m) or feet ([ft_i]) - + - AIRMET.AEC3: directionOfMotion shall be reported in degrees (deg). + AIRMET.AIRMETEvolvingCondition-3: directionOfMotion shall be reported in degrees (deg) - + - AIRMET.AEC4: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + AIRMET.AIRMETEvolvingCondition-4: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]) - + - AIRMET.AEC5: surfaceVisibility shall be reported in metres (m). + AIRMET.AIRMETEvolvingCondition-5: surfaceVisibility shall be reported in metres (m) - + - AIRMET.AEC7: surfaceWindDirection shall be reported in the degrees unit of measure ('deg'). + AIRMET.AIRMETEvolvingCondition-8: surfaceWindDirection and surfaceWindSpeed must be reported together - + - AIRMET.AEC6: surfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + AIRMET.AIRMETEvolvingCondition-7: surfaceWindDirection shall be reported in the degrees unit of measure ('deg') - + - AIRMET.AEC8: surfaceWindDirection and surfaceWindSpeed must be reported together + AIRMET.AIRMETEvolvingCondition-6: surfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]) - - - AIRMET.AIRMET5: AIRMET can not have both a forecastPositionAnalysis and expected speed and/or direction of motion + + + AIRMET iwxxm:phenomenon elements should be a member of http://codes.wmo.int/49-2/AirWxPhenomena - + - AIRMET.AIRMET2: A canceled AIRMET only include identifying information (time and airspace) and no other information + AIRMET.AIRMET-4: iwxxm:analysis//iwxxm:phenomenonTime must be equal to iwxxm:validPeriod//gml:beginPosition - + - AIRMET.AIRMET3: There must be at least one analysis when a AIRMET does not have canceled status + AIRMET.AIRMET-2: A 'CANCELLATION' report should have appropriately filled elements including Iwxxm:issueTime, iwxxm:issuingAirTrafficServicesUnit, iwxxm:originatingMeteorologicalWatchOffice, iwxxm:issuingAirTrafficServicesRegion, iwxxm:sequenceNumber, iwxxm:validPeriod, iwxxm:cancelledSequenceNumber, iwxxm:cancelledValidPeriod, iwxxm:phenomenon (inapplicable) and iwxxm:analysis (inapplicable) - + - AIRMET.AIRMET4: The procedure of an AIRMET analysis should be a metce:Process + AIRMET.AIRMET-3: A 'NORMAL' report should have appropriately filled elements including Iwxxm:issueTime, iwxxm:issuingAirTrafficServicesUnit, iwxxm:originatingMeteorologicalWatchOffice, iwxxm:issuingAirTrafficServicesRegion, iwxxm:sequenceNumber, iwxxm:validPeriod, iwxxm:phenomenon, iwxxm:analysis, iwxxm:forecastPositionAnalysis (optional) - + - AIRMET.AIRMET1: OBS and FCST classifications must have a result type of AIRMETEvolvingConditionCollection + AIRMET.AIRMET-1: A report that failed translation should have as a minimum appropriately filled elements including Iwxxm:issueTime, iwxxm:issuingAirTrafficServicesUnit and iwxxm:validPeriod - + - TCA.TCFC1: maximumSurfaceWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + TropicalCycloneAdvisory.TropicalCycloneForecastConditions-1: 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 + TropicalCycloneAdvisory.TropicalCycloneAdvisory-1: A report that failed translation should have as a minimum appropriately filled elements including Iwxxm:issueTime, and iwxxm:issuingTropicalCycloneAdvisoryCentre - - - 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). + TropicalCycloneAdvisory.TropicalCycloneObservedConditions-1: centralPressure shall be reported in hectopascals (hPa) - + - TCA.TCOC2: meanMaxSurfaceWind shall be reported in metres per second (m/s) or knots ([kn_i]). + TropicalCycloneAdvisory.TropicalCycloneObservedConditions-2: meanMaxSurfaceWind shall be reported in metres per second (m/s) or knots ([kn_i]) - + - TCA.TCOC3: movementDirection shall be reported in degrees (deg). + TropicalCycloneAdvisory.TropicalCycloneObservedConditions-3: movementDirection shall be reported in degrees (deg) - + - TCA.TCOC4: movementSpeed shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + TropicalCycloneAdvisory.TropicalCycloneObservedConditions-4: movementSpeed shall be reported in kilometres per hour (km/h) or knots ([kn_i]) - + - VAA.VAC1: directionOfMotion shall be reported in degrees (deg). + VolcanicAshAdvisory.VolcanicAshCloud-1: directionOfMotion shall be reported in degrees (deg) - + - VAA.VAC2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]). + VolcanicAshAdvisory.VolcanicAshCloud-2: speedOfMotion shall be reported in kilometres per hour (km/h) or knots ([kn_i]) - + - VAA.VAC3: windDirection shall be reported in degrees (deg). + VolcanicAshAdvisory.VolcanicAshCloud-3: windDirection shall be reported in degrees (deg) - + - VAA.VAC4: windSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + VolcanicAshAdvisory.VolcanicAshCloud-4: 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 + + + VolcanicAshAdvisory iwxxm:colourCode elements should be a member of http://codes.wmo.int/49-2/AviationColourCode - + - VAA.VAA1: The result of a VAA analysis should be a VolcanicAshConditions + VolcanicAshAdvisory.VolcanicAshAdvisory-1: A report that failed translation should have as a minimum appropriately filled elements including Iwxxm:issueTime and iwxxm:issuingVolcanicAshAdvisoryCentre - + + + SpaceWeatherRegion iwxxm:locationIndicator elements should be a member of http://codes.wmo.int/49-2/SpaceWxLocation + + + + + SpaceWeatherAdvisory iwxxm:phenomenon elements should be a member of http://codes.wmo.int/49-2/SpaceWxPhenomena + + + + + SpaceWeatherAdvisory.SpaceWeatherAdvisory-1: A report that failed translation should have as a minimum appropriately filled elements including Iwxxm:issueTime and iwxxm:issuingSpaceWeatherCentre + + + + + MeteorologicalAerodromeTrendForecast iwxxm:weather elements should be a member of http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather + + + + + MeteorologicalAerodromeForecast iwxxm:weather elements should be a member of http://codes.wmo.int/49-2/AerodromePresentOrForecastWeather + + + + + CloudLayer iwxxm:cloudType elements should be a member of http://codes.wmo.int/49-2/SigConvectiveCloudType + + + + + CloudLayer iwxxm:amount elements should be a member of http://codes.wmo.int/49-2/CloudAmountReportedAtAerodrome + + + - COMMON.CL1: base shall be reported in metres (m) or feet ([ft_i]). + COMMON.CloudLayer-1: 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.Report-5: All gml:ids in IWXXM reports must be prefixed with 'uuid.' and must be UUID version 4 - - - COMMON.Report2: Operational reports should not include a permissibleUsageReason + + + COMMON.Report-4: Total size of extension content must not exceed 5000 characters per report - - - COMMON.Report1: Non-operational reports must include a permissibleUsageReason + + + COMMON.Report-1: 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.Report-2: Operational reports should not include a permissibleUsageReason + + + + + COMMON.Report-3: Translated reports must include @translatedBulletinID, @translatedBulletinReceptionTime, @translationCentreDesignator, @translationCentreName, @translationTime and optionally @translationFailedTAC if translation failed + + + + + COMMON.AerodromeCloudForecast-2: If cloud layers are reported vertical visibility should be empty - + - COMMON.ACF1: Vertical visibility cannot be reported together with cloud layers + COMMON.AerodromeCloudForecast-1: If vertical visibility is reported cloud layers should be empty - + - COMMON.ACF2: verticalVisibility shall be reported in metres (m) or feet ([ft_i]). + COMMON.AerodromeCloudForecast-3: verticalVisibility shall be reported in metres (m) or feet ([ft_i]) - + - COMMON.ASWF1: Wind direction is not reported when variable winds are indicated + COMMON.AerodromeSurfaceWindForecast-1: Wind direction is not reported when variable winds are indicated - + - COMMON.ASWTF1: meanWindDirection shall be reported in degrees (deg). + COMMON.AerodromeSurfaceWindTrendForecast-1: meanWindDirection shall be reported in degrees (deg) - + - COMMON.ASWTF2: meanWindSpeed shall be reported in metres per second (m/s) or knots ([kn_i]). + COMMON.AerodromeSurfaceWindTrendForecast-2: 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]). + COMMON.AerodromeSurfaceWindTrendForecast-3: windGustSpeed shall be reported in metres per second (m/s) or knots ([kn_i]) diff --git a/IWXXM/sigmet.xsd b/IWXXM/sigmet.xsd index 61184064..367ad0ed 100644 --- a/IWXXM/sigmet.xsd +++ b/IWXXM/sigmet.xsd @@ -1,9 +1,7 @@ - + - - SIGMET reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. @@ -12,6 +10,114 @@ 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. + + + Evolving condition collection for tropical cyclone SIGMETs + + + + + + + + + The position of a tropical cyclone + + + + + + The ID of the relevant tropical cyclone + + + + + + + + + + + + + + + Position collection for tropical cyclone SIGMETs + + + + + + + + + The position of a tropical cyclone + + + + + + The ID of the relevant tropical cyclone + + + + + + + + + + + + + + + Evolving condition collection for volcanic ash SIGMETs + + + + + + + + + The ID of the relevant erupting volcano + + + + + + + + + + + + + + + Position collection for volcanic ash SIGMETs + + + + + + + + + The ID of the relevant erupting volcano + + + + + + + + + + + + A collection of SIGMETEvolvingConditions, each representing a location where SIGMET observed or forecast conditions exist. All members of this collection are of type SIGMETEvolvingCondition. @@ -21,8 +127,17 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - - + + + The time at which meteorological phenomena occur + + + + + The members of this collection + + + Extension block for optional and/or additional parameters for element SIGMETEvolvingConditionCollection @@ -56,12 +171,12 @@ In cases where the position covers an entire FIR or CTA, ("ENTIRE CTA or ENTIRE - + The geographic region affected by the reported phenomenon at a particular time (thunderstorms, volcanic ash, etc.). This geometry covers all combinations of phenomenon historically reported in Annex 3: a boundary with a base and top, a TC centre position, and a VA line with a width - + Extension block for optional and/or additional parameters for element SIGMETPosition @@ -95,6 +210,11 @@ SIGMETs may report either observed or forecast hazardous conditions. Additionall + + + The time at which this report was issued + + The ATS unit serving the FIR or CTA to which the SIGMET refers @@ -103,21 +223,26 @@ ICAO Annex 3 / WMO No. 49-2: A6-1: "Location indicator of FIR/CTA" - + MWO originating this report - + + + The ATS region (FIR, UIR, CTA, or FIR/UIR) + + + The sequence number of this message. For example: "5", "A3", or "2" - The valid period for the entire report, including all observations and forecast conditions. Each observation/forecast phenomenon includes its own period of validity for described meteorological conditions, which is represented as the O&M Observation validTime. + The valid period for the entire report covering all observations and forecast conditions. Each observation/forecast phenomenon includes its own temporal description for the described meteorological conditions, which is represented as phenomenonTime. -For example, an issued tropical cyclone SIGMET may be valid from 1600 UTC to 2200 UTC with an observed position at 1600 UTC and a forecast position of the centre of the tropical cyclone at 2200 UTC. In this case the SIGMET validPeriod would be 1600 UTC to 2200 UTC, the analysis validTime would be 1600 UTC, and the forecastPositionAnalysis validTime would be 2200 UTC. +For example, an issued tropical cyclone SIGMET may be valid from 1600 UTC to 2200 UTC with an observed position at 1600 UTC and a forecast position of the centre of the tropical cyclone at 2200 UTC. In this case the SIGMET validPeriod would be 1600 UTC to 2200 UTC, the analysis phenomenonTime would be 1600 UTC, and the forecastPositionAnalysis phenomenonTime would be 2200 UTC. @@ -141,16 +266,16 @@ YUDD SIGMET A3 VALID ... 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. + A SIGMET report may include a phenomenon covering more than one area within the FIR/UIR/CTA. This translates into 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 SIGMETEvolvingCondition. -Each analysis has a single EvolvingMeteorologicalCondition as its result. +Each analysis has a single SIGMETEvolvingConditionCollection as its result. - + - One or more forecast positions at the end of the valid period - one for each phenomenon area within an FIR. These are modeled as a single OM_Observation sub-type with a feature collection result due to the shared time and other observation metadata for all forecast positions. + A forecast of the phenomenon at the end of the valid period. This is modeled by SIGMETPosition for individual area of the phenomenon and aggregated into a single SIGMETPositionCollection as a result to forecastPositionAnalysis. @@ -158,7 +283,7 @@ Each analysis has a single EvolvingMeteorologicalCondition as its result. The FIR to which volcanic ash has moved. Reported only on SIGMET cancellation reports - + Extension block for optional and/or additional parameters for element SIGMET @@ -190,14 +315,7 @@ TC TOP (ABV and BLW) conditions are represented by the vertical component of the - - - This element refers to the expected direction of movement which the phenomenon is moving towards, .e.g, "moving east". When no movement is expected, this is a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason and the speedOfMotion will be 0. - -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 @@ -216,6 +334,13 @@ To report an airspace lower limit of below FL 300, airspace lower limit is repor 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 + + + This element refers to the expected direction of movement which the phenomenon is moving towards, .e.g, "moving east". When no movement is expected, this is a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason and the speedOfMotion will be 0. + +This element value is given in degrees from true North. Plane angle unit of measure (uom) is "deg". + + The expected speed of movement of a meteorological condition. When no movement is expected, this will have a value of 0 and directionOfMotion will have a http://www.opengis.net/def/nil/OGC/0/inapplicable nilReason. @@ -223,7 +348,7 @@ To report an airspace upper limit of above FL 300, airspace upper limit is repor speedOfMotion can be provided in either two units of measures: "km/h" or "[kn_i]" (knots). - + Extension block for optional and/or additional parameters for element SIGMETEvolvingCondition @@ -258,16 +383,9 @@ speedOfMotion can be provided in either two units of measures: "km/h" or "[kn_i] - + - 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 for element TropicalCycloneSIGMET + The tropical cyclone being reported in this SIGMET, required in all cases other than cancellations. When reporting the tropical cyclone name, 'NN' may be used if the tropical cyclone is unnamed @@ -290,14 +408,9 @@ When reporting the tropical cyclone name, 'NN' may be used if the tropical cyclo - - - The volcano that is erupting - - - + - Extension block for optional and/or additional parameters for element VolcanicAshSIGMET + The volcano that is erupting - required in all cases other than cancellations @@ -320,8 +433,17 @@ When reporting the tropical cyclone name, 'NN' may be used if the tropical cyclo - - + + + The time at which meteorological phenomena occur + + + + + The members of this collection + + + Extension block for optional and/or additional parameters for element SIGMETPositionCollection diff --git a/IWXXM/spaceWxAdvisory.xsd b/IWXXM/spaceWxAdvisory.xsd new file mode 100755 index 00000000..85684d22 --- /dev/null +++ b/IWXXM/spaceWxAdvisory.xsd @@ -0,0 +1,177 @@ + + + + + + Space Weather Advisory reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. + +Space Weather Advisories report the occurrence and/or expected occurrence of space weather phenomena which may affect the safety of aircraft operations, and of the development of those phenomena in time and space. These phenomena are reported as impacted regions of airspace. + +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. + + + + An advisory of space weather conditions of significance to aviation as represented in ICAO Annex 3 / WMO No. 49-2. Volcanic ash advisories are issued by space weather centres (SWXCs) + + + + + + + + + The time at which this report was issued + + + + + The issuing space weather centre (SWXC) + + + + + Advisory number: four digit year and unique message number. Example "2018/1" + + + + + The number of the advisory being replaced. Example "2018/1" + + + + + The space weather phenomenon, such as radiation or satellite communication + + + + + Observed and forecast space weather information. Analyses should be reported in the order in which they occur, starting with the initial observed/forecast conditions and proceeding through each subsequent forecast to the end of the period + + + + + Remarks, as necessary. + +When the remark is nil, it should be indicated by a missing remarks with a nil reason of 'inapplicable' + + + + + The time at which the next advisory will be issued + +Use attribute indeterminatePosition to element timePosition to indicate if the actual temporal position is before or after the specified value. + +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 for element SpaceWeatherAdvisory + + + + + + + + + + + + + + + + Observed or forecast space weather phenomena + + + + + + + + + The time at which meteorological phenomena occur + + + + + + Extension block for optional and/or additional parameters for element SpaceWeatherAnalysis + + + + + + Indicator of observed or forecast conditions + + + + + + + + + + + + + + + + + + + + The geographic location at which space weather phenomena occur + + + + + The location of phenomena relative to the location lower limit. Typically used to report conditions above a lower limit specified in the location + + + + + The geographic area code, such as high northern latitudes + + + + + Extension block for optional and/or additional parameters for element SpaceWeatherRegion + + + + + + + + + + + + + + + + + http://codes.wmo.int/49-2/SpaceWxLocation + none + + + + + + + + + + http://codes.wmo.int/49-2/SpaceWxPhenomena + none + + + + + + + diff --git a/IWXXM/taf.xsd b/IWXXM/taf.xsd index 9e11c838..1c85686d 100644 --- a/IWXXM/taf.xsd +++ b/IWXXM/taf.xsd @@ -1,7 +1,6 @@ - + - TAF reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. @@ -32,17 +31,22 @@ Prevailing conditions and forecast changes differ in that the prevailing conditi The time at which this report was issued. Note that this should be identical to the resultTime of each MeteorologicalAerodromeForecast, whose results are made available at the same time as this report. TAF reports have an issueTime to assist in discovery and to provide unambiguous semantics at the report level. + + + The aerodrome location for this report + + The time frame at which this report is valid. All forecast elements should be valid within this period - + The prevailing conditions. Mandatory in all cases except missing or cancelled reports - + Forecast that modifies the base forecast. While there is no maximum number of forecasts, this should normally not exceed five in number. <b><u> </u></b>ICAO Annex 3 / WMO No. 49-2: Section 1.5: "The number of change and probability groups should be kept to a minimum and should not normally exceed five groups". @@ -57,7 +61,7 @@ Prevailing conditions and forecast changes differ in that the prevailing conditi The valid time period for the previously amended and/or cancelled report - + Extension block for optional and/or additional parameters for element TAF @@ -80,9 +84,9 @@ 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. + Meteorological conditions forecast at an aerodrome. This class is also related but not identical to MeteorologicalAerodromeTrendForecast, 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. @@ -93,10 +97,15 @@ Note that the TAC representations for "FM", "TL", and "AT" are represented by th AT - a phenomenonTime with a TimeInstant - + + + + The time at which the reported phenomena or change of phenomena occur. For change indicators of FROM, PROB 30/40, and TEMPO this is the period of time at which reported meteorological conditions occur. For BECOMING conditions this represents the time over which conditions are changing. This is equivalent to how time information is reported in the TAC codes + + The prevailing horizontal visibility, mandatory except when ceiling and visibility is reported as OK @@ -120,9 +129,9 @@ When no operator is reported, prevailing visibility represents an exact value wi - + - Extension block for optional and/or additional parameters for element MeteorologicalAerodromeForecastRecord + Extension block for optional and/or additional parameters for element MeteorologicalAerodromeForecast @@ -130,7 +139,7 @@ When no operator is reported, prevailing visibility represents an exact value wi The type of change being reported (FROM, BECOMING, TEMPORARY, etc.). -A change indicator is required for all MeteorologicalAerodromeForecastRecords excepting reported base conditions. +A change indicator is required for all MeteorologicalAerodromeForecasts excepting reported base conditions. @@ -143,9 +152,9 @@ When CAVOK conditions are observed, no other information on visibility, runway v - + - + @@ -197,7 +206,7 @@ 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 54f8892d..a0a492ab 100644 --- a/IWXXM/tropicalCycloneAdvisory.xsd +++ b/IWXXM/tropicalCycloneAdvisory.xsd @@ -1,7 +1,6 @@ - + - Tropical Cyclone Advisory reporting constructs as defined in ICAO Annex 3 / WMO No. 49-2. @@ -29,39 +28,43 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha The issuing TCAC - + The tropical cyclone name. If the tropical cyclone is unnamed, 'NN' may be used - + - Advisory number, starting with 1 for each cyclone + Advisory number: year in full and message number (separate sequence for each cyclone) - + The observed conditions of the tropical cyclone - + The forecast conditions of the tropical cyclone, one each for the 6 hour, 12 hour, 18 hour, and 24 hour forecast periods - + - Remarks, as necessary + Remarks, as necessary. + +When the remark is nil, it should be indicated by a missing remarks with a nil reason of 'inapplicable' - + The time at which the next advisory is expected to be issued. +Use attribute indeterminatePosition to element timePosition to indicate if the actual temporal position is before or after the specified value. + 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 for element TropicalCycloneAdvisory @@ -86,6 +89,21 @@ When no subsequent advisory is expected to be issued it should be indicated by a + + + The time at which meteorological phenomena occur + + + + + The tropical cyclone position + + + + + Location of cumulonimbus cloud + + The movement observed for the tropical cyclone @@ -111,7 +129,7 @@ When no subsequent advisory is expected to be issued it should be indicated by a The mean maximum surface wind near the cyclone centre over 10 minutes. Mean maximum wind speeds shall be provided in either two units of measures: "m/s" or "[kn_i]" (knot). - + Extension block for optional and/or additional parameters for element TropicalCycloneObservedConditions @@ -136,12 +154,22 @@ When no subsequent advisory is expected to be issued it should be indicated by a + + + The time at which meteorological phenomena occur + + + + + The tropical cyclone position + + The forecast maximum surface wind speed. Maximum wind speeds shall be provided in either two units of measures: "m/s"or "[kn_i]" (knot). - + Extension block for optional and/or additional parameters for element TropicalCycloneForecastConditions @@ -159,7 +187,7 @@ When no subsequent advisory is expected to be issued it should be indicated by a - The movement type for a tropical cyclone, either MOVING, MOVING_SLOWLY, or STATIONARY + The movement type for a tropical cyclone, either MOVING or STATIONARY @@ -167,11 +195,6 @@ When no subsequent advisory is expected to be issued it should be indicated by a The tropical cyclone is moving and will be reported with the associated movement speed and direction - - - The tropical cyclone is moving slowly (< 6 km/h or 3 kt) and will not have a reported movement speed or direction - - The tropical cyclone is stationary (< 2 km/h or 1 kt) and will not have a reported movement speed or direction diff --git a/IWXXM/volcanicAshAdvisory.xsd b/IWXXM/volcanicAshAdvisory.xsd index d5cd3d0f..9ed34d7b 100644 --- a/IWXXM/volcanicAshAdvisory.xsd +++ b/IWXXM/volcanicAshAdvisory.xsd @@ -1,8 +1,7 @@ - + - @@ -21,23 +20,27 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - + + + The time at which this report was issued + + The issuing VAAC - + The erupting volcano that is the source of volcanic ash - + Advisory number: year in full and message number (separate sequence for each volcano) - + Information source - described in free text @@ -47,27 +50,28 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha The aviation colour code - + The observed and estimated positions of volcanic ash clouds. Each analysis represents an observed or 6/12/18 hour forecast of volcanic ash. - - - Remarks, as necessary - - - + - The latest time at which the next advisory will be issued + Remarks, as necessary. + +When the remark is nil, it should be indicated by a missing remarks with a nil reason of 'inapplicable' - + - The earliest time at which the next advisory will be issued + The time at which the next advisory will be issued + +Use attribute indeterminatePosition to element timePosition to indicate if the actual temporal position is before or after the specified value. + +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 for element VolcanicAshAdvisory @@ -92,8 +96,13 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha + + + The time at which meteorological phenomena occur + + - + Extension block for optional and/or additional parameters for element VolcanicAshConditions @@ -118,7 +127,7 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha - + The horizontal and vertical extent of the ash cloud @@ -163,7 +172,7 @@ References to WMO and ICAO Technical Regulations within this XML schema shall ha The lower limit vertical reference of wind conditions. Only reported when volcanic ash is not identifiable from satellite data. - + Extension block for optional and/or additional parameters for element VolcanicAshCloud diff --git a/LATEST_VERSION b/LATEST_VERSION index d09e16f9..3ec1ea74 100644 --- a/LATEST_VERSION +++ b/LATEST_VERSION @@ -1,2 +1,2 @@ -2.1.1 +3.0.0RC1 IWXXM