issue_comments

Table actions

1 row where issue = 1194993450 and user = 3924836 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • scottyhq · 1 ✖

issue 1

  • Writing GDAL ZARR _CRS attribute not possible · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1098327424 https://github.com/pydata/xarray/issues/6448#issuecomment-1098327424 https://api.github.com/repos/pydata/xarray/issues/6448 IC_kwDOAMm_X85BdyWA scottyhq 3924836 2022-04-13T17:53:21Z 2022-04-13T17:53:21Z MEMBER

One of the main motivations behind the the rioxarray extension is GDAL compatibility. It looks like @snowman2 and @TomAugspurger have discussed saving many geotiffs loaded into xarray as GDAL-compatible Zarr for example https://github.com/corteva/rioxarray/issues/433#issuecomment-967685356.

While it seems that the ultimate solution is agreeing on a format standard, here is another small example using the rioxarray extension where format conversion doesn't currently work as you might expect:

```python

https://github.com/pydata/xarray-data

ds = xr.open_dataset('xarray-data/air_temperature.nc', engine='rasterio')

TooManyDimensions: Only 2D and 3D data arrays supported.

ds.rio.to_raster('test.zarr', driver='ZARR')

Does not error, but output not equivalent to gdal_translate -of ZARR xarray-data/air_temperature.nc gdal_air_temp.zarr

for example, gdalinfo xarray-tutorial-airtemp.zarr gives

Warning 1: Too many samples along the > 2D dimensions of /air.

ds.to_zarr('xarray-tutorial-airtemp.zarr')

```

 
{
    "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

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);