issue_comments

Table actions

7 rows where issue = 1702025553 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 3

issue 1

  • Can't open datasets with the `rasterio` engine. · 7 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1541877797 https://github.com/pydata/xarray/issues/7831#issuecomment-1541877797 https://api.github.com/repos/pydata/xarray/issues/7831 IC_kwDOAMm_X85b5zAl simonrp84 13449576 2023-05-10T10:20:35Z 2023-05-10T10:20:35Z NONE

Thanks for the replies. Yes, that second suggestion sounds good @kmuehlbauer!

I realise it's not practical to add specific checks / messages for all engines, so something like this that links to a webpage that describes potential solutions seems like an excellent compromise. Your earlier solution (rephasing the error) I think would not help, however, as it still doesn't show users what the actual missing package is rioxarray vs rasterio.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can't open datasets with the `rasterio` engine. 1702025553
1541410601 https://github.com/pydata/xarray/issues/7831#issuecomment-1541410601 https://api.github.com/repos/pydata/xarray/issues/7831 IC_kwDOAMm_X85b4A8p kmuehlbauer 5821660 2023-05-10T06:13:20Z 2023-05-10T06:13:39Z MEMBER

Yet another idea would be to add and Engines heading on https://docs.xarray.dev/en/stable/ecosystem.html where engines/backends and there respective packages can be listed. The error could include a link to that page. 

{
    "total_count": 3,
    "+1": 3,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can't open datasets with the `rasterio` engine. 1702025553
1540845511 https://github.com/pydata/xarray/issues/7831#issuecomment-1540845511 https://api.github.com/repos/pydata/xarray/issues/7831 IC_kwDOAMm_X85b12_H kmuehlbauer 5821660 2023-05-09T20:26:32Z 2023-05-09T20:26:32Z MEMBER

Maybe it would also help to rephrase the error, something along the lines

"Engine rasterio is not available. Please install the needed package. Engines [xxx, yyy, zzz] are available."

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can't open datasets with the `rasterio` engine. 1702025553
1540816942 https://github.com/pydata/xarray/issues/7831#issuecomment-1540816942 https://api.github.com/repos/pydata/xarray/issues/7831 IC_kwDOAMm_X85b1wAu dcherian 2448579 2023-05-09T20:02:27Z 2023-05-09T20:02:27Z MEMBER

I was suggesting to special-case rioxarray only just because we recently deleted the rasterio backend, and that might ease the transition. Can we do it at the top-level open-dataset when engine=="rasterio" but rioxarray is not importable?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can't open datasets with the `rasterio` engine. 1702025553
1540811425 https://github.com/pydata/xarray/issues/7831#issuecomment-1540811425 https://api.github.com/repos/pydata/xarray/issues/7831 IC_kwDOAMm_X85b1uqh headtr1ck 43316012 2023-05-09T19:57:48Z 2023-05-09T19:57:48Z COLLABORATOR

I don't know how we would implement that, it's probably not a good idea to special case all external backends within xarray.

Either the package is installed and then it works or it is not installed and then we don't know which backend/package is missing.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can't open datasets with the `rasterio` engine. 1702025553
1540435470 https://github.com/pydata/xarray/issues/7831#issuecomment-1540435470 https://api.github.com/repos/pydata/xarray/issues/7831 IC_kwDOAMm_X85b0S4O dcherian 2448579 2023-05-09T15:44:55Z 2023-05-09T15:44:55Z MEMBER

I think this would be nice since we recently removed the rasterio backend.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can't open datasets with the `rasterio` engine. 1702025553
1540113095 https://github.com/pydata/xarray/issues/7831#issuecomment-1540113095 https://api.github.com/repos/pydata/xarray/issues/7831 IC_kwDOAMm_X85bzELH welcome[bot] 30606887 2023-05-09T13:20:07Z 2023-05-09T13:20:07Z NONE

Thanks for opening your first issue here at xarray! Be sure to follow the issue template! If you have an idea for a solution, we would really welcome a Pull Request with proposed changes. See the Contributing Guide for more. It may take us a while to respond here, but we really value your contribution. Contributors like you help make xarray better. Thank you!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can't open datasets with the `rasterio` engine. 1702025553

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