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/475#issuecomment-121790688,https://api.github.com/repos/pydata/xarray/issues/475,121790688,MDEyOklzc3VlQ29tbWVudDEyMTc5MDY4OA==,4383303,2015-07-16T00:42:08Z,2015-07-16T00:42:08Z,NONE,"Unidata also has a [blog post](http://www.unidata.ucar.edu/blogs/developer/en/entry/accessing_netcdf_data_by_coordinates) benchmarking cKDTree and other methods and concludes ""Your Mileage May Vary"". I'd probably just go with a KDTree, but something to aware of. 
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,95114700
https://github.com/pydata/xarray/issues/475#issuecomment-121701139,https://api.github.com/repos/pydata/xarray/issues/475,121701139,MDEyOklzc3VlQ29tbWVudDEyMTcwMTEzOQ==,4383303,2015-07-15T18:15:49Z,2015-07-15T18:15:49Z,NONE,"Seems like if your method is going to be named `sel_points` then `points` is a reasonable dimension name. Maybe support a `name` kwarg?

One thing to keep in mind is that for many of us the ""nearest-neighbor"" part isn't really `method='nearest'`, but instead more like, `method='ingridcell'` where the grid cell might be roughly square or might be something pretty different. At least that's how I think of my data. Maybe what I really want is some other kind of more explicit support for gridded data, although my thoughts on this are too half-baked to clearly write down. I thought there was another issue related to this, but I couldn't find it.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,95114700