Skip to content

DOC: Explain why the rioxarray import is required #935

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

Open
VolodymyrLinuxovich wants to merge 1 commit into
base: master
Choose a base branch
from
Open

DOC: Explain why the rioxarray import is required #935

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/getting_started/getting_started.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,11 @@ with the `rio` accessor. The `rio` accessor is activated by importing rioxarray

.. code-block:: python

import rioxarray
import rioxarray # noqa: F401

Importing rioxarray registers the ``rio`` accessor, even though the module is not
used directly in this example. The ``# noqa: F401`` comment keeps linters from
removing the import as unused.


You can learn how to `clip`, `merge`, and `reproject` rasters in the :ref:`usage_examples`
Expand Down