html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/6570#issuecomment-1117276228,https://api.github.com/repos/pydata/xarray/issues/6570,1117276228,IC_kwDOAMm_X85CmEhE,5821660,2022-05-04T12:51:18Z,2022-05-04T12:51:18Z,MEMBER,"> The change is somewhere between version 0.12.0 and 1.0.0 [(one user](https://github.com/wradlib/wradlib/issues/562) says from 0.14, but I haven't verified).

It's from h5netcdf 0.14 onwards, please see  https://github.com/h5netcdf/h5netcdf/blob/main/CHANGELOG.rst.

> Adding the invalid_netcdf=True argument when loading does not change the behaviour.

That keyword argument is distributed verbatim to `h5netcdf`. It tells `h5netcdf` to **write** [invalid netcdf features](https://github.com/h5netcdf/h5netcdf#invalid-netcdf-files) if there are any. This will then effectively create files which might not be readable by `netcdf-c/netcdf4-python`. It has no meaning for reading files.

> I have tested that direct reading by h5py.File gives str, ndarray, ndarray so the change is not in the writing or h5py.

The change is in `h5netcdf` reading attributes, where we have aligned it with `netcdf4-python`.

I think updating the docs as suggested is fine.

","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1225191984