Skip to content

Teleconference 9 and 10.12.2020

Jitsuko Hasegawa edited this page Jan 19, 2021 · 10 revisions

Task Team on Table Driven Code Forms (TT-TDCF)

Teleconference 9-10.12.2020

Meeting Minutes

The team reviewed the following issues.

No. GRIB2 Issue Link Assignee Status
1. Issue 53 New Product Definition Templates to generalize the percentiles (100-quantiles) forecast Templates to any q-quantiles https://github.com/wmo-im/GRIB2/issues/53 Sébastien in validation, sample to be provided, two independent software applications might not be available, which would make impossible to complete validation, Jitsuko will check procedure
2. Issue 54 Add potential evapotranspiration rate in Code Table 4.2, product discipline 2, category 0 https://github.com/wmo-im/GRIB2/issues/54 Sébastien validated
3. Issue 56 Add "first guess" and "difference between First guess and Analysis" https://github.com/wmo-im/GRIB2/issues/56 Sébastien validated
4. Issue 57 Add new parameters for ocean modelling in Code table 4.2 Discipline 10a https://github.com/wmo-im/GRIB2/issues/57 Sébastien validated
5. Issue 58 Add new temperatures in Code table 4.2 https://github.com/wmo-im/GRIB2/issues/58 Sébastien validated
6. Issue 59 Add new entries in Code Table 4.2, product discipline 0, category 1 (moisture) https://github.com/wmo-im/GRIB2/issues/59 Sibylle validated
7. Issue 32 Ocean Wave Table 4.2 additions https://github.com/wmo-im/GRIB2/issues/32 Tom validated
8. Issue 6 Composite local time in GRIB message https://github.com/wmo-im/GRIB2/issues/6 Sébastien in validation, sample to be provided, the same issue with Issue 53
No. BUFR4 Issue Link Assignee Status
1. Issue 21 Revision of E-Profile Sequences https://github.com/wmo-im/BUFR4/issues/21 Richard validated, Jitsuko will update E-Profile team
2. Issue 16 New Table D sequence for reporting observations from ocean gliders https://github.com/wmo-im/BUFR4/issues/16 David in validation, some issues identified, delay to FT2021-2
3. Issue 17 Table D sequence for reporting trajectory profile data from marine animal tags https://github.com/wmo-im/BUFR4/issues/17 David validated, seek pre-operational status
4. Issue 18 New Sequence and descriptors for GNSS Slant Total Delay BUFR https://github.com/wmo-im/BUFR4/issues/18 Sibylle validated
5. Issue 5 Additional bio-geochemical sequences for data from Argo profiling floats https://github.com/wmo-im/BUFR4/issues/5 David keep "in validation" status
6. Issue 51 BUFR sequence for DAYCLI https://github.com/wmo-im/BUFR4/issues/51 Denis (ET-DRC) target FT2021-2, proposal being discussed
7. Issue 50 WIGOS Station Identifier https://github.com/wmo-im/BUFR4/issues/50 Jitsuko no submission to INFCOM (Part III)

BUFR sequence for DAYCLI (Issue 51)

  • The team reviewed the current proposal and advised: 1) the height descriptor should be included in data, 2) the quality flag also should be included in data, 3) instrument classification information (Siting Classification (SC) and Measurement Quality Classification (MQC)) can be indicated in OSCAR/Surface, but need consultation with user/instrument community.
  • Team members agreed in general that metadata (parameters of instruments, e.g. height and quality information) should be included in data to make sure the link between data and metadata, especially in real-time observation data, but it generally applies to statistical data such as CLIMAT to ensure the use of archived data in future.

WIGOS Station Identifier (Issue 50)

  • Chair summarized the discussion and stated that the team needs to find a solution for stations that have traditional identifiers and she prefers to have a realistic implementation schedule for Members rather than rushing into mandating reporting WSI in BUFR, e.g. get it a recommended practice for 5 years and then change it to mandate.
  • The team agreed that it is not responsible for making reporting WSI mandate, but responsible for giving guidance on how to report WSI through Manual on Codes and Members require the guidance.
  • The team recognized that the difficulty in the migration to WSI is not its decoding/encoding of BUFR but the use of the identifier in down stream systems.
  • The team agreed that it was not the stage to submit a proposal of MoC amendments of a note to the WSI sequence (3 01 150) with a "shall" statement.
No. CCT Issue Link Assignee Status
1. Issue 22 Maupuia is misspelled in Table C-12 https://github.com/wmo-im/CCT/issues/22 Anna validated
2. Issue 24 Additions to Common Code Table C-3 Instrument make and type for water temperature profile measurements https://github.com/wmo-im/CCT/issues/24 David validated
3. Issue 26 Add new entry to Common Code Table C-5 to identify HY-2C satellite of China https://github.com/wmo-im/CCT/issues/26 Fang validated

Issues related to publication of Manuals

Review of the change in procedure to manage tables on Github through amendment process

  • The team reviewed the process using a "validation branch."
  • There was a comment that the intermediate branch may be out of sync with master depending on when it was created.
  • The process will be reviewed once again after the completion of FT2021-1.

Non-operational

  • The "Non-operational" files are maintained by the Secretariat to block code figures that are used in validation; therefore the question is if code figures that are once used in validation should be blocked or not.
  • It would be useful if numbers are blocked through the validation to operational phase, because data producers can start using them internally and prepare for wider dissemination. (Is it still valid if a validation process requires duration longer than once FT cycle?)
  • The Secretariat and Chair need to reserve the possibility to change code figures used in validation when the team finalizes all the proposals that are approved in a FT cycle, because unexpected crush can happen.

Pre-operational

  • The term "Pre-operational" should be used carefully because it is defined to mean the specific status that is approved by CBS President to allow use of new codes before they become operational in May/November.
  • The team needs to decide if the "Pre-operational" phase can be discontinued as proposed by the Secretariat; there are cases required by data users.
  • The Secretariat expressed its opinion that the pre-operational phase requires a serious roll-out (full version of tables with a version number), if the team decides to keep the pre-operational phase.

Next step

  • The team agreed that another meeting would be set in January to discuss this issue after Chair and the Secretariat discuss the proposals for change.
  • Chair TT-AvData explained the use of the Codes Registry by IWXXM, and asked if TT-TDCF is happy for TT-AvData to maintain contents of the aviation specific tables, and the future of other BUFR tables and common code tables on the registry, if they can be used/even maintained by other communities.
  • The team agreed with the proposal of TT-AvData's maintaining aviation specific tables, which is now part of BUFR tables (as components of aviation BUFR sequences not in use as such) and used in IWXXM, by making them independent from BUFR tables.
  • The team also agreed that the existing aviation specific tables (as components of aviation BUFR sequences) cannot be deleted even after the dependency is solved, because old IWXXM versions refer the tables and the deletion will break the link in historical data.
  • Regarding the use of common code tables by other communities, the Secretariat expressed its opinion that common codes/tables can only be useful when they are domain specific, because update cycle is different depending on the communities; at the moment there is no mechanism to update the BUFR tables in the codes registry and they are not ready for a wider use.
  • Chair TT-AvData proposed to add tags to each common table on the Codes Registry to show which domains (communities) are using the table and to know who to consult in changing it; the idea is good, but in reality it might be difficult to maintain.
  • The team was informed by the Secretariat that hydrology community is using the registry for hydrology ontology to improve through semantic discovery.
  • The team will consider the solution that will be proposed by Met Office team for the registry to support table version control and make decisions about how to move forward about BUFR/GRIB tables and common codes tables on the registry.

Agenda

  1. Opening and schedule
  2. Review of GRIB proposals
  3. Review of BUFR proposals
  4. Review of Common Code Tables proposals
  5. Review of Issues related to amendment process and publication of Manuals
  6. Next teleconference
  7. AOB

The team will review the following issues.

No. GRIB2 Issue Link Assignee Status
1. Issue 53 New Product Definition Templates to generalize the percentiles (100-quantiles) forecast Templates to any q-quantiles https://github.com/wmo-im/GRIB2/issues/53 Sébastien in validation, branch updated
2. Issue 54 Add potential evapotranspiration rate in Code Table 4.2, product discipline 2, category 0 https://github.com/wmo-im/GRIB2/issues/54 Sébastien in validation, branch updated
3. Issue 56 Add "first guess" and "difference between First guess and Analysis" https://github.com/wmo-im/GRIB2/issues/56 Sébastien in validation, branch created, waiting for conclusion on entry 21
4. Issue 57 Add new parameters for ocean modelling in Code table 4.2 Discipline 10a https://github.com/wmo-im/GRIB2/issues/57 Sébastien in validation, branch updated
5. Issue 58 Add new temperatures in Code table 4.2 https://github.com/wmo-im/GRIB2/issues/58 Sébastien in validation, branch updated
6. Issue 59 Add new entries in Code Table 4.2, product discipline 0, category 1 (moisture) https://github.com/wmo-im/GRIB2/issues/59 Sibylle in validation, a note added, branch updated
7. Issue 32 Ocean Wave Table 4.2 additions https://github.com/wmo-im/GRIB2/issues/32 Tom in validation, branch updated
8. Issue 6 Composite local time in GRIB message https://github.com/wmo-im/GRIB2/issues/6 Sébastien proposal submitted (new entry 4 to Code table 1.2, PDT4.88, a new Code Table 4.248), branch created
No. BUFR4 Issue Link Assignee Status
1. Issue 21 Revision of E-Profile Sequences https://github.com/wmo-im/BUFR4/issues/21 Richard in validation, branch created and merged to validation branch
2. Issue 16 New Table D sequence for reporting observations from ocean gliders https://github.com/wmo-im/BUFR4/issues/16 David in validation, branch created and merged to validation branch, some issues identified
3. Issue 17 Table D sequence for reporting trajectory profile data from marine animal tags https://github.com/wmo-im/BUFR4/issues/17 David validation completed, will be in FT2021-1, seek pre-operational status
4. Issue 18 New Sequence and descriptors for GNSS Slant Total Delay BUFR https://github.com/wmo-im/BUFR4/issues/18 Sibylle in validation, branch created, validation confirmed by Jeff, Marijana and Sergio
5. Issue 5 Additional bio-geochemical sequences for data from Argo profiling floats https://github.com/wmo-im/BUFR4/issues/5 David in validation, samples required, Marijana volunteering for validation
6. Issue 51 BUFR sequence for DAYCLI https://github.com/wmo-im/BUFR4/issues/51 Denis (ET-DRC) target FT2021-2, proposal being discussed
7. Issue 50 WIGOS Station Identifier https://github.com/wmo-im/BUFR4/issues/50 Jitsuko target INFCOM (Part III), proposal being discussed

BUFR sequence for DAYCLI (Issue 51)

  • Update from ET-DRC

WIGOS Station Identifier (Issue 50)

  • Update from Chair and the Secretariat
  • Proposal to add a new not to the WSI sequence (3 01 150), see Issue 50: FT2021-1 or submit to INFCOM in February
  • Other actions that TT-TDCF should take at this stage
No. CCT Issue Link Assignee Status
1. Issue 22 Maupuia is misspelled in Table C-12 https://github.com/wmo-im/CCT/issues/22 Anna in validation, branch will be created
2. Issue 24 Additions to Common Code Table C-3 Instrument make and type for water temperature profile measurements https://github.com/wmo-im/CCT/issues/24 David in validation, branch will be created
3. Issue 26 Add new entry to Common Code Table C-5 to identify HY-2C satellite of China https://github.com/wmo-im/CCT/issues/26 Fang in validation, branch created and merged to validation branch

Issues related to publication of Manuals

Review of the change in procedure to manage tables on Github through amendment process

  • The team will review the process using a "validation branch" and modify/discontinue as necessary; the team needs to pay attention to the cases where validation takes long time and does not go to the next Fast Track.
  • See wiki page on WIS-IM Workflow
  • Validate machine-readable legacy format for BUFR4, GRIB2 and CCT
  • Remove docs/pdfs of different sections of the manual, because the details are published in the amendment documents which can be found: https://community.wmo.int/activity-areas/wis/wis-manuals.
  • Remove non-operational - rely on GitHub instead
  • Remove pre-operational (decision may be subject to policy)
  • Remove experimental - rely on GitHub instead
  • Updates since last meeting
  • Use case of TT-AvData
  • Use case by hydrological community

List of participants

No. Name Agency Dec. 9 Dec. 10
1 Jitsuko HASEGAWA JMA X X
2 Enrico FUCILE WMO Secretariat X
3 Abderrazak LEMKHENTER Météo Maroc X X
4 Fang ZHAO CMA X X
5 Sergio Henrique Soares FERREIRA National Institute for Space Research, Brazil X X
6 Tom KRALIDIS Environment and Climate Change Canada X X
7 Jeffrey ATOR NOAA X X
8 Sibylle KREBBER DWD X X
9 Richard WEEDON Met office X X
10 Sébastien VILLAUME ECMWF X X
11 Marijana CREPULJA ECMWF X X
12 Simon Stuart ELLIOTT EUMETSAT X X
13 Daniel LEE EUMETSAT
14 Marian MAJAN HMEI X X
15 David Berry NOC X X
16 B. L. CHOY HKO X
17 Denis STUBER France, ET-DRC X
18 Christina Lief USA, ET-DRC
19 Anna MILAN WMO Secretariat X X
20 Xiaoxia CHEN WMO Secretariat X X
21 Igor CHERNOV WMO Secretariat X
Clone this wiki locally