Conversation
|
Thanks @marqh |
29a5df5 to
d494ebc
Compare
| continue | ||
| # Restrict to one-dimensional with name as dimension OR zero-dimensional scalar | ||
| if not ((nc_var.ndim == 1 and nc_var_name in nc_var.dimensions) or (nc_var.ndim == 0)): | ||
| # Restrict to one-dimensional with name as dimension |
There was a problem hiding this comment.
A zero dimensional scalar variable can never be a netcdf coordinate variable. The definitions within the CF Conventions and the netCDF user guide are explicit on this.
A 'coordinate variable' is one dimensional, with the same name as the dimension it is defining.
A scalar variable is not defined with respect to a dimension, it is a scalar.
|
I am getting test failures unrelated to my change, e.g. |
|
Looks like an issue around the new masked array functionality in Dask. |
|
@djkirkham: would you mind helping to add a unit test that covers the issue identified with dask? |
|
I've added a workaround and unit tests in #2878 |
|
@marqh, would you mind rebasing this and adding a what's new? I think the tests should go green what that done, and I'd be happy to merge for the |
d494ebc to
0254de6
Compare
@pelson I have rebased and added a what's new sentence to the 2.0.rst directly awaiting test results ... ... |
|
Thanks @marqh. |
new test to check that a scalar data variable in a netcdf file will be loaded into a cube
addressing long standing bug reports, including #1427