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/1115#issuecomment-442858136,https://api.github.com/repos/pydata/xarray/issues/1115,442858136,MDEyOklzc3VlQ29tbWVudDQ0Mjg1ODEzNg==,1197350,2018-11-29T14:43:13Z,2018-11-29T14:43:13Z,MEMBER,Hey @hrishikeshac -- any progress on this? Need any help / advice from xarray devs?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,188996339
https://github.com/pydata/xarray/issues/1115#issuecomment-260387059,https://api.github.com/repos/pydata/xarray/issues/1115,260387059,MDEyOklzc3VlQ29tbWVudDI2MDM4NzA1OQ==,1197350,2016-11-14T16:37:05Z,2016-11-14T16:37:05Z,MEMBER,"To be clear, I am not say that this does not belong in xarray.

I'm saying that we lack clear general guidelines for how to determine whether a particular function belongs in xarray. The criterion of a ""pretty fundamental operation for working with data"" is a good starting point. I would add:
- used across a wide range of scientific disciplines
- clear, unambiguous / uncontroversial definition
- numpy implementation already exists

`corr` meets all of these criteria. Many others (e.g. interpolation, convolution, curve fitting) do as well. Expanding xarray beyond the numpy ufuncs opens the door to supporting these things. I'm just saying it should be conscious, deliberate decision, given the limits on developer time.

Many of these things will be pretty trivial once `.apply()` is here. So perhaps it's not a big deal.
","{""total_count"": 7, ""+1"": 7, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,188996339
https://github.com/pydata/xarray/issues/1115#issuecomment-260333267,https://api.github.com/repos/pydata/xarray/issues/1115,260333267,MDEyOklzc3VlQ29tbWVudDI2MDMzMzI2Nw==,1197350,2016-11-14T13:24:10Z,2016-11-14T13:24:10Z,MEMBER,"I agree this would be very useful. But it is also feature creep. There is an extremely wide range of such functions that could hypothetically be put into the xarray package. (all of [scipy.signal](https://docs.scipy.org/doc/scipy-0.18.1/reference/signal.html) for example) At some point the community should decide what is the intended scope of xarray itself vs. packages built on top of xarray.
","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,188996339