issue_comments
5 rows where user = 43126798 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- nedclimaterisk · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
504238699 | https://github.com/pydata/xarray/issues/3026#issuecomment-504238699 | https://api.github.com/repos/pydata/xarray/issues/3026 | MDEyOklzc3VlQ29tbWVudDUwNDIzODY5OQ== | nedclimaterisk 43126798 | 2019-06-20T23:51:10Z | 2019-06-20T23:51:10Z | CONTRIBUTOR | For example, you might have a rectilinear grid in a non-geodetic coordinate system, for example a rotated pole:
Obviously this case is a little more complicated, because x/y and lon/lat don't have a one-to-one correspondence. But I want to be able to write code that works with both cases, ideally without special casing stuff. Being able to have separately named dim and coordinate variables would help a lot. However, now that I look at this example, I guess in my case I have both x/y and lat/lon in the coordinates anyway, so maybe I should just duplicate them, with different names. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename dims independently from coords? 456769766 | |
502882609 | https://github.com/pydata/xarray/issues/3026#issuecomment-502882609 | https://api.github.com/repos/pydata/xarray/issues/3026 | MDEyOklzc3VlQ29tbWVudDUwMjg4MjYwOQ== | nedclimaterisk 43126798 | 2019-06-17T23:04:34Z | 2019-06-17T23:04:34Z | CONTRIBUTOR | Is there even any work-around at the moment? I could try a pull request, if I could figure it out. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Rename dims independently from coords? 456769766 | |
465362210 | https://github.com/pydata/xarray/issues/2780#issuecomment-465362210 | https://api.github.com/repos/pydata/xarray/issues/2780 | MDEyOklzc3VlQ29tbWVudDQ2NTM2MjIxMA== | nedclimaterisk 43126798 | 2019-02-20T00:00:41Z | 2019-02-20T00:00:41Z | CONTRIBUTOR | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Automatic dtype encoding in to_netcdf 412180435 | ||
427207012 | https://github.com/pydata/xarray/pull/2463#issuecomment-427207012 | https://api.github.com/repos/pydata/xarray/issues/2463 | MDEyOklzc3VlQ29tbWVudDQyNzIwNzAxMg== | nedclimaterisk 43126798 | 2018-10-05T00:05:01Z | 2018-10-05T00:05:01Z | CONTRIBUTOR | whoops, sorry, fixed that commit. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add swap_coords to relevant 'See also' sections 366711310 | |
426905460 | https://github.com/pydata/xarray/issues/2461#issuecomment-426905460 | https://api.github.com/repos/pydata/xarray/issues/2461 | MDEyOklzc3VlQ29tbWVudDQyNjkwNTQ2MA== | nedclimaterisk 43126798 | 2018-10-04T06:53:35Z | 2018-10-04T06:53:35Z | CONTRIBUTOR | Awesome, thank you @fujiisoup. It might be worth putting a "see also" note in the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Set one-dimensional data variable as dimension coordinate? 366626025 |
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]);
issue 4