issue_comments: 121703276
This data as json
| 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-121703276 | https://api.github.com/repos/pydata/xarray/issues/475 | 121703276 | MDEyOklzc3VlQ29tbWVudDEyMTcwMzI3Ng== | 1217238 | 2015-07-15T18:22:03Z | 2015-07-15T18:22:03Z | MEMBER | 
 Yes, this is a reasonable choice for the case of 1d indexers. 
 This is also a good idea, though I would probably call the parameter  
 Indeed. As a start, we should be able to do nearest neighbor lookups with a tolerance soon -- I have a pandas PR that should add some of that basic functionality (https://github.com/pydata/pandas/pull/10411). In the long term, it would be useful to have some sort of representation of grid cells in the index itself, possibly something similar to  | {
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
} | 95114700 |