issue_comments
1 row where author_association = "MEMBER", issue = 216621142 and user = 6815844 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
These facets timed out: issue
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
289030691 | https://github.com/pydata/xarray/issues/1323#issuecomment-289030691 | https://api.github.com/repos/pydata/xarray/issues/1323 | MDEyOklzc3VlQ29tbWVudDI4OTAzMDY5MQ== | fujiisoup 6815844 | 2017-03-24T14:02:24Z | 2017-03-24T14:02:24Z | MEMBER | @shoyer Thank you for the comment.
I'm currently use tag data in tiff files. I guess some people may use exif metadata in jpg files.
Yes, I agree. skimage is the best candidate? I did not know much about skimage, but this library looks great. open_image method is possibly overkill...? I will keep this issue just open for a while until similar request comes out.
My second request seems more general. I will post it as a separate issue. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Image related methods 216621142 |
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