issue_comments: 400415380
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/issues/2251#issuecomment-400415380 | https://api.github.com/repos/pydata/xarray/issues/2251 | 400415380 | MDEyOklzc3VlQ29tbWVudDQwMDQxNTM4MA== | 90008 | 2018-06-26T18:24:35Z | 2018-06-26T18:24:35Z | CONTRIBUTOR | @fmaussion, I am in fact now storing them as coordinates as a work around. in fact, for my particular application, I think the array was meant more as the time the particular index was taken at, in which case a coordinate seems perfect, that said, I am mutating the coordinate array through data acquisition. I think an acceptable solution would be to state this limitation in the description of what attributes are. in learning how to use xarray, I ran into the fact that boolean variables cannot be stored in netcdf4, and the array limitation reported. I worked around the boolean problem by replacing it with a more descriptive (and ultimately more forward compatible) string. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
335608017 |