issue_comments

Table actions

3 rows where issue = 271000579 and user = 4414299 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • maaleske · 3 ✖

issue 1

  • Incorrect y-coordinates for non-georeferenced data from open_rasterio · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
343766018 https://github.com/pydata/xarray/issues/1686#issuecomment-343766018 https://api.github.com/repos/pydata/xarray/issues/1686 MDEyOklzc3VlQ29tbWVudDM0Mzc2NjAxOA== maaleske 4414299 2017-11-12T20:42:13Z 2017-11-12T20:42:13Z CONTRIBUTOR

Just looking at the rasterio quickstart, it seems that it'd be easy to generate the coordinates using the Affine instance (though that is only available in Rasterio > 1.0a, with 0.36.0 you just have the tuple containing the multipliers). I think that might solve the problem though, since I would expect the sign of resand the transform to be synchronized to the same convention on the rasterio side, which might be breaking with the current code.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Incorrect y-coordinates for non-georeferenced data from open_rasterio 271000579
341754146 https://github.com/pydata/xarray/issues/1686#issuecomment-341754146 https://api.github.com/repos/pydata/xarray/issues/1686 MDEyOklzc3VlQ29tbWVudDM0MTc1NDE0Ng== maaleske 4414299 2017-11-03T16:23:02Z 2017-11-03T16:23:02Z CONTRIBUTOR

@fmaussion Thanks! I get the feeling there's probably something odd with rasterio here. I played around a bit and found that rasterio doesn't seem to care about the signs in the transform if the given upper left is (0,0) . Giving any of from_origin(0, 0, i, j) for i, j = +-1 as the transform gives a warning about using the default geotransform and doesn't save it to the file.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Incorrect y-coordinates for non-georeferenced data from open_rasterio 271000579
341746553 https://github.com/pydata/xarray/issues/1686#issuecomment-341746553 https://api.github.com/repos/pydata/xarray/issues/1686 MDEyOklzc3VlQ29tbWVudDM0MTc0NjU1Mw== maaleske 4414299 2017-11-03T15:59:25Z 2017-11-03T15:59:25Z CONTRIBUTOR

@fmaussion I've tested with both rasterio 0.36.0 and the current master branch (1.0a11), both seem to have the same behaviour.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Incorrect y-coordinates for non-georeferenced data from open_rasterio 271000579

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);