On Fri, 4 Oct 2019, Johannes Radinger wrote:
AFAIK, the tool v.stream.order was developed to work with grass vector
files only (no raster input needed). So, the input needed for
v.stream.order is the vector lines representing the streams (lines must be
connected) and points that define the
On Fri, 4 Oct 2019, Micha Silver wrote:
The v.stream.* modules all take vector maps as input.
Micha,
That's what the manual pages suggest.
Maybe yes, but if this refers to the project that you've posted about
recently, then you have a high resolution LIDAR-based DEM of the basin.
These
On 03/10/2019 23:56, Rich Shepard
wrote:
Reading
the manual pages for v.stream.network, v.stream.order, and
v.stream.profiler in the extensions doc I see details for the
input options
but all descriptions refer to raster files.
Hi Rich,
AFAIK, the tool v.stream.order was developed to work with grass vector
files only (no raster input needed). So, the input needed for
v.stream.order is the vector lines representing the streams (lines must
be connected) and points that define the outlet of each river network
that
Reading the manual pages for v.stream.network, v.stream.order, and
v.stream.profiler in the extensions doc I see details for the input options
but all descriptions refer to raster files.
Are there more detailed docs that show examples using the vector modules
along with the raster modules?
I've
