issue_comments
5 rows where author_association = "NONE" and issue = 327725925 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- HoloViews based plotting API · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
401603966 | https://github.com/pydata/xarray/issues/2199#issuecomment-401603966 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDQwMTYwMzk2Ng== | philippjfr 1550771 | 2018-07-01T12:35:56Z | 2018-07-01T12:35:56Z | NONE | Thanks for everyone's feedback, due to trademark concerns we decided to rename both the library and the API to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HoloViews based plotting API 327725925 | |
394179490 | https://github.com/pydata/xarray/issues/2199#issuecomment-394179490 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDM5NDE3OTQ5MA== | philippjfr 1550771 | 2018-06-03T17:56:40Z | 2018-06-03T17:56:40Z | NONE | Thanks again for the feedback, I've decided to go with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HoloViews based plotting API 327725925 | |
393309581 | https://github.com/pydata/xarray/issues/2199#issuecomment-393309581 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDM5MzMwOTU4MQ== | philippjfr 1550771 | 2018-05-30T20:34:39Z | 2018-05-30T20:37:24Z | NONE |
Actually I suppose that's not what it would be, it could be |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HoloViews based plotting API 327725925 | |
393300042 | https://github.com/pydata/xarray/issues/2199#issuecomment-393300042 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDM5MzMwMDA0Mg== | philippjfr 1550771 | 2018-05-30T20:06:29Z | 2018-05-30T20:16:45Z | NONE |
Okay thanks, given xarray's preference for accessor names to match projects I'm now leaning toward
HoloPlot explicitly does not deal with
That should happen automatically.
You can facet in a number of ways:
will produce three subplots which are linked on the x- and y-axis, i.e. zooming on one will zoom on all unless you set
This is also already supported, the API here is:
Will provide a widget to select between the 'air' and 'surface' data variable.
Currently working on that, it's basically just waiting on new HoloViews/GeoViews releases. The API here is as follows:
|
{ "total_count": 7, "+1": 4, "-1": 0, "laugh": 0, "hooray": 3, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HoloViews based plotting API 327725925 | |
393284049 | https://github.com/pydata/xarray/issues/2199#issuecomment-393284049 | https://api.github.com/repos/pydata/xarray/issues/2199 | MDEyOklzc3VlQ29tbWVudDM5MzI4NDA0OQ== | philippjfr 1550771 | 2018-05-30T19:16:32Z | 2018-05-30T19:16:32Z | NONE | Thanks for the feedback! I'll try to drive the pandas conversation along, but since I doubt that will be resolved in the near term so I think until then we should definitely pursue the accessor approach (which is much better than the property monkey patching we're doing now). Personally I'd prefer @rabernat Since you have used HoloViews with xarray in the past I'd very appreciate your input as well. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
HoloViews based plotting API 327725925 |
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