issue_comments: 370913422
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/1970#issuecomment-370913422 | https://api.github.com/repos/pydata/xarray/issues/1970 | 370913422 | MDEyOklzc3VlQ29tbWVudDM3MDkxMzQyMg== | 1197350 | 2018-03-06T20:16:14Z | 2018-03-06T20:16:14Z | MEMBER | What is the role of the netCDF API in the backend API? My understanding of the point of h5netcdf was to provide a netCDF-like interface for HDF5, thereby making it easier to interface with xarray. So one potential answer to the backend API question is simply: make a netCDF-like interface for your library and then xarray can use it. However we still need a separate h5netcdf backend within xarray, so this design is perhaps not as clean as we would like. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
302806158 |