issue_comments
3 rows where author_association = "NONE", issue = 225846258 and user = 4992424 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Changing projections under plot() · 3 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 299194997 | https://github.com/pydata/xarray/issues/1397#issuecomment-299194997 | https://api.github.com/repos/pydata/xarray/issues/1397 | MDEyOklzc3VlQ29tbWVudDI5OTE5NDk5Nw== | darothen 4992424 | 2017-05-04T14:05:48Z | 2017-05-04T14:05:48Z | NONE | Cool; please keep me in the loop if you don't mind, because I also have an application which I'd really like to just be able use the built-in faceting for rather than building my plot grids manually. A good comparison case is to perform the same plots (with the same set aspect/size/ratio at both the figure and subplot level) but just don't use the Cartopy transformations. In these cases, I have all the control that I would expect. There are also important differences between |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Changing projections under plot() 225846258 | |
| 299191499 | https://github.com/pydata/xarray/issues/1397#issuecomment-299191499 | https://api.github.com/repos/pydata/xarray/issues/1397 | MDEyOklzc3VlQ29tbWVudDI5OTE5MTQ5OQ== | darothen 4992424 | 2017-05-04T13:53:09Z | 2017-05-04T13:53:09Z | NONE | @fmaussion What happens if you add I'm tempted to have us move this discussion to StackOverflow (for heightened visibility), but I suspect there might actually be a bug somewhere in the finalization of the faceting that undoes the specifications you pass to the initial subplot constructor. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Changing projections under plot() 225846258 | |
| 299056235 | https://github.com/pydata/xarray/issues/1397#issuecomment-299056235 | https://api.github.com/repos/pydata/xarray/issues/1397 | MDEyOklzc3VlQ29tbWVudDI5OTA1NjIzNQ== | darothen 4992424 | 2017-05-03T22:43:55Z | 2017-05-03T22:43:55Z | NONE |
You just need to pass the "pad" argument to The trickier problem is that sometimes cartopy can be a bit unpredictable in controlling the size and aspect ratio of axes after you've plotted maps on them. You can force a plot to respect the aspect ratio you use when you construct an axis by using the keyword |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Changing projections under plot() 225846258 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1