issues: 614814400
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 614814400 | MDExOlB1bGxSZXF1ZXN0NDE1MjkyMzM3 | 4047 | Document Xarray zarr encoding conventions | 1197350 | closed | 0 | 3 | 2020-05-08T15:29:14Z | 2020-05-22T21:59:09Z | 2020-05-20T17:04:02Z | MEMBER | 0 | pydata/xarray/pulls/4047 | When we implemented the Zarr backend, we made some ad hoc choices about how to encode NetCDF data in Zarr. At this stage, it would be useful to explicitly document this encoding. I decided to put it on the "Xarray Internals" page, but I'm open to moving if folks feel it fits better elsewhere. cc @jeffdlb, @WardF, @DennisHeimbigner |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/4047/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |