issue_comments

Table actions

10 rows where issue = 404088563 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

author_association 2

issue 1

  • Implementation of CRS storage in rasterio with PROJ.4 & WKT · 10 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
582984655 https://github.com/pydata/xarray/issues/2723#issuecomment-582984655 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDU4Mjk4NDY1NQ== snowman2 8699967 2020-02-06T16:20:54Z 2020-02-06T16:20:54Z CONTRIBUTOR

@dcherian Maybe a link to these examples in that section then? https://corteva.github.io/rioxarray/stable/examples/examples.html

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
582975828 https://github.com/pydata/xarray/issues/2723#issuecomment-582975828 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDU4Mjk3NTgyOA== dcherian 2448579 2020-02-06T16:02:56Z 2020-02-06T16:02:56Z MEMBER

@snowman2 Any/all of those "common operations" sounds good. We don't have a single geoTIFF example: https://xarray.pydata.org/en/stable/examples.html so at this point anything would be a big improvement

I think we should seriously consider removing all rasterio logic in xarray and make rioxarray an optional dependency to read geotiff files with xarray.

:+1: Though maybe we should wait till the backends refactor is done so that things are a little more easy.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
582972581 https://github.com/pydata/xarray/issues/2723#issuecomment-582972581 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDU4Mjk3MjU4MQ== fmaussion 10050469 2020-02-06T15:56:33Z 2020-02-06T15:56:33Z MEMBER

I think we should seriously consider removing all rasterio logic in xarray and make rioxarray an optional dependency to read geotiff files with xarray.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
582965693 https://github.com/pydata/xarray/issues/2723#issuecomment-582965693 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDU4Mjk2NTY5Mw== snowman2 8699967 2020-02-06T15:42:35Z 2020-02-06T15:42:35Z CONTRIBUTOR

Adding an example on doing these manipulations would also be very welcome.

What types of manipulations are you thinking about? Reprojection? Export to geotiff? Clip? Reading in files?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
582961469 https://github.com/pydata/xarray/issues/2723#issuecomment-582961469 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDU4Mjk2MTQ2OQ== dcherian 2448579 2020-02-06T15:33:58Z 2020-02-06T15:33:58Z MEMBER

@snowman2 @djhoese It'd be nice to update our docs to link to rioxarray and other relevant packages. (e.g. here https://xarray.pydata.org/en/stable/io.html#rasterio).

Adding an example on doing these manipulations would also be very welcome.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
582944232 https://github.com/pydata/xarray/issues/2723#issuecomment-582944232 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDU4Mjk0NDIzMg== snowman2 8699967 2020-02-06T14:58:07Z 2020-02-06T14:58:07Z CONTRIBUTOR

Going to close this as it is over a year old.

For reference, WKT support is in rioxarray. https://corteva.github.io/rioxarray/stable/examples/crs_management.html

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 1,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
506403269 https://github.com/pydata/xarray/issues/2723#issuecomment-506403269 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDUwNjQwMzI2OQ== snowman2 8699967 2019-06-27T15:49:52Z 2019-06-27T15:49:52Z CONTRIBUTOR

@fmaussion just a ping for what are your thoughts are for next steps on this?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
460428737 https://github.com/pydata/xarray/issues/2723#issuecomment-460428737 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDQ2MDQyODczNw== snowman2 8699967 2019-02-04T21:55:16Z 2019-02-04T21:55:16Z CONTRIBUTOR

I definitely agree 💯 with you on avoiding redundancy. I actually had the same thought. However, part of the reason for using crs_wkt is motivated by CF 1.7 convention. I figured it was a small change that sacrifices redundancy for consistency across the community. The crs_proj4 name was just an attempt to be consistent with your original comment and the crs_wkt. But, I think renaming it to proj4 to remove redundancy is a good choice as well.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
460396203 https://github.com/pydata/xarray/issues/2723#issuecomment-460396203 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDQ2MDM5NjIwMw== fmaussion 10050469 2019-02-04T20:15:36Z 2019-02-04T20:15:36Z MEMBER

Sorry for being late on this one. Yes, I agree that the "coordinate attribute" is worth a try.

To avoid redundancy in the name one could name the coord variable attributes simply wkt and proj4, like:

<xarray.DataArray 'crs' ()> array(0) Coordinates: crs int64 0 Attributes: wkt: PROJCS["UTM Zone 15, Northern Hemisphere",GEOGCS["WGS 84",D... proj4: +proj=...

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563
458669281 https://github.com/pydata/xarray/issues/2723#issuecomment-458669281 https://api.github.com/repos/pydata/xarray/issues/2723 MDEyOklzc3VlQ29tbWVudDQ1ODY2OTI4MQ== snowman2 8699967 2019-01-29T19:14:49Z 2019-01-29T19:14:49Z CONTRIBUTOR

Tag: @fmaussion @djhoese

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implementation of CRS storage in rasterio with PROJ.4 & WKT 404088563

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