home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where author_association = "MEMBER", issue = 258913450 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

  • Projection issue with plot.imshow and cartopy projection · 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
330673880 https://github.com/pydata/xarray/issues/1581#issuecomment-330673880 https://api.github.com/repos/pydata/xarray/issues/1581 MDEyOklzc3VlQ29tbWVudDMzMDY3Mzg4MA== fmaussion 10050469 2017-09-19T21:07:32Z 2017-09-19T21:07:32Z MEMBER

Regarding your comment about the doc: maybe it would be useful to specify somewhere that imshow will work only for regularly spaced data indeed.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Projection issue with plot.imshow and cartopy projection 258913450
330673189 https://github.com/pydata/xarray/issues/1581#issuecomment-330673189 https://api.github.com/repos/pydata/xarray/issues/1581 MDEyOklzc3VlQ29tbWVudDMzMDY3MzE4OQ== fmaussion 10050469 2017-09-19T21:04:42Z 2017-09-19T21:04:42Z MEMBER

Thanks for the detailed and well documented question. I had a look at your data, and there are two issues that imshow cannot handle well: - your data isn't well centred (lons go from -300 to 60, which explains the shape of your image on the globe). This wouldn't be a big deal if it wasn't for the other problem, which is: - your latitude data isn't regular.

python plt.plot(ds.lath[1:].values - ds.lath[:-1].values) Gives:

which is quite... interesting.

Anyways, imshow is so much faster because it needs regular, nicely sorted data. In your case I don't think there is much other choice than pcolormesh or contourf... Note also that plotting on Robinson is slower than plotting on a plate carree projection.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Projection issue with plot.imshow and cartopy projection 258913450

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]);
Powered by Datasette · Queries took 51.847ms · About: xarray-datasette