Hello,

I'm using GeoServer's and App-Schema-Plugin's current stable version 2.8.2
for complex feature mappings. In general this is working fine. While doing
some WFS requests I noticed a difference between the output of a gml polygon
property with WFS version 1.1.0 (GML 3.1.1) and the same property with WFS
version 2.0.0 (GML 3.2.1).

this is the WFS 1.1.0 output for the geometry property of my feature type:
<iso19112:geographicExtentPolygon>
  <gml:Polygon gml:id="polygon.dog_hauskoordinaten.2395723" srsDimension="2"
srsName="urn:x-ogc:def:crs:EPSG:25832">
    <gml:exterior>
      <gml:LinearRing srsDimension="2">
        <gml:posList>695559.9950007958 5762290.559994311 695559.9950007958
5762291.559994311 695560.9950007958 5762291.559994311 695560.9950007958
5762290.559994311 695559.9950007958 5762290.559994311</gml:posList>
      </gml:LinearRing>
    </gml:exterior>
  </gml:Polygon>
</iso19112:geographicExtentPolygon>

this is the WFS 2.0.0 output of the same property of the feature type:
<iso19112:geographicExtentPolygon>POLYGON ((695559.9950007958
5762290.559994311, 695559.9950007958 5762291.559994311, 695560.9950007958
5762291.559994311, 695560.9950007958 5762290.559994311, 695559.9950007958
5762290.559994311))</iso19112:geographicExtentPolygon>

The underlying database is a postgis database and the column used for this
property mapping is a geometry column. This is the corresponding property
mapping of the feature type:
<AttributeMapping>
  <targetAttribute>iso19112:geographicExtentPolygon</targetAttribute>
  <idExpression><OCQL>strConcat('polygon.', getId())</OCQL></idExpression>
  <sourceExpression><OCQL>geographicextent</OCQL></sourceExpression>
</AttributeMapping>

The schema definition for the property is the following:
<xsd:element name="geographicExtentPolygon" type="gml:SurfacePropertyType"
minOccurs="0"></xsd:element>

I'm a bit confused why the WFS 2.0.0 output shows the WKT of the geometry
column instead of a gml geometry representation. I'm not sure if this is the
intended behaviour or if I have a flaw in my configuration.
If I change the outputFormat to "GML3" for the WFS 2.0.0 request I receive
the same response as if I requested the WFS in version 1.1.0.



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-8-2-WFS-2-0-0-Output-for-gml-Polygon-is-unexpected-WKT-String-for-outputFormat-GML32-tp5252749.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to