|
132 | 132 | "The `open_dataset()` method is our entry point to n-dimensional data with xarray, the first argument we pass indicates what we want to open and is used by xarray to get the right backend and in turn is used by the backend to open the file locally or remote. The accepted types by xarray are:\n", |
133 | 133 | "\n", |
134 | 134 | "\n", |
135 | | - "* **str**: \"my-file.nc\" or \"s3:://my-zarr-store/data.zarr\"\n", |
| 135 | + "* **str**: `my-file.nc` or `s3:://my-zarr-store/data.zarr`\n", |
136 | 136 | "* **os.PathLike**: Posix compatible path, most of the times is a Pathlib cross-OS compatible path.\n", |
137 | 137 | "* **BufferedIOBase**: some xarray backends can read data from a buffer, this is key for remote access.\n", |
138 | 138 | "* **AbstractDataStore**: This one is the generic store and backends should subclass it, if we do we can pass a \"store\" to xarray like in the case of Opendap/Pydap\n", |
|
178 | 178 | "id": "11", |
179 | 179 | "metadata": {}, |
180 | 180 | "source": [ |
181 | | - "xarray iterated through the registered backends and netcdf4 returned a `\"yes, I can open that extension\"` see: [netCDF4_.py#L618](https://github.com/pydata/xarray/blob/6c2d8c3389afe049ccbfd1393e9a81dd5c759f78/xarray/backends/netCDF4_.py#L618). However, **the backend doesn't know how to \"talk\" to a remote store** and thus it fails to open our file.\n", |
| 181 | + "xarray iterated through the registered backends and netcdf4 returned a `\"yes, I can open that extension\"` see: [netCDF4_.py#L618](https://github.com/pydata/xarray/blob/6c2d8c3389afe049ccbfd1393e9a81dd5c759f78/xarray/backends/netCDF4_.py#L618). However, **the backend doesn't know how to \"talk\" to a remote store** and thus it fails to open our file.\n", |
182 | 182 | "\n" |
183 | 183 | ] |
184 | 184 | }, |
|
0 commit comments