Opened 12 years ago

Closed 12 years ago

#100 closed defect (fixed)

Petascope WPS lists ProcessCoverages support, but Execute request fails

Reported by: jpass@… Owned by: Dimitar Misev
Priority: major Milestone:
Component: petascope Version:
Keywords: WPS ProcessCoverages Execute Cc:
Complexity: Medium

Description

Our Earthserver Petascope WPS GetCapabilities response below
reports that Execute operation supports the ProcessCoverages process using either a GET or POST request.

http://earthserver.bgs.ac.uk/petascope?service=WPS&Request=GetCapabilities&version=1.0.0&

However neither request can be made to work.

An XML-POST request based on the Earthlook example http://kahlua.eecs.jacobs-university.de/~earthlook/demos/wps-wcps/execute.php like below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<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:ogc="http://www.opengis.net/ogc" 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>ProcessCoverages</ows:Identifier>
    <wps:DataInputs>
        <wps:Input>
            <ows:Identifier>Query</ows:Identifier>
            <wps:Data>
                <wps:ComplexData mimeType="text/plain">
 for c in (bgs_rs) return encode(c[x(3000:3500),y(5000:5500)],"png") 
                </wps:ComplexData>
            </wps:Data>
        </wps:Input>
    </wps:DataInputs>
    <wps:ResponseForm>
        <wps:RawDataOutput mimeType="image/png">
             <ows:Identifier>CoverageList</ows:Identifier>
        </wps:RawDataOutput>
    </wps:ResponseForm>
</wps:Execute> 

fails with error:

<ows:ExceptionReport version="2.0.0" 
    xsd:schemaLocation="http://www.opengis.net/ows/2.0 
    http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd" 
    xmlns:ows="http://www.opengis.net/ows/2.0" 
    xmlns:xsd="http://www.w3.org/2001/XMLSchema-instance" 
    xmlns:xlink="http://www.w3.org/1999/xlink">
    <ows:Exception exceptionCode="NoApplicableCode">
        <ows:ExceptionText>
            No suitable parser found.
        </ows:ExceptionText>
    </ows:Exception>
</ows:ExceptionReport>

For a live demo of this issue see: http://earthserver.bgs.ac.uk/petascopeWPS.html


Change History (3)

comment:1 by anonymous, 12 years ago

Please check: http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/wiki/PetascopeUserGuide#WPS

The WPS demo on earthlook is based on this integration with the 52 north WPS server. You're invoking the WPS server implemented in petascope, which is a very incomplete work, and should probably be removed at some point..

comment:2 by anonymous, 12 years ago

Yes, I saw that the Earthlook demo calls the petascope.wps.n52.ProcessCoverages process whereas the 'out of the box' petascope only cites an internal version.

My issue is that petascope is again declaring functionality that it doesn't support.

So the fix should be remove the false declaration, until such time as the declared support is available, add the support, and add back the declaration.

comment:3 by Dimitar Misev, 12 years ago

Resolution: fixed
Status: newclosed

Ok support for WPS by petascope is removed now, so only the integrated solution with 52n server can be used.

Note: See TracTickets for help on using tickets.