<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello Emmanuel<br>
<br>
I'm not familiar with WPS myself, so I asked Quentin to teach me a
little bit about this issue. There is my understanding:<br>
<br>
The WPS output format is apparently not restricted by the WPS
standard. It could be GML, a Feature, a Coverage, a sensor
observation or any objects defined by an other standard. So it seems
difficult to said if we implement fully WPS, because the spectrum
seems endless.<br>
<br>
The output XML schema is inferred from the MIME type. For this
reason, "application/xml" is hard to use because it does not give
indication about that schema. Indeed, "application/xml" does not
appear in the list of MIME types recommended by WPS. Geotk
nevertheless tries to guess the schema when facing some MIME types.
But this guess is limited to a set of pre-defined schemas known to
Geotk.<br>
<br>
We could add "application/xml" to the list of MIME types for which
Geotk tries to guess the schema, but we are not sure that it would
be sufficient. Alternatively if you have some control on the WPS
server, you may try to change the MIME type to one of the types
listed in <a class="moz-txt-link-freetext" href="https://portal.opengeospatial.org/files/?artifact_id=47860">https://portal.opengeospatial.org/files/?artifact_id=47860</a>
and add a schema declaration. Next, whether Geotk will be able to
parse the output or not depends on the schema used. If this is GML,
there is chances that Geotk can parse it.<br>
<br>
Martin<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">Le 03/02/14 16:45, Emmanuel Blondel a
écrit :<br>
</div>
<blockquote cite="mid:52EFB982.2040502@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Thanks Martin,<br>
<br>
I've further tested the WPS. For some processes in the Demo
52North WPS, and for this example: <a moz-do-not-send="true"
href="http://wps01.i-marine.d4science.org/wps/WebProcessingService?service=WPS&request=DescribeProcess&version=1.0.0&identifier=com.terradue.wps_hadoop.processes.fao.intersection.Intersection">http://wps01.i-marine.d4science.org/wps/WebProcessingService?service=WPS&request=DescribeProcess&version=1.0.0&identifier=com.terradue.wps_hadoop.processes.fao.intersection.Intersection</a>,
I get a warning because of the WPS output.<br>
<br>
Indeed the process here above, only specifies a
"application/xml" mimetype as output, hence no class is found by
WPSIO.findClass(). I'm not fully aware of the supported formats
(including mimetype, encoding & schema) in OGC WPS spec and
I'd like to have confirmation (or not) that the WPSIO fully
aligns the OGC WPS spec. In case yes, it will allow me to
request improvements to properly manage WPSoutput formats in
iMarine WPS.<br>
<br>
Thanks in advance for your reply<br>
<br>
Emmanuel<br>
</div>
</blockquote>
<br>
</body>
</html>