resultType hits and maxFeatures limit
-------------------------------------
Key: GEOS-1724
URL: http://jira.codehaus.org/browse/GEOS-1724
Project: GeoServer
Issue Type: Improvement
Components: WFS
Reporter: Chris Tweedie
Assignee: Andrea Aime
This has appeared as part of the featuretype level maxFeatures work in GEOS-1659.
When requesting the hits number through WFS1.1, Geoserver returns the maxfeatures limit as the response (or the user defined maxFeatures value) instead of the full count of the query response (eg. not limited)
<wfs:FeatureCollection numberOfFeatures="10" timeStamp="2008-02-04T14:52:50.937+08:00" xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd"/>
What does everyone think of this behaviour? Personally i would prefer hits to be the only query that can bypass the maxfeatures limit defined by this task. This would allow a best practice for using WFS to be implemented as ..
1. Submit query with resultType = hits first.
2. If hits > nominated maxfeatures described in the abstract, warn user of an incomplete response eg. narrow your filter
Thoughts? Is there a reason it behaves like it does currently? A use case i havent thought of perhaps?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira