issue_comments

Table actions

3 rows where author_association = "NONE" and issue = 1583216781 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • contiguous time axis · 3 ✖

author_association 1

  • NONE · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1449348940 https://github.com/pydata/xarray/issues/7525#issuecomment-1449348940 https://api.github.com/repos/pydata/xarray/issues/7525 IC_kwDOAMm_X85WY09M danhamill 11522898 2023-03-01T04:59:58Z 2023-03-01T04:59:58Z NONE

Hey!

Thanks for the thoughts. Took me a wile to realize the edge array and the time coordinates aren't the same thing. The time coordinates are really labels and the edge array is calculated from it.

Not sure I agree with the default calculation as the mid point of the time coordinate labels, but I think that is a battle I won't take up.

+1 for supporting this kind of coordinate attribute in xarray. Based on the other issues linked here, it seems it still has not been implemented? 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   contiguous time axis  1583216781
1448491096 https://github.com/pydata/xarray/issues/7525#issuecomment-1448491096 https://api.github.com/repos/pydata/xarray/issues/7525 IC_kwDOAMm_X85WVjhY ethanrd 673250 2023-02-28T16:34:36Z 2023-02-28T16:34:36Z NONE

So, I believe the results you are seeing above are the expected results with the edge value half way between neighboring coordinate values.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   contiguous time axis  1583216781
1448488762 https://github.com/pydata/xarray/issues/7525#issuecomment-1448488762 https://api.github.com/repos/pydata/xarray/issues/7525 IC_kwDOAMm_X85WVi86 ethanrd 673250 2023-02-28T16:32:58Z 2023-02-28T16:32:58Z NONE

If cell bounds/edges are not provided with a coordinate variable, the coordinate values are assumed to represent the center points of a set of contiguous cells. In this default case, the cell edges can be represented as an (n+1) sized array with all but the first and last values shared between neighboring cells. In the non-contiguous case, the bounds/edges must be represented as an (n,2) sized array.

Looks like there's already an xarray issue (#1475 ) on handling cell bounds.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   contiguous time axis  1583216781

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