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/712#issuecomment-723241066,https://api.github.com/repos/pydata/xarray/issues/712,723241066,MDEyOklzc3VlQ29tbWVudDcyMzI0MTA2Ng==,14808389,2020-11-06T18:47:35Z,2020-11-06T18:48:54Z,MEMBER,"true, it seems I didn't read this issue carefully enough","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,125708367
https://github.com/pydata/xarray/issues/712#issuecomment-723239452,https://api.github.com/repos/pydata/xarray/issues/712,723239452,MDEyOklzc3VlQ29tbWVudDcyMzIzOTQ1Mg==,2448579,2020-11-06T18:44:07Z,2020-11-06T18:44:07Z,MEMBER,"#4515 is consistent with this comment up above:
> display coordinates corresponding to dimensions first in lists of coordinates, and to always display them in the same order as dimensions.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,125708367
https://github.com/pydata/xarray/issues/712#issuecomment-723193550,https://api.github.com/repos/pydata/xarray/issues/712,723193550,MDEyOklzc3VlQ29tbWVudDcyMzE5MzU1MA==,14808389,2020-11-06T17:07:55Z,2020-11-06T17:07:55Z,MEMBER,"what should we do about this? We did touch the subject in #4409, but decided to keep the order the coordinates were passed in rather than sorting by dimension (or alphabetically). I think there's a lot of confusion about the difference between the dimensions in the summary line of `DataArray` objects and the order in the coordinates section.
A fix for #4515 might make sorting by dimension order much more important.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,125708367
https://github.com/pydata/xarray/issues/712#issuecomment-458305117,https://api.github.com/repos/pydata/xarray/issues/712,458305117,MDEyOklzc3VlQ29tbWVudDQ1ODMwNTExNw==,2443309,2019-01-28T21:18:13Z,2019-01-28T21:18:13Z,MEMBER,@anntzer - would you be interested in working on this? ,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,125708367
https://github.com/pydata/xarray/issues/712#issuecomment-211418692,https://api.github.com/repos/pydata/xarray/issues/712,211418692,MDEyOklzc3VlQ29tbWVudDIxMTQxODY5Mg==,1217238,2016-04-18T15:04:30Z,2016-04-18T15:04:30Z,MEMBER,"OK, I didn't read your first post carefully last time. Your complaint was about the order of coordinates in `ds.d1` and `ds.d2`, not the original DataArrays. So this is a more subtle issue than I thought.
We _could_ add some sort of ad-hoc adjustment to the order in which we display coordinates, but I'm reluctant because it's not obvious to me what that ""correct"" order would be. For example, that you can directly supply the `coords` argument as a mapping with any arbitrary order to construct a DataArray.
I suppose once principled choice would always be to display coordinates corresponding to dimensions first in lists of coordinates, and to always display them in the same order as dimensions. If we do this, it should be consistent between both DataArray and Dataset.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,125708367
https://github.com/pydata/xarray/issues/712#issuecomment-174843391,https://api.github.com/repos/pydata/xarray/issues/712,174843391,MDEyOklzc3VlQ29tbWVudDE3NDg0MzM5MQ==,1217238,2016-01-26T05:41:28Z,2016-01-26T05:41:28Z,MEMBER,"This should be fixed in v0.7.0... please reopen if it resurfaces.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,125708367
https://github.com/pydata/xarray/issues/712#issuecomment-170155759,https://api.github.com/repos/pydata/xarray/issues/712,170155759,MDEyOklzc3VlQ29tbWVudDE3MDE1NTc1OQ==,1217238,2016-01-08T23:28:44Z,2016-01-08T23:28:44Z,MEMBER,"yes, in the next week, hopefully.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,125708367
https://github.com/pydata/xarray/issues/712#issuecomment-170149315,https://api.github.com/repos/pydata/xarray/issues/712,170149315,MDEyOklzc3VlQ29tbWVudDE3MDE0OTMxNQ==,1217238,2016-01-08T22:49:37Z,2016-01-08T22:50:03Z,MEMBER,"I think this may have been fixed by the recent rewrite of DataArray internals. On master, I have:
```
In [2]: d1
Out[2]:
array([[ 0.00000000e+000, 0.00000000e+000],
[ 2.15725662e-314, 2.15893204e-314]])
Coordinates:
* foo (foo) int64 0 1
* bar (bar) int64 0 1
In [3]: d2
Out[3]:
array([[ 0.00000000e+000, 0.00000000e+000],
[ 2.15906985e-314, 2.14458868e-314]])
Coordinates:
* bar (bar) int64 0 1
* foo (foo) int64 0 1
```
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,125708367