You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this should really be done in xarray, but I've been using the xbitinfo .to_compressed_netcdf() and .to_compressed_zarr() convenience functions even when I'm not using bitrounding because... they are convenient! :)
Hi @rsignell-usgs,
Sorry for the slow response! Glad you like the convenience functions. Part of why I haven't responded yet, is that I'm not a big fan in implementing functions that should be done at a different place. However, the convenience functions could be an exception as they wrap stuff anyway. Just to be clear here, your suggestion does not get rid of missing coordinates, but rather gets rid of the _FillValue attribute so it looks like no coordinate is missing, am I right?
I know this should really be done in xarray, but I've been using the xbitinfo
.to_compressed_netcdf()
and.to_compressed_zarr()
convenience functions even when I'm not using bitrounding because... they are convenient! :)CF conventions don't allow missing values in coordinates but xarray produces them nonetheless. I usually remove them via this little code snippet:
Would there be any downside to adding this to
to_compressed_netcdf
so users don't have to?The text was updated successfully, but these errors were encountered: