issues: 1830038411
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1830038411 | PR_kwDOAMm_X85W2FcN | 8034 | sort when encoding coordinates for deterministic outputs | 3383837 | closed | 0 | 0 | 2023-07-31T21:16:31Z | 2023-08-03T16:27:28Z | 2023-08-03T16:27:27Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/8034 |
The PR changes The PR adds a test, but also changes two pre-existing tests that allowed for non-deterministic ordering of the coordinates string. In reviewing the netCDF data model and CF convenstions, I confirmed that there is no requirement on the ordering of names in the coordinates attribute. I also learned that the global coordinates attribute created by XArray for non-dimension coordinates that are not associated with a variable is not compliant with CF conventions, as was discussed in 2014. In 2021, CF-Conventions 1.9 added "Domain Variables", which appear to provide a CF compliant way to handle this situation. I will likely open an enhancement issue to weigh making that change. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/8034/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |