[GRASS-dev] proposal for g.search module

Vaclav Petras wenzeslaus at gmail.com
Sun Nov 29 20:10:22 PST 2015

On Sun, Nov 29, 2015 at 7:06 AM, Jachym Cepicky <jachym.cepicky at gmail.com>

> the code is in the same repository but packed in the g.search.module
> directory now, not sure, if the g.extension will work again

g.extension supports only directories which have Makefile, i.e. Makefile
must be in the root directory of the repository. See r.modis (it might be
more complicated then you need):


On Sun, Nov 29, 2015 at 4:06 PM, Jachym Cepicky <jachym.cepicky at gmail.com>

> I've patched r3.info a bit (not sure, whether it's ok)
> https://trac.osgeo.org/grass/changeset/66983/ for potential better
> g.search.data output

Not really looked to the source code but with the commands:

r3.mapcalc "test1 = rand(0, 1)" -s
r3.flow in=test1 flowaccumulation=test2
r3.info test2 -gh

I get:

description="generated by r3.flow"

(comments at the same row)

BTW, have you considered writing a test? :)

On Sun, Nov 29, 2015 at 4:06 PM, Jachym Cepicky <jachym.cepicky at gmail.com>

> i would like to move colorize, print_results from g.search.module to some
> reachable place within existing grass python code base - any hint?

There are three options, not sure now what is better:

grass.script.utils (scripting related, grass specific)
grass.utils (more general functions, to be created)
grass.tools (compilation, html related, to be created)

We will need grass.tools at some point anyway to organize the code which
now spreads over several files in tools and man directories.

Not that you can also keep some functions in a "package directory" inside
the addon like in r.modis but at least print_results looks like it should
go to trunk.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20151129/a35bda42/attachment.html>

More information about the grass-dev mailing list