issue_comments

Table actions

3 rows where issue = 211888882 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1

  • shoyer · 3 ✖

issue 1

  • Terminology for the various coordinates · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
284468168 https://github.com/pydata/xarray/issues/1295#issuecomment-284468168 https://api.github.com/repos/pydata/xarray/issues/1295 MDEyOklzc3VlQ29tbWVudDI4NDQ2ODE2OA== shoyer 1217238 2017-03-06T17:25:59Z 2017-03-06T17:25:59Z MEMBER

I agree that "auxiliary coordinate" is a better name, but I think "non-dimension coordinate" is clearer for the rare cases where we want to refer to these coordinates, given that we don't have any name for these coordinates in the xarray data model itself.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Terminology for the various coordinates 211888882
284273455 https://github.com/pydata/xarray/issues/1295#issuecomment-284273455 https://api.github.com/repos/pydata/xarray/issues/1295 MDEyOklzc3VlQ29tbWVudDI4NDI3MzQ1NQ== shoyer 1217238 2017-03-05T23:40:57Z 2017-03-05T23:40:57Z MEMBER

I think it's confusing to use "coordinate" to refer to only variables matching dimension names and that "auxiliary coordinates" are not a type of coordinate. It just doesn't make any sense in terms of the usual rules for categorizing things. This is especially problematic for software like xarray which people use without looking carefully at the docs, and for which many users aren't familiar with CF conventions.

So I feel pretty strongly that CF/NUG conventions get this one wrong, and for xarray we should say that anything in .coords is a coordinate variable, which we can further qualify in various ways.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Terminology for the various coordinates 211888882
284198109 https://github.com/pydata/xarray/issues/1295#issuecomment-284198109 https://api.github.com/repos/pydata/xarray/issues/1295 MDEyOklzc3VlQ29tbWVudDI4NDE5ODEwOQ== shoyer 1217238 2017-03-05T01:32:51Z 2017-03-05T01:32:51Z MEMBER

Should we simply call the former dimension coordinates and the latter optional coordinates?

Yes, let's call them "dimension coordinates".

The later could be called "non-dimension coordinates", but even dimension coordinates are optional so we shouldn't call these "optional".

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Terminology for the various coordinates 211888882

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