Hi, I would read this http://docs.geoserver.org/stable/en/user/services/wfs/schemamapping.html and then try something like <xsd:element maxOccurs="1" minOccurs="0" name="geometry" nillable="true" type="gml:MultiLineStringPropertyType"/>
MultiSurface is what GML 3 most often uses and I suggest to file a feature request for your application about that. However, mismatch between DescribeFeatureType and GetFeature may be a bug in Geoserver 2.8 but I am not sure. MultiCurve with just linear members is the same as MultiLineString but I can't say if client that is prepared to receive MultiLineStrings but is getting those enclosed inside MultiCurves has good enough reason for throwing an error. -Jukka Rahkonen- Dominik Gärner wrote: Hi, upgrading Geoserver from 2.7.3 to 2.8.0 results in some changes in the response of WFS (1.1.0) GetFeature requests. I have a normal Shape source with geometry type MultiLineString. In Geoserver 2.7.3 (and earlier) GetFeature und DescribeFeature returns MultiLineString to this layer. In the newer version 2.8.0 the GetFeature returns a MultiCurve (even though the layer itself and DescribeFeature is still telling MultiLineString). Is this a bug or is there a reason for it? Can I change this behaviour (my application connected to Geoserver can't handle MultiCurves)? Best Regards Dominik -- Dominik Gärner GRINTEC GmbH Anzengrubergasse 6, 8010 Graz, Austria Tel: +43(316)383706-0 mailto:[email protected] http://www.grintec.com FN 47845k Handelsgericht Graz
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
