You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to how open_dataset has an additional **kwargs parameter, would it be reasonable to add a similar parameter, maybe engine_kwargs to the to_netcdf to allow users to pass additional parameters to the engine?
Is your feature request related to a problem?
I briefly tried to see if any issue was brought up but couldn't.
I'm hoping to be able to pass additional keyword arguments to the engine when using
to_netcdf
. https://xarray.pydata.org/en/stable/generated/xarray.open_dataset.htmlHowever, it doesn't seem to easy to do so.
Similar to how
open_dataset
has an additional**kwargs
parameter, would it be reasonable to add a similar parameter, maybeengine_kwargs
to theto_netcdf
to allow users to pass additional parameters to the engine?Describe the solution you'd like
Describe alternatives you've considered
One could forward the additional keyword arguments with
**kwargs
. I just feel like this makes things less "explicit".Additional context
h5netcdf emits a warning that is hard to disable without passing a keyword argument to the constructor.
h5netcdf/h5netcdf#132
Also, for performance reasons, it might be very good to tune things like the storage data alignment.
The text was updated successfully, but these errors were encountered: