Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ERA5 data gives "cannot guess the engine" error with xarray 0.18.0 #52

Closed
pont-us opened this issue May 17, 2021 · 2 comments
Closed

ERA5 data gives "cannot guess the engine" error with xarray 0.18.0 #52

pont-us opened this issue May 17, 2021 · 2 comments
Assignees
@pont-us
Labels
bug Something isn't working

Comments

@pont-us
Copy link
Member

pont-us commented May 17, 2021

With the recently released version 0.18.0 version of xarray installed, any ERA5 request via xcube-cds fails with the error "ValueError: cannot guess the engine, try passing one explicitly".
@pont-us pont-us self-assigned this May 17, 2021
@pont-us pont-us added the bug Something isn't working label May 17, 2021
@pont-us
Copy link
Member Author

pont-us commented May 17, 2021 •
edited
Loading

Cause: the name of the downloaded NetCDF file doesn't have a ".nc" suffix. xarray 0.17.0 was able to select the NetCDF engine automatically on the basis of the file's contents. xarray 0.18.0 is apparently unable to do this, and requires an appropriate file suffix or explicitly specified engine instead.

@pont-us
Copy link
Member Author

pont-us commented May 17, 2021

Fixed in commit f8f5b76.

@pont-us pont-us closed this as completed May 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pont-us pont-us

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pont-us