issue_comments
1 row where issue = 273268690 and user = 4414299 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Use rasterio's transform instead of homemade coordinates · 1 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 352397809 | https://github.com/pydata/xarray/pull/1712#issuecomment-352397809 | https://api.github.com/repos/pydata/xarray/issues/1712 | MDEyOklzc3VlQ29tbWVudDM1MjM5NzgwOQ== | maaleske 4414299 | 2017-12-18T11:17:33Z | 2017-12-18T11:17:33Z | CONTRIBUTOR | @fmaussion Seems okay to me. The rasterio version check is a bit iffy but I can't think of a way to do it better. I do agree with @snowman2 though, having the coordinate generation separately exposed would be nice (and easier to write unit tests for). Something like ```python def xy_pixel_coordinates(nx, ny, transform=None) transform = Affine.identity if not transform else transform
``` would probably suffice, though I don't know which module this would fall under. I'd imagine it might be useful for backends besides rasterio, though. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Use rasterio's transform instead of homemade coordinates 273268690 |
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