html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/pull/5609#issuecomment-887324339,https://api.github.com/repos/pydata/xarray/issues/5609,887324339,IC_kwDOAMm_X840436z,35919497,2021-07-27T08:37:35Z,2021-07-27T08:38:30Z,COLLABORATOR,"> I would try to stay as close to `open_dataset` as possible, which would make migrating to `rioxarray`'s engine easier once we deprecate `open_rasterio`. If I understand the signature of `open_dataset` correctly, this is called `backend_kwargs`?

The idea was to deprecate in the future `open_dataset` `backend_kwargs`. Currently, in `open_dataset` signature, you can use either `backend_kwargs` or `kwargs` to pass the backend additional parameters. I would avoid adding `backend_kwargs` in `open_rasterio` interface.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,945434599