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/2231#issuecomment-397185013,https://api.github.com/repos/pydata/xarray/issues/2231,397185013,MDEyOklzc3VlQ29tbWVudDM5NzE4NTAxMw==,1217238,2018-06-14T06:24:47Z,2018-06-14T06:24:47Z,MEMBER,One thing I’ll note is that you probably want to make the time bounds variables *coordinates* rather than data variables. But that means the time bounds will probably simply be dropped when you resample.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,332018176
https://github.com/pydata/xarray/issues/2231#issuecomment-397167282,https://api.github.com/repos/pydata/xarray/issues/2231,397167282,MDEyOklzc3VlQ29tbWVudDM5NzE2NzI4Mg==,1217238,2018-06-14T04:32:25Z,2018-06-14T04:32:25Z,MEMBER,"Sorry, xarray doesn’t handle time bounds directly, nor does it update metadata according to cfconventions. These were intentional design choices to keep xarray simple, but in principle you could layer cf convention handling on top of xarray.

For this sort of analysis, using a tool like Iris designed to follow cf conventions might make sense. You can convert directly between iris cubes and xarray DataArray objects.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,332018176