ET‐ACDM‐5: 13‐August‐2024 - wmo-im/et-acdm GitHub Wiki

Date and Time

13 August 2024 11:00-12:30 UTC (13:00-14:30 CEST)

Venue

telecon

Participants

Markus Fiebig, Jörg Klausen, Kjetil Torseth, Debra Kollonige, Judd Welton, Tom Kralidis, Jeannette Wild, Oksana Tarasova, Anna Milan, Paolo Laj, Sergi Moreno

Provisional agenda

1. Approval of last minutes

https://github.com/wmo-im/et-acdm/wiki/ET%E2%80%90ACDM-2024%E2%80%904:-18-June-2024

2. GAW updates from Secretariat

  • Secretariat is comparing information in GAWSIS with uploaded data in WDC to get the real picture of the GAW stations status, currently focused on ozone and aerosols.

  • Updates in WIGOS metadata representation implemented in OSCAR/GAWSIS: MeteoSwiss provided a list of entries that need to be amended in OSCAR/GAWSIS, these changes need to be communicated to the stations and then they should decide to apply the changes themselves or ask MeteoSwiss to do it.

  • Trainings on measurement of GHG (RA-II & V) and Air Pollution Prediction (RA-I) planned at the beginning of October.

  • GGMT meeting report from 2024 will include a section about data management, including reporting uncertainty to WDCGG and data products like ObsPack.

3. Oksana briefing about Global Greenhouse Gas Watch (G3W)

  • G3W will be managed by an Advisory Group (AG-G3W) co-chaired by Research Board (Greg Carmichael) and INFCOM (Vincent-Henri). There were three dedicated Task Teams, one of them on data management and data architecture. That group will be chaired by Laurence Rouil and will be sitting under INFCOM Standing Committee on Information Management and Technology (SC-IMT).

  • The final deliverable of that team would be the architecture for international data exchange for operational application.

Draft of ToR for the G3W TT on data:

  • Identify current practices in data exchange, data management and data policies within the modelling community,

  • Collect information on the types of prior information required for the implementation of G3W,

  • Identify needs and establish requirements for global data exchange and long-term archiving within all elements of G3W (observations, prior information and modelling components),

  • Collect information on the measurement platforms (i.e. surface-based or space-based observing systems) within the observational tasks of the implementation Plan, that are required to support G3W implementation, document used data collection and exchange protocols and related data policies,

  • Contribute to ensure convergence/compatibility/? from existing practices toward a standard WMO compliant approach,

  • Develop architecture for global data sharing (this includes data producers, data format,...) for the G3W,

  • Report on the activities of the group to SC-IMT and AG-G3W

Q&A

  • Suggestion about ET-ACDM supporting with the specificities related to atmospheric composition domain: QA/QC, procedures to operate in WIS 2.0, interface of the data exchange with the instrument.

  • Remarks on the importance to not duplicate efforts in GAW/G3W. ET-ACDM should be aware of the work in G3W and pursue compatibility until some extend, because data users are not going to be the same for research or operations.

  • Suggestion to establish a formal link ET-ACDM-G3W TT on data.

  • Role of WDCGG unclear in the G3W IP, in other domains WDC archives high quality climatological data while NRT data for operational purposes don't need to be store always, however metadata should be compatible.

  • Suggestion to test WIS 2.0 with a couple of WDC to see how atmospheric composition fits in.

  • Opportunity for WDCs to monitor the evolution of data exchange/archiving in the GHG domain (G3W).

  • Concerns raised about ToRs too centered in the modelling side and how the data requirements are going to be linked with existing protocols, for example NDACC-ECMWF. The idea is that the observation data is shared via WIS 2.0 exchange protocol and modelling centres pull it from there, G3W should aim for compatibility for different workflows.

  • WDC should support the G3W architecture taking into account the new user requirements driven by operational needs. However, until now ET-ACDM and WDCs have not received the mandate to support that architecture.

3. Open issues in github

Agreement to keep it open. Lead: Kaisa Lakkala

Agreement to keep it open. Lead: Tom Kralidis The topic hierarchy agreed by the Team needs to be tested by WDC. Suggestion to start a new issue with the last version of the topic hierarchy for clarification. Closed by now.

Closed.

Too generic, closed.

OAI PMH instance is up and running. Closed.

Sergi to review issue and follow up with DCs who have not responded yet.

Suggestion to advise GAW Programme on how uncertainties can be documented in the WDC, finding if possible, an interoperable approach. Gao Chen suggested as a lead.

Issues 6, 7 & 8 closed. Discussion about GEOMS can led to another open issue in the future.

Close by now, it could be opened as a different issue.

Closed 2 & 3.

6. AOB, topics for the next meeting 12 September