[GRASS-user] ideas on how to handle 3D topology

[Michael Barton]

r.surf.area 

will calculate a topographically corrected area for rasters. So if you convert your vector areas to raster, this will do the trick.

Michael
______________________________
C. Michael Barton 
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 	480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax:          480-965-7671(SHESC), 480-727-0709 (CSDC)
www: 	http://csdc.asu.edu, http://shesc.asu.edu
		http://www.public.asu.edu/~cmbarton

On Nov 16, 2011, at 10:00 AM, grass-user-request at lists.osgeo.org wrote:

> Date: Wed, 16 Nov 2011 12:39:48 +0100
> From: "Benjamin Ducke" <benducke at fastmail.fm>
> Subject: [GRASS-user] ideas on how to handle 3D topology
> To: "grass" <grass-user at lists.osgeo.org>
> Message-ID:
> 	<1321443588.28786.140660999631021 at webmail.messagingengine.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> Dear List --
> 
> I have sketched up some ideas on how to reduce the
> complexity of 3D topology handling:
> 
> http://grass.osgeo.org/wiki/GRASS_7_ideas_collection#3D_topology
> 
> I have some hope that it should be possible to implement
> 3D topological correctness in GRASS 7 and v.clean without
> having to add a lot of code to the existing 2D methods.
> 
> I would be delighted to discuss the whole topic of 3D
> topology, as I think it currently stands between GRASS 
> and more complex 3D vector data management/analysis. 
> Not sure if this mailing list or the wiki itself would 
> be the best place for discussion.
> 
> Best,
> 
> Ben
> 
> -- 
> Benjamin Ducke
> {*} Geospatial Consultant
> {*} GIS Developer
> 
>  benducke at fastmail.fm
>