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

GRASS GIS trac at osgeo.org
Wed Aug 29 08:47:43 PDT 2012

#386: Thematic grouping of grass modules in the command line
  Reporter:  nikos        |       Owner:  grass-dev@…              
      Type:  enhancement  |      Status:  reopened                 
  Priority:  minor        |   Milestone:  7.0.0                    
 Component:  Docs         |     Version:  svn-trunk                
Resolution:               |    Keywords:  grouping grass modules   
  Platform:  Unspecified  |         Cpu:  Unspecified              

Comment(by mlennert):

 Replying to [comment:16 neteler]:
 > Replying to [comment:13 neteler]:
 > > Replying to [comment:12 mlennert]:
 > > > * database only links to v.db.* modules, none of the db.*
 > Fixed in r52973m using "attribute table" everywhere since "database"
 > is already the first category.
 > > > * raster links to a series of diverse modules, none of them
 > >
 > > Right, all have the wrong second keyword. Working on it.
 > Done.
 > > > * interpolation only links to t.rast.gapfill[[BR]]
 > >
 > > The others under "surface". This requires some more discussion how to
 > > classify them.

 Thanks for all the work on the keywords. At least now things are more
 consistent. I would have looked first for database, and would probably not
 have thought of looking for "attribute table" as a keyword, but that's me.
 What this does raise as a question is why do we have to limit ourselves to
 one keyword per module. Can't you just create this list with all the key
 words, with modules appearing under different keywords ? Thus you multiply
 the chance of people finding the module.


 P.S. Sorry if my comment about my students using the list sounded harsh.
 I'm aware that this is a new effort, but was a bit surprised that it was
 published so quickly on the web site. Then again, GRASS7 _is_ a
 development version.

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

More information about the grass-dev mailing list