[GRASS-dev] [GRASS GIS] #386: Thematic grouping of grass modules in the command line
GRASS GIS
trac at osgeo.org
Wed Aug 29 04:33:17 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
--------------------------+-------------------------------------------------
Changes (by neteler):
* status: closed => reopened
* resolution: fixed =>
Comment:
Replying to [comment:12 mlennert]:
> I think such as list is very useful, but the result is still quite
unsatisfactory at this point. E.g.
>
> * database only links to v.db.* modules, none of the db.* modules[[BR]]
As written, the current mechanism is based on the second keyword. Each
topic corresponds to this. The db.* have: "attribute table" there, while
the v.db.* have "database". It is a trivial change to reorder this, just
some agreement is needed first.
> * imagery only lists r.in.aster[[BR]]
Fixed in r , now it results in "Import".
> * raster links to a series of diverse modules, none of them r.*[[BR]]
Right, all have the wrong second keyword. Working on it.
> * interpolation only links to t.rast.gapfill[[BR]]
The others under "surface". This requires some more discussion how to
classify them.
> etc
>
> I guess this means that many modules do not have the right (or any?)
keywords. But IMHO, as much as I like the idea, I'm afraid that in its
current state this list might be counterproductive for new users. I
definitely would not recommend my students to use it right now when trying
to find modules by topics.
Ok, it exists for a few days only - tell them to wait a week :-)
Markus
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/386#comment:13>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list