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

[GRASS GIS]

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

 Replying to [comment:9 glynn]:
 > Replying to [comment:7 martinl]:
 >
 > > Probably we should think about the optimalization of the attributes in
 struct Option
 >
 > Yes please.
 >
 > I've been suggesting that the "type system" should be re-worked since
 roughly forever. I would have hoped that the wxGUI development would
 produce some feedback, but so far that hasn't happened.

 Reworking the "type system" is a good idea. I would be happy to help. My
 main focus is that most of the data processing grass modules supports the
 generation of a fully machine readable description of its inputs and
 outputs (raster, vector, file  ... as well as literal data).
 This will allow the automated generic connection of modules in graphical
 work-flow builder as well as in WPS process builder.
 The current approach leads in the right direction but could e improved.
 E.g.: putting the age, element and prompt into the gisprompt string may be
 replaced using functions like G_option_set_age(), G_option_set_element()
 and so on. So the Option structure can be enhanced with additional
 variables, which are accessed with library functions, so better parameter
 storage schemes may be implemented and data handling is easier (no parsing
 overhead)?

 From the WPS describe process point of view, i need the following
 variables:
 {{{
 key                    Identifier in WPS execute request
 multiple               maxOccurs in WPS execute request
 description and label  abstract and title for inputs and outputs
 age                    Is used to distinguish between old -> input
 (ComplexData, LiteralData) and new -> output (ComplexOutput,
 LiteralOutput)
 required               minOccurs in WPS execute request
 answer                 Default value
 options                Allowed values
 prompt                 Is used to distinguish between raster, vector and
 file
 type                   LiteralData type
 }}}

 Additionally the following parameter would be very useful:
 * The mime types of input and output files
 * The specification of multiple outputs see #1033
 * In case no output was defined (e.g. r.univar) the definition of the data
 type printed to stdout is useful. There is currently no way to define the
 literal data type of printed output ... and may never be, because this
 mostly depends on flags or different options

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