html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/1295#issuecomment-284437032,https://api.github.com/repos/pydata/xarray/issues/1295,284437032,MDEyOklzc3VlQ29tbWVudDI4NDQzNzAzMg==,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}",,211888882
https://github.com/pydata/xarray/issues/1295#issuecomment-284280733,https://api.github.com/repos/pydata/xarray/issues/1295,284280733,MDEyOklzc3VlQ29tbWVudDI4NDI4MDczMw==,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}",,211888882
https://github.com/pydata/xarray/issues/1295#issuecomment-284199623,https://api.github.com/repos/pydata/xarray/issues/1295,284199623,MDEyOklzc3VlQ29tbWVudDI4NDE5OTYyMw==,1197350,2017-03-05T02:11:50Z,2017-03-05T02:12:03Z,MEMBER,"Wherever possible we should try to adhere to [CF convention terminology](http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html#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}",,211888882