[GRASS-user] Panning with r.profile or the gis.m profiler

GRASS GRASS user
1

Craig,

For your pipeline, the better solution is to use the r.profile module that
underlies the interactive profiler.

Set your computational region to match your entire pipeline with g.region.
Then put the xy coordinates of the transect nodes into r.profile, along with
the interval parameter (how often do you want an elevation calcuated). It
will output a text file with the coordinates and elevations for each point
along the transect with the interval you specify.

No need to stitch anything.

Michael

On 5/15/08 5:02 AM, "grass-user-request@lists.osgeo.org"
<grass-user-request@lists.osgeo.org> wrote:

Message: 2
Date: Thu, 15 May 2008 10:21:03 +0200
From: Craig Leat <craig@pid.co.za>
Subject: Re: [GRASS-user] Panning with r.profile or the gis.m profiler
To: grass-user@lists.osgeo.org
Message-ID: <482BF26F.7060301@pid.co.za>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Michael Barton wrote:

You can pan the display, but not at the same time you are trying to draw a
profile line.
  
So then the best that can be done is to run multiple transects with
r.profile while outputting a file with co-ordinates, then stitch them
together and calculate the chainage from the co-ordinates? I suppose
calculating the chainage from the co-ordinates is easier than trying to
ensure the end point of one transect coincides with the start point of
the next.

Craig

PS. I'm doing some long-sections for a pipe network.

__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

2

Michael:

For your pipeline, the better solution is to use the
r.profile module that underlies the interactive profiler.

Set your computational region to match your entire pipeline
with g.region.
Then put the xy coordinates of the transect nodes into
r.profile, along with the interval parameter (how often do
you want an elevation calcuated). It
will output a text file with the coordinates and elevations
for each point along the transect with the interval you specify.

or to avoid manual labor: v.extract the pipeline in question, then 'v.out.ascii format=standard'-> r.profile. or another way, v.to.points [-v|-i] + v.what.rast or v.extrude + v.out.ascii or 'v.to.db coor' + v.db.select.

Hamish