Thanks for mentioning v.segment Helmut.
If I read the docs correctly, it is necessary to send v.segment a text string or file with one line for each point to be created, indicating which cat in the line object is being referenced. I’m trying to automate this for different streams where there can be a variable number of cats, representing line segments of different lengths. And I’m trying to create somewhere between several hundred to several thousand points. So a wrapper like v.fixed.segmentpoint makes more sense, but would need to work for an entire line object or for a set of cats (rather than a single cat).
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
On Nov 30, 2014, at 12:21 PM, grass-user-request@lists.osgeo.org wrote:
From: Helmut Kudrnovsky <hellik@web.de>
To: <grass-user@lists.osgeo.org>
Date: November 30, 2014 at 12:04:09 PM MST
Subject: Re: [GRASS-user] how to change all cats in a vector line
v.fixed.segmentpoints is just a wrapper script of v.Segment
http://grass.osgeo.org/grass71/manuals/v.segment.html
v.segment is very flexible.
you have to define rules (e.g. lines with different cats). IMHO it’s the way
to go if the river segments have different cats.in v.fixed.segmentpoints I’ve implemented that the attribute table contains
the distance from source, but that’s not implemented in v.segment.
best regards
HelmutView this message in context: http://osgeo-org.1560.x6.nabble.com/how-to-change-all-cats-in-a-vector-line-tp5175575p5175693.html
Sent from the Grass - Users mailing list archive at Nabble.com.