3


I have a bit of a problem with WPS(1.0) chaining on GeoServer (2.9.1.).
I am following this tutorial for
http://geoserver.geo-solutions.it/edu/en/wps/chaining_processes.html
Chain 1: Extract the rivers into the “restricted areas” polygons
Problem is in third step, when i am choosing SUBPROCES of gs:CollectGeometries, imput XML looks empty

    <?xml version="1.0" encoding="UTF-8"?><wps:Execute version="1.0.0"service="WPS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.opengis.net/wps/1.0.0" xmlns:wfs="http://www.opengis.net/wfs" xmlns:wps="http://www.opengis.net/wps/1.0.0" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:gml="http://www.opengis.net/gml" xmlns:ogc="http://www.opengis.net/ogc" xmlns:wcs="http://www.opengis.net/wcs/1.1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd">
  <ows:Identifier/>
  <wps:DataInputs/>
  <wps:ResponseForm/>
</wps:Execute>

It have no imput at all, and execute of the process will end up with ErrorMessage
"Failed to parse process inputs"
It happends not only with this example, but with all the chaining Settings of WPS chaining

This is a whole XML from process imputs/outputs

    <?xml version="1.0" encoding="UTF-8"?><wps:Execute version="1.0.0" service="WPS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.opengis.net/wps/1.0.0" xmlns:wfs="http://www.opengis.net/wfs" xmlns:wps="http://www.opengis.net/wps/1.0.0" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:gml="http://www.opengis.net/gml" xmlns:ogc="http://www.opengis.net/ogc" xmlns:wcs="http://www.opengis.net/wcs/1.1.1" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd">
  <ows:Identifier>gs:Clip</ows:Identifier>
  <wps:DataInputs>
    <wps:Input>
      <ows:Identifier>features</ows:Identifier>
      <wps:Reference mimeType="text/xml" xlink:href="http://geoserver/wfs" method="POST">
        <wps:Body>
          <wfs:GetFeature service="WFS" version="1.0.0" outputFormat="GML2" xmlns:sf="http://www.openplans.org/spearfish">
            <wfs:Query typeName="sf:streams"/>
          </wfs:GetFeature>
        </wps:Body>
      </wps:Reference>
    </wps:Input>
    <wps:Input>
      <ows:Identifier>clip</ows:Identifier>
      <wps:Reference mimeType="text/xml; subtype=gml/3.1.1" xlink:href="http://geoserver/wps" method="POST">
        <wps:Body>
          <wps:Execute version="1.0.0" service="WPS">
            <ows:Identifier/>
            <wps:DataInputs/>
            <wps:ResponseForm/>
          </wps:Execute>
        </wps:Body>
      </wps:Reference>
    </wps:Input>
  </wps:DataInputs>
  <wps:ResponseForm>
    <wps:RawDataOutput mimeType="text/xml; subtype=wfs-collection/1.0">
      <ows:Identifier>result</ows:Identifier>
    </wps:RawDataOutput>
  </wps:ResponseForm>
</wps:Execute>
  • please add the whole WPS xml file for us to look at – Ian Turton Oct 6 '16 at 13:58
  • I just added whole XML request – David Oct 6 '16 at 14:02
2

I can confirm it's an issue. It's probably a side effect of the Wicket 7 migration. I'd open a bug report at https://osgeo-org.atlassian.net/projects/GEOS/issues

  • Was this problem ever fixed? Iam experiencing same issues using version 2.10.2 – algone Mar 30 '17 at 9:09
  • its still not fixed – David Aug 24 '17 at 18:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.