[GRASS-dev] [GRASS GIS] #386: Thematic grouping of grass modules in the command line

[GRASS GIS]

#386: Thematic grouping of grass modules in the command line
------------------------------------+---------------------------------------
 Reporter:  nikos                   |       Owner:  grass-dev at lists.osgeo.org
     Type:  enhancement             |      Status:  new                      
 Priority:  minor                   |   Milestone:  6.4.0                    
Component:  default                 |     Version:  unspecified              
 Keywords:  grouping grass modules  |    Platform:  Unspecified              
      Cpu:  Unspecified             |  
------------------------------------+---------------------------------------
 Some weeks ago I started grouping the grass (raster) modules in order to
 have a rough overview table of "what is there to use and for what". I find
 the grouping of the modules in the GUI good. But I would like some helpful
 commands in the CL.

 1. Is it feasible to have some sort of another (deeper) level of grouping
 (of the grass-modules)?[[BR]]Something like a "thematic" grouping (see
 atached .csv file).

 2. Would it be useful to have commands that will list available modules
 for a specific "group"? For example, I want to get listed all modules that
 are related directly with "landscape analysis" or to know which modules
 are available for "statistical analysis".

 ** The following naming(s) are just ideas... :-) **

 For example:

 # listing "groups of modules"[[BR]]
 g.list -c(ategories)[[BR]]

 import[[BR]]
 metadata manipulation[[BR]]
 queries[[BR]]
 categories/classes/codes[[BR]]
 editing[[BR]]
 pre-processing[[BR]]
 resampling[[BR]]
 conversion[[BR]]
 processing[[BR]]
 topographic analysis (+ surface + volume...)[[BR]]
 statistics[[BR]]
 irradiation[[BR]]
 agro(...)[[BR]]
 hydrological modelling[[BR]]
 landscape analysis[[BR]]
 validation[[BR]]
 export[[BR]]

 # listing the "statistics" group[[BR]]
 g.listmod -stat(istics)[[BR]]
 # etc. Use your imagination & logic for more names/groups

 3. What speaks against those ideas?

 Kind Regards, Nikos

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/386>
GRASS GIS <http://grass.osgeo.org>