issue_comments: 50978946
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/197#issuecomment-50978946 | https://api.github.com/repos/pydata/xarray/issues/197 | 50978946 | MDEyOklzc3VlQ29tbWVudDUwOTc4OTQ2 | 1217238 | 2014-08-03T00:49:47Z | 2014-08-03T00:49:47Z | MEMBER | Some further thinking suggests that we can allow for multi-dimensional coordinates, but the only sane way to handle conflicting non-index coordinates is to drop them. Even Iris, with its strict interpretation of CF conventions, takes this approach. Raising an exception for conflicting non-scalar variables would make multi-dimensional coordinates impractical. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
39264845 |