issue_comments
2 rows where author_association = "CONTRIBUTOR" and issue = 110979851 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Circular longitude axis · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
147962600 | https://github.com/pydata/xarray/issues/623#issuecomment-147962600 | https://api.github.com/repos/pydata/xarray/issues/623 | MDEyOklzc3VlQ29tbWVudDE0Nzk2MjYwMA== | j08lue 3404817 | 2015-10-14T07:33:44Z | 2015-10-14T07:33:44Z | CONTRIBUTOR | Alright, I see. In that case we should not create an entirely new syntax for this - unless there are more people than just me interested in this feature. I can just use my own little convenience function that generates a series of array indices that can be fed to
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Circular longitude axis 110979851 | |
147727880 | https://github.com/pydata/xarray/issues/623#issuecomment-147727880 | https://api.github.com/repos/pydata/xarray/issues/623 | MDEyOklzc3VlQ29tbWVudDE0NzcyNzg4MA== | j08lue 3404817 | 2015-10-13T14:17:08Z | 2015-10-13T14:17:08Z | CONTRIBUTOR | @jhamman You guys seem to be always ahead of me - which is great! (I just did not notice it this time before I raised the issue...) But it would actually not be that hard to make selecting regions across the boundary of a circular dimension more convenient in It would of course be great if it worked with real coordinate (longitude) values:
which, however, only works if the axis explicitly covers this range (e.g. has range -180E to 180E). If it ranges, say, from 0E to 360E, an empty DataArray is returned. There is no nice way of resolving this, I guess, because you would need to hard-code 360 or have it as a clumsy, non-CF-standard parameter and transform all values to some common range before trying to find the requested region. But it should be less problematic with
i.e. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Circular longitude axis 110979851 |
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