[ZOO-Discuss] ZOO OGR Buffer demo

[Gérald Fenoy]

Hi Eric ,
my answers follow.


>
> This is great to see a demo!
>
> I have a couple questions. I don't know WPS, so forgive me if these
> are dump questions.
>
> - looking at the DescribeProcess response it looks like the default
> Execute response output format is "text/xml", though the actual output
> format  is GeoJSON. Is this me not understanding the DescribeProcess
> response?

The default output format is set to "application/json" currently, even  
if the process overwrite this value to text/plain (this explains why  
ZOO Kernel output a text/plain response).

> - IIRC there's not specific mime-type for GeoJSON, could this become  
> a problem?

I think also that it will become a problem on the client side when  
automatic HTML Forms / Tool activation production will be done. The  
client side won't be able to determine what tool to activate or what  
input type it have to fill if it can't determine the semantic of an  
input.

Nevertheless, I wonder about how to bring semantic using WPS for this  
kind of datatype. We get already semantic for major datatypes. If we  
consider the schema of a ComplexData Input ("http://fooa/gml/3.1.0/point.xsd 
" for intance which means it's a geometry, and a point even, but I  
don't know an equivalent for others) and for LiterralData also if we  
use the "ows:reference" (and example here: http://demo.zoo-project.org/zoo/?Service=WPS&Request=DescribeProcess&Version=1.0.0&Language=en-CA&Identifier=Multiply 
  , where the semantic is that inputs and the output are floats).  
Nothing to say about BoundingBox :) By the way, BoundingBox is not  
currently supported by ZOO Kernel.

> - in the demo the feature is provided in input as a href to the
> appropriate WFS GetFeature request. I'm sure WPS would allow directly
> sending the feature coordinates in the request. Can you confirm this?

The demo uses an href, so ZOO Kernel will provide the link and the  
content of the downloaded data to the process which should be run. You  
can use what ever you want as input datatype until it is supported by  
the process, and if its mimeType is specified. So you can pass a full  
XML document rather than the href in the Centroid example. The service  
can use JSON string as input also. We can use the following urls to  
test different kind of input type :

   * json string, specifying "mimeType=application/json" for  
InputPolygon :
    * full text  :
http://demo.zoo-project.org/zoo/? 
request 
= 
Execute 
&service=WPS&version=1.0.0&Identifier=Buffer&DataInputs=InputPolygon= 
{ "type": "Polygon", "coordinates": [ [ [ -115.946617, 41.994698 ],  
[ -117.017906, 41.994904 ], [ -117.235909, 44.390099 ], [ -117.030975,  
49.000000 ], [ -116.062500, 48.999996 ], [ -111.318436, 44.727940 ],  
[ -111.050789, 44.473396 ], [ -111.045998, 43.515606 ], [ -111.046028,  
42.503323 ], [ -111.047951, 41.996265 ], [ -115.946617,  
41.994698 ] ] ] }@mimeType=application/ 
json&ResponseDocument=BufferedPolygon
    * as reference :
http://demo.zoo-project.org/zoo/?request=Execute&service=WPS&version=1.0.0&Identifier=Buffer&DataInputs=InputPolygon=Reference@xlink:href=http%3A%2F%2Fdemo.zoo-project.org%2Fogr%2Fdemo.json@mimeType=application/json&ResponseDocument=BufferedPolygon

  * GML :
    * as reference :
http://demo.zoo-project.org/zoo/?request=Execute&service=WPS&version=1.0.0&Identifier=Buffer&DataInputs=BufferDistance=1@datatype=float@uom=meter;InputPolygon=Reference@xlink:href=http%3A%2F%2Fdemo.opengeo.org%2Fgeoserver%2Fows%3FSERVICE%3DWFS%26REQUEST%3DGetFeature%26VERSION%3D1.0.0%26typename%3Dtopp%3Astates%26SRS%3DEPSG%3A4326%26FeatureID%3Dstates.29&RawDataOutput=BufferedPolygon

So I confirm, you could pass a JSON string or other kind of data.

>
> Thanks for putting this demo together.
>
> -- 
> Eric

Regards,

Djay
Just a ZOO Monkey
gerald.fenoy at geolabs.fr

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/zoo-discuss/attachments/20091111/6dc457c6/attachment.html>