issue_comments

Table actions

3 rows where issue = 211888882 and user = 1197350 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

  • rabernat · 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
284437032 https://github.com/pydata/xarray/issues/1295#issuecomment-284437032 https://api.github.com/repos/pydata/xarray/issues/1295 MDEyOklzc3VlQ29tbWVudDI4NDQzNzAzMg== rabernat 1197350 2017-03-06T15:51:55Z 2017-03-06T15:51:55Z MEMBER

I personally like "auxiliary coordinate" for the second type. This makes it clear that the variable gives additional information that is not as fundamental as the "dimension coordinate". 

{
    "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
284280733 https://github.com/pydata/xarray/issues/1295#issuecomment-284280733 https://api.github.com/repos/pydata/xarray/issues/1295 MDEyOklzc3VlQ29tbWVudDI4NDI4MDczMw== rabernat 1197350 2017-03-06T01:20:08Z 2017-03-06T01:20:08Z MEMBER

I don't feel very strongly about this...just pointing out that CF conventions do define terminology relevant to this discussion.

I'm fine with departing from CF convention terminology where we think it is unnecessarily confusing. But we should try to explain how and why we depart in the docs. @shoyer's comment above would in fact be a useful addition to the docs.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Terminology for the various coordinates 211888882
284199623 https://github.com/pydata/xarray/issues/1295#issuecomment-284199623 https://api.github.com/repos/pydata/xarray/issues/1295 MDEyOklzc3VlQ29tbWVudDI4NDE5OTYyMw== rabernat 1197350 2017-03-05T02:11:50Z 2017-03-05T02:12:03Z MEMBER

Wherever possible we should try to adhere to CF convention terminology.

Some relevant definitions are:

coordinate variable We use this term precisely as it is defined in section 2.3.1 of the NUG . It is a one-dimensional variable with the same name as its dimension [e.g., time(time) ], and it is defined as a numeric data type with values that are ordered monotonically. Missing values are not allowed in coordinate variables.

auxiliary coordinate variable Any netCDF variable that contains coordinate data, but is not a coordinate variable (in the sense of that term defined by the NUG and used by this standard - see below). Unlike coordinate variables, there is no relationship between the name of an auxiliary coordinate variable and the name(s) of its dimension(s).

multidimensional coordinate variable An auxiliary coordinate variable that is multidimensional.

Using these definitions, it seems that @shoyer's "dimension coordinate" == CF's "coordinate variable" and @shoyer's "non-dimension coordinate" == CF's "auxiliary coordinate variable"

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