issue_comments

Table actions

1 row where issue = 991857313 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 · 1 ✖

issue 1

  • rio.crs seems to misbehave with geopandas.to_crs · 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
915810862 https://github.com/pydata/xarray/issues/5782#issuecomment-915810862 https://api.github.com/repos/pydata/xarray/issues/5782 IC_kwDOAMm_X842liou jhamman 2443309 2021-09-09T06:47:46Z 2021-09-09T06:47:46Z MEMBER

Hi @dimzog. Thank you for taking time to report this issue. However, it seems to me that this would be better reported on the geopandas and/or rioxarray issue tracker. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   rio.crs seems to misbehave with geopandas.to_crs 991857313

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