issue_comments

Table actions

2 rows where issue = 200364693 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
272308784 https://github.com/pydata/xarray/issues/1201#issuecomment-272308784 https://api.github.com/repos/pydata/xarray/issues/1201 MDEyOklzc3VlQ29tbWVudDI3MjMwODc4NA== shoyer 1217238 2017-01-12T22:48:57Z 2017-01-12T22:48:57Z MEMBER

I don't really understand what you mean here. Neither facetted nor non-facetted plots have any logic to greate geoaxes automatically.

Oops, I was indeed mixed up.

If we add a projection argument for faceted plots, we should certainly add it for non-faceted plots, too.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   pass projection argument to plt.subplot when faceting with cartopy transform 200364693
272233221 https://github.com/pydata/xarray/issues/1201#issuecomment-272233221 https://api.github.com/repos/pydata/xarray/issues/1201 MDEyOklzc3VlQ29tbWVudDI3MjIzMzIyMQ== shoyer 1217238 2017-01-12T17:52:19Z 2017-01-12T17:52:19Z MEMBER

This seems totally reasonable to me, and would be nice because it would improve the consistency between facetted and non-facetted plotting.

Going even further, we might even default to projection=ccrs.PlateCarree() if a cartopy transform is provided (see https://github.com/SciTools/cartopy/issues/645).

@fmaussion @jhamman any opinions?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   pass projection argument to plt.subplot when faceting with cartopy transform 200364693

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