-
Notifications
You must be signed in to change notification settings - Fork 77
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
Using cfgrib to open Stage-IV rainfall data #27
Comments
Perhaps related to #17? There are many different flavors of grib files out there in the wild. It would be good to be clear about which ones that cfgrib is committed to supporting. |
@edougherty32 looks like I assumed ecCodes could provide geographic coordinates for In current @rabernat regarding coordinate systems support the commitment is the one in the README:
More in general we aim of cfgrib is quite simple: to support all GRIB files that
|
@edougherty32 as a quick update: I had a quick conversation with the ecCodes developers and looks like |
@alexamici Thanks for the update. For now, I will stick with the
function, setting the engine to 'pynio' to read in the Stage-IV rainfall. However, I look forward to any developments on the use of cfgrib to work with Stage-IV files, as it might be more efficient than just using xarray. |
Next release of ecCodes will enable Closing the issue. |
Hi,
I was wondering if it's possible to use cfgrib to open Stage-IV GRIB rainfall data (downloaded here). I attempted this in Jupyter notebook:
cfgrib.open_dataset('/glade/scratch/doughert/stage_iv/2008/ST4.2008031900.01h')
And received the following error:
I am guessing this is due to the structure of the Stage-IV data, which is seen by opening the dataset via the usual xarray function:
xr.open_dataset('/glade/scratch/doughert/stage_iv/2008/ST4.2008031900.01h', engine='pynio')
Where the coordinates and variables aren't the usual "latitude" and "longitude" I've seen in the examples of cfgrib so far. So does this mean this package would be unusable for Stage IV data?
The text was updated successfully, but these errors were encountered: