#96: v.surf.bspline column option broken -----------------------+---------------------------------------------------- Reporter: cmbarton | Owner: [email protected] 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 cmbarton):
The GUI is not defining what is an illegal value. -1 is not a valid value for a layer. There is no layer -1. Using 3D points instead of a column in an attribute table has nothing to do with picking layers. It is a choice of using a value from the attribute table OR using the z value of 3D points. It is easy for the GUI to create a spin box for layer selection that runs from -1 to a max. But that would be the case for all interfaces that use layers. What happens with d.vect layer=-1? The problem is using the layer selection to make the module do something that has nothing to do with layer selection. For ease of parsing in scripts and for consistent creation of a GUI interface, each distinct function should have it's own argument (option or flag). Trying to combine two different functions into one argument leads to problems in using the module syntax for anything beyond human command-line use. I guess I don't see what the problem is in having a z flag. BTW, I see that Martin has already fixed the r.bilinear entry a day or two ago. Michael -- Ticket URL: <https://trac.osgeo.org/grass/ticket/96#comment:21> GRASS GIS <http://grass.osgeo.org>
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
