TT AvData Teleconference 2023 Sep 5

Details

2023-Aug-31, 12:00-13:00 UTC, Microsoft Teams

Agenda

1. Welcome
2. Review agenda
3. Secretariat update
   • Two members are still not in the WMO Contacts DB (Raquel, Boonchai)
4. Updates since last meeting (Team)
   • All to review the proposed changes to SWA (Issue #308) and VAA (Issue #307) and provide comments there.
   • Anna to find out if registry http://codes.wmo.int/common/nil is under the responsibility of TT-AvData. (AM: Yes and other teams if needed, see MoC vI.3 Section 3, p. 6)
   • Mark to ask NOAA SWA experts if there is a chance of having more than 4 previous advisories to be replaced. (MO: Consulted w/ Rob Steenburgh; Four is sufficient.)
5. Discussion on the progress of schema development (Choy)
   • Design choices to consider:
     • Can we not use the word "product"? Can we use the term "collective", "collection" to indicate the potentially loose relationship among objects the collective carries?
     • For elements with non-existing or nil content make it either (i) optional or (ii) mandatory but "nillable" and with nilReason

       <element1>
           ...
       </element1>
       
       or
       
       <element1>
           <element2 xsi:nil="true" nilReason="http://codes.wmo.int/common/nil/missing"/>
           ...
       </element1>
       

     • In VONA a volcano is referenced by name and IAVCEI number, and we also want to share these in defining a volcano in QVACI. Should we also make reference to the "volcano information database" and its number in the database?
     • A WxObject is an instance of MeteorologicalFeature and is supposed to be prepared by the originator. For the volcano object should we allow QVA/VONA producer to introduce additional stuff (e.g. remarks) in it? Recall that a WxObject need not be explicitly defined in an IWXXM instance but can reference online resources with a URL.
     • In QVACI if we want to make back references to VONA, do we want to do it as part of volcano properties or as part of QVACI?
     • How can we best present a category (ashDensityCategory) as well as the value it refers to (ashDensityEqualsOrExceeds)?
6. Forthcoming events:
   • Conduct public consultation on changes in the proposed Amendment 81 (early September to early December 2023)
   • Review of responses from public consultation (mid-Nov- 6 December 2023)
   • Review and approve changes to IWXXM involved in Amendment 81 for FT2024-1 (Tentatively mid-Dec 2023. Release date subject to when Amendment 81 is approved by ANC (if there are impacts to IWXXM) and the difference between the approved and proposed versions of Annex 3/PANS-MET)
   • ICAO WG-MIE/11 4-7 December
7. Next meeting date and time
8. [Shelved] Outstanding work of previous meetings (Team): There were no further updates to these topics.
   • XSD locations for IWXXM packages (#271) (Jan)
   • On-going populating new examples in wmo-im/iwxxm-translation (Mark, Jan and Dmitry)
9. [Shelved] Review outstanding issues with no milestones (Anna).
   • https://github.com/wmo-im/iwxxm/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone

Notes

Actions

Next Meeting

TBD

Attendees

• BL Choy
• Mark Oberfield
• Boonchai Tepyose
• Raquel Viquez
• Rodrigo Cortees
• Anna Milan
• Dirk Zinkhan
• Youssef Darari
• Wilberforce Kikwasi
• Yann Génin
• Dmitry Moryakov
• Hyein Yu
• Ján Körösi

Apologies