Page Comparison

0

Review of actions from the last meeting

Hassan

• Action 1: Secretariat to check the Cg-Ext(2021)/Res.1 to verify the coherence of “no issue in making "more" core data available”

  • Confirmed: No issue in making more core data available. It can be found in Annex 2 to Resolution 1 (Cg-Ext(2021)): (https://library.wmo.int/doc_num.php?explnum_id=11113#page=21)

3.4 The recommendation to Members is therefore to adopt the following national practice regarding the exchange of Earth system data

(e) Members are encouraged to broaden the provision of their data with a minimum of conditions beyond the minimum set of data listed in Annex 1 to the present resolution.

• Action 2: GTS to WIS2 Gateway: Secretariat to confirm with DWD and JMA if they are providing these gateways

  • DWD is doing it using Topic Hierarchy: cache/a/wis2/xxg/gts_to_wis2_dwd/TTAAii

• Action 3: WIS2 to GTS Gateway: Secretariat to check if TTAAii is enough or we need CCCC

  • CCCC is needed for mapping from after consultation with GTS experts in BoM, JMA, DWD and Morocco Météo.

1

"Urgent" 

1. Assignment of topics for multidisciplinary datasets https://github.com/wmo-im/wis2-topic-hierarchy/issues/36  

2. Notification mechanism on updated data https://github.com/wmo-im/tt-nwpmd/issues/9  

3. Clarify broker protocol elements https://github.com/wmo-im/wis2-guide/issues/5  

4. WP8.2 WIS2 -> GTS Gateway https://github.com/wmo-im/wis2pilot/issues/9  

5. KPIs for the transition from GTS to WIS2 https://github.com/wmo-im/wis2-guide/issues/20  

6. Lifecycle management of discovery metadata in WIS2 https://github.com/wmo-im/wis2pilot/issues/85  

7. Non-functional performance measures need to be defined https://github.com/wmo-im/wis2-guide/issues/23  (or at least start defining them) 

8. GTS -> WIS2 Gateway will operate a decision made, but ET-W2AT should confirm how to operate. 

Discussion

1.Assignment of topics for multidisciplinary datasets  https://github.com/wmo-im/wis2-topic-hierarchy/issues/36

• (

• Rémy)

• : agreed with the current decision

Timo: to provide supporting documents of MQTT best practice.

The topic_hierarchy will only be used to identify a channel for pub/sub. When a dataset is applicable under multiple domains, the data producer should choose one domain (that is a best fit) and use the WCMP2 metadata record for further descriptions.

• (Timo): In general, MQTT best practice is to publish the message with two (multiple) topics.

• (

• Rémy): Please provide supporting evidence of this MQTT best practice.

2. Notification Mechanism on updated data  https://github.com/wmo-im/tt-nwpmd/issues/9

• Decision: properties.operation is included in the notification message

• Decision: value= create/update/delete, if multiple update messages are received, compare by pub_time

• Action: write an AsciiDoc describing why and how and make in available on github.

• Agreed that WIS2 Guide will be a collection of all

• individual AsciDoc

(3)clarify QoS parameters as well as retention for brokers

Decision: to park this now

Action: For Remy 3. Clarify broker protocol elements https://github.com/wmo-im/wis2-guide/issues/5  

• Agreed that: MQTT experts advice is required to select the right parameters

• Action: (Remy) to check with Verne MQ

• for their advice to selecting the parameters

• Action (TBC):

• (Peng) to discuss with

• EMQX experts for possible suggestion

• about the parameters selection

4. WP8.2 WIS2 to GTS gateway ,  https://github.com/wmo-im/wis2pilot/issues/9  

• TTAAii and CCCC to be added in the message to make it easy to do the mapping from WIS2 to GTS

• This will not be included in the WIS2 Notification Message standard. It will be included in the GTS → WIS2 transition document.

• Data provider who wants to stop dissemination on GTS shall use the GTS properties as described in GitHub issue #24 https://github.com/wmo-im/wis2-notification-message/issues/24

Action: Hassan to provide the document with decisions and relevant information( update ASCII code, MQTT parameters (needed) as an individual document, all independent documents that can be integrated into WIS2 guidance)

• Who will operate those gateways?

  • Considering there is no volunteer for the Gateway, a proposed solution is for one or two RTHs per region to do the gateway from WIS2 to GTS.

  • Action: Hassan will collect all RTH contact points

  . Hassan proposed to have

  • ; organize meetings with potential RTH providers and

  prepares

  • prepare one page for this.

(5) . KPIs for the transition from GTS to WIS2

Decision: Kai agrees to run the GTS to WIS2 Gateway by DWD during transition

Action: Kenji to check the possibility of providing the gateway by JMAWIS2 https://github.com/wmo-im/wis2-guide/issues/20

• (Kai) DWD metrics include number of observations received in DWD and WIS2 network

• per station and per country. There is a need to develop metrics: names of metrics and their purpose.

• (Enrico) High-level KPIs, not too technical, for communication to EC/Cg is needed to get started. For example, the number of Members disseminating data in GTS but not WIS2; the number of Members migrating to WIS2

• Action: (Enrico) to provide a drafted version of high-level KPIs to be submitted to INFCOM-3

8. GTS to WIS2 gateway

• DWD: all data received in GTS are published the Global cache using the topic cache/a/wis2/xxg/gts_to_wis2_dwd/TTAAii

• New data is only available in WIS2

• Decision: DWD to run GTS to WIS2 Gateway during transition

• Action: (Kenji) to check internally the possibility of providing the GTS to WIS2 Gateway by JMA

2

"We need to figure this out for the pilot project" 

• Clarify whether data other than "core data" can be cached by Global Cache https://github.com/wmo-im/tt-nwpmd/issues/10  

• How to push alerts back to originating WIS2node? https://github.com/wmo-im/wis2-guide/issues/8  

• Non-functional performance measures need to be defined https://github.com/wmo-im/wis2-guide/issues/23  

• Portal for WIS2 https://github.com/wmo-im/wis2-guide/issues/21  

• Guidance for data consumers https://github.com/wmo-im/wis2-guide/issues/22  

• Are Global Caches required to validate the data they cache? https://github.com/wmo-im/wis2pilot/issues/86  

Not discussed

3

"We need to figure this out for INFCOM3" 

• Approval procedures of Global Services and nodes https://github.com/wmo-im/wis2-guide/issues/17  

• Version management of Topic Hierarchy https://github.com/wmo-im/wis2-topic-hierarchy/issues/25  

• Clarify the retention for the WIS2 node https://github.com/wmo-im/wis2-guide/issues/18  

• ICAO and GTS headers https://github.com/wmo-im/wis2-guide/issues/19  

Not discussed