[GRASS-dev] Re: [GRASS-user] Scripting i.ortho.photo

[Michael Barton]

On Oct 16, 2008, at 8:09 AM, <grass-user-request at lists.osgeo.org> wrote:

> Date: Thu, 16 Oct 2008 11:34:00 +0100
> From: Andy Harfoot <ajph at geodata.soton.ac.uk>
> Subject: Re: [GRASS-user] Scripting i.ortho.photo
> To: hamish_b at yahoo.com
> Cc: GRASS user list <grass-user at lists.osgeo.org>
> Message-ID: <48F71898.7000509 at geodata.soton.ac.uk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hamish wrote:
>> right, if you look at the end of imagery/i.ortho.photo/menu/menu.c  
>> you
>> can see that each program runs as "$PGM group_name", except i.group
>>
>> e.g., Andy try running:  $GISBASE/etc/photo.rectify group_name
>>
>>
>> I am not sure, do all the photo.* modules require interaction or does
>> e.g. photo.rectify just start running once you call it?
>>
>
> Unfortunately photo.rectify is interactive still so I think there's
> modification to the code required before it can be executed using
> parameters alone.
>
> I think photo.rectify is the key as all the other elements of the
> i.ortho.photo sequence generate text files in the group directory to
> store the parameters, and these could be created independently
>
> Thanks very much for having a look though.

I'm pretty sure that if i.ortho.photo modules could be made to work  
like other GRASS modules in which the old interactive terminal  
interface was optional (i.e., they can take arguments and run without  
needing an interactive terminal), they could be scripted to work in  
the wxPython GUI. Most of the important interactive part is for  
rectification and we already have an interactive rectification system  
built in wxPython.

Michael