2
WMS is requesting an image so there is no CORS issue. When you request a WFS feature collection the browser is more worried and needs you to handle CORS correctly.
2
Thanks to @AndreaAime, I was able to determine that this was due to decimal truncation by Geoserver. This is really a duplicate of the following question.
What causes these geometry differences between original PostGIS data and Geoserver WFS?
1
I you switch your WFS from Complete to Basic on the WFS settings page then no transactional requests will be supported but the end points will still appear in the capabilities document.
Changing permissions will not affect the output of the GetCapabilities request.
I don't think there is any way in GeoServer to limit requests to just GET (there is no ...
1
A select interaction is used to select features using a pointer. You should avoid using it when selecting by other means You cannot force the interaction to select a feature, which is why you are having to set the style - so you must also clear that style when deselecting:
function selectByDistrict(selectiddist) {
var view = new ol.View({
projection:...
1
Turn off on-the-fly simplification in your postgis datastore. This is used to speed up data display when a store is just used for WMS displays.
1
I'm not sure if it's possible in the attribute table unless the WFS defines the identifier as an attribute.
You can check by doing a DescribeFeatureType request like:
http://services.sandre.eaufrance.fr/geo/zon_FXX?SERVICE=WFS&REQUEST=DescribeFeatureType&VERSION=2.0.0&TYPENAMES=sa:Sage&outputformat=text/xml;%20subtype=gml/2.1.2&
Which ...
Only top voted, non community-wiki answers of a minimum length are eligible
