I can confirm your suggestion, but would call it a bug: Look at the *s Insert says this.srsName=..., update does not
wfst.v1.js says "Insert": function(feature) { var node = this.createElementNSPlus("wfs:Insert"); ****** hier wird was mit SRS gemacht ******* this.srsName = this.getSrsName(feature); this.writeNode("feature:_typeName", feature, node); return node; }, "Update": function(feature) { var node = this.createElementNSPlus("wfs:Update", { attributes: { typeName: (this.featureNS ? this.featurePrefix + ":" : "") + this.featureType } }); if(this.featureNS) { node.setAttribute("xmlns:" + this.featurePrefix, this.featureNS); } // add in geometry if (this.geometryName !== null) { ***** Hier scheint was zu fehlen ***** this.writeNode( "Property", {name: this.geometryName, value: feature}, node ); } 00:08, schrieb Matt Priour: > It sounds like you need to explicitly set the srsName in the WFST format > options. > Matt Priour > Kestrel Computer Consulting > > > Dipl. Inf. Carsten Eider wrote: >> Hi list, >> >> i am focussing a heavy bug being a hard showstopper in my project. >> Problem: >> We have developed a so called GeoEditor. It works fine if we stay in >> EPSG:31467. >> Now we switched to EPSG:900913 in order to be able to use GoogleMaps >> EPSG:900913 is our internalProjection, whereas data is saved in the >> backend as EPSG:31467. >> There are nearly no problems while joining, splitting and creating >> multipolygons. >> The trouble starts, whenever we modify a feature using a >> ModifyFeatureControl. >> After removing or moving a point data is send to the server in >> EPSG:31467 declared as EPSG:900913. >> Data is send via WFS-T to our GeoServer-Backend. >> >> Any suggestions where my problems come from? >> >> TIA >> Carsten >> _______________________________________________ >> Dev mailing list >> Dev@openlayers.org >> http://openlayers.org/mailman/listinfo/dev >> >> _______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev