[Pywps-devel] creating GRASS locations per default
Ludwig Max Brinckmann
ludwigbrinckmann at gmail.com
Sat Nov 11 13:40:36 CET 2006
I think there are two issues: one is to support the WPS specfication, which
will require temporary storage and this should be defined in a common way.
The other issue are the requirements of different back-end environments,
such as GRASS. A generic WPS framework should none of this built in, as it
weighs things down for those who do not need it.
I think we do agree on this.
I would suggest abstracting GRASS support out into a base class for
processes that use GRASS, maybe as a mix-in class. Processes that use GRASS
would inherit from it, so all general GRASS stuff stays in one place.
Such a base class could also be the model for other framework adapters.
The way pyWPS is built it should not be difficult to achieve this.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pywps-devel