pull_requests: 25319567
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 25319567 | MDExOlB1bGxSZXF1ZXN0MjUzMTk1Njc= | 282 | closed | 0 | Serialize non-index coordinates to netCDF files | 1217238 | Fixes #231 This PR ensures non-index coordinates can be roundtripped to netCDF and back by using the CF convention of the 'coordinates' attribute on a "data variable". In cases where there are no data variables available, we fall back to the (extended, non-CF) convention of saving 'coordinates' as a global attribute. I also added the `xray.decode_cf` function to the API. This function can decode either datasets or datastores into decoded datasets, which is handy, for example, if a dataset is serialized according to CF conventions but already in memory (e.g., saved in JSON). @akleeman: I could use some guidance from you on want to do about `test_roundtrip_coordinates` on `TestCFEncodedDataStore`. I am tentatively skipping it, but it would be nice to get it working. To do so will require some tweaks to the API for the `Datastore.load` method. | 2014-12-02T05:11:23Z | 2014-12-07T02:44:14Z | 2014-12-07T02:44:11Z | 2014-12-07T02:44:11Z | 8b25628a5cad01444dc957c44399bcbcc577af18 | 836999 | 0 | e1000d680cc9fee011ec0eff29b3ae2f9017d7f9 | a5837164f80a4bffcfda52a3edcc4f40c947d336 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/282 |
Links from other tables
- 3 rows from pull_requests_id in labels_pull_requests