[GRASS-dev] Re: [GRASS GIS] #1031: More specific parameter information in command line help

GRASS GIS trac at osgeo.org
Sun Apr 11 09:14:06 EDT 2010


#1031: More specific parameter information in command line help
--------------------------+-------------------------------------------------
  Reporter:  huhabla      |       Owner:  grass-dev at lists.osgeo.org
      Type:  enhancement  |      Status:  new                      
  Priority:  minor        |   Milestone:  7.0.0                    
 Component:  libgis       |     Version:  svn-trunk                
Resolution:               |    Keywords:  parser, help             
  Platform:  All          |         Cpu:  All                      
--------------------------+-------------------------------------------------
Comment (by huhabla):

 I am aware that some of informations i requests are given by the usage
 string. But IMHO it is more convenient and easier to understand
 (especially for command line beginner) to make these informations also
 available in the help description. My enhancement request is only related
 to the command line. It does not touch the automated gui generation.

 The usage string does not always provide the convenient information if the
 parameter is of type raster, vector, volume, integer or float. In many
 modules input and output parameter are named related to the modules
 purpose, the information if its an input or output is only present if you
 read the help page.

 Martin Landa currently renamed in several modules the input and output
 parameter to make clear which of them are inputs or outputs. I.e:
 elevation -> elevation_input, direction -> direction_output, but this is
 IMHO not a good idea. It is redundant information, especially if you are
 using the gui.
 In my opinion there is no need to rename the parameters, we can provide
 the information which the gui uses to make the data handling easy in the
 command line too.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/1031#comment:2>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list