issues: 352677925
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 352677925 | MDExOlB1bGxSZXF1ZXN0MjA5OTMxMjYz | 2375 | Make `dim` optional on unstack | 4806877 | closed | 0 | 13 | 2018-08-21T19:29:06Z | 2018-09-05T16:01:23Z | 2018-09-05T15:19:07Z | CONTRIBUTOR | 0 | pydata/xarray/pulls/2375 |
Not sure if this is a desirable change but I thought it could be easily discussed as a PR. Just for context I was looking at flattening spatial data for machine learning pipelines and then reshaping after the output had been acquired. I have a NxM array called
Then I use that flat_input in my ML pipeline and get back an
This PR just makes the
As a follow on PR I was thinking of making a function called 1) Would something like Here is a gist of the workflow using a tweaked datashader example and datashader example data https://gist.github.com/jsignell/79a6cf2da5c1458211d9dcf34d4417df |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2375/reactions",
"total_count": 4,
"+1": 4,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |