I now believe this might be an issue with the use of 'location' as a column name - it loads ok using WFS 1.0.0 but 1.1.0 and 2.0.0 it does not load.
Did anything change in the specification between 1.0.0 and 1.1.0 to not allow these reserved word types as normal columns? Are there work arounds for this issue or would I need to rename any columns using 'location'? From: Chris Buckmaster Sent: 22 August 2016 14:51 To: geoserver-users@lists.sourceforge.net Subject: [Geoserver-users] Problems with adding WFS layers Hi Not sure if this is a QGIS or Geoserver issue... I have a WFS provided through Geoserver v2.5 - I have no issues adding layers from the WFS using QGIS v2.14, but in QGIS v2.16 I am encountering some problems with a selection of layers (within a specific Geoserver store). The store which holds the layers that are not loading has the 'Expose primary keys' option ticked whereas others do not that are loading ok (I need to expose the primary keys), would this cause any problems? Below is the error I am getting when trying to access layers from this store... 2016-08-22T14:44:41 1 Server generated an exception in GetFeature response: java.lang.RuntimeException: Failed to get property: axisLabels Failed to get property: axisLabels java.lang.String cannot be cast to com.vividsolutions.jts.geom.Geometry 2016-08-22T14:44:41 1 Download of features for layer planning:tree_preservation_orders failed or partially failed: Server generated an exception in GetFeature response: java.lang.RuntimeException: Failed to get property: axisLabels Failed to get property: axisLabels java.lang.String cannot be cast to com.vividsolutions.jts.geom.Geometry. You may attempt reloading the layer with F5 Chris
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
