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/4118#issuecomment-876397215,https://api.github.com/repos/pydata/xarray/issues/4118,876397215,MDEyOklzc3VlQ29tbWVudDg3NjM5NzIxNQ==,7611856,2021-07-08T12:27:58Z,2021-07-08T12:27:58Z,NONE,"As a user who (so far) does not use any netCDF or HDF5 features of xarray I obviously would not like to have a otherwise potentially useful feature blocked by restrictions imposed by netCDF or HDF5 ;-).

That said - I think @tacaswell comment about round trips is very reasonable and such invariants should be maintained! It would be extremely confusing for users if netcdf -> xarray-> netcdf is not a  ""no-op"". The same obviously holds true for any other storage format. As a user I would generally expect something like the following:
```python
a1= xarray.load(""foo.myformat"")
xarray.save( a1, ""bar.myformat"")
a2= xarray.load(""bar.myformat"")
assert a1 == a2, ""Why should they not be exactly equal?!?"" 
```","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,628719058