Page Comparison

INFCOM deadlines and update

Summary:

• INFCOM 24 - 28th October

• Deadline for documents to be submitted TBC (expected to be 29th July or earlier).

• Information papers can be submitted later.

• At the INFCOM management group meeting it was agreed to include the guide as a chapter in the WIS Guide.

Question on glossaryQuestions:

GP: Does

the glossary need to be ready by the same deadline?

DB: Yes, all the documentation for INFCOM needs to be ready.

WW: within WMO-No. 49 , the climate section is being rewritten , new definitions also in there. (WW)and this includes definitions (related to climate data) that may be relevant to the guide.

Action: WW to circulate.

Action: DB to update list of WMO publications .on confluence

WMO No. 1131 Review

WW: leading William Wright noted that he was leading a review and update of 1131

Going through thoroughly, finding areas that need updating. Out of date in places.

Number of areas where the information could be incorporated into these guidelines, esp. Ch. 5 on DM and Ch. to the WMO Climate Data Management System specification (WMO-No. 1131). Whilst there are many areas out of date within the document there are other sections that may be relevant to the new guide, especially chapter 5 on data mangement and chapter 8 on data delivery services. Examples sections include:

• Mapping and web services, symbology (see https://www.ogc.org/standards/se ).

• Geosychonisation

  • Making sure users have access to most up to date data

• Quality classification and monitoring, network monitoring

• Coding - WWR, during another meeting (on WWR) it was recognised that in all various standard WMO messages one of the major problems is that there are many formatting errors in when submitting the codes.Push in guidelines document the need to automate these things.

• Status logs for ingests, flagging when data expected and not received etc. How to recover the data

• Data lifecycle

Update on reviews received

Approaches to addressing / capturing reviews

WW noted that there should be a push in guidelines to document the need to automate the encoding of data to minimise errors.

• One topic that we may need to cover in the guide is the hardware/infrastructure lifecycle in addition to the information lifecycle.

• One solution would be to flag the need to be aware of the issue and to refer to other documents.

Update on reviews received

GP: updated the team on reviews received. External to the Team, reviews were received from:

• Tom Kralidis (ET-Metadata)

• Tommaso Abrate (JET-HYDMON)

• Johanna Korhonen (JET-HYDMON)

• Dennis Stuber (ET-DRC)

• Kevin O’Brien (GOOS OCG)

• Robert Dunn (ET-DRC)

• Gerald Fletzer (ET-AC)

Reviews all collated to a single document, available from sharepoint (DB) and google (GP). The original submissions have also been placed in the google drive for reference alongside an xls document to track the responses.

links to follow

Approaches to addressing / capturing reviews

In order to manage and track reviews the comments will be copied to the xlsx document (action DB).

Individuals nominated / assigned to lead the response on different chapters:

Chapter 1 - Introduction (DB/GP)

Chapter 2 - Definitions (GP/XC)

Chapter 3 - IM principles (RS/WW)

Chapter 4 - IM lifecycle (WW/RS)

Chapter 5 - Other considerations (HH)

Chapter 6 - Summary and conclusions (WW)

Other items

GP: The ET-DRC are having an in person meeting in Geneva 27th - 29th September. There is cross over between the ET-DRC and ET-IM membership, would it be worth having an in person meeting of the ET-IM the same week?

Action: DB and XC to look into the possibility of this.

• future of ET-IM post INFCOM.

DB to check

Next meeting