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/486#issuecomment-348556569,https://api.github.com/repos/pydata/xarray/issues/486,348556569,MDEyOklzc3VlQ29tbWVudDM0ODU1NjU2OQ==,2443309,2017-12-01T17:28:13Z,2017-12-01T17:28:13Z,MEMBER,@mraspaud - What functionality are you interested in bringing over? I've been watching pyresample for a while and would love to see our two packages leverage each other's functionality (where possible).,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,96211612
https://github.com/pydata/xarray/issues/486#issuecomment-271682285,https://api.github.com/repos/pydata/xarray/issues/486,271682285,MDEyOklzc3VlQ29tbWVudDI3MTY4MjI4NQ==,2443309,2017-01-10T20:03:19Z,2017-01-10T20:03:19Z,MEMBER,"@rabernat - I've more or less settled that this belongs in a separate package that uses xarray's [accessor](http://xarray.pydata.org/en/stable/internals.html#extending-xarray) features. 

I've setup a little project (`xmap`) to get this started that I hope we can garner some volunteers to help push forward (nudge @godfrey4000 and @forman): https://github.com/jhamman/xmap

There will likely be some overlap between features that `xmap` and `xarray`. In those cases, we can try to push relevant features toward `xarray`. ","{""total_count"": 5, ""+1"": 5, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,96211612
https://github.com/pydata/xarray/issues/486#issuecomment-207529535,https://api.github.com/repos/pydata/xarray/issues/486,207529535,MDEyOklzc3VlQ29tbWVudDIwNzUyOTUzNQ==,2443309,2016-04-08T17:34:37Z,2016-04-08T17:34:37Z,MEMBER,"@forman - no progress on my end and no plans to work on this in the next 6 months. If your team is interested in working on this, we can discuss the api further and I'm happy to provide input and guidance along the way. One option is to wrap `pyresample` and possibly fill in some of the missing pieces in their api. I'd like to see a user interface that looks something like this:

``` python
da.resample_like(other, kind='bilinear', dims=('lat', 'lon'))
```

As @rabernat mentions, for some remapping/resampling, the multi-dimensional groupby will help with some of these applications.  
","{""total_count"": 3, ""+1"": 3, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,96211612
https://github.com/pydata/xarray/issues/486#issuecomment-123413440,https://api.github.com/repos/pydata/xarray/issues/486,123413440,MDEyOklzc3VlQ29tbWVudDEyMzQxMzQ0MA==,2443309,2015-07-21T17:45:51Z,2016-04-08T17:22:48Z,MEMBER,"I'd be interested in helping build a wrapper / api that supports the following types of regridding operations. I don't think pyresample handles all of these:
1. Bilinear interpolation
2. Bicubic interpolation
3. Distance-weighted average remapping
4. Nearest neighbor remapping
5. Conservative (area) remapping
6. Largest area fraction remapping

I would also like to see some better support for 2D coordinate variables.  These are specifically outlined in the [cf-conventions](http://cfconventions.org/Data/cf-conventions/cf-conventions-1.6/build/cf-conventions.html#coordinate-types) in section: _5.2. Two-Dimensional Latitude, Longitude, Coordinate Variables_. Maybe we can open an additional issue for that...
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,96211612