issue_comments

Table actions

4 rows where issue = 344058811 and user = 8699967 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

  • snowman2 · 4 ✖

issue 1

  • Proposal: Update rasterio backend to store CRS/nodata information in standard locations. · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
428177967 https://github.com/pydata/xarray/issues/2308#issuecomment-428177967 https://api.github.com/repos/pydata/xarray/issues/2308 MDEyOklzc3VlQ29tbWVudDQyODE3Nzk2Nw== snowman2 8699967 2018-10-09T12:46:54Z 2018-10-09T12:46:54Z CONTRIBUTOR

Feel free to re-open if this becomes something of interest. Thanks!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Proposal: Update rasterio backend to store CRS/nodata information in standard locations. 344058811
407862762 https://github.com/pydata/xarray/issues/2308#issuecomment-407862762 https://api.github.com/repos/pydata/xarray/issues/2308 MDEyOklzc3VlQ29tbWVudDQwNzg2Mjc2Mg== snowman2 8699967 2018-07-25T19:07:27Z 2018-07-25T19:07:27Z CONTRIBUTOR

@fmaussion, I guess the main reason for the proposed change is to be able to read in the raster using open_rasterio() and be able to generate a netCDF using to_netcdf() that would be compatible with the rasterio model when using rasterio.open().

Also, since: "xarray.Dataset is an in-memory representation of a netCDF file", to me it makes more sense to store the data in a standard netCDF location that is consistent regardless of the backend. In doing so, other parts of xarray and libraries build off of xarray won't be required to find the same data in multiple locations.

Thanks for taking the time to consider this idea. I have used it quite a bit and it has made the datasets compatible across the various GIS tools I use (rasterio, GDAL, QGIS). It has definitely made my life easier and so I wanted to share what I have learned. But, it is just an idea. I really appreciate the work of the xarray developers and whatever y'all decide is fine with me.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Proposal: Update rasterio backend to store CRS/nodata information in standard locations. 344058811
407610465 https://github.com/pydata/xarray/issues/2308#issuecomment-407610465 https://api.github.com/repos/pydata/xarray/issues/2308 MDEyOklzc3VlQ29tbWVudDQwNzYxMDQ2NQ== snowman2 8699967 2018-07-25T02:12:16Z 2018-07-25T02:12:16Z CONTRIBUTOR

That is strange. Was the variable put in data_vars and not in coords?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Proposal: Update rasterio backend to store CRS/nodata information in standard locations. 344058811
407541054 https://github.com/pydata/xarray/issues/2308#issuecomment-407541054 https://api.github.com/repos/pydata/xarray/issues/2308 MDEyOklzc3VlQ29tbWVudDQwNzU0MTA1NA== snowman2 8699967 2018-07-24T20:28:28Z 2018-07-24T20:28:28Z CONTRIBUTOR

I don't think so. The crs should already exist on the dataset beforehand and I think it may be a bit too much to expect it to add it to the dataset in that function as there are some that don't have it and not all xarray datasets are geospatially located.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Proposal: Update rasterio backend to store CRS/nodata information in standard locations. 344058811

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