issue_comments: 306832308
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/1444#issuecomment-306832308 | https://api.github.com/repos/pydata/xarray/issues/1444 | 306832308 | MDEyOklzc3VlQ29tbWVudDMwNjgzMjMwOA== | 221526 | 2017-06-07T15:32:03Z | 2017-06-07T15:32:03Z | CONTRIBUTOR | HDF5 doesn't come without its own draw backs...such as vastly more complicated (and admittedly more capable) on-disk format. We should not presume to know better than the data providers what their trade-offs are. Also, while unsigned types are a feature of the netCDF4/HDF5, strictly speaking, the netCDF4 unsigned types are not compatible with any released version of the CF specification (see list of acceptable data types here: http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html#_data_types). So it's not exactly as simple as you'd like it to be. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
233992696 |