[GRASSLIST:8497] Re: New GRASS Module: v.drape

[Michael Barton]

This sounds VERY interesting. I can see a number of potential uses.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402

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



> From: Dylan Beaudette <dylan at iici.no-ip.org>
> Date: Wed, 28 Sep 2005 14:20:29 -0700
> To: Radim Blazek <radim.blazek at gmail.com>
> Cc: Markus Neteler <neteler at itc.it>, <GRASSLIST at baylor.edu>
> Subject: [GRASSLIST:8447] New GRASS Module: v.drape
> 
> Hi Radim and Markus,
> 
> Per Radim's suggestions I have created a new module called v.drape, wich will
> create a 3D vector from a 2D vector and an elevation surface. Vector code was
> borrowed from v.split, and raster sampling was based on code from v.sample.
> 
> Attached is an initial version of the source code, which seams to work fine
> for lines. I still need to add support for points, and add some error
> checking. Also, I have commented using Doxygen-style formatting, for later
> programmer's manual creation. If this looks ok to you guys, I will write up
> the description.html as soon as I can.
> 
> The new command works like this:
> v.drape -C in=trails output=trails3d rast=elev_meters
> 
> A new 3D vector file is created, with a copy of the original DB table.
> 
> Cheers,
> 
> -- 
> Dylan Beaudette
> Soils and Biogeochemistry Graduate Group
> University of California at Davis
> 530.754.7341
> 
> 
> On Wednesday 28 September 2005 12:09 am, Radim Blazek wrote:
>> Hi,
>> I intended
>> v.drape input=my2d rast=dem output=my3d
>> v.out.pov input=my3d
>> Would it be a problem to create one more map?
>> 
>> But if you put most of functionality to
>> G_sample_raster(raster_file, method, point_x, point_y)
>> it is ok for me also to add it to v.out.pov.
>> Also it would be nice if you could contribute also v.drape
>> (should be simple with G_sample_raster).
>> 
>> Note that output of v.drape (or v.to.3d?) can be also used in
>> nviz.
>> 
>> Radim
>>