Skip to content

Commit

Permalink
include 3.0.0RC1
Browse files Browse the repository at this point in the history
  • Loading branch information
marqh committed Feb 11, 2019
1 parent 2a9ae5a commit 8c3ceaa
Show file tree
Hide file tree
Showing 69 changed files with 3,916 additions and 4,498 deletions.
29 changes: 28 additions & 1 deletion IWXXM/ReleaseNotes-IWXXM.txt
Original file line number Diff line number Diff line change
@@ -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
====================================
Expand All @@ -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
Expand Down
81 changes: 54 additions & 27 deletions IWXXM/TAC-to-XML-Guidance.txt
Original file line number Diff line number Diff line change
Expand Up @@ -16,49 +16,58 @@ 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

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
Expand All @@ -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
Expand All @@ -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
Expand All @@ -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
==========================
Expand All @@ -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"
Loading

0 comments on commit 8c3ceaa

Please sign in to comment.