TT AvData Teleconference 17 March 2021

Details

2020-March-17, 13:30-15:00 UTC, Microsoft Teams

Agenda 

1. Review previous actions
2. Outcomes of ICAO WG-MIE/7 meeting worth mentioning (Choy)
3. IWXXM code list repository on GitHub (Choy, Anna and Jan)
4. IWXXM 3.1-dev
5. Schedule next meeting
6. CoB

Minutes (draft) 

Review previous actions

(Previous Minutes)

1. Ask Enrico: can we release/make applicable/operational on 4 November (same as the applicable date mentioned in Annex 3) instead? (not critical, but nice to have): It may be resolved if FT process ends sooner than Nov 16.
2. All: review the content https://github.com/wmo-im/iwxxm/wiki/Validation:IWXXM-3.1-dev and provide comments in the team's discussion board https://github.com/orgs/wmo-im/teams/tt-avdata/discussions/3: No comments on the discussion board. Mark would like more information about what kind of tests you are looking for.
3. All: take a look at the weather objects and comment as necessary

Outcomes of ICAO WG-MIE/7 meeting worth mentioning (Choy)

1. Versioning of IWXXM:
   • During the ICAO meeting there was no objection to using the new way (see /wmo-im/iwxxm/wiki/New-proposal-on-IWXXM-versioning).
   • There was a discussion about also versioning the code table, how this versioning relates to the IWXXM versioning and how it should be presented in the Code URL (see Issue /wmo-im/IWXXMCodeLists/issues/11). DECISIONS (almost): Codelists will be a column in the version table. The IWXXM version changes when a code table changes, even when none of the schemas change.
   • Can we implement this new versioning method now? (EF) yes, but we need to consider what goes in the MoC and how to include it in the schemas. ACTION: Enrico and Anna research options for representing the version table in the MoC and consider how we can simplify what is in the MoCs. e.g. the WaterML just has a link to the schemas.
2. IWXXM Extensions
   • There was an agreement to request a portal to hold state extensions, but no one knows who is going to be responsible for this. WMO can host, be WMO cannot be responsible for the content. The MIE team is thinking of this and it will probably not affect this team.
3. Metadata for meteorological information: (EF) What is the purpose of this metadata? Discovery? (Choy) The metadata is going to describe the physical properties of the data parameters, how it's measured, etc. (EF) you need a framework first.
4. MET over SWIM: still unclear how to exchange MET services with SWIM
5. WIS 2.0 and MET-SWIM: (EF) They don't communicate because they use different messaging protocols. SWIM will not be a part of WIS, but they will interact somehow
6. MET-SWIM architecture and service requirements
7. Relaxation of TAC Constraints in IWXXM: Community is starting to cautiously divorce the two.
8. Map projection
9. New design incorporating existing information requirements contained in METAR/SPECI, Local Routine/Special Reports and any new requirements from stakeholders
10. New MET information requirements (VONA and QVA) for Amendment 81
11. IWXXM code list repository on GitHub (Choy, Anna, and Jan)
12. IWXXM 3.1-dev
    1. Applicable date (Enrico)
    2. Granularity of the validation page on wiki (All)
    3. Weather Objects and WAFS SIGWX Forecast (All)
13. Schedule next meeting
14. CoB

Decisions 

*(almost): Codelists will be a column in the version table. The IWXXM version changes when a code table changes, even when none of the schemas change. Team still needs to consider other use cases (e.g. user wants to use an older version of a code with a newer version of the schema)

Actions

Attendees

• BL Choy
• Dirk Zinkhan
• Mark Oberfield
• Yann Génin
• Ján Korösi
• Anna Milan
• Xiaoxia Chen
• Enrico Fucile