Tag Info

Hot answers tagged

2

From the WFS 1.1.0 specification which is freely available in the net: Individual exception messages are contained within the element. The mandatory code attribute may be used to associate an exception code with the accompanying message. The optional locator attribute may be used to indicate where an exception was encountered in the request that ...


2

GeoTools provides a WFS module that will create WFS-T requests programatically, see http://docs.geotools.org/latest/userguide/library/data/wfs.html for details.


1

when you add a point with new OpenLayers.Control.DrawFeature(wfs, OpenLayers.Handler.Point), by default feature state set to "Insert" but when you add a point with vectorLayer.addFeatures() command, the feature state is null. when OpenLayers wants to save change, it see to the state of the feature, and you have to set the added feature state to ...


1

I use GeoServer in OpenGeo Suite 4.1. In this package, the "Service access rules list" page has a rule that only "ADMIN" roles have permission for WFS-Transaction. wfs.Transation --> ADMIN You must delete this rule.


1

WFS locking is so seldom used that the best documentation about the usage can be found from the WFS standards. Locks are only released after successful transaction or after the expiry period is passed. In WFS standard 1.1.0 default expiry time for locks is 5 minutes <xsd:attribute name="expiry" type="xsd:positiveInteger" use="optional" default="5"/> ...


1

I know that this question is 3 years old, but I think it will help future people reading this subject. You can find an OpenLayers implementation of topology here: http://dev.openlayers.org/sandbox/bjornharrtell/eventbasedtopology2/examples/topology.html


1

Just testes with a recent Geoserver 2.5 snapshot - update request with a fid that does not exist does not create a new feature - default fid handling in Geoserver is that server is creating the fid; it is taken from a sequence or if sequence is not defined the new fid will be Max(fid)+1. Conclusion: Update does not behave as Insert, not Insert as Update. If ...


1

I had originally thought that perhaps the problem was that your internalProjection and externalProjection values were reversed (and just to note that internalProjection would be used for the map background and external for your data and are used as like this format: new OpenLayers.Format.GeoJSON({ internalProjection: new ...


1

draw.events.register("featureadded", this, function (e) { alert(e.feature); pointNumber = 1; draw.deactivate(); noktasil(e.feature); }); i wrote this codes and it's fine, works


1

It looks like you're incorrectly capturing the eastings/northings (x/y) components of your coordinates in your saveFeature javascript function: e.g. featCoordinates = vertices[nd].y + " " + vertices[nd].x I think should be featCoordinates = vertices[nd].x + " " + vertices[nd].y



Only top voted, non community-wiki answers of a minimum length are eligible