issue_comments: 473364973
This data as json
| 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/2811#issuecomment-473364973 | https://api.github.com/repos/pydata/xarray/issues/2811 | 473364973 | MDEyOklzc3VlQ29tbWVudDQ3MzM2NDk3Mw== | 5821660 | 2019-03-15T16:59:38Z | 2019-03-15T16:59:38Z | MEMBER | @shoyer Yes, that was what I was assuming. But was a bit confused too, as the concat docs say, that dimension order is not affected. But maybe I get this wrong and the order of dimensions is not affected only for DataArrays. IIUC xarray creates a new dataset during concat, because the dimensions cannot be expanded (due to netCDF4 limitations). So I would need to look at that specific part, where this creation process takes place. I would also not speak of "bug" here, but if such reordering happens only in certain conditions users (I mean at least me) can get confused. I'll try to find out under what conditions this happens and try to come up with some workaround. Will also try ti find my way through the concat-mechanism. Again, I really appreciate your help in this issue. I can rename the issue to a somewhat better name, do you have a suggestion? Ambiguous dimension reorder in Dataset concat maybe? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
420930870 |