issue_comments

Table actions

4 rows where issue = 200593854 and user = 10050469 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

  • fmaussion · 4 ✖

issue 1

  • transfer projection to implied subplots when faceting · 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
272612691 https://github.com/pydata/xarray/pull/1205#issuecomment-272612691 https://api.github.com/repos/pydata/xarray/issues/1205 MDEyOklzc3VlQ29tbWVudDI3MjYxMjY5MQ== fmaussion 10050469 2017-01-14T09:22:48Z 2017-01-14T09:22:48Z MEMBER

I know at least one usage where the projection keyword is needed for something else than cartopy (for polar plots, see example here by @hoonhout), but I don't know how often do people need a transform though.

In the end, I'm still in favor of this change: - I suspect the large majority of the use cases are for cartopy - it's still possible to override the this default behavior by setting the projection kwarg yourself

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   transfer projection to implied subplots when faceting 200593854
272416983 https://github.com/pydata/xarray/pull/1205#issuecomment-272416983 https://api.github.com/repos/pydata/xarray/issues/1205 MDEyOklzc3VlQ29tbWVudDI3MjQxNjk4Mw== fmaussion 10050469 2017-01-13T10:59:53Z 2017-01-13T10:59:53Z MEMBER

As it is, the xarray code becomes tied up with cartopy. If cartopy somehow changes its syntax (e.g. by renaming the transform kw) this code won't work.

cartopy uses transform because this is an interface provided by matlotlib: http://matplotlib.org/users/transforms_tutorial.html . This is not likely to change anytime soon.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   transfer projection to implied subplots when faceting 200593854
272414825 https://github.com/pydata/xarray/pull/1205#issuecomment-272414825 https://api.github.com/repos/pydata/xarray/issues/1205 MDEyOklzc3VlQ29tbWVudDI3MjQxNDgyNQ== fmaussion 10050469 2017-01-13T10:48:49Z 2017-01-13T10:48:49Z MEMBER

In that case, matplotlib will get an unintended projection argument. That is a corner case though.

Yes, I was about to ask @jhamman and @shoyer about their opinion about this. I'm actually not sure if this really is a corner case...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   transfer projection to implied subplots when faceting 200593854
272412800 https://github.com/pydata/xarray/pull/1205#issuecomment-272412800 https://api.github.com/repos/pydata/xarray/issues/1205 MDEyOklzc3VlQ29tbWVudDI3MjQxMjgwMA== fmaussion 10050469 2017-01-13T10:37:57Z 2017-01-13T10:37:57Z MEMBER

Thanks! I think we need to document this somewhere, and also some tests would be nice.

Do you feel like trying to add the same functionality to normal 2d plots also? (this will represent a little more work so if you don't have time no big deal).

Also, you should credit yourself in the "what's new" section of whats-new.rst

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   transfer projection to implied subplots when faceting 200593854

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