issue_comments

Table actions

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

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • Time bounds returned after an operation with resample-method · 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
658438489 https://github.com/pydata/xarray/issues/2231#issuecomment-658438489 https://api.github.com/repos/pydata/xarray/issues/2231 MDEyOklzc3VlQ29tbWVudDY1ODQzODQ4OQ== dcherian 2448579 2020-07-14T22:09:47Z 2020-07-14T22:09:47Z MEMBER

@rpnaut see the discussion in https://github.com/xarray-contrib/cf-xarray/issues/10 . That discussion focuses more on using the bounds to properly weight points when resampling.

But we could also make .cf.resample generate time bounds and set appropriate attributes on the returned object.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Time bounds returned after an operation with resample-method 332018176
397185013 https://github.com/pydata/xarray/issues/2231#issuecomment-397185013 https://api.github.com/repos/pydata/xarray/issues/2231 MDEyOklzc3VlQ29tbWVudDM5NzE4NTAxMw== shoyer 1217238 2018-06-14T06:24:47Z 2018-06-14T06:24:47Z MEMBER

One thing I’ll note is that you probably want to make the time bounds variables coordinates rather than data variables. But that means the time bounds will probably simply be dropped when you resample.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Time bounds returned after an operation with resample-method 332018176
397167282 https://github.com/pydata/xarray/issues/2231#issuecomment-397167282 https://api.github.com/repos/pydata/xarray/issues/2231 MDEyOklzc3VlQ29tbWVudDM5NzE2NzI4Mg== shoyer 1217238 2018-06-14T04:32:25Z 2018-06-14T04:32:25Z MEMBER

Sorry, xarray doesn’t handle time bounds directly, nor does it update metadata according to cfconventions. These were intentional design choices to keep xarray simple, but in principle you could layer cf convention handling on top of xarray.

For this sort of analysis, using a tool like Iris designed to follow cf conventions might make sense. You can convert directly between iris cubes and xarray DataArray objects.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Time bounds returned after an operation with resample-method 332018176

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]);