Tag Info

Hot answers tagged

17

Take a look at my answer on this post. Make sure your featureNS value is in the "Edit Workspace Page under Namespace URI" in your GEOSERVER. Do not use something as generic as "http://postgis.org". Use something like "http://yourdomain/application/catalogLayer" or something unique like that. You can make this URI up, just make it unique. You ...


8

Desktop GIS Opensource: udig, QGIS (Releases currently only supports WFS, developer version contains experimental WFS-T support check the QGIS bug tracker.) Commercial: Mapinfo Professional Web GIS Opensource: OpenLayers, Mapbuilder & Mapbender Commercial: Internet Mapping Framework (IMF) Most information taken from geoserver.org.


8

GeoServer has its own convention for JSONP callbacks, which is described here (coudn't find it mentioned in the official docs). So I quickly hacked a jsfiddle showing how you can use it with jQuery, just remember to set the url, workspace and layers so that they point to your geoserver.


6

The GeoTools library supports WFS-T. By using the class org.geotools.data.wfs.WFSDataStoreFactory you can connect to a WFS service. A transaction can be created using any class that implements the interface org.geotools.data.Transaction, for instance, the class org.geotools.data.DefaultTransaction. GeoTools has also classes that will allow you to work ...


5

You should be able to achieve this using a either Data/Layer or Service level security rules (they cannot be combined). See http://docs.geoserver.org/2.1.4/user/security/index.html for exact details, but something like this in layer permissions: WorkspaceA.*.r=* WorkspaceB.*.w=* I haven't tried this out, so I'm afraid I can't tell whether GetCapabilities ...


5

The "How" is actually quite easy - all you need is a WFS-T server and a WFS-T capable client. You have already picked OpenLayers as your client which is a good choice as it has no problems with talking WFS-T (see http://openlayers.org/dev/examples/wfs-protocol-transactions.html). For the server you have a choice to make - since your data is in PostGIS you ...


4

Have you considered writing a mobile web app using OpenLayers? It supports mobile phone browsers and WFS-T, and can play happily with GeoServer as a backend. The next version will support gestures and direct access to the phone's location services. It does mean you'll have to use Javascript and HTML of course, but it would make your application easily ...


4

To expand on my earlier comment for the benefit of Janne and other readers. When you use OpenLayers to make a WFS (and WFS-T) request you need to be aware of the same-origin policy, this is a clever way to prevent unscrupulous web sites from running malicious javascript exploits on your web browser. Basically what it says is that if a javascript app wants ...


4

Simply add the attribute to the feature before the wfs-commit: // feat is the feature with the area the user drawn feat.attributes.INVADED_BY_ARMY_ID = 42; Of course, you should save somewhere the army id...


3

According to Wikipedia: The WFS specification defines interfaces for describing data manipulation operations of geographic features. Data manipulation operations include the ability to: get or query features based on spatial and non-spatial constraints create a new feature instance delete a feature instance update a feature instance ...


3

You don't say what versions of the software you are using but if it is a recent PostGIS (1.9+) and an older GeoServer (2.1.x -) then you will need to run the legacy.sql script to add geomFromText() (and other functions) back into PostGIS. See http://postgis.refractions.net/docs/PostGIS_FAQ.html#legacy_faq for more details.


3

On the protocol definition, you need to set srsName: new OpenLayers.Layer.Vector('Wells', { strategies: [new OpenLayers.Strategy.BBOX(), config.saveStrategy], protocol: new OpenLayers.Protocol.WFS({ url: config.vectorWfs, featureType: "Wells_PRS", featureNS: "http://gisxxxx", ...


3

In the ESRI world, WFS-T is supported starting with version 9.3 in ArcGIS Desktop for visualization of WFS only and ArcGIS Server for publishing and edition through a WFS-T client.


3

"How" you do it is likely strongly linked to your toolset. But, I suspect in any toolset your flow will be something like this: Select the feature you want to edit (by map click, by search, etc...) and store the unique identifier. Retrieve the row from the database using the unique identifier as the filter. Parse the database row and create an "editor" ...


3

Gaia a light client with WFS-T functionality


3

UPDATE 2 The link to the Community Edition of the OpenGeo Suite can be found here. UPDATE It would seem that OpenGeo has removed the community edition. You can still use GeoExplorer though. The OpenGeo Suite Community edition has a GeoExplorer web app that you can use to style and edit layers. You can install it along with the OpenGeo Suite or by ...


3

I had a similar problem before, what helped me, that I uncommented the line that starts with "schema", so like this: geometryName: "the_geom", //schema: "http://localhost/geoserver/wfs/DescribeFeatureType?version=1.1.0&;typename=IIRS1:india_state" }) and also I think this line is maybe wrong: url: "http://localhost:8089/geoserver/IIRS1/wms", ...


3

Solved! ..by using refresh Strategy: 1.Intitalize: var refreshStrategy = new OpenLayers.Strategy.Refresh(); 2.Apply strategy to WFS-Layer: var POIs = new OpenLayers.Layer.Vector("Schneeampel", { strategies: [new OpenLayers.Strategy.Fixed(), saveStrategy, refreshStrategy], projection: WGS84, // empty style ...


3

This looks like a bug in GeoServer. GeoServer needs to identify when a schemaLocation references the GeoServer's own WFS service and does this by looking at the hostname of the URL and comparing it to a list of known hostnames it generates at start up by looking at the network interfaces. If it fails to recognize itself it will make an HTTP request to ...


3

You need to use WFS-T, the T standing for transactional, which is what's required to be able to write-back. Both Openlayers and GeoServer support this. This question may help on the script side - WFS-T: changes not saved on an OpenLayers map There's also a sample tutorial here: ...


3

You'll need to enable Transactional in the global WFS settings in the Services section of the side menu. Be careful with the workspace-specific service settings because they don't usually do what people think they do. Those settings only come into effect when you use the virtual endpoints such as http://localhost:8080/geoserver/myworkspace/wfs, but they have ...


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


2

Current development version of QGis suopports WFS-T


2

First thing to check: is your server / test webpage on 'medford.opengeo.org'? If it isn't, you won't be able to access WFS because of the Same Origin Policy. You can technically use a proxy to fix this. (though in my opinion this is just a case of WFS being a poorly designed protocol)


2

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


2

Only clues, don't think OpenLayers is able to do it. Most open source Desktop GIS are not able to do snapping on a line of differents vertex so doing this online seems for me a dream. For simple geometry, the snapping can be enough http://openlayers.org/dev/examples/snapping.html Not enough mature, I hope https://github.com/bjornharrtell/jsts will be a way ...


2

Paste your script to http://jslint.com/ and check. At beginning it will look evil-strict but once you'll get used to it it can be your best friend.


2

ArcGIS Server has supported WFS-T since 2009. Their help site has a tutorial on publishing WFS-T layers. You might want to check it out. There's also a paper on the ESRI developer library that shows an overview of the OGC capabilities that you can leverage with ArcGIS Server. I suggest that you check the paper first and then dive into the tutorial once ...


2

I have been struggling with the same issue, and so far the simple solution is to force the server side WFS-T handler (in my case tinyows v1.0.0) to ignore the schema validation. This has potential security side effects, so it is not a 'production-ready' solution, but a step in the right direction. Looking at the generated XML, it appears that the schema for ...


2

If I understood your problem correctly - just set attributes for your feature in OpenLayers, and that's all. For example, presuming your table has roadname and roadtype fields: feature.attributes.roadname = 'Foo'; feature.attributes.roadtype = 10;



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