On 25/02/16 22:15, Andrea Aime wrote: > I'm not sure app-schema can "invent" a new schema on the fly, one that > is based on GML 3.2 instead of GML 3.1
It cannot. Andrea, I am sure your diagnosis and solution are correct. TRD, a WFS 2.0.0 request is required to default to a GML 3.2.1 response. Because a GML 3.1.1 application schema cannot encode the GML 3.2.1 geometries that app-schema prepares for you (different geometry types in different namespaces), the encoder falls back to encoding the bare WKT. When using a WFS 2.0.0, try outputformat=gml3 to request a GML 3.1.1 response. Kind regards, -- Ben Caradoc-Davies <b...@transient.nz> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
