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/665#issuecomment-159678567,https://api.github.com/repos/pydata/xarray/issues/665,159678567,MDEyOklzc3VlQ29tbWVudDE1OTY3ODU2Nw==,1217238,2015-11-25T17:18:44Z,2015-11-25T17:18:44Z,MEMBER,"@spencerahill if you get a similar error with 2d latitude/longitude arrays please do report it in a separate issue. I'm pretty sure this one is specific to timedeltas.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,118525173
https://github.com/pydata/xarray/issues/665#issuecomment-159423714,https://api.github.com/repos/pydata/xarray/issues/665,159423714,MDEyOklzc3VlQ29tbWVudDE1OTQyMzcxNA==,1217238,2015-11-24T22:16:29Z,2015-11-24T22:16:29Z,MEMBER,"No worries -- thanks for the bug report! I'm sure someone will get to this
eventually.

On Tue, Nov 24, 2015 at 2:15 PM, naught101 notifications@github.com wrote:

> Sorry, this is just something I stumbled across in a workshop, it's not a
> problem that's affecting my work, so I don't have much time for it. But
> I'll make the MOM developers aware of it - they might have an interest in
> helping out.
> 
> —
> Reply to this email directly or view it on GitHub
> https://github.com/xray/xray/issues/665#issuecomment-159423524.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,118525173
https://github.com/pydata/xarray/issues/665#issuecomment-159421963,https://api.github.com/repos/pydata/xarray/issues/665,159421963,MDEyOklzc3VlQ29tbWVudDE1OTQyMTk2Mw==,1217238,2015-11-24T22:10:40Z,2015-11-24T22:10:40Z,MEMBER,"OK, I just tried this out and this is a legit bug.

The array that needs to be converted to time deltas is 2D, and pandas can't handle that. We need to flatten out the array [in `decode_cf_timedelta`](https://github.com/xray/xray/blob/76d15b27974b10eae88f343ab568deb815073323/xray/conventions.py#L162-L172) and then unflatten it, similarly to [what we do in `decode_cf_datetime`](https://github.com/xray/xray/blob/76d15b27974b10eae88f343ab568deb815073323/xray/conventions.py#L115-L151).

Any interest in putting together a pull request with a fix?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,118525173
https://github.com/pydata/xarray/issues/665#issuecomment-159193866,https://api.github.com/repos/pydata/xarray/issues/665,159193866,MDEyOklzc3VlQ29tbWVudDE1OTE5Mzg2Ng==,1217238,2015-11-24T08:29:54Z,2015-11-24T08:29:54Z,MEMBER,"Did you try specifying a different engine to read the netcdf file? That might at least give you different error ;).

On Mon, Nov 23, 2015 at 9:31 PM, naught101 notifications@github.com
wrote:

> ## I updated to 1.2.1 from pypi, it still fails.
> 
> Reply to this email directly or view it on GitHub:
> https://github.com/xray/xray/issues/665#issuecomment-159153806
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,118525173
https://github.com/pydata/xarray/issues/665#issuecomment-159143368,https://api.github.com/repos/pydata/xarray/issues/665,159143368,MDEyOklzc3VlQ29tbWVudDE1OTE0MzM2OA==,1217238,2015-11-24T03:54:24Z,2015-11-24T03:54:24Z,MEMBER,"What version of netcdf4-Python are you using? I have a strong hunch this is the same issue as https://github.com/xray/xray/issues/662
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,118525173