[GRASS-dev] Re: grass-dev Digest, Vol 4, Issue 44

[David Finlayson]

It would be if you did it by hand. I would write a Python program to do
this.
David


On 8/13/06, Michael Barton <michael.barton at asu.edu> wrote:
>
>  There are some 350 GRASS commands, all with arguments and some with LOTS
> of arguments (e.g., r.watershed, v.surf.rst). This seems like a lot of
> work.
>
> Michael
> __________________________________________
> Michael Barton, Professor of Anthropology
> School of Human Evolution & Social Change
> Center for Social Dynamics & Complexity
> Arizona State University
>
> phone: 480-965-6213
> fax: 480-965-7671
> www: http://www.public.asu.edu/~cmbarton<http://www.public.asu.edu/%7Ecmbarton>
>
>
>
>
> *From: *<grass-dev-request at grass.itc.it>
> *Reply-To: *<grass-dev at grass.itc.it>
> *Date: *Mon, 14 Aug 2006 06:39:40 +0200
> *To: *<grass-dev at grass.itc.it>
> *Subject: *grass-dev Digest, Vol 4, Issue 44
>
>
> The Python interpreter is interactive, but it is not a general purpose
> shell. You would need to wrap external programs in an os.system or
> os.popen call. One attractive way of getting around this is to pre-wrap
> each program in a python object. For example:
>
> class Display:
>
>     def rast(self, rastername):
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev
>
>


-- 
David Finlayson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/20060817/0ba31bd4/attachment.html