ZooCompliancyReport - ZOO-Project/ZOO-Project GitHub Wiki

Table of Contents ZOO Project WPS implementation testing ZOO Project WPS testing details GetCapabilities request DescribeProcess request Execute request Synchronous call using asReference Synchronous call with data included Asynchronous call with data asReference Asynchronous call with full data included RawDataOutput test

ZOO Project WPS implementation testing

ZOO-PSC would like to report results of tests conducted on ZOO-Kernel WPS implementation. Comparison of some current WPS implementation was reported in presentation entitled "COMPLIANCE TESTING OF OPEN SOURCE SOFTWARE FOR WEB PROCESSING SERVICES" link.

Our testing results are presented in more details below. The test with ZOO WPS are contrary to the presentation mentioned above link. We call upon the authors of the presentation referred above to make appropriate corrections in their presentation in light of our test results outlined below. We hope that a more well planned and coordinated implementation testing can be done in the future.

Gérald Fenoy (Chair ZOO PSC)

ZOO Project WPS testing details

In the FOSS4G2010 presentation link, some unusual behavior of the ZOO Kernel was pointed out. Hence, the ZOO PSC decided to conduct our own tests with ZOO WPS implementation using the same method reported in the FOSS4G2010 presentation.

First note about this response that we have prepared, we weren't able to use XMLSpy 2007 Professional version as no more Evaluation version is available, so we used the XMLSpy 2011 Professional one as we can use it for an evaluation period of 30 days.

All the following requests give documents which are valid (using XMLSpy 2011 Professional) against the used schemas.

GetCapabilities request

In the FOSS4G2010 presentation link, an error was pointed out about some unexpected metadata : namely Test attribute to the Metadata node getting the "Demo" value. This was due to wrong ZCFG files of the first Services we made in the beginning of the 2009 year.

The provided URL to run this test is wrong, the correct one to use is as below :

http://zoo-project.org/cgi-bin-new/zoo_loader.cgi?REQUEST=GetCapabilities&SERVICE=WPS&version=1.0.0

#html

So, for the GetCapabilities request, the Capabilities document output by the ZOO Kernel is Valid.

DescribeProcess request

It was also reported in the presentation that ZOO Kernel can not handle the DescribeProcess request and output a valid ProcessDescriptions Document. Indeed the first versions of ZOO Kernel was wrong in that, but hopefully the last one, included in OSGeoLiveDVD 4.0 returns already the valid ProcessDescriptions document.

http://zoo-project.org/cgi-bin-new/zoo_loader.cgi?REQUEST=DescribeProcess&SERVICE=WPS&version=1.0.0&Identifier=Buffer

Using the url above we can confirm that ZOO Kernel provide Valid response for the DescribeProcess request.

Note that this request is Valid also :

http://zoo-project.org/cgi-bin-new/zoo_loader.cgi?REQUEST=DescribeProcess&SERVICE=WPS&version=1.0.0&Identifier=Buffer,Boundary,Centroid,ConvexHull,Simplify,Union,Intersection,Difference,SymDifference

Execute request

ZOO WPS provides valid response for Execute as XML POST requests, as it is the mandatory method.

To use the XML POST requests, please copy/paste from this page, please follow this link to paste in the HTML form.

Synchronous call using asReference

#xml
<wps:Execute service="WPS" version="1.0.0" xmlns:wps="http://www.opengis.net/wps/1.0.0" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsExecute_request.xsd">
<ows:Identifier>Buffer</ows:identifier>
<wps:DataInputs>
<wps:Input>
<ows:Identifier>InputPolygon</ows:identifier>
<ows:Title>Playground area</ows:title>
<wps:Reference xlink:href="http://dreal-official.geolabs.fr/mapjax/webservices/wfs/dreal_lr_general/?VERSION=1.1.0&amp;version=1.0.0&amp;request=GetFeature&amp;typename=Znieff1&amp;maxfeatures=1"/></wps:input>
<wps:Input>
<ows:Identifier>BufferDistance</ows:identifier>
<ows:Title>Distance which people will walk to get to a playground.</ows:title>
<wps:Data>
<wps:LiteralData>10</wps:literaldata>
</wps:data>
</wps:input>
</wps:datainputs>
<wps:ResponseForm>
<wps:ResponseDocument storeExecuteResponse="false">
<wps:Output asReference="true">
<ows:Identifier>Result</ows:identifier>
</wps:output>
</wps:responsedocument>
</wps:responseform>
</wps:execute>

Synchronous call with data included

#xml
<wps:Execute service="WPS" version="1.0.0" xmlns:wps="http://www.opengis.net/wps/1.0.0" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsExecute_request.xsd">
<ows:Identifier>Buffer</ows:identifier>
<wps:DataInputs>
<wps:Input>
<ows:Identifier>InputPolygon</ows:identifier>
<ows:Title>Playground area</ows:title>
<wps:Reference xlink:href="http://dreal-official.geolabs.fr/mapjax/webservices/wfs/dreal_lr_general/?VERSION=1.1.0&amp;version=1.0.0&amp;request=GetFeature&amp;typename=Znieff1&amp;maxfeatures=1"/></wps:input>
<wps:Input>
<ows:Identifier>BufferDistance</ows:identifier>
<ows:Title>Distance which people will walk to get to a playground.</ows:title>
<wps:Data>
<wps:LiteralData>10</wps:literaldata>
</wps:data>
</wps:input>
</wps:datainputs>
<wps:ResponseForm>
<wps:ResponseDocument storeExecuteResponse="false">
<wps:Output asReference="false">
<ows:Identifier>Result</ows:identifier>
</wps:output>
</wps:responsedocument>
</wps:responseform>
</wps:execute>

Asynchronous call with data asReference

#xml
<wps:Execute service="WPS" version="1.0.0" xmlns:wps="http://www.opengis.net/wps/1.0.0" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsExecute_request.xsd">
<ows:Identifier>Buffer</ows:identifier>
<wps:DataInputs>
<wps:Input>
<ows:Identifier>InputPolygon</ows:identifier>
<ows:Title>Playground area</ows:title>
<wps:Reference xlink:href="http://dreal-official.geolabs.fr/mapjax/webservices/wfs/dreal_lr_general/?VERSION=1.1.0&amp;version=1.0.0&amp;request=GetFeature&amp;typename=Znieff1&amp;maxfeatures=1"/></wps:input>
<wps:Input>
<ows:Identifier>BufferDistance</ows:identifier>
<ows:Title>Distance which people will walk to get to a playground.</ows:title>
<wps:Data>
<wps:LiteralData>10</wps:literaldata>
</wps:data>
</wps:input>
</wps:datainputs>
<wps:ResponseForm>
<wps:ResponseDocument storeExecuteResponse="true" status="true">
<wps:Output asReference="true">
<ows:Identifier>Result</ows:identifier>
</wps:output>
</wps:responsedocument>
</wps:responseform>
</wps:execute>

Here both statusLocation file and response are Valid.

Asynchronous call with full data included

You can also use the storeExecuteReponse="true" for ResponseDocument with the asReference attribute for the Output settled to true as in the following request :

#xml
<wps:Execute service="WPS" version="1.0.0" xmlns:wps="http://www.opengis.net/wps/1.0.0" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsExecute_request.xsd">
<ows:Identifier>Buffer</ows:identifier>
<wps:DataInputs>
<wps:Input>
<ows:Identifier>InputPolygon</ows:identifier>
<ows:Title>Playground area</ows:title>
<wps:Reference xlink:href="http://dreal-official.geolabs.fr/mapjax/webservices/wfs/dreal_lr_general/?VERSION=1.1.0&amp;version=1.0.0&amp;request=GetFeature&amp;typename=Znieff1&amp;maxfeatures=1"/></wps:input>
<wps:Input>
<ows:Identifier>BufferDistance</ows:identifier>
<ows:Title>Distance which people will walk to get to a playground.</ows:title>
<wps:Data>
<wps:LiteralData>10</wps:literaldata>
</wps:data>
</wps:input>
</wps:datainputs>
<wps:ResponseForm>
<wps:ResponseDocument storeExecuteResponse="true" status="true">
<wps:Output asReference="false">
<ows:Identifier>Result</ows:identifier>
</wps:output>
</wps:responsedocument>
</wps:responseform>
</wps:execute>

The resulting document and the statusLocation document are both Valid.

RawDataOutput test

#xml
<wps:Execute service="WPS" version="1.0.0" xmlns:wps="http://www.opengis.net/wps/1.0.0" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsExecute_request.xsd">
<ows:Identifier>Buffer</ows:identifier>
<wps:DataInputs>
<wps:Input>
<ows:Identifier>InputPolygon</ows:identifier>
<ows:Title>Playground area</ows:title>
<wps:Reference xlink:href="http://dreal-official.geolabs.fr/mapjax/webservices/wfs/dreal_lr_general/?VERSION=1.1.0&amp;version=1.0.0&amp;request=GetFeature&amp;typename=Znieff1&amp;maxfeatures=1"/></wps:input>
<wps:Input>
<ows:Identifier>BufferDistance</ows:identifier>
<ows:Title>Distance which people will walk to get to a playground.</ows:title>
<wps:Data>
<wps:LiteralData>10</wps:literaldata>
</wps:data>
</wps:input>
</wps:datainputs>
<wps:ResponseForm>
<wps:RawDataOutput>
<ows:Identifier>Result</ows:identifier>
</wps:rawdataoutput>
</wps:responseform>
</wps:execute>

The result is valid in the sens that it is a JSON string representing the resulting polygon.