issue_comments: 790851791
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/4987#issuecomment-790851791 | https://api.github.com/repos/pydata/xarray/issues/4987 | 790851791 | MDEyOklzc3VlQ29tbWVudDc5MDg1MTc5MQ== | 24235303 | 2021-03-04T19:00:38Z | 2021-03-04T19:00:38Z | CONTRIBUTOR | @alexamici @shoyer To be clear, my short term plan is absolutely to move the TileDB backend from my draft pull request here to a small plugin in library (thanks for linking the cfgrib @alexamici!). I only bring up the protocol thing because the backend is really close to a place where a lot of the boilerplate for the lazy loading, etc. could be provided on the xarray side with a simple API requirement on the third-party library side. I'll push up a small proof-of-concept with a read-only netCDF4 example shortly. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
820480606 |