-
Notifications
You must be signed in to change notification settings - Fork 42
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
loadGridData fails to find named variable in netCDF file #19
Comments
I have the same issue with a netcdf file retrieved from the ipcc interactive atlas (which uses climate4R btw). Any chance on a reaction on this issue as it is quite cumbersome that some ncdf files can be read and others can't. |
Dear @cs2239, can you provide access to the .nc file (MPI-ESM-LR_FWI_ET017_cal.nc) you are trying to open with? |
@AranJM, there is an issue with metadata for the netcdf files generated by the interactive atlas. These files are been parsed and generated by the backend that is using GDAL which is manipulating/truncating some attributes and coordinates of the original files. |
@cofinoa Thanks for the answer. Any workaround/solution you can think of perhaps? |
@AranJM I can provide you a workaround ... please let me know which .nc file are you interested on ... and I would check exactly what is the metadata to be changed. |
@AranJM, as workaround you can create a .ncml file, besides (i.e. same directory) the downloaded file from the interactive atlas, and with the following XML contente: <?xml version="1.0" encoding="UTF-8"?>
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2" location="{{ FILE.nc }}">
<variable name="{{ VARIABLE }}">
<logicalReduce dimNames="baseline period time_filter" />
</variable>
</netcdf> you must replace |
netcdf file in question:
So loadGridData can't find the var named fwi... I should note this is take 2. The original calendar was gregorian (not proleptic_gregorian). Loading that file yielded:
I switched calendars with CDO and that has disappeared the var even though it is there per ncdump...
The text was updated successfully, but these errors were encountered: