Hot answers tagged

6

This is because boundedBy / bbox is a property that OpenLayers creates when parsing the GML, it is not a real feature property. So when you update, you should clone the feature and get rid of it. Some example code: // do a WFS transaction to update the geometry var properties = feature.getProperties(); // get rid of bbox which is not a real property delete ...


3

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" ...


3

Have a look at my blog for a bit on WFS-T. This uses the OL 3.5 library. http://wordpress-dbauszus.rhcloud.com/?p=71


2

HttpServletRequest request=...; org.geotools.xml.parser.Parser parser = new Parser(new org.geotools.wfs.v1_1.WFSConfigration()); TransactionType tt = (TransactionType) parser.parse(request.getReader()); InsertElementType insert1 = (InsertElementType) tt.getInsert().get(0);


2

I have the latest Geoserver 2.7.2 and latest Qgis at the time of my writing 2.10.1-Pisa After lot of trial and error and googling this worked for me in geoserver admin global settings add a proxy base url to be base url of your geoserver i used http://hostname:8080/geoserver save the details suddenly no more errors from QGIS all working


2

I don't need it everyday so I didn't reuse it recently but you can look at https://github.com/boundlessgeo/suite/tree/master/sdk/src/main/resources/client It's the place where the code for OpenLayers 3 templates in OpenGeo Suite is. One of these templates is for using WFS-T. You have to look at ol3edit and also ol3-common. You will need to analyse ...


2

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 ...


2

Yes WFS-T is more appropriate and can be used to edit non spatial attributes as well. Look at: http://openlayers.org/en/v3.14.2/apidoc/ol.format.WFS.html#writeTransaction on how to generate the payload.


1

You don't really need any geospatial Python libraries. WFS-T is simply based on http requests. OGR does not support all WFS-T operations e.g no lock support according to official OGR WFS documentation. As long as you provide the payload, the authentication, the URL endpoint, you may just use Python requests library to simplify calls to the WFS-T endpoint. ...


1

Based on the Schema returned from DescribeFeature request it seems that your XML file is invalid, so the error message is correct if unhelpful. The schema specifies a sequence of attributes so the order is important. Try reordering your attributes to match the schema, like this: <wfs:Insert> <tows:target ...


1

There was an error in the GML Format featureType Parameter: var formatGML = new ol.format.GML({ featureNS: 'http://my-address:8080/geoserver/web/myworkspace', featureType: 'MyLayer', srsName: myProjectionName }); The featureType just needs the layername and not the "Workspace:LayerName"-format!


1

I guess you are using an older version of ol3. If this is true: This function of Openlayers accepts an extent (first argument) and not a geometry or an array of coordinates. Try to make up the extent of your geometry. This should be an array of four coords --> [xmin,ymin,xmax,ymax]. And then pass this extent as the first argument of the function. like ...


1

Geoserver dose not work properly with shape file datastore. For reliable transaction you must define a postgis datastore.


1

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.


1

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 ...


1

Any valid URI should be working, if it's not, it might be a client issue. I know we do a lot of WFS-T with URIs setup as <company's site>/<projectName> (e.g, http://my.company.com/myproject) from OpenLayers with no issues, but don't have direct experience doing it with QGis.


1

You cannot have WFS for Grouped Layers. Grouped Layers are an Geoserver specific service, which works as a Single WMS service containing multiple Layers. This is outside the scope of OGC standards, and it only returns images. Having a vector group layer for multiple layers does not make sense. You should be able to access the individual layers as WFS.



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