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/3213#issuecomment-521596825,https://api.github.com/repos/pydata/xarray/issues/3213,521596825,MDEyOklzc3VlQ29tbWVudDUyMTU5NjgyNQ==,8238804,2019-08-15T10:34:30Z,2019-08-15T10:34:30Z,NONE,That's fair. I just think it would be useful to have an assurance that indices are sorted you read them. I don't see how to express this within the CF specs while still looking like a COO array though.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,479942077
https://github.com/pydata/xarray/issues/3213#issuecomment-521530770,https://api.github.com/repos/pydata/xarray/issues/3213,521530770,MDEyOklzc3VlQ29tbWVudDUyMTUzMDc3MA==,8238804,2019-08-15T06:28:24Z,2019-08-15T07:33:04Z,NONE,"Would it be feasible to use the [contiguous ragged array spec](http://cfconventions.org/cf-conventions/cf-conventions.html#_contiguous_ragged_array_representation) or the [gathering based compression](http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-conventions.html#compression-by-gathering) when the COO coordinates are sorted? I think this could be very helpful for read efficiency, though I'm not sure if random writes were a requirement here.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,479942077