issues: 264049503
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 264049503 | MDU6SXNzdWUyNjQwNDk1MDM= | 1614 | Rules for propagating attrs and encoding | 2443309 | open | 0 | 15 | 2017-10-09T22:56:02Z | 2020-04-05T19:12:10Z | MEMBER | We need to come up with some clear rules for when and how xarray should propagate metadata (attrs/encoding). This has come up routinely (e.g. #25, #138, #442, #688, #828, #988, #1009, #1271, #1297, #1586) and we don't have a clear direction as to when to keep/drop metadata. I'll take a first cut: | operation | attrs | encoding | status | |------------ |------------ |------------ |------------ | | reduce | drop | drop | | | arithmetic | drop | drop | implemented | | copy | keep | keep | | | concat | keep first | keep first | implemented | | slice | keep | drop | | | where | keep | keep | | cc @shoyer (following up on https://github.com/pydata/xarray/issues/1586#issuecomment-334954046) |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/1614/reactions",
"total_count": 3,
"+1": 3,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | issue |