Re: [Geoserver-users] WFS Request Namespace Inconsistency?

Hi Ben, We added the secondary namespace and all is well. Very interesting that it affected GetFeature but not GetPropertyValue. Thanks! -Gavin On Fri, Jul 28, 2017 at 6:14 PM, Ben Caradoc-Davies wrote: > Gavin, > > both of these problems are likely caused by the lack of a

Re: [Geoserver-users] WFS Request Namespace Inconsistency?

Gavin, both of these problems are likely caused by the lack of a secondary namespace. I saw the difference in encoding (the xmlns on the non-root element), which is odd. Incremental improvements might have changed the manifestation of the problem (no longer an exception), and

Re: [Geoserver-users] WFS Request Namespace Inconsistency?

Hi Ben, That's probably what it is. I don't have a secondary namespace for gml. Weird that it's not throwing an error when encoding the response. With respect to your second question, we do see wfs:FeatureCollection and wfs:ValueCollection when using App Schema. However, in the

[Geoserver-users] WFS Request Namespace Inconsistency?

Hi, I think this is a bug, probably in App Schema, but I want to ensure I'm not doing something wrong before filing a report. I am using App Schema to output GeodesyML for WFS requests. I noticed recently that Geoserver fails to resolve one of my namespaces in GetFeature requests. This confused