inconsistent bounds (lat_bnds etc) after subset operation about clisops HOT 7 CLOSED

@cehbrecht: It looks like using the example code above (from PR #204) is the best place to clean up the dataset. Hopefully, it will only involve adding a few extra lines of code.

from clisops.

This issue is also related to #198. The FixValue issue was (partially) fixed already in our 0.9.0 release by PR #204

from clisops.

The unnecessary coordinate at the bounds variables, like:

double lat_bnds(lat, bnds) ;
    lat_bnds:coordinates = "height" ;

... was already reported to xarray by @ellesmith88 :
pydata/xarray#5510

A workaround to get rid off these coordinates is provided in xarray:
pydata/xarray#5514

For example like this:

ds.lat_bnds.encoding["coordinates"] = None

from clisops.

Workaround?

In the test notebook above I'm applying all mentioned workarounds on the xarray dataset:

ds.time.encoding["_FillValue"] = None
ds.lon.encoding["_FillValue"] = None
ds.lat.encoding["_FillValue"] = None
ds.height.encoding["_FillValue"] = None

ds.lat_bnds.encoding["_FillValue"] = None
ds.lat_bnds.encoding["coordinates"] = None

ds.lon_bnds.encoding["_FillValue"] = None
ds.lon_bnds.encoding["coordinates"] = None

ds.time_bnds.encoding["_FillValue"] = None
ds.time_bnds.encoding["coordinates"] = None

Then I write the dataset as netcdf file:

ds.to_netcdf("/tmp/out.nc")

Both cdo sinfo and ncdump -h seem to be happy with the new netcdf file.

from clisops.

@Zeitsperre @sol1105 @agstephens thoughts?

from clisops.

workaround can be added like this (from PR #204):

from clisops.

Fixed in clisops by #225. Works also now in daops and rook.

from clisops.