-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRS Template 5.42 #204
Comments
NCL uses g2clib to read GRIB2. Does anyone know if g2clib can currently handle the CCSDS compression method? If so, how would I make that updated library available in NCL v6.6.2? |
Found this on a google search, as I ran into this issue as well (not with NCL, but with GDAL). Looks like you can use the ecCodes tool to decompress the data and get it into a usable format by NCL or GDAL or whatever.
Hope this workaround helps you, and other strangers that search for this issue. |
… 5.42). Requires building GDAL against libaec (Cf https://gitlab.dkrz.de/k202009/libaec) Cf NCAR/ncl#204 Fixes OSGeo#8092
… 5.42). Requires building GDAL against libaec (Cf https://gitlab.dkrz.de/k202009/libaec) Cf NCAR/ncl#204 Fixes OSGeo#8092
… 5.42). Requires building GDAL against libaec (Cf https://gitlab.dkrz.de/k202009/libaec) Cf NCAR/ncl#204 Fixes OSGeo#8092
Describe the bug
ECMWF recently upgraded the GRIB2 compression method to CCSDS (using data representation template 5.42). This is resulting in an error while attempting to read ECMWF-produced GRIB2 files in NCL. NCL does not exit with this error, but my script quickly fails because no GRIB2 data is actually read. The full error is:
Provide the following:
https://data.ecmwf.int/forecasts/20230627/12z/0p4-beta/oper/20230627120000-0h-oper-fc.grib2
Computing environment
Additional context
I think this problem might be resolved by adding the correct table information in this sub-directory, but I'm not sure exactly what to change/add:
${NCARG_ROOT}/lib/ncarg/grib2_codetables/ecmwf/5/
I am in the process of migrating from NCL to Python. It would be nice to continue to process ECMWF data using NCL until that migration is complete.
The text was updated successfully, but these errors were encountered: