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/2847#issuecomment-476699976,https://api.github.com/repos/pydata/xarray/issues/2847,476699976,MDEyOklzc3VlQ29tbWVudDQ3NjY5OTk3Ng==,1197350,2019-03-26T15:22:43Z,2019-03-26T15:22:43Z,MEMBER,Also xref #2844,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,424538928
https://github.com/pydata/xarray/issues/2847#issuecomment-476696252,https://api.github.com/repos/pydata/xarray/issues/2847,476696252,MDEyOklzc3VlQ29tbWVudDQ3NjY5NjI1Mg==,1197350,2019-03-26T15:15:14Z,2019-03-26T15:21:36Z,MEMBER,"In the longer term, we could move towards supporting `IntervalIndex` as an in-memory representation of CF-conventions' [cell bounds](http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-conventions.html#cell-boundaries) concept. In addition to many other benefits, this would allow us to encode and decode such indices from netCDF files.

xref #1475","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,424538928
https://github.com/pydata/xarray/issues/2847#issuecomment-476252880,https://api.github.com/repos/pydata/xarray/issues/2847,476252880,MDEyOklzc3VlQ29tbWVudDQ3NjI1Mjg4MA==,10050469,2019-03-25T15:39:09Z,2019-03-25T15:39:09Z,MEMBER,"> A hint in the documentation may hinder others to fall into this pit.

Agreed. Would you like to submit a pull-request?

> Also it would be nice to have intervals serialized into netCDF since they are quite common structures.

There are ways to deal with intervals in the CF conventions, but what we really need is a way for xarray to truly *understand* intervals, which is a much bigger endeavor. ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,424538928
https://github.com/pydata/xarray/issues/2847#issuecomment-475964357,https://api.github.com/repos/pydata/xarray/issues/2847,475964357,MDEyOklzc3VlQ29tbWVudDQ3NTk2NDM1Nw==,2539336,2019-03-24T14:26:14Z,2019-03-24T14:26:14Z,NONE,"Thank you @spencerkclark for the fast response. 
I did exactly as you advices and it works fine.
A hint in the documentation may hinder others to fall into this pit.
Also it would be nice to have intervals serialized into netCDF since they are quite common structures.

Cheers,
Volker","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,424538928
https://github.com/pydata/xarray/issues/2847#issuecomment-475918645,https://api.github.com/repos/pydata/xarray/issues/2847,475918645,MDEyOklzc3VlQ29tbWVudDQ3NTkxODY0NQ==,6628425,2019-03-24T01:09:25Z,2019-03-24T01:09:25Z,MEMBER,"Thanks for the issue.  I think the main problem is that we currently do not have a way of saving an `IntervalIndex`, which `groupby_bins` produces, to a netCDF file:
```
In [7]: out.indexes['data_bins']
Out[7]:
IntervalIndex([(0, 2], (2, 4], (4, 6], (6, 8]],
              closed='right',
              dtype='interval[int64]')
```
One way to work around this in the meantime is to redefine the bins coordinate before saving things to a file.  See @jhamman's answer to a [related StackOverflow question](https://stackoverflow.com/questions/54848671/using-xarray-groupby-bins-results-in-coordinates-that-are-an-object-and-cant-be) for an example.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,424538928
https://github.com/pydata/xarray/issues/2847#issuecomment-475917578,https://api.github.com/repos/pydata/xarray/issues/2847,475917578,MDEyOklzc3VlQ29tbWVudDQ3NTkxNzU3OA==,2448579,2019-03-24T00:46:35Z,2019-03-24T00:46:35Z,MEMBER,Try `data = np.array(...)`,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,424538928