VONA And QVACI Design Review Teleconference 2023 Nov 2

Details

2023-Nov-2, 02-03 UTC, Webex

Agenda

Welcome
Review agenda

Review of the designs of IWXXM VONA and QVACI

IWXXM VONA:

Representation of a volcano:

<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>

Representation of re-suspended volcanic ash:

<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>

Representation of a volcanic ash cloud:

<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>

Representation of the VONA collection:

<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>
        <!-- Representation of a volcano or re-suspended volcanic ash -->
    </iwxxm:feature>
    <iwxxm:feature>
        <!-- Representation of a volcanic ash cloud -->
    </iwxxm:feature>
    <iwxxm:starteOrRegion .../>
    <iwxxm:noticeNumber .../>
    <iwxxm:currentColourCode .../>
    <iwxxm:previousColourCode .../>
    <iwxxm:contacts .../>
    <iwxxm:remarks .../>
    <iwxxm:nextNotice .../>
</iwxxm:VolcanoObservatoryNoticeForAviation>

IWXXM QVACI:

Representation of a volcano (same as IWXXM VONA), with iwxxm:IAVCEINumber, iwxxm:sourceElevation, iwxxm:activityStatus, iwxxm:lastVolcanicAshEmission and iwxxm:onsetTime as optional items

Representation of a volcanic ash cloud:

<iwxxm:MeteorologicalFeature .../>
    <gml:identifier .../>
    <iwxxm:issueTime .../>
    <iwxxm:originatingCentre>
        <aixm:Unit .../>
    </iwxxm:originatingCentre>
    <iwxxm:phenomenonCategory>volcanicForecasts</iwxxm:phenomenonCategory>
    <iwxxm:phenomenonTime .../>
    <iwxxm:phenomenon xlink:href="https://codes.wmo.int/49-2/MeteorologicalFeature/VOLCANIC_ASH"/>
    <iwxxm:phenomenonGeometry>
        <iwxxm:ElevatedVolume .../>
    </iwxxm:phenomenonGeometry>
    <iwxxm:phenomenonProperty>
        <iwxxm:VolcanicAshCloudConcentration>
            <iwxxm:ashDensityCategory .../>
            <iwxxm:ashDensityEqualsOrExceeds .../>
        </iwxxm:VolcanicAshCloudConcentration>
    </iwxxm:phenomenonProperty>
</iwxxm:MeteorologicalFeature>

Representation of the QVACI collection:

<iwxxm:QuantitativeVolcanicAshConcentrationInformation ...>
    <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>
        <!-- Representation of a volcano (position, name, and may be IAVCEI Number too) -->
    </iwxxm:feature>
    <iwxxm:feature>
        <!-- Representation of a volcanic ash cloud -->
    </iwxxm:feature>
    <iwxxm:feature>
        <!-- More volcanic ash clouds -->
    </iwxxm:feature>
    <iwxxm:dispersionModelInitialisationTime .../>
    <iwxxm:dispersionModelSourceElevation .../>
    <iwxxm:dispersionModelAshCloudHeight .../>
</iwxxm:QuantitativeVolcanicAshConcentrationInformation>

Real life examples are available (vona-A7-1.xml and qvaci-Example.xml).
It is interesting to see the description of an area of re-suspended ash source only involves an average height of the ash field but not the lower and upper boundaries. It might be worth to have at least the upper boundary as an optional reporting item in case the vertical extend of this source is significant?
Note that the geometry of a volcanic ash cloud in VONA (which only contains vertical extent) is different from that in a QVA (which is a 2.5D volume). Ditto the associated properties (iwxxm:heightSource + iwxxm:movement Vs iwxxm:ashDensityCategory + iwxxm:ashDensityEqualsOrExceeds). It would be interesting to see if the two can be generalized into a single representation without violating the VONA TAC template.
Another point is that gml:identifier uniquely identifies a VONA message, QVACI message, as well as the volcano, re-suspended volcanic ash and volcanic ash cloud. Theoretically, online systems can be set up to provide messages or WxObjects using a URL with the gml:identifier as the filtering parameter. WG-MOG may want to determine how gml:identifier is created for the messages and WxObjects. Initial thoughts on definitions of codeSpace include:
- VONA:
  - http://vona/centre/[name_of_observatory] <-- for use with the VONA collective
  - http://vona/volcano <-- for use with the volcano object
  - http://vona/volcanic_ash_cloud <-- for use with re-suspended ash cloud and observed ash cloud object
- QVACI:
  - http://qvaci/centre/[name_of_VAAC] <-- for use with the QVACI collective
  - http://qvaci/volcano <-- for use with the volcano object
  - http://qvaci/volcanic_ash_cloud <-- for use with the forecast ash cloud object

Discussions and actions

Paula asked:
- Whether there are indications that an IWXXM VONA message is being translated from a TAC VONA message: (Choy) There are attributes describing translations being made on behalf of the TAC originating centre and they are avialble in all IWXXM messages by default.
- How to handle the case where a centre is issuing an IWXXM VONA on behalf on another, for example in a fallback situation: (Choy) Normally iwxxm:originatingCentre only documents the actual centre that prepares the message. The IWXXM schemas will have to be revised if we want to document the "on behalf" arrangement. (Paula) It may suffix to include this information in iwxxm:remarks for the time being.
Choy enquired if gml:Point is enough for the description of the geometry of a volcano. Paula mentioned that it is a general practice to use a point to describe the location of a volcano. There exist cases in which the potential region for eruption is so large so that the location of "the volcano" will have to be changed after an eruption has occurred. (Choy) In that case a constraint will be added to mandate the use of gml:Point until the community has changed their practice.
Choy enquired if gml:LinearRing together with the average height of the ash field is sufficient for the description of an area of re-suspended volcanic ash. Paula indicated that cases involving re-suspended ash are rare and the boundary is probably the best endevour observatories can be made. (Choy) In that case a constraint will be added to mandate the use of gml:LinearRing until there are requests to relax the use.
Choy enquired if a 2.5D representation similar to what is being used in QVACI to describe volcanic ash cloud instead of iwxxm:ElevatedLevel in VONA. Paula mentioned that the ash cloud an observatory is trying to describe during an eruption will look more like a straight line or a narrow cone pointing up. It is also difficult for observatories to provide lateral boundaries of the volcanic ash cloud. Therefore providing volcanic ash cloud height is probably the best they can do. (Choy) So a constraint will be added to mandate the use of iwxxm:ElevatedLevel for the geometry of volcanic ash cloud in VONA.
Paula confirmed that the position will be a unique identifier of a volcano which can have no name and/or IAVCEI number at the time of report. She, however, also mentioned that the position of the volcano in the same series of VONA may change with time due to the volcanic activities involved. Choy indicated that the gml:identifier is used to identify an instance of the WxObject describing a volcano and its activity. It is possible to include additional attributes in the volcano WxObject to chain up the gml:identifier of all volcano WxObject instances to allow the user to see the variation of the volcano instance from one time to another. However, there is no use case of this capability right now, and we will wait until such needs arise.
Choy mentioned that the codeSpace in gml:identifier can be used to describe the taxonomy of the WxObject or messages involved which can help the searching of information in information systems. He has provided some examples of codeSpace and Paula will discuss with members of the workstream to see if there is anything they want to do with it before TT-AvData submits the revised IWXXM schemas to WMO FT2024-2 by mid-2024.
As Choy understands that UK may be the first of the VAAs to provide QVACI he will contact Karen to see if her team can take a look at the draft schema and may be developing some additional examples for illustration.

Attendees

BL Choy
Paula Acethorp

... go to TT-AvData Homepage on WMO Community website

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

VONA And QVACI Design Review Teleconference 2023 Nov 2

Details

Agenda

Discussions and actions

Attendees

Clone this wiki locally