Skip to content

Commit

Permalink
include 2.1.0
Browse files Browse the repository at this point in the history
  • Loading branch information
marqh committed Feb 11, 2019
1 parent 72a6a9e commit 780aed9
Show file tree
Hide file tree
Showing 36 changed files with 1,853 additions and 547 deletions.
28 changes: 28 additions & 0 deletions IWXXM/ReleaseNotes-IWXXM.txt
Original file line number Diff line number Diff line change
@@ -1,3 +1,31 @@
====================================
2.1 - March 2017
====================================
* Modified AIRMET and SIGMET to correctly handle complex cases where there are multiple OBS/FCST elements and forecast
position elements. See http://bit.ly/2lZroAM for more information.
* AIRMET and SIGMET analysis results are now Collection types which may include up to two sets of conditions as
allowed by ICAO Annex 3 Amendment 77 Table A6-1A Note 27 on "AND" elements. AIRMET and SIGMET XML elements were
renamed to be more consistent. The OBS/FCST time indicator was moved to the Collection types, and all other
information may be repeated on EvolvingCondition types. EvolvingCondition types may now only have a single geometry
+ New elements: SIGMETEvolvingConditionCollection and AIRMETEvolvingConditionCollection
* Renamed elements: (SIGMET) EvolvingMeteorologicalCondition -> SIGMETEvolvingCondition,
AIRMETEvolvingMeteorologicalCondition -> AIRMETEvolvingCondition, SIGMET MeteorologicalPosition -> SIGMETPosition,
SIGMET MeteorologicalPositionCollection -> SIGMETPositionCollection
* AIRMET and SIGMET analysis elements are now 0..1 and there must now be exactly one geometry element per member
element. Multiple polygons for an OBS or FCST are represented as multiple member elements in the result
* No significant change (NSC) is now represented on TAFs as a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance".
The TAF ForecastChangeIndicator "NO_SIGNIFICANT_CHANGES" has been removed and "changeForecast" references are now nillable
* The TAC to XML Guidance document has been updated to be more internally consistent and readable
* Added translation failed examples for each product and slightly improved SIGMET Schematron rules to properly support
these types of messages
* Per AIXM developer feedback, all AIXM snippets now use the correct "SNAPSHOT" terminology for time slices instead of
"BASELINE". This required changes to a number of examples
* The METAR LKKV example has been updated to include a wind shear section
* Made relevant elements mentioned in TAC-to-XML-Guidance.txt nillable to allow the inclusion of nilReason as indicated
in the text
* Corrected syntax errors in contraints METAR_SPECI.ASW6 and COMMON.ACF2
* Fixed issues with regard to the placement and associated constraints of extension blocks

====================================
2.0 - August 2016
====================================
Expand Down
114 changes: 41 additions & 73 deletions IWXXM/TAC-to-XML-Guidance.txt
Original file line number Diff line number Diff line change
@@ -1,159 +1,127 @@
==========================
==========================
Introduction
==========================
This document provides guidance on how abbreviations and codes from the Traditional Alphanumeric Codes (TAC)
are represented in XML (IWXXM).
This document provides guidance on how abbreviations and codes from the Traditional Alphanumeric Codes (TAC) are represented in XML (IWXXM).

==========================
METAR/SPECI
==========================
NIL (report)
(Represented as a status of "MISSING" on METAR/SPECI and TAF reports)
NIL report
NIL reports shall be represented as a status of "MISSING" on METAR/SPECI and TAF reports

CAVOK - Cloud and visibility OK
When CAVOK conditions apply, the appropriate Record type shall have "cloudAndVisibilityOK" set to true and visibility,
runway visual range, weather, and cloud information shall be missing.
When CAVOK conditions apply, the appropriate Record type shall have "cloudAndVisibilityOK" set to true and visibility, runway visual range, weather, and cloud information shall be missing

CLRD - Runway contamination is cleared
When runway contamination has been cleared, AerodromeRunwayState shall have "cleared" set to true

NSC - No clouds of operational significance
When no cloud of operational significance is observed/forecast, and no restriction on vertical
visibility and 'CAVOK' is not appropriate, the cloud group shall be missing with a nil reason of
http://codes.wmo.int/common/nil/nothingOfOperationalSignificance
When no cloud of operational significance is observed/forecast, and no restriction on vertical visibility and 'CAVOK' is not appropriate, "cloud" shall be nil with a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance"

NCD - No clouds detected (by auto system)
When no clouds are detected by the automatic observing system, it shall be indicated by a
missing cloud group with a nil reason of http://codes.wmo.int/common/nil/notDetectedByAutoSystem
When no clouds are detected by an automatic observing system, this shall be indicated by a nil "cloud" with a nil reason of "http://codes.wmo.int/common/nil/notDetectedByAutoSystem"

NOSIG - No significant changes are forecast
When no change is expected to occur, this shall be indicated by a single missing trend forecast with a nil
reason of http://codes.wmo.int/common/nil/noSignificantChange
When no change is expected to occur, this shall be indicated by a single nil "trendForecast" with a nil reason of "http://codes.wmo.int/common/nil/noSignificantChange"

NSW - No weather of operational significance
The expected end of occurrence of weather phenomena shall be indicated by a change forecast with a missing weather
group with a nil reason of http://codes.wmo.int/common/nil/nothingOfOperationalSignificance

The expected end of occurrence of weather phenomena shall be indicated by a nil "forecastWeather" with a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance"

R88 (runway designator for runway state)
When all runways are being indicated, the AerodromeRunwayState shall have "allRunways" set to true

R99 (runway designator for runway state)
When a new runway state report is not available in time for dissemination of the METAR message, the
previous runway state report will be repeated
When a new runway state report is not available in time for dissemination of the METAR message, the previous runway state report will be repeated

SNOCLO - Runway closed due to snow
When a runway is closed due to snow, AerodromeRunwayState shall have "snowClosure" set to true

Present weather "//"
When present weather cannot be observed by the automatic observing system due to a temporary failure of the
system/sensor, the present weather shall be missing with a nil reason of
http://codes.wmo.int/common/nil/notObservable
When present weather cannot be observed by the automatic observing system due to a temporary failure of the system/sensor, "presentWeather" shall be nil with a nil reason of "http://codes.wmo.int/common/nil/notObservable"

Vertical visibility "VV///" (METAR/SPECI observations)
When the sky is obscured and the value of the vertical visibility cannot be determined by the automatic observing
system due to a temporary failure of the system/sensor, the vertical visibility shall be missing with a nil reason of
http://codes.wmo.int/common/nil/notObservable
When the sky is obscured and the value of the vertical visibility cannot be determined by the automatic observing system due to a temporary failure of the system/sensor, the "verticalVisibility shall be nil with a nil reason of "http://codes.wmo.int/common/nil/notObservable"

Cloud amount and base "//////"
When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the
cloud amount and the height of cloud base cannot be observed, this shall be indicated by a missing cloud layer
with a nil reason of either http://codes.wmo.int/common/nil/notObservable if the value could not be observed due to
a sensor or system failure, or http://codes.wmo.int/common/nil/notDetectedByAutoSystem if the automated system is
working properly but did not observe any values
When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the cloud amount and the height of cloud base cannot be observed, this shall be indicated by a nil cloud "layer" with a nil reason of either "http://codes.wmo.int/common/nil/notObservable" if the value could not be observed due to a sensor or system failure, or "http://codes.wmo.int/common/nil/notDetectedByAutoSystem" if the automated system is working properly but did not observe any values

Cloud amount "///015"
When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the
cloud amount cannot be observed, this shall be indicated by a CloudLayer with a missing "amount" with a nil reason
of either http://codes.wmo.int/common/nil/notObservable if the value could not be observed due to
a sensor or system failure, or http://codes.wmo.int/common/nil/notDetectedByAutoSystem if the automated system is
working properly but did not observe any values
When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the cloud amount cannot be observed, this shall be indicated by a cloud "layer" with a nil "amount" and a nil reason of either "http://codes.wmo.int/common/nil/notObservable" if the value could not be observed due to a sensor or system failure, or "http://codes.wmo.int/common/nil/notDetectedByAutoSystem" if the automated system is working properly but did not observe any values

Cloud base "BKN///"
When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the height of
cloud base cannot be observed, this shall be indicated by a CloudLayer with a missing "base" with a nil reason
of either http://codes.wmo.int/common/nil/notObservable if the value could not be observed due to
a sensor or system failure, or http://codes.wmo.int/common/nil/notDetectedByAutoSystem if the automated system is
working properly but did not observe any values
When cumulonimbus clouds or towering cumulus clouds are detected by the automatic observing system and the height of cloud base cannot be observed, this shall be indicated by a cloud "layer" with a nil "base" and a nil reason of either "http://codes.wmo.int/common/nil/notObservable" if the value could not be observed due to a sensor or system failure, or "http://codes.wmo.int/common/nil/notDetectedByAutoSystem" if the automated system is working properly but did not observe any values

Cloud type "///"
When cloud type cannot be observed by an auto system due to sensor limitations this shall be indicated by
http://codes.wmo.int/common/nil/notObservable.
When cloud type cannot be observed by an auto system due to sensor limitations "cloudType" shall be nil with a nil reason of "http://codes.wmo.int/common/nil/notObservable"

Runway depth of deposit "//"
When the runway depth of deposits is operationally insignificant or is not measurable this shall be indicated by
a missing depthOfDeposits and a nilReason of either http://codes.wmo.int/common/nil/notObservable or
http://codes.wmo.int/common/nil/nothingOfOperationalSignificance.
When the runway depth of deposits is operationally insignificant or is not measurable this shall be indicated by a nil "depthOfDeposits" and a nil reason of either "http://codes.wmo.int/common/nil/notObservable" or "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance"

Runway depth of deposit "99" (value from WMO code table 1079)
When the runway depth of deposits is not reported due to runway or runways non-operational due to snow, slush, ice,
large drifts or runway clearance this shall be indicated by a missing depthOfDeposits and a nilReason of
http://www.opengis.net/def/nil/OGC/0/unknown.
When the runway depth of deposits is not reported due to runway or runways non-operational due to snow, slush, ice, large drifts or runway clearance this shall be indicated by a nil "depthOfDeposits" and a nil reason of "http://www.opengis.net/def/nil/OGC/0/unknown"



==========================
TAF
==========================
NIL (report)
(Represented as a status of "MISSING" on METAR/SPECI and TAF reports)
NIL report
NIL reports shall be represented as a status of "MISSING" on METAR/SPECI and TAF reports

CAVOK - Cloud and visibility OK
When CAVOK conditions apply, the appropriate Record type shall have "cloudAndVisibilityOK" set to true and visibility,
runway visual range, weather, and cloud information shall be missing.
When CAVOK conditions apply, the appropriate Record type shall have "cloudAndVisibilityOK" set to true and visibility, runway visual range, weather, and cloud information shall be missing

NSC - No clouds of operational significance
When no cloud of operational significance is observed/forecast, and 'CAVOK' is not appropriate, the cloud group shall be missing with a nil reason of
http://codes.wmo.int/common/nil/nothingOfOperationalSignificance
When no cloud of operational significance is observed/forecast, and 'CAVOK' is not appropriate, "cloud" shall be nil with a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance"

NSW - No weather of operational significance
The expected end of occurrence of weather phenomena shall be indicated by a change forecast with a missing weather
group with a nil reason of http://codes.wmo.int/common/nil/nothingOfOperationalSignificance
The expected end of occurrence of weather phenomena shall be indicated by a nil "weather" with a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance"

Vertical visibility "VV///"
When the vertical visibility is not available for any reason, vertical visibility shall be missing with no nil reason.
When the vertical visibility is not available for any reason, "verticalVisibility" shall be missing with no nil reason

==========================
SIGMET
==========================
NO VA EXP - No volcanic ash expected
The expected end of occurrence of volcanic ash shall be indicated with a missing VolcanicAshSIGMET "phenomenon" with a
nil reason of http://codes.wmo.int/common/nil/nothingOfOperationalSignificance
The expected end of occurrence of volcanic ash shall be indicated with a nil "VolcanicAshSIGMET/phenomenon" and a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance"

==========================
Volcanic Ash Advisory
==========================
'UNKNOWN' volcano name
An unknown volcano name shall be indicated with an EruptingVolcano name of "UNKNOWN"
An unknown volcano name shall be indicated with an "EruptingVolcano/name" of "UNKNOWN"

'UNNAMED' volcano name
An unnamed volcano shall be indicated with an EruptingVolcano name of "UNNAMED"
An unnamed volcano shall be indicated with an "EruptingVolcano/name" of "UNNAMED"

'UNKNOWN' volcano location
An unknown volcano location shall be indicated with a missing EruptingVolcano position with a nilReason of "unknown"
An unknown volcano location shall be indicated with a nil "EruptingVolcano/position" and a nil reason of "unknown"

'UNKNOWN' aviation colour code
An unknown aviation colour code shall be indicated with a missing colourCode with a nilReason of "unknown"
An unknown aviation colour code shall be indicated with a nil "colourCode" and a nil reason of "unknown"

'NOT GIVEN' aviation colour code
An aviation colour code that is not given shall be indicated with a missing colourCode with a nilReason of "withheld"
An aviation colour code that is not given shall be indicated with a nil "colourCode" and a nil reason of "withheld"

'NIL' aviation colour code
A NIL aviation colour code shall be indicated with a missing colourCode with a nilReason of "missing"
A NIL aviation colour code shall be indicated with a nil "colourCode" with a nil reason of "missing"

'VA NOT IDENTIFIABLE FM SATELLITE DATA'
Unidentifiable volcanic ash from satellite data shall be indicated with a nil ashCloudExtent with a nilReason of "unknown"
Unidentifiable volcanic ash from satellite data shall be indicated with a nil "ashCloudExtent" and a nil reason of "unknown"

'NO VA EXP'
When no volcanic ash is expected it shall be indicated with a nil ashCloudExtent with a nilReason of
http://codes.wmo.int/common/nil/nothingOfOperationalSignificance
When no volcanic ash is expected it shall be indicated with a nil "ashCloudExtent" and a nil reason of "http://codes.wmo.int/common/nil/nothingOfOperationalSignificance"

'NOT AVBL'
When volcanic ash is not available it shall be indicated with a nil ashCloudExtent with a nilReason of 'missing'
When volcanic ash is not available it shall be indicated with a nil "ashCloudExtent" and a nil reason of "missing"

'NOT PROVIDED'
When volcanic ash is not provided it shall be indicated with a nil ashCloudExtent with a nilReason of 'withheld'
When volcanic ash is not provided it shall be indicated with a nil "ashCloudExtent" and a nil reason of "withheld"

==========================
Tropical Cyclone Advisory
==========================
'
'UNNAMED' volcano name
An unnamed tropical cyclone shall be indicated with a "tropicalCycloneName" of "UNNAMED"

'NIL' remarks
NIL remarks shall be indicated with an missing "remarks" element
Loading

0 comments on commit 780aed9

Please sign in to comment.