issue_comments: 220884502
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/pull/849#issuecomment-220884502 | https://api.github.com/repos/pydata/xarray/issues/849 | 220884502 | MDEyOklzc3VlQ29tbWVudDIyMDg4NDUwMg== | 1217238 | 2016-05-23T04:19:31Z | 2016-05-23T04:19:31Z | MEMBER | I think it's fine to write all booleans data using this encoding. It's pretty obvious how it works, and it's compatible with all versions of netCDf. Unfortunately, netCDF-C libraries can't read variables with the enum dtype created by h5py for boolean data (https://github.com/Unidata/netcdf-c/issues/267), so I don't think we should encourage that option. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
155181260 |