issue_comments

Table actions

2 rows where issue = 446722089 and user = 1828519 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

  • djhoese · 2 ✖

issue 1

  • Confusing handling of NetCDF coordinates · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
494597663 https://github.com/pydata/xarray/issues/2976#issuecomment-494597663 https://api.github.com/repos/pydata/xarray/issues/2976 MDEyOklzc3VlQ29tbWVudDQ5NDU5NzY2Mw== djhoese 1828519 2019-05-21T23:36:21Z 2019-05-21T23:36:21Z CONTRIBUTOR

Rad doesn't include the "band_id" coordinate because "band_id" includes a "band" dimension, which isn't found on the Rad variable.

Ah, that's what I was looking for! Ok, that makes sense. To be as generic as possible xarray is using the dimensions to determine if a coordinate "belongs" to a variable rather than the "coordinates" attribute of that variable. I can live with that. Thanks for the explanation and the link to that part of the code.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Confusing handling of NetCDF coordinates 446722089
494589615 https://github.com/pydata/xarray/issues/2976#issuecomment-494589615 https://api.github.com/repos/pydata/xarray/issues/2976 MDEyOklzc3VlQ29tbWVudDQ5NDU4OTYxNQ== djhoese 1828519 2019-05-21T22:59:24Z 2019-05-21T22:59:24Z CONTRIBUTOR

Ok, but then why are coordinates that exist in the Dataset and in the netcdf variable's 'coordinates' attribute not listed in the DataArray for that variable?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Confusing handling of NetCDF coordinates 446722089

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