issue_comments
2 rows where user = 15717873 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
user 1
- wankoelias · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1098371121 | https://github.com/pydata/xarray/issues/6448#issuecomment-1098371121 | https://api.github.com/repos/pydata/xarray/issues/6448 | IC_kwDOAMm_X85Bd9Ax | wankoelias 15717873 | 2022-04-13T18:45:23Z | 2022-04-13T18:45:23Z | NONE | so just to make it clear... GDAL doesn't actually need the CRS stored with the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Writing GDAL ZARR _CRS attribute not possible 1194993450 | |
1090132193 | https://github.com/pydata/xarray/issues/6374#issuecomment-1090132193 | https://api.github.com/repos/pydata/xarray/issues/6374 | IC_kwDOAMm_X85A-hjh | wankoelias 15717873 | 2022-04-06T10:54:19Z | 2022-04-06T10:54:51Z | NONE | As it is currently it is also not possible to write a zarr which follows the GDAL ZARR driver conventions. Writing the
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Should the zarr backend support NCZarr conventions? 1172229856 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
issue 2