We're using an app-schema based on GML 3.1.1 and would like to use your WFS 2.0 client plugin. However, GeoServer defaults to WKT when there is a mismatch between the default GML version of WFS 2.0 (GML 3.2) and the GML version of the schema. That means the layer won't be recognised as containing geometry.
The workaround is to encode the outputFormat as GML3 in the GetFeature request. Would it be possible for a GML outputFormat selection box to enable these use cases?
Hi Juergen
We're using an app-schema based on GML 3.1.1 and would like to use your WFS 2.0 client plugin. However, GeoServer defaults to WKT when there is a mismatch between the default GML version of WFS 2.0 (GML 3.2) and the GML version of the schema. That means the layer won't be recognised as containing geometry.
The workaround is to encode the outputFormat as GML3 in the GetFeature request. Would it be possible for a GML outputFormat selection box to enable these use cases?
Kinda regards
Michael Sexton