issue_comments

Table actions

3 rows where author_association = "MEMBER" and issue = 114773593 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

issue 1

  • Feature request: only allow nearest-neighbor .sel for valid data (not NaN positions) · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1150280375 https://github.com/pydata/xarray/issues/644#issuecomment-1150280375 https://api.github.com/repos/pydata/xarray/issues/644 IC_kwDOAMm_X85Ej-K3 shoyer 1217238 2022-06-08T18:56:17Z 2022-06-08T18:56:17Z MEMBER

This might fit more naturally into interp() as a new method like "nearest-valid" rather than in sel().

The difference is that sel() only looks at indexes (and not the data) to select out a single value, whereas interp() can combine adjacent values in arbitrary ways.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature request: only allow nearest-neighbor .sel for valid data (not NaN positions) 114773593
721440664 https://github.com/pydata/xarray/issues/644#issuecomment-721440664 https://api.github.com/repos/pydata/xarray/issues/644 MDEyOklzc3VlQ29tbWVudDcyMTQ0MDY2NA== shoyer 1217238 2020-11-04T00:10:41Z 2020-11-04T00:10:41Z MEMBER

There hasn't been any progress on this to my knowledge, unfortunately

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature request: only allow nearest-neighbor .sel for valid data (not NaN positions) 114773593
155611625 https://github.com/pydata/xarray/issues/644#issuecomment-155611625 https://api.github.com/repos/pydata/xarray/issues/644 MDEyOklzc3VlQ29tbWVudDE1NTYxMTYyNQ== shoyer 1217238 2015-11-11T00:27:10Z 2015-11-11T00:27:10Z MEMBER

This is tricky to put into .sel because that method currently works by only looking at coordinate labels, not at data values.

One way to fix this would be to unravel your two dimensions corresponding to latitude and longitude into a single "lat_lon" dimension. At this point, you could apply a sea mask, to produce a compressed lat_lon coordinate corresponding to only unmasked points. Now, it's relatively straightforward to imagine doing nearest neighbor lookups on this set of labels.

This later solution will require a few steps (all of which are on the "to do" list, but without any immediate timelines): 1. support for multi-level indexes in xray 2. support for "unraveling" multiple dimensions into 1-dimension 3. support for looking up nearest locations in multiple dimensions via some sort of spatial index (e.g., a KD tree)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature request: only allow nearest-neighbor .sel for valid data (not NaN positions) 114773593

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);