Date
13:00-15:00 UTC
\uD83D\uDC65 Invited Participants
Jeremy TANDY (ET-W2IT Chair)
Rémy GIRAUD (SC-IMT Chair)
Hyumin EOM (KMA)
Masato FUJIMOTO (JMA)
Kari Sheets (NOAA)
Steve Olson (NOAA)
Max Marno (Synoptic)
José Mauro(INMET)
Tom Kralidis (ECCC)
Kai Wirt-Thorsten (DWD)
Elena Arenskotter (DWD)
Saad Mohammed Almajnooni
Majed Mahjoub (NCM)
WMO Secretariat
Enrico Fucile
Hassan Haddouch
Xiaoxia Chen
David Inglis Berry
Anna Milan
Timo Proescholdt
Apologies
Lei XUE (CMA)
Xinqiang HAN (CMA)
Wenjing GU (CMA)
Ping GUO (CMA)
Yoritsugi YUGE (JMA)
Chems eddine ELGARRAI (DGM)
Meeting agenda
Proposals for other types of centres
Sensor Centres and data availability/quality monitoring
Global Replay service
Global Cache “for friends” (i.e., for NMHS institutions only)
Metadata publisher / validator service
Domain/theme-specific portals
Proposals for future of RTHs (requested by Exec Council) - i.e., encouraging them to operate a WIS2 service once their RTH function expires? Option: run 2x workshops Sep-Dec 2025 angled at on-boarding RTHs to be WIS2 service operators.
Meeting Note
Discussion on the additional global services - a shared broker for those entities who have already published data to website.
Jeremy introduced the agenda and then presented the first topic, focusing on other types of centers. He introduced the five proposals outlined in the agenda and emphasized the importance of considering how many instances might be required—or whether it is even possible to determine the necessary number of such services.
Rémy reported on the example of ARGO data and asked how we can support them while lowering the barriers for their integration into WIS2. He suggested considering Broker that could be provided by a suitable entity.
In response to questions regarding the architecture of WIS2—such as whether it will be changed or if additional Global Services will be added—Rémy clarified that this is solely about providing an MQTT service to data providers that already have websites, making it easier for them to onboard into WIS2. He emphasized that the existing organization of WIS, including NCs and DCPCs, will remain unchanged.
This approach can be extended to various communities, including ocean, climate, and cryosphere.
(Kai) DWD’s current practice (Israel wis2 node running on DWD infrastructure) is based on the bilateral agreement. If this to become an official service, a formal procedure needs to established.
Key considerations for the MQTT service:
Eligibility: Who will be allowed to access and use the service?
Service Structure: Ensuring an efficient and streamlined MQTT server for users.
Number of Instances: No fixed number, but an estimate is needed based on demand.
Scope of Responsibility: Should it be a global or regional service? This depends on the service provider’s decision.
Timeline: When should it be available? Possibly by mid-year, though the service does not currently exist.
Global Replay service :
Description: Tom introduced the Global Relay as a service listening to the Global Broker, that collects, caches, and distributes messages, ensuring that users who were offline can retrieve any missed notifications once they reconnect. API are based on OGC APIs; implementation on GitHub repo: https://github.com/wmo-im/wis2-grep
Key considerations for the Global Replay:
Number of Instances: At least 2
Scope of Responsibility: Global
Retention: at lest 24 hours
Timeline: No specific milestone for implementation
Candidate operator: ECCC, which already has an instance running this service.
Sensor Centres
Regarding the sensor centers, a discussion took place and it was concluded to create a GitHub page to present these proposals for review and completion.
Action: Rémy will describe the sensor center on the evaluation of the GTS2WIS2 gateway, on which Chems is working, as well as that one on the evaluation of global caches.
Action: Hassan to share the team the right repo for discussion on sensor centres.
Action: Everyone is encouraged to contribute ideas for other types of sensor centers
Metadata publisher / validator service
Description: Tom introduced the Metadata publisher as standalone web applications metadata editors, designed to edit, validate, and assess the quality of the metadata. This tool aimed ensuring the accuracy and completness of metadata prior to submission to GDC. (it is a software)
Key considerations:
Instances: at least one
Global or regional responsibility: Global
When is it needed: as soon as people start using WIS2 regularly
Candidate operator: Option 1: a metadata editor available in wis2box. Option 2: metadata editor provided by SYNOPTIC
Action: Tom to provide an analysis on both options and report back
Domain/theme-specific portals
Description: The purpose is to develop a Shiny portal that enhances the visibility and accessibility of WIS2. This platform will serve as a central hub for users to easily access WIS2-related information, data, and services. It will also play a key role in marketing WIS2, promoting its capabilities and engaging stakeholders, ultimately increasing its adoption and usage across the community.
The WIPPS portal Current WIPPS portal has been discussed as example, however, the team agreed to focus more on a WIS portal. The WIS2 catalogue is more enough for domains to build their portals.
Actions
1-Write a "one-pager" describing each of the additional WIS2 services, currently:
"Shared broker" service
Global Replay service
Metadata manager
2-Write proposals for Sensor Centres to be discussed at next ET-W2IT meeting (24-Feb)
3-Develop a simple "how-to" guide for registering a WIS2 Node
... EUMETNET RODEO project will be working on such documentation, which we could re-use
Proposals for future of RTHs (requested by Exec Council) - i.e., encouraging them to operate a WIS2 service once their RTH function expires? Option: run 2x workshops Sep-Dec 2025 angled at on-boarding RTHs to be WIS2 service operators.
"Requests from the Executive Council for INFCOM to consider the elaboration of a comprehensive guidance for the cease of functions of RTH;" Quote from EC-78
Action: to create a dedicated page for the RTH functions and eventual roles in WIS2. The first step will be to develop a prototype, which will then be demonstrated to the RTHs in Q4 2025 workshop for hosting and further feedback.
Next meeting
24 February
0 Comments