issue_comments

Table actions

8 rows where issue = 767941842 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

author_association 2

issue 1

  • deprecate open_rasterio in favour of a rioxarray entrypoint? · 8 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
864139294 https://github.com/pydata/xarray/issues/4697#issuecomment-864139294 https://api.github.com/repos/pydata/xarray/issues/4697 MDEyOklzc3VlQ29tbWVudDg2NDEzOTI5NA== keewis 14808389 2021-06-18T16:05:15Z 2021-06-18T16:05:15Z MEMBER

Since it comes up pretty often: should we go through with deprecating open_rasterio and the builtin rasterio backend?

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842
849762298 https://github.com/pydata/xarray/issues/4697#issuecomment-849762298 https://api.github.com/repos/pydata/xarray/issues/4697 MDEyOklzc3VlQ29tbWVudDg0OTc2MjI5OA== keewis 14808389 2021-05-27T16:13:38Z 2021-05-27T16:13:38Z MEMBER

if we deprecate xr.open_rasterio we should also do the same for xr.tutorial.open_rasterio and get xr.tutorial.open_dataset("RGB.byte") to work.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842
822647062 https://github.com/pydata/xarray/issues/4697#issuecomment-822647062 https://api.github.com/repos/pydata/xarray/issues/4697 MDEyOklzc3VlQ29tbWVudDgyMjY0NzA2Mg== max-sixty 5635139 2021-04-19T17:32:56Z 2021-04-19T17:32:56Z MEMBER

OK great @alexamici 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842
822646296 https://github.com/pydata/xarray/issues/4697#issuecomment-822646296 https://api.github.com/repos/pydata/xarray/issues/4697 MDEyOklzc3VlQ29tbWVudDgyMjY0NjI5Ng== alexamici 226037 2021-04-19T17:31:38Z 2021-04-19T17:32:11Z MEMBER

@max-sixty I'm +1 on deprecating xarray flavour of open_rasterio and direct users to rioxarray.

BTW, I would rather prefer the next release to be 0.18.0 as the backend changes are both large and user visible (open_dataset now accept **kwargs that are added to **backend_kwargs).

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842
822641695 https://github.com/pydata/xarray/issues/4697#issuecomment-822641695 https://api.github.com/repos/pydata/xarray/issues/4697 MDEyOklzc3VlQ29tbWVudDgyMjY0MTY5NQ== max-sixty 5635139 2021-04-19T17:23:59Z 2021-04-19T17:23:59Z MEMBER

I think we could release 0.17.1 fairly soon — nothing is pending but it's also fairly easy to do a release.

Do we want to deprecate open_rasterio and point people towards rioxarray? We can do that now.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842
822618516 https://github.com/pydata/xarray/issues/4697#issuecomment-822618516 https://api.github.com/repos/pydata/xarray/issues/4697 MDEyOklzc3VlQ29tbWVudDgyMjYxODUxNg== snowman2 8699967 2021-04-19T16:48:12Z 2021-04-19T16:48:20Z CONTRIBUTOR

@alexamici added the entrypoint here; https://github.com/corteva/rioxarray/pull/281. It seems xarray 0.18+ is required for it to work. Any timeline for the 0.18 release?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842
748539314 https://github.com/pydata/xarray/issues/4697#issuecomment-748539314 https://api.github.com/repos/pydata/xarray/issues/4697 MDEyOklzc3VlQ29tbWVudDc0ODUzOTMxNA== keewis 14808389 2020-12-19T23:29:53Z 2020-12-19T23:29:53Z MEMBER

What is the timeline for the next release?

There's no timeline, yet. Since we just released 0.16.2, maybe in about 2-3 months?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842
746518824 https://github.com/pydata/xarray/issues/4697#issuecomment-746518824 https://api.github.com/repos/pydata/xarray/issues/4697 MDEyOklzc3VlQ29tbWVudDc0NjUxODgyNA== snowman2 8699967 2020-12-16T15:52:34Z 2020-12-16T15:52:34Z CONTRIBUTOR

Looks like entrypoint support was added in #4577. What is the timeline for the next release?

and rioxarray agrees

Is rioxarray agreeing to allow the addition of entrypoint support? If so, :+1:

 
{
    "total_count": 2,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 1,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   deprecate open_rasterio in favour of a rioxarray entrypoint? 767941842

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