Skip to content

2022 02 17 TT WIGOSMD 19

Jump to bottom
xchen edited this page Mar 22, 2022 · 2 revisions

Task Team WIGOS Metadata (TT-WIGOSMD-19)

Date and Venue

17 Feb 2022, 1400-1600 UTC
MS Teams

Attendees

Team Members  

Name Present
Jörg Klausen (Switzerland Chair TT-WIGOSMD) X
Tom Kralidis (Canada ET-Metadata Chair)
Gao Chen (USA) X
Lara Ferrighi (Norway) X
Rainer Maerz (Germany) X
Ying Wang (China)
Juan Bianchi (Argentina) X

WMO Secretariat  

Name Present
Enrico Fucile  
Anna Milan X
Xiaoxia Chen  
Rodica Nitu
Igor Zahumensky
Lize Anthonin (OceanOPS) X
Johanna Korhonen
Magali Krieger (OceanOPS) X
Washington Otieno X

Collaborators

Name Present
Franziska Stürzl X
Jitze van der Meulen (KNMI) X
John Eyre (UK MetOffice)
Tanja Kleinart X
Samantha Linnerts X
Thinesh Sornalingam X

Agenda

  • Welcome, adoption of minutes (5')
  • Introductions for attendees from ET-WT (10')
  • Previous actions (10')
  • Discuss options for version 2 of the information model and the codes (25')
  • KPIs - status of implementation (20')
  • Review proposals for FT22-2 (40')

Notes

  • Round table introductions, because there are three new participants from the ET-WT.
  • Joerg introduced the scope of the team's work (WMDS and WMDR), GitHub and the process for amending the codes.
  • The team reviewed previous actions and discussed the challenges of collaborating with other groups such as RDA and CF terms. Lara pointed out that many groups don't adopt the WMO codes, because they evolve too slowly. (JKL) It would be good if we could introduce codes in an experimental mode for faster evolution.(GC) Vocabularies are less important than their definitions. It's critical to be more flexible. (JKL) It's important to be able to respond to the communities needs and we are shutting them out by evolving to slow. (WO) The researchers will always be ahead of us if we don't connect with them more. We could have a test registry before standardization. (FS) OSCAR/Surface developers are improving the workflow of adding new codes. New codes are already there, but the more complex cases need more time to support. (GC) I like the idea of a test registry or experimental tag for immediate use that could reveal problems that were not foreseen.
  • (FS) Briefly presented on the status of issue 190. Updating the mapping from the latest FT and still grouping similar issues. (JVDM) [...?...]
  • KPIs: (JB) Most of the KPIs are implemented in the code, but there are some outstanding issues that need to be resolved. e.g. Time zone table at https://github.com/wmo-im/pywmdr/issues. Downloading records from OSCAR/Surface are encoded in an older version from 2017 and it's different than the schema in GitHub. (JKL) 1.0 was never implemented in OSCAR/Surface. It would be good to get example records from Singapore and DWD. (LF) Presented a brief example of running pwmdr with a couple of the KPIs. (JB) should the KPIs check case sensitivity? (JKL) the only table where case is important is the 'units' table. Otherwise, it doesn't matter (JB) we still need to develop a code list for timezones. (JKL) Juan is responsible for developing this list. And we need a mapping to make sure the coordinates match the time zone. (AM) we need to present the KPIs at INFCOM and we need to determine where it should be applied/described. (LF) it would be good for people to test with their own records (JKL) it would be interesting to consider a visual graph display of the results per station (AM) proof of concept for WCMP KPIs will be to roll up the KPI grades for all records in a GISC and display in a pie chart.
  • Proposals The team reviewed some proposals in https://github.com/wmo-im//wmds/projects/6

Actions

  • Anna: research how to introduce test or experimental approach in the WIGOS Codes
  • Anna: set up meeting with Tom and Joerg to discuss where the KPIs should go in alignment with WIS KPIs

Next meeting

23 March 2022, 14:00-16:00 UTC

TT-WIGOSMD Official WMO Page

Home

Meetings

Changing Codetables

Clone this wiki locally