Closed krishnaap closed 3 years ago
Hello @krishnaap,
Panoply and cfgrib use different GRIB decoders. A GRIB field does not itself contain a human-readable description of a variable, but instead something like parameter-number=232:114. It is then up to the decoder to have tables that translate this into strings such as 'Temperature'. cfgrib uses the ecCodes decoder, which translates these parameters into two different strings - the 'name' is a long string such as 'Temperature', and 'shortName' is an abbreviation, such as 't'. We decided it was nicer to use the shortName for the variable names in cfgrib. But even the longer name does not have to match what Panoply uses - it is up to each GRIB decoder to decide the exact name for any given parameter. If you want to inspect the GRIB data further and understand better what each variable is, you can print the details like this:
print(ds2.gust)
This will also give you the 'cf' name, which might more closely match what Panoply gives.
Best regards, Iain
I am trying to read GFS grib data using cfgrib and xarray, but the variable names show differently on cfgrib and on panoply. While reading surface data,
ds2 Out[241]: