issue_comments

Table actions

2 rows where issue = 259057144 and user = 2443309 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

  • jhamman · 2 ✖

issue 1

  • Rasterio tags are not accessible through open_rasterio · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
330909334 https://github.com/pydata/xarray/issues/1582#issuecomment-330909334 https://api.github.com/repos/pydata/xarray/issues/1582 MDEyOklzc3VlQ29tbWVudDMzMDkwOTMzNA== jhamman 2443309 2017-09-20T16:36:11Z 2018-03-16T18:48:46Z MEMBER

I don't know what kind of data tags() might contain in general.

I'm not opposed to decoding the values that are in tags as part of the rasterio backend. @maaleske, perhaps you can do some research to let us know what types of values the tags method is going to return.

@fmaussion - I'm not entirely opposed to this. It may require a bit of effort to make sure modifying the file object as part of the public API doesn't do nasty things.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Rasterio tags are not accessible through open_rasterio 259057144
331010431 https://github.com/pydata/xarray/issues/1582#issuecomment-331010431 https://api.github.com/repos/pydata/xarray/issues/1582 MDEyOklzc3VlQ29tbWVudDMzMTAxMDQzMQ== jhamman 2443309 2017-09-20T23:39:15Z 2017-09-20T23:39:15Z MEMBER

This is still a bit confusing. Maybe we should open a discussion/issue with the rasterio team. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Rasterio tags are not accessible through open_rasterio 259057144

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