WFS 2 may be quite useful for large responses because it allows the retrieval of parts of a response through multiple requests. A client can request resultType "hits" (same as WFS 1.1) to find out how many features match, and then make multiple requests with startIndex and count to get subsets. I haven't used it yet, but this is one of the big new features added in WFS 2.
On 02/12/11 04:25, Phil Scadden wrote: > Just a caveat, that while geoserver will cope with large datasets, browsers > would choke on more than 1000 points sent from a WFS query. Use WMS for > rendering, WFS for querying, -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
