On Fri, Nov 23, 2012 at 3:24 PM, wrote:
> Even we use currently only mainly output via references I would also
> expect to receive binary data in XML in this case. It’s nice if you can
> trust standards ;-)
>
I agree. At the same time code does not write itself (at least, not so far).
The usual
erver-users@lists.sourceforge.net
Betreff: Re: [Geoserver-users] WPS complex data results
On Fri, Nov 23, 2012 at 11:56 AM, Fabrizio Tringali
mailto:ftring...@gmail.com>> wrote:
The patch is ready but it involves also Geotools;
Looking for solutions I found different aspects on the WPS c
On Fri, Nov 23, 2012 at 11:56 AM, Fabrizio Tringali wrote:
> The patch is ready but it involves also Geotools;
>
> Looking for solutions I found different aspects on the WPS complex data
> management to improve so the patch grew a bit in different directions.
>
> I'm wondering which is the best wa
The patch is ready but it involves also Geotools;
Looking for solutions I found different aspects on the WPS complex data
management to improve so the patch grew a bit in different directions.
I'm wondering which is the best way to share a draft solution and to agree
on the improvements (please c
On Tue, Sep 18, 2012 at 4:56 PM, Fabrizio Tringali wrote:
>
> Looking for a reason in wps-core I found the method
> ExecuteProcessResponse.write(...), it seems that when the response is not a
> raw one the writeComplex method is never called so BinaryEncoderDelegate
> has no chance to deliver Jpeg
Hello everyone,
I'm investigating about a difference between geoserver and deegree WPS.
according to OGC WPS IS
"If storage of a ComplexData output has not been requested via the
―asReference
attribute (see Table 51), the ExecuteResponse document will contain that
output. For
ComplexData such as
