Meeting 2026 03 10 - wmo-im/tt-wismd GitHub Wiki

Date/Time

Tuesday 10 March 2026 13h - 14h UTC

Location

MS Teams

Attendees

Team

Name	Affiliation/Country	GitHub handle	Attendance
Tom KRALIDIS (Chair)	Canada	@tomkralidis	X
Guillaume AUBERT	EUMETSAT	@gaubert
Takumu EGAWA (observing member)	Japan
Lara FERRIGHI	Norway	@ferrighi
Sylvain GRELLET	France	@sgrellet
Xinqiang HAN	China	@Amienshxq	X
Vera KORBULAKOVA	Russian Federation	@VeraKorbulakova
Ian MCDONALD	EUMETSAT	@McDonald-Ian
Steve OLSON	USA	@solson-nws	X
Ján OSUSKY	HMEI	@josusky	X
David PODEUR	France	@davidpodeur
Julia SIELAND	Germany	@jsieland	X
Yutaro TONOOKA	Japan	YutaroJMA
Anna MILAN	WMO Secretariat	@amilan17	X

Agenda

• Previous meeting minutes and actions (all)
• Secretariat updates (Anna)
• WCMP2
  • example wis2box records
  • minor editorial update DONE
• WTH
  • marine warnings and forecasts
  • atmospheric composition topics
  • hydrology topics
  • RADOB
  • SAREP
  • public forecast
  • additional types for surface observations
  • FT2026-1 satellites/instruments

Notes (DRAFT)

1. The meeting opened with the team reviewing previous actions.

2. Anna explained that we need to wrap up the proposals for FT2026-1 soon so they can be approved by June.

3. WIS2 Box Test Examples & Center ID Validation: The WIS2 box test examples that are failing CI due to center ID mismatches between the metadata ID and the channel. Tom clarified that center IDs ending in "test" are bypassed in validation. The fix is to align the center IDs. The team discussed whether example records should use real data from the catalog (~400 records) or wis2box examples. The consensus (Julia, Ján, Tom) was to prefer real, domain-based examples, as they offer inspiration for correct keyword/theme usage across domains (e.g., NWP products, satellite, hydrology).

4. Topic Hierarchy — Marine Warnings & Forecasts: Anna presented a pull request adding "warnings," "forecasts," "sea ice," and "maritime safety information" under the weather branch. The secretariat had been consulted and was flexible on the exact structure. Ján flagged a consistency issue (singular "warning" vs. plural "warnings"), which Anna acknowledged and agreed to correct to plural throughout. DECISION: No objections. Tom merged the PR into Fast Track 2026-1. Note: The new topics will carry "experimental" status in codes.wmo until Fast Track approval makes them stable/operational.

5. Topic Hierarchy — Atmospheric Composition: The updated pull request had been approved by Jorg (chair of the expert team on Atmospheric Composition Data Management). A comment from JMA's Kintaro was reviewed and deemed to require no further changes. DECISION: No objections. Tom merged the PR into Fast Track 2026-1 and closed the related milestone.

6. Topic Hierarchy — Hydrology: A long-running item (~25 months in discussion). The current PR has outstanding comments from Remy questioning whether "lake/reservoir/stream" containers are needed vs. focusing on what is measured.

7. Topic Hierarchy — Radar (RADOB / FM 20): No existing pull request. The question was whether to follow the SYNOP/TEMP pattern and call it "RADOB," or use a more descriptive name. Ján noted radar data may already be flowing under some existing topic. Anna proposed consulting the secretariat colleague who supports the operational weather radar task team.

8. Topic Hierarchy — SAREP (FM 85 — Synoptic Satellite Cloud Interpretation): The team reviewed this topic; Anna suggested consulting CGMS for input.

9. Topic Hierarchy — Public Forecast (EUMETNET Proposal): Sebastian (chair of TT-NWPMetadata team) provided feedback. The key distinguishing feature of this topic is that it's a textual, human-readable forecast for a specific point or small area, as opposed to gridded NWP output. The team debated terminology ("human generated" was flagged as awkward) — Ján argued the more important distinguishing features are that it's textual and point-based. Tom noted it can also be machine-generated (his team automates text/icon forecasts via OGC API). Next step: Tom will draft a proposal framed around short-range and medium-range, and engage TTNWP for input. The team will continue this discussion at Thursday's meeting (on notification messages/monitoring events), which Anna flagged as urgent — EUMETNET is ready to exchange data and currently plans to publish everything under the generic "surface-based.observations" topic.

10. Next Meeting: Thursday — agenda will include the EUMETNET topic proposal and remaining items.

Actions

• Steve add provenance link to one of the examples and open a PR
• Anna: Fix the center ID mismatch in the examples.
• Tom update validation to report on all errors instead of stopping at the first error (after Anna fixes wis2box examples) DONE: https://github.com/wmo-im/wcmp2/pull/296
• Anna: Check with Maaike on the original rationale for issue #267, then close it and follow up in the broader issue #225 (general request for additional examples, including NWP inputs).
• Anna: Check with Washington (hydrology team) whether Remy's comments were seen and whether they have a response, then report back.
• Tom: Draft a PR for a radar topic (likely "RADOB") DONE https://github.com/wmo-im/wis2-topic-hierarchy/pull/279
• Tom: Draft a PR for public forecast DONE https://github.com/wmo-im/wis2-topic-hierarchy/pull/280
• Anna: Consult the relevant secretariat colleague and the weather radar task team for domain input, as she did for marine topics. Also check if this overlaps with a separate "add weather radar" issue (273), which was identified as a duplicate/mistake and closed.
• Anna: Reach out to CGMS (starting with Heikki) for guidance on appropriate topic naming.

Next meeting

YYYY-MM-DD