pull_requests: 659675320
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 659675320 | MDExOlB1bGxSZXF1ZXN0NjU5Njc1MzIw | 5427 | closed | 0 | DOC: zarr note on encoding | 17162724 | It took me a while to realize this so I wanted to make a note in the docs for myself in the future and others uses. I was playing with pint-xarray and I couldn't work out why I couldn't round trip a file (https://github.com/xarray-contrib/pint-xarray/issues/109). It turns out the DataArray had an enconding attribute which was being used (and overriding my unit conversion). In addition, I was also scratching my head for a while as to where my zarr store was getting chunks from which didn't correspomd to my numpy array (https://github.com/pydata/xarray/discussions/5407). This PR just makes a note of the importance of encoding attribute of DataArray(s) when writing to a zarr store. docs page change is here: https://xray--5427.org.readthedocs.build/en/5427/generated/xarray.Dataset.to_zarr.html?highlight=zarr#xarray.Dataset.to_zarr | 2021-06-02T03:27:15Z | 2021-06-21T18:14:15Z | 2021-06-21T17:47:47Z | 2021-06-21T17:47:46Z | 6a101a92860bdfb41337d13976f753c656d165c5 | 0 | b7d0a4001160dfa263cf41cc332675d30f34ccd3 | 83eda1a8542a9dbd81bf0e08c8564c044df64c0a | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/5427 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests