issues: 51863801
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
51863801 | MDU6SXNzdWU1MTg2MzgwMQ== | 293 | Use "coordinate variables"/"data variables" instead of "coordinates"/"variables"? | 1217238 | closed | 0 | 799013 | 0 | 2014-12-12T23:09:30Z | 2015-02-19T19:31:11Z | 2015-02-19T19:31:11Z | MEMBER | Recently, we introduced a distinction between "coordinates" and "variables" (see #197). CF conventions make an analogous distinction between "coordinate variables" and "data variables": http://cfconventions.org/Data/cf-conventions/cf-conventions-1.6/build/cf-conventions.html Would it be less confusing to use the CF terminology? I am leaning toward making this shift, because netCDF already has defined the term "variable", and xray's code still uses that internally. From a practical perspective, this would mean renaming CC @akleeman @toddsmall |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/293/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |