#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 mmetz):

 Replying to [comment:21 cmbarton]:
 >
 > 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?
 >
 In grass7, nearly all modules have a layer option because of direct OGR
 read access added by Martin. Layer=-1 means, use all layers, as for
 d.vect. For most modules, the layer option is optional, i.e. it must be
 possible in the GUI to either leave it empty or specify a layer if
 necessary.

 > 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 agree, there should be a possibility to choose where the z values are
 coming from.
 >
 > I guess I don't see what the problem is in having a z flag.
 >
 Added in trunk r41098, please test. Works for me in nc_spm_08 with both
 precip_30ynorm...@permanent and precip_30ynormals...@permanent. When using
 z coordinates of precip_30ynormals...@permanent, be aware that these are
 elevation, not precipitation.

 If it passes your testing, backport to all grass6 branches?

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/96#comment:23>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to