New answers tagged

3

You can also switch off WFS-T for your service by going to the WMS menu page (Services->WMS) and changing the service level from Complete to Basic.


3

There are multiple ways of achieving this: Use Geoserver's Service Security Connect to the PostGIS table with a user who only has Read-Only access on the Table. Ideally you should do both.


0

Problem was solved by enabling jsonp in the geoserver


0

Another reason for GeoServer considering a table read only is having a column with a type that GeoServer does not understand... and thus cannot write onto. If that's the case, you should find in your logs, the first time that table is used, and at least at the default logging level, a message such as: Could not find mapping for theColumn, ignoring the ...


0

I had a problem with WFS like you, I solved it by enabling jsonp in Geoserver


1

So finally, here is the solution I used thanks to Barrett ! If it can help someone else here is the code : var defaultParameters = { service : 'WFS', version : '1.0.0', request : 'GetFeature', typeName : 'database:table’, outputFormat : 'text/javascript', format_options : 'callback:callEP', srsName : 'EPSG:4326', }; var ...


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


0

It's happening because by OGC Filter specification the first element of an intersects filter must be a property name. Now, that said, GeoServer should be able to deal with an expression as the first argument internally, it's just that there is one class in GeoServer that's still enforcing the the above limitation while processing the request. You can open a ...


1

Try using preventDefault() or try changing #formulaire from a 'submit' type to a 'button' type and just have the script execute on click. At that point the data will submit but the updated image won't show since it not calling a new request to geoserver (which was happening when the page was refreshed). You need to find a function in leaflet to force your ...


0

Turns out it got solved by setting the projection to EPSG 3857


2

It seems to me that you could just add the features to the local layer as well as sending them to PostGIS. I'd comment further but the key part of the code is missing from your question. As an aside why not use the WFS-T functionality built in to GeoServer instead of reinventing it using PHP?


0

You need to enable jsonp in your Geoserver to be able to post code In order to edit you need the following code: var formatWFS = new ol.format.WFS(); var formatGML = new ol.format.GML({ featureNS: 'yourfeatureNS', featureType: 'stores', srsName: 'EPSG:3857' }); var s = new XMLSerializer(); var sourceWFS = new ol.source.Vector({ loader: ...


0

The typical reason for this errors is that the underlying table does not have a primary key, it's a view in the database, or the layer is configured as "sql view" in GeoSever


1

Turns out the answer was that Geoserver didn't allow for jsonp to be shown in web applications. After I asked the web dev responsible for dealing with servers he was able to write a few lines of code to the server and now my layers suddenly all work in the web apps!


1

In the very end, I got a response from the vendor a month after we stopped working on the project. The vendor's response was that I was using the wrong letter casing in the CQL_FILTER parameters. The 'featureid' parameter needed to have a capital 'i' so that it ends up as 'featureId'. I tested my original WMS query with the single letter change, and sure ...


1

Based on the comment from user30184 I recognized, that all fields in my geoserver layer were not really of numeric type, also I assumed this. After changing field type to real/double in database (which is float in geoserver feature type description), I could do the interpolation of a layer column. This works according to my tests from at least QGIS 2.8.2 ...



Top 50 recent answers are included