issue_comments
3 rows where issue = 341331807 and user = 10050469 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
issue 1
- Add CRS/projection information to xarray objects · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
405166458 | https://github.com/pydata/xarray/issues/2288#issuecomment-405166458 | https://api.github.com/repos/pydata/xarray/issues/2288 | MDEyOklzc3VlQ29tbWVudDQwNTE2NjQ1OA== | fmaussion 10050469 | 2018-07-16T07:23:53Z | 2018-07-16T07:23:53Z | MEMBER | Correct me if I'm wrong, but from the xarray side it would already be enough if there is a way in xarray to have a special The solution currently is to store What could also be a possibility (without knowing how the internals would look like) is to have a registry of "special attributes" names which would always be preserved by xarray's operations. This registry would live in xarray and can be updated by downstream libraries and/or accessors. (xref: https://github.com/pydata/xarray/issues/1614 ). [1] : my preference goes for a simple PROJ4 string |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add CRS/projection information to xarray objects 341331807 | |
405106421 | https://github.com/pydata/xarray/issues/2288#issuecomment-405106421 | https://api.github.com/repos/pydata/xarray/issues/2288 | MDEyOklzc3VlQ29tbWVudDQwNTEwNjQyMQ== | fmaussion 10050469 | 2018-07-15T17:42:21Z | 2018-07-16T07:18:44Z | MEMBER | This has been discussed from time to time, although not in such an extensive way: thanks! For me, the long list of discussion points that you mention is a clear argument for a dedicated package which will have to solve all these issues. A good example of difficulty to tackle is the fact that geo libraries often do not use the same standards (see the incompatibility between Regarding the xarray side: I also brought this up for my own geo-lib a while ago, and it seems that the cleanest solution to carry a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add CRS/projection information to xarray objects 341331807 | |
405113116 | https://github.com/pydata/xarray/issues/2288#issuecomment-405113116 | https://api.github.com/repos/pydata/xarray/issues/2288 | MDEyOklzc3VlQ29tbWVudDQwNTExMzExNg== | fmaussion 10050469 | 2018-07-15T19:39:28Z | 2018-07-15T19:39:28Z | MEMBER | geopandas would be a great template for a geoxarray package ;-) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Add CRS/projection information to xarray objects 341331807 |
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