issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 404088563 and user = 10050469 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

  • fmaussion · 2 ✖

issue 1

  • Implementation of CRS storage in rasterio with PROJ.4 & WKT · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
582972581 https://github.com/pydata/xarray/issues/2723#issuecomment-582972581 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDU4Mjk3MjU4MQ== fmaussion 10050469 2020-02-06T15:56:33Z 2020-02-06T15:56:33Z MEMBER

I think we should seriously consider removing all rasterio logic in xarray and make rioxarray an optional dependency to read geotiff files with xarray.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
460396203 https://github.com/pydata/xarray/issues/2723#issuecomment-460396203 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDQ2MDM5NjIwMw== fmaussion 10050469 2019-02-04T20:15:36Z 2019-02-04T20:15:36Z MEMBER

Sorry for being late on this one. Yes, I agree that the "coordinate attribute" is worth a try.

To avoid redundancy in the name one could name the coord variable attributes simply wkt and proj4, like:

<xarray.DataArray 'crs' ()> array(0) Coordinates: crs int64 0 Attributes: wkt: PROJCS["UTM Zone 15, Northern Hemisphere",GEOGCS["WGS 84",D... proj4: +proj=...

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563

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