New answers tagged


Have you tried to use QgsMapLayerRegistry().instance().removeMapLayers( or QgsMapLayerRegistry().instance().removeMapLayers([]) instead? (Note the plural "s" at removeMapLayers) This worked for me.


One way would be to serve the layer from GeoServer in GeoJSON format, and on the client side digest the layer with Mapbox-GL.js, then let MapboxGL convert & render the layer as a vector tile. This is not a recommended approach for very layer vector layers, but I have had success with layers with under 10 million vertices. Check out: ...


My answer is a bit late, but it might help others. I just had the same problem and I managed to find a solution. Here is an image of the result: This is my code: var style1 = new OpenLayers.Style(); var risk1 = new OpenLayers.Rule({ filter: new OpenLayers.Filter.Comparison({ type: OpenLayers.Filter.Comparison.EQUAL_TO, property: "r_voie_fai", ...


An example of a geoserver layer WFS bbox request would go something like this: http://myserver/geoserver/wfs?srsname=EPSG:4326&BBOX=xMinimumValue,yMinimumValue,xMaximumValue,yMaximumValue&typename=workspaceName:layerName&version=1.0.0&request=GetFeature&service=WFS


I had to change the catalog mode to mixed! The issue had nothing to do with the dispatcher servlet mapping. The "no handler mapping found" warning still exists but everything works like before.


I am not sure but I think I had some kind of this problem. Instead of using writeFeatures, iterate through your features and use the writeFeature method. try something like this: select.getFeatures().on('change:length', function(e) { var feature_buff = select.getFeatures(); var geojson = new ol.format.GeoJSON(); var json = new ...

Top 50 recent answers are included