Closed amilan17 closed 2 months ago
New products and changes to existing schemas should originate in the iwxxm-modelling repository, yes?
Are you suggesting that I move this type of issue to the modelling repo?
Hi @amilan17! Yes. Or at least, open a new issue in the iwxxm-modelling branch paralleling this one since its a new product. Prior instances of a new IWXXM product, the UML model is developed first and the resulting schema originates from EA.
Summary of changes:
The instance will look something like (with an erupting volcano as source):
<iwxxm:VolcanoObservatoryNoticeForAviation ...>
<gml:identifier .../>
<iwxxm:boundingPeriod .../>
<iwxxm:boundingVolume .../>
<iwxxm:phenomenaList xlink:href="http://codes.wmo.int/49-2/MeteorologicalFeature/VOLCANO"/>
<iwxxm:phenomenaList xlink:href="http://codes.wmo.int/49-2/MeteorologicalFeature/VOLCANIC_ASH"/>
<iwxxm:issueTime .../>
<iwxxm:originatingCentre>
<aixm:Unit .../>
</iwxxm:originatingCentre>
<iwxxm:phenomenonCategory>volcanicObservations</iwxxm:phenomenonCategory>
<iwxxm:phenomenonTime .../>
<iwxxm:feature>
<iwxxm:MeteorologicalFeature .../>
<gml:identifier .../>
<iwxxm:issueTime .../>
<iwxxm:originatingCentre>
<aixm:Unit .../>
</iwxxm:originatingCentre>
<iwxxm:phenomenonCategory>volcanicObservations</iwxxm:phenomenonCategory>
<iwxxm:phenomenonTime .../>
<iwxxm:phenomenon xlink:href="https://codes.wmo.int/49-2/MeteorologicalFeature/VOLCANO"/>
<iwxxm:phenomenonGeometry>
<gml:Point .../>
</iwxxm:phenomenonGeometry>
<iwxxm:phenomenonProperty>
<iwxxm:Volcano>
<iwxxm:name .../>
<iwxxm:IAVCEINumber .../>
<iwxxm:sourceElevation .../>
<iwxxm:activityStatus .../>
<iwxxm:lastVolcanicAshEmission .../>
<iwxxm:onsetTime .../>
</iwxxm:Volcano>
</iwxxm:phenomenonProperty>
</iwxxm:MeteorologicalFeature>
</iwxxm:feature>
<iwxxm:feature>
<iwxxm:MeteorologicalFeature .../>
<gml:identifier .../>
<iwxxm:issueTime .../>
<iwxxm:originatingCentre>
<aixm:Unit .../>
</iwxxm:originatingCentre>
<iwxxm:phenomenonCategory>volcanicObservations</iwxxm:phenomenonCategory>
<iwxxm:phenomenonTime .../>
<iwxxm:phenomenon xlink:href="https://codes.wmo.int/49-2/MeteorologicalFeature/VOLCANIC_ASH"/>
<iwxxm:phenomenonGeometry>
<iwxxm:ElevatedLevel .../>
</iwxxm:phenomenonGeometry>
<iwxxm:phenomenonProperty>
<iwxxm:VolcanicAshCloudVerticalExtent>
<iwxxm:heightSource .../>
<iwxxm:movement .../>
</iwxxm:VolcanicAshCloudVerticalExtent>
</iwxxm:phenomenonProperty>
</iwxxm:MeteorologicalFeature>
</iwxxm:feature>
<iwxxm:starteOrRegion .../>
<iwxxm:noticeNumber .../>
<iwxxm:currentColourCode .../>
<iwxxm:previousColourCode .../>
<iwxxm:contacts .../>
<iwxxm:remarks .../>
<iwxxm:nextNotice .../>
</iwxxm:VolcanoObservatoryNoticeForAviation>
The instance will look something like (with re-suspended volcanic ash as source):
<iwxxm:VolcanoObservatoryNoticeForAviation ...>
<gml:identifier .../>
<iwxxm:boundingPeriod .../>
<iwxxm:boundingVolume .../>
<iwxxm:phenomenaList xlink:href="http://codes.wmo.int/49-2/MeteorologicalFeature/VOLCANO"/>
<iwxxm:phenomenaList xlink:href="http://codes.wmo.int/49-2/MeteorologicalFeature/VOLCANIC_ASH"/>
<iwxxm:issueTime .../>
<iwxxm:originatingCentre>
<aixm:Unit .../>
</iwxxm:originatingCentre>
<iwxxm:phenomenonCategory>volcanicObservations</iwxxm:phenomenonCategory>
<iwxxm:phenomenonTime .../>
<iwxxm:feature>
<iwxxm:MeteorologicalFeature .../>
<gml:identifier .../>
<iwxxm:issueTime .../>
<iwxxm:originatingCentre>
<aixm:Unit .../>
</iwxxm:originatingCentre>
<iwxxm:phenomenonCategory>volcanicObservations</iwxxm:phenomenonCategory>
<iwxxm:phenomenonTime .../>
<iwxxm:phenomenon xlink:href="https://codes.wmo.int/49-2/MeteorologicalFeature/VOLCANIC_ASH"/>
<iwxxm:phenomenonGeometry>
<gml:LinearRing .../>
</iwxxm:phenomenonGeometry>
<iwxxm:phenomenonProperty>
<iwxxm:ResuspendedVolcanicAsh>
<iwxxm:height .../>
</iwxxm:ResuspendedVolcanicAsh>
</iwxxm:phenomenonProperty>
</iwxxm:MeteorologicalFeature>
</iwxxm:feature>
<iwxxm:feature>
<iwxxm:MeteorologicalFeature .../>
<gml:identifier .../>
<iwxxm:issueTime .../>
<iwxxm:originatingCentre>
<aixm:Unit .../>
</iwxxm:originatingCentre>
<iwxxm:phenomenonCategory>volcanicObservations</iwxxm:phenomenonCategory>
<iwxxm:phenomenonTime .../>
<iwxxm:phenomenon xlink:href="https://codes.wmo.int/49-2/MeteorologicalFeature/VOLCANIC_ASH"/>
<iwxxm:phenomenonGeometry>
<iwxxm:ElevatedLevel .../>
</iwxxm:phenomenonGeometry>
<iwxxm:phenomenonProperty>
<iwxxm:VolcanicAshCloudVerticalExtent>
<iwxxm:heightSource .../>
<iwxxm:movement .../>
</iwxxm:VolcanicAshCloudVerticalExtent>
</iwxxm:phenomenonProperty>
</iwxxm:MeteorologicalFeature>
</iwxxm:feature>
<iwxxm:starteOrRegion .../>
<iwxxm:noticeNumber .../>
<iwxxm:currentColourCode .../>
<iwxxm:previousColourCode .../>
<iwxxm:contacts .../>
<iwxxm:remarks .../>
<iwxxm:nextNotice .../>
</iwxxm:VolcanoObservatoryNoticeForAviation>
Included in IWXXM 2025-2RC1.
Initial request
Recommendation 7/1 — VONA Introduction, VAA and Aerodrome Warning Template Improvements That the METP; b) request the WMO to develop appropriate headers and priorities for VONA in both TAC and IWXXM format, noting the request by the WG-MOG/IAVW work stream for the highest priority to be assigned; c) task WG-MIE to develop the IWXXM schema necessary for digital dissemination of the VONA; [source METP_5.Final Report.pdf, 2021 June]
See the extracted Template for Volcano Observatory Notice to Aviation (VONA) from the proposed text in working paper METP/5-WP/4102.
Other requirements mentioned in METP/5-WP/4102 include:
(PANS-MET/Para. 6.1.6) VONA shall be in abbreviated plain language, using approved ICAO abbreviations and numerical values of self-explanatory nature, and shall be in accordance with the template shown in Appendix 7, Table A7-1. When no approved ICAO abbreviations are available, English plain language text, kept to a minimum, shall be used to describe elements for which the template allows the use of free text.
(PANS-MET/Para 6.1.8) Only the following aviation colour codes shall be reported in the VONA:
Note.— The aviation colour code applies only to current volcanic activity associated with a volcano and does not apply to re-suspended volcanic ash
(PANS-MET/Para. 6.1.9) ... Further information on VONA is included in the Handbook on the International Airways Volcano Watch (IAVW) - Operational Procedures and Contact List (Doc 9766).
See Example A7-1.
Amendment details
TBD
Comments
No response
Requestor(s)
ICAO METP/5 for Amendment 81(?)
Stakeholder(s)
Enter list of stakeholder(s).
Publication(s)
Example: Manual on Codes (WMO-No. 306), Volume I.3
Expected impact of change
No response
Collaborators
No response
References
No response
Validation
No response