Skip to content

Commit 3ef950f

Browse files
author
Taher Chegini
committed
DOC: Improve writing. [skip ci]
1 parent e792545 commit 3ef950f

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.rst

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -141,14 +141,15 @@ The following functionalities are currently available:
141141
- Height Ellipsoidal
142142
- Contour 25
143143
- Contour Smoothed 25
144-
- ``get_dem``: Get DEM data from either the dynamic or static 3DEP service. Considering
145-
that the static service is much faster, if the target DEM resolution is 10 m, 30 m, or
146-
60 m, then the static service is used. Otherwise, the dynamic service is used.
147144
- ``static_3dep_dem``: Get DEM data at 10 m, 30 m, or 60 m resolution from the staged 3DEP
148145
data. Since this function only returns DEM, for computing other terrain attributes you
149146
can use `xarray-spatial <https://xarray-spatial.org/>`__. Just note that you should
150147
reproject the output ``DataArray`` to a projected CRS like 5070 before passing it to
151148
``xarray-spatial`` like so: ``dem = dem.rio.reproject(5070)``.
149+
- ``get_dem``: Get DEM data from either the dynamic or static 3DEP service. Considering
150+
that the static service is much faster, if the target DEM resolution is 10 m, 30 m, or
151+
60 m, then the static service is used (``static_3dep_dem``). Otherwise, the dynamic
152+
service is used (``get_map`` using ``DEM`` layer).
152153
- ``elevation_bygrid``: For retrieving elevations of all the grid points in a 2D grid.
153154
- ``elevation_bycoords``: For retrieving elevation of a list of ``x`` and ``y`` coordinates.
154155
- ``elevation_profile``: For retrieving elevation profile along a line at a given spacing.

0 commit comments

Comments
 (0)