[Qgis-developer] WPS server

[rldhont]

Hi Martin,

I think we need both :
* QgsExpression for simple Process on Geometry and simple parameters
* SEXTANTE for complexe Process on Raster, Vector Layer, multiple Layer, etc

After some tests on WFS-Transaction, I need a way to validate my 
geometry before updating or adding feature. In this case SEXTANTE will 
be too big, QgsExpression is exactly what I need no more no less. I do 
not need to Process layer.

For SEXTANTE, Vincent Picavet give the good solution :
/* Making sextante totally independant of qgis GUI, to be able to run 
sextante processes in batch in command line mode//
//This will open the door to use Sextante as a real WPS processes 
generator, //
//with features not unlike an ETL (or ELT)./

René-Luc D'Hont
3Liz

Le 03/12/2012 17:43, Martin Dobias a écrit :
>
> On Mon, Dec 3, 2012 at 2:31 PM, rldhont <rldhont at gmail.com 
> <mailto:rldhont at gmail.com>> wrote:
>
>     My idea was to have a simple WPS server based on QGIS-Server, very
>     simple for simple vector case, and I thought it's a good idea. I
>     only need to validate geometry, constructing simple buffer or
>     intersection.
>
>     For big processing, I think SEXTANTE is better suitable, but for a
>     WPS serveur, SEXTANTE didn't need QGIS. We can construct a WPS
>     Server based on pySextante with pyWPS.
>
>     I don't really want to hack QgsExpression, just accesses to very
>     simple processing, I'll just it. For SEXTANTE, It will be better
>     to work on someting based on pyWPS.
>
>
> I don't think PyWPS would be a good choice for WPS server 
> implementation. From a broader view, PyWPS does the same thing as 
> SEXTANTE does: it allows users to run processes and it allows 
> developers to provide custom processes. The main difference is that 
> PyWPS processing is meant to be triggered by WPS requests, while 
> SEXTANTE processing may be triggered by anything (currently mainly 
> GUI). On the backend side, PyWPS supports GRASS, while SEXTANTE offers 
> much more by default. It's true that one could attach SEXTANTE to 
> PyWPS and let QGIS server call PyWPS all the time, but that would 
> bring just additional limitations.
>
> In fact, the server-side WPS support could be implemented directly 
> within SEXTANTE, the only thing that would QGIS server do would be to 
> pass WPS request to SEXTANTE routine and send its response back to server.
>
> So the bottom line from my point of view:
> SEXTANTE +1
> QgsExpression -1
> PyWPS -1
>
> Regards
> Martin
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20121204/6c5066b3/attachment.html>