I just miss type, I wanted to say cfgrib instead of cfdisk. The goal
here was to try makes _get_default_engine_grib returning cfgrib to see
what happen but it ended with a key error as cfgrib isn't in the
writeable_store.
Best regards,
Fabrice
On Fri, 27 Mar 2020 13:13:32 + Alastair McKinstr
Hi,
I shall forward to upstream. It does appear that setting engine=cfgrib
should not be necessary if the file is a grib file (by extension) and
cfgrib is present.
I Agree with your point on writable_stores / cfdisk.
Best regards
Alastair
On 27/03/2020 12:44, Fabrice Meyer wrote:
> Just addin
Just adding a detail, to avoid messing with xarray code, you just need
to call to_netcdf with an engine define in your parameters. It is just
the default engine selection which appears to be broken on this version
of xarray (and also in stable).
Regards
Le 26/03/2020 à 21:07, Fabrice Meyer a écr
Package: python3-xarray
Version: 0.15.0-3
Severity: important
Dear Maintainer,
I was trying to use to_netcdf() located in
/usr/lib/python3/dist-packages/xarray/backends/api.py on a grib file without
specifying the engine and it appears that the default engine selection end up
on grib engine.
4 matches
Mail list logo