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
Since we are generating artificial data, we need to specify the dimensions (number of rows and columns).
83
-
We also need to let GRASS know the actual coordinates; we will do that by setting
87
+
We also need to let GRASS know the actual coordinates we want to use; we will do all that by setting
84
88
the [computational region](https://grass.osgeo.org/grass-stable/manuals/g.region.html). Lower-left (south-west) corner of the data will be at the coordinates (0, 0),
85
89
the coordinates of the upper-right (nort-east) corner are number of rows times cell resolution and number of columns times cell resolution.
90
+
We chose a cell resolution of 10 horizontal units, which would impact certain terrain analyses, such as slope computation, and certain hydrology processes.
Directly passing NumPy arrays to GRASS tools and receiving them back is a new feature in GRASS v8.5.
110
115
If you work with older versions of GRASS, you can use
111
-
[grass.script.array](https://grass.osgeo.org/grass-stable/manuals/libpython/grass.script.html#script.array.array) and [grass.script.array3d](https://grass.osgeo.org/grass-stable/manuals/libpython/grass.script.html#script.array.array3d):

277
+
244
278
::: {.callout-note title="What about N-dimensional arrays?"}
245
279
246
280
For 3D arrays, you can use [grass.script.array3d](https://grass.osgeo.org/grass-stable/manuals/libpython/grass.script.html#script.array.array3d) package.
0 commit comments