issues: 909046909
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 909046909 | MDExOlB1bGxSZXF1ZXN0NjU5Njc1MzIw | 5427 | DOC: zarr note on encoding | 17162724 | closed | 0 | 4 | 2021-06-02T03:27:15Z | 2021-06-21T18:14:15Z | 2021-06-21T17:47:47Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/5427 | 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 |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/5427/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |