Opened 3 years ago
Closed 3 years ago
#287 closed Defect (fixed)
Suddenly ECMWF files have a GRIB2 message with shortName=unknown
Reported by: | anphi | Owned by: | anphi |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | FP input data | Version: | flex_extract_v7.1 |
Keywords: | Cc: |
Description
There was a reported problem that since the 25th of November 2020 the GRIB2 surface field message snow depth has a shortName=unknown instead of sd.
Change History (2)
comment:1 Changed 3 years ago by anphi
comment:2 Changed 3 years ago by anphi
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Why do we have this problem?
============================
In October, there was an announcement of a change in default modules on ECMWF servers on Wednesday 25 November 2020 10:00 - 10:30 UTC.
https://confluence.ecmwf.int/pages/viewrecentblogposts.action?key=UDOC
They changed the default version of eccodes from 2.17. to 2.19.1. Since version 2.19.0 there is
a change in the encoding of the snow depth parameter 141 in GRIB2 format:
https://confluence.ecmwf.int/display/ECC/ecCodes+version+2.19.0+released
This causes all older versions of eccodes to misinterpret the GRIB2 message of snow depth if the conversion of GRIB1 to GRIB2 was done with eccodes version >= 2.19.0.
The new GRIB2 snow depth message has parameter ID 254 while the old one has 11.
Possible solutions
==================