[Pywps-devel] creating GRASS locations per default

[xianfeng song]

Hey, Jachym,

I mention a few points that is just for your reference.
(1) The PyWPS processes need a 'temp' folder to hold their input and
output temporarily. To some degree, one 'temp' folder should be there
for any pywps processes because of complex inputs and outputs etc. This
may not only for grass, but also for others.
(2) PyWPS is now a WPS Service that supports GRASS by default. In fact,
a little change could make pywps being a general wps service to support
more software. It may be appreciated if pywps is configurable, i.e.
using self.grassLocation for GRASS. That is, GRASS is wrapped into pywps
only when GRASS is installed and users do need a grass process. Users
will decides whether PyWPS works with grass or not, when they set pywps
package and fill grassenvsetting varibles.

Regards,
Song

On 2006-11-11 3:52, Jachym Cepicky wrote:
> Hallo,
> when we started the work on PyWPS, we were thinking, that GRASS will be
> nearly allways used as *the* working tool for all processes.
>
> When I saw Song's work [1] (great on-line R examples) I see, that other
> tools will be / are allready used not less, then GRASS.
>
> Currently, everytime, wps.py is called, temporary GRASS  location is
> created and all environment variables are set, so direct usage of GRASS
> modules is possible (starting with g.region and r.in.ogr or v.in.ogr
> ..).
>
> But as this will be not wanted feature, I'm thinking about, how to get
> rid of this feature.
>
> I see these possibilities:
>
>     1 - temporary location will be created, only when self.grassLocation
>         is set to "[temp]" key word
>
>     2 - temporary location will NOT be created only when self.grassLocation
>         exists in process definition and is set to None, but it would be
>         created by default.
>
> This sollutions do have following issues:
>
>     1 - all allready defined processes, which are using GRASS will have
>         to define self.grassLocation="[temp]"
>
>     2 - all processes, which do not want to use GRASS will have to think
>         at, that they have to add self.grassLocation=None to the process
>
> What do you think? IMHO better sollution for the future is #1
>
> Thanks
>
> Jachym
>
> [1] http://zihuan.gucas.ac.cn/PyWPS_GNUR_Example.html
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Pywps-devel mailing list
> Pywps-devel at wald.intevation.org
> http://lists.wald.intevation.org/mailman/listinfo/pywps-devel
>