[GRASS-dev] Re: [GRASS GIS] #96: v.surf.bspline column option broken
GRASS GIS
trac at osgeo.org
Thu Feb 18 16:42:42 EST 2010
#96: v.surf.bspline column option broken
-----------------------+----------------------------------------------------
Reporter: cmbarton | Owner: grass-dev at lists.osgeo.org
Type: defect | Status: reopened
Priority: major | Milestone: 7.0.0
Component: Raster | Version: svn-releasebranch64
Resolution: | Keywords: v.surf.bspline
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Comment (by mmetz):
Replying to [comment:25 hamish]:
> (this module being designed for massive LIDAR point datasets, where
there is no DB layer & attribute table, and probably no topology built
either FWTW. that's not to say the module shouldn't be useful for other
tasks, but that's what the module designers were thinking about)
Yes, most probably the module was designed to interpolate a DTM that is
the result of the whole LiDAR processing procedure. But the module also
works with z values taken from an attribute table (quite nice AFAICT), no
need for topology here.
The layer option problem is IMHO purely a problem of the GUI because it
must be possible to not give a layer number (layer option is optional),
and if a layer number is given, that number must be given by the GUI to
the module. As for other options expecting an integer value.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/96#comment:26>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list