Hot answers tagged

4

The best place to look for details like this is in the standard. Inserting non spatial attributes is done in exactly the same way as adding spatial attributes. First check the schema of the feature type by using a describeFeature request, then construct a Transaction request with the attribute values in the same order as the schema requires.


4

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


3

You can use the security subsystem to disallow writes on a specific set of layers: http://geoserver.geo-solutions.it/edu/en/security/layer_level.html http://docs.geoserver.org/stable/en/user/security/layer.html


3

While it's possible and common to publish views in GeoServer WFS, the access is limited to read-only usage, you won't be able to edit them. GeoServer normally marks views as read only because it cannot find a primary key in them (pk is mandatory to generate the gml:id and to support featureid filters). To make the view editable, assuming you can find a ...


3

Make sure that you are using an EPSG code of http://www.opengis.net/gml/srs/epsg.xml#4326 instead of epsg:4326 so that the X/Y lat/Lon mapping is fixed rather than variable as it is with epsg:4326. Then make sure you are encoding the geometries that you send in the same order as you have told GeoServer to expect them. See the GeoServer documentation for a ...


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


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

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.


2

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


2

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

This is the XML structure that worked after all: <wfs:Transaction service="WFS" version="1.1.0" xmlns:ogc="http://www.opengis.net/ogc" xmlns:wfs="http://www.opengis.net/wfs" xmlns:gml="http://www.opengis.net/gml"> <wfs:Update typeName="geonode:wld_nhr_adameqepic14days_wfp_test_1_1_1"> <wfs:Property> <wfs:Name>the_geom</...


1

There were two issues in my requests. The first one was related with the URL. Initially I was using this URL: url = 'http://localhost:8080/geoserver/wfs' Including my_workspace name in the URL is necessary for this WFS-T Insert (according to here): url = 'http://localhost:8080/geoserver/my_workspace/wfs' The second issue was related with the namespace ...


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

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 xmlns:tows="http://www.vizexperts.com/"&...


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



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