issue_comments

Table actions

4 rows where issue = 403458737 and user = 1828519 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

  • djhoese · 4 ✖

issue 1

  • Fix CRS being WKT instead of PROJ.4 · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
472102830 https://github.com/pydata/xarray/pull/2715#issuecomment-472102830 https://api.github.com/repos/pydata/xarray/issues/2715 MDEyOklzc3VlQ29tbWVudDQ3MjEwMjgzMA== djhoese 1828519 2019-03-12T17:31:50Z 2019-03-12T17:31:50Z CONTRIBUTOR

@shoyer Any idea when a 0.11.4 or 0.12 will be released? I'm trying to work around some other rasterio bugs and would like to remove the restriction on the rasterio version used in my CI tests, but that requires this PR.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix CRS being WKT instead of PROJ.4 403458737
461097743 https://github.com/pydata/xarray/pull/2715#issuecomment-461097743 https://api.github.com/repos/pydata/xarray/issues/2715 MDEyOklzc3VlQ29tbWVudDQ2MTA5Nzc0Mw== djhoese 1828519 2019-02-06T16:52:06Z 2019-02-06T16:52:06Z CONTRIBUTOR

@shoyer Added something to the whats-new. Let me know if anything needs changing.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix CRS being WKT instead of PROJ.4 403458737
461084264 https://github.com/pydata/xarray/pull/2715#issuecomment-461084264 https://api.github.com/repos/pydata/xarray/issues/2715 MDEyOklzc3VlQ29tbWVudDQ2MTA4NDI2NA== djhoese 1828519 2019-02-06T16:17:41Z 2019-02-06T16:17:41Z CONTRIBUTOR

@dcherian @shoyer This PR isn't changing any functionality. It is making the same functionality available with newer versions of rasterio.

There are discussions going on regarding changing the behavior: https://github.com/pydata/xarray/issues/2723

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix CRS being WKT instead of PROJ.4 403458737
458260485 https://github.com/pydata/xarray/pull/2715#issuecomment-458260485 https://api.github.com/repos/pydata/xarray/issues/2715 MDEyOklzc3VlQ29tbWVudDQ1ODI2MDQ4NQ== djhoese 1828519 2019-01-28T19:07:24Z 2019-01-28T19:07:24Z CONTRIBUTOR

@fmaussion Done. And I merged @snowman2's suggestion and fixed the indent (I'm guessing github's editor made it difficult to see but it was off by one indentation).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix CRS being WKT instead of PROJ.4 403458737

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