Tag Info

New answers tagged

1

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);


3

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


0

I am thinking about the same questions at the moment. We are looking into securing a WFS-T for a government contract. Depending on your setup you may send the request from your client to a custom service using XACML which checks the current user and then either rejects or forwards the AJAX call to Geoserver. There is probably a lot of work involved to get ...


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.


0

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.



Top 50 recent answers are included