[Qgis-user] Re: GML2/GML3 encoding in WPS input (WPS plugin 0.6.16)

[Augusttown]

Hi Horst,

I know the plugin is not manipulating the data coming back from server, but
my question is about the data (request) sent by the WPS plugin, why is it
GML2 instead of GML3?

Thanks,
Yingqi

On Fri, Feb 10, 2012 at 1:32 AM, Horst Düster [via OSGeo.org] <
ml-node+s1560n4382758h10 at n6.nabble.com> wrote:

> Im not sure what happend in your case. But the Plugin doesnt manipulate
> incoming data. It only downloads the resultand features from the server
> as it is and integrates them into QGIS.
>
> Regards
> Horst
>
> Dr. Horst Düster
> Kappasys
> Alte Bernstrasse 13
> CH-4500 Solothurn
>
> Tel.: +41 (0) 32 514 00 40
> Mobil: +41 (0) 76 408 51 06
> eMail: [hidden email]<http://user/SendEmail.jtp?type=node&node=4382758&i=0>
> skype: horstduester
> Twitter: moazagotl
> Web: www.kappasys.ch
>
> lat: N 47° 12' 06.408" lon: E 7° 32' 13.740"
>
> Am 10.02.2012 07:25, schrieb Augusttown:
>
> > Hi folks,
> >
> > I am using the QGIS WPS plugin to consume one WPS process. One of the
> input
> > parameter type is defined as below in process description:
> >
> > ...
> > <ComplexData>
> >      <Default>
> >          <Format>
> > <MimeType>text/xml</MimeType>
> > <Encoding>UTF-8</Encoding>
> > <Schema>http://schemas.opengis.net/gml/3.1.1/base/gml.xsd</Schema>
> > </Format>
> >      </Default>
> >      ...
> > </ComplexData>
> > ...
> >
> > So I selected one feature from a shapefile layer as input and execute
> the
> > process, and in the Execute request WPS plugin sends I captured
> following
> > GML as complexData
> > ...
> > <gml:featureMember>
> >      <ogr:qt_temp fid="F1">
> >      <ogr:geometryProperty>
> >          <gml:Point>
> > <gml:coordinates>-13629600.1153,4547314.1181999967</gml:coordinates>
> >          </gml:Point>
> >      </ogr:geometryProperty>
> >      </ogr:qt_temp>
> > </gml:featureMember>
> > ...
> > Obviously the input feature is encoded as GML2, so I wonder why the
> input
> > feature is encoded as GML2 instead of GML3? Is it a limitation of
> QGIS/WPS
> > plugin or did I miss anything.
> >
> > I do notice that WPS plugin can successfully parse GML3 for some other
> > process that output GML3, so how I can configure it to make WPS client
> > encode input features as GML3?
> >
> > Thanks
> >
> > --
> > View this message in context:
> http://osgeo-org.1560.n6.nabble.com/GML2-GML3-encoding-in-WPS-input-WPS-plugin-0-6-16-tp4382424p4382424.html
> > Sent from the Quantum GIS - User mailing list archive at Nabble.com.
> > _______________________________________________
> > Qgis-user mailing list
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=4382758&i=1>
> > http://lists.osgeo.org/mailman/listinfo/qgis-user
> _______________________________________________
> Qgis-user mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=4382758&i=2>
> http://lists.osgeo.org/mailman/listinfo/qgis-user
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://osgeo-org.1560.n6.nabble.com/GML2-GML3-encoding-in-WPS-input-WPS-plugin-0-6-16-tp4382424p4382758.html
>  To unsubscribe from GML2/GML3 encoding in WPS input (WPS plugin 0.6.16), click
> here<http://osgeo-org.1560.n6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4382424&code=YW5ha2ludGFuZ0BnbWFpbC5jb218NDM4MjQyNHwtMjY2NTI4OTUx>
> .
> NAML<http://osgeo-org.1560.n6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>


--
View this message in context: http://osgeo-org.1560.n6.nabble.com/GML2-GML3-encoding-in-WPS-input-WPS-plugin-0-6-16-tp4382424p4383461.html
Sent from the Quantum GIS - User mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20120210/a2087e79/attachment.html>