New answers tagged wfs
3
The reasons why it is so slow is
you retrieve megabytes of data doing your WFS request. To confirm, open Firebug (Firefox addon debugger) or Chrome and look into Net(work) panel. You will see it's too huge. This data takes time to be process (your "page is unresponsive" syndrom)
browser capabilities: you never display more than one thousand of feature in ...
3
You should access it through http protocol. file protocol is not allowed with a WFS server.
see this StackOverflow question.
To test geoserver WFS try GetCapabilities request.
For your case try this:
http://localhost:8080/geoserver/wfs?service=wfs&version=1.1.0&request=GetCapabilities.
More info at geoserver manual
0
Found a solution!
just combining the two layers in one by UNION. It works for me.
0
Increase the size of a querystring (http://www.iis.net/configreference/system.webserver/security/requestfiltering/requestlimits)
0
I have solved this question and worked in my case:
build1.filter = new OpenLayers.Filter.Comparison({
type: ty,
property: propertyOP,
value: ValOP
});
build1.refresh({force:true});
0
I have now resolved this issue.
It appears that the maxFeatures setting is under layer.protocol.options.maxFeatures.
I now have two references but updating both has the desired impact.
Top 50 recent answers are included
