Hot answers tagged wfs-t
Your Insert request contains an feature that doesn't match your Schema which is expecting the Point attribute to be called the_geom. You don't get an error because you have marked that feature as Nillable (or optional). <xsd:schema xmlns:gml="http://www.opengis.net/gml" xmlns:opengeo="http://opengeo.org" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ...
GeoServer indeed tends to swap coordinates on several occasions when using WFS. I couldn't backtrack this phenomenon to its exact origin, only to this post, where it is assumed, this confusion is created by the different axis orientation of EPSG:4326, and CRS:84, which are otherwise identical projections. A possible workaround could be implemented on the ...
OL3.8.2 only supports WFS 1.1.0. See docs: ol.format.WFS Feature format for reading and writing data in the WFS format. By default, supports WFS version 1.1.0. You can pass a GML format as option if you want to read a WFS that contains GML2 (WFS 1.0.0). Also see ol.format.GMLBase which is used by this format.
Looking at the source code, the ol.format.WFS constructor can be customized to support different WFS formats (with gmlFormat, and schemaLocation), but it only affects the reading process, not its writeTransaction method. As you can see in the code below, the method is hard coded to support only WFS 1.1.0 transactions. There is a mail on the ol3 dev mailing ...
Only top voted, non community-wiki answers of a minimum length are eligible