issue_comments

Table actions

4 rows where author_association = "CONTRIBUTOR" and issue = 1194993450 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

issue 1

  • Writing GDAL ZARR _CRS attribute not possible · 4 ✖

author_association 1

  • CONTRIBUTOR · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1098400102 https://github.com/pydata/xarray/issues/6448#issuecomment-1098400102 https://api.github.com/repos/pydata/xarray/issues/6448 IC_kwDOAMm_X85BeEFm snowman2 8699967 2022-04-13T19:21:59Z 2022-04-13T19:21:59Z CONTRIBUTOR

GDAL doesn't actually need the CRS stored with the _CRS convention as documented in their ZARR driver specification?

GDAL may need to update the ZARR driver. The NetCDF driver does support CF. It would be good for them to be consistent.

 
{
    "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
1098342334 https://github.com/pydata/xarray/issues/6448#issuecomment-1098342334 https://api.github.com/repos/pydata/xarray/issues/6448 IC_kwDOAMm_X85Bd1-- snowman2 8699967 2022-04-13T18:11:21Z 2022-04-13T18:11:21Z CONTRIBUTOR

Top reasons for using CF over a CRS attribute:

  • Supported by geospatial & netCDF software (GDAL/Esri/Unidata)
  • Attributes are easily lost ref
  • Encourage more usage of standard mechanisms of CRS storage
 
{
    "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
1098333054 https://github.com/pydata/xarray/issues/6448#issuecomment-1098333054 https://api.github.com/repos/pydata/xarray/issues/6448 IC_kwDOAMm_X85Bdzt- snowman2 8699967 2022-04-13T18:00:12Z 2022-04-13T18:00:12Z CONTRIBUTOR

This document is also a useful reference for storing CRS in xarray: https://corteva.github.io/rioxarray/stable/getting_started/crs_management.html

 
{
    "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
1098331427 https://github.com/pydata/xarray/issues/6448#issuecomment-1098331427 https://api.github.com/repos/pydata/xarray/issues/6448 IC_kwDOAMm_X85BdzUj snowman2 8699967 2022-04-13T17:58:19Z 2022-04-13T17:58:19Z CONTRIBUTOR

Instead, it recommends to use CF conventions for encoding CRS. This is more compatible with NetCDF, but won't be parsed correctly by GDAL.

GDAL does support the CF conventions for storing the CRS.

https://gdal.org/drivers/raster/netcdf.html#georeference

"The driver first tries to follow the CF-1 Convention from UNIDATA looking for the Metadata named “grid_mapping”."

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