Opened 18 years ago
Last modified 13 years ago
#1678 closed defect
wfs_maxfeatures = 0 — at Initial Version
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | 5.6 release |
Component: | Documentation - MapServer | Version: | 4.6 |
Severity: | normal | Keywords: | |
Cc: | banders@… |
Description
Presently, When one specifies wfs_maxfeatures = 0, it is essentially ignored, and all features are returned with a WFS GetFeature request. I plan on modifying this behavior such that wfs_maxfeatures = 0 returns 0 features with a WFS GetFeature request. [Example MapFile] Map ... WEB METADATA ... "wfs_maxfeatures" "0" END #end metadata End #WEeb ... End #Map [Example Http request] http://localhost/cgi-bin/mapserv.exe?map=C:\Program%20Files\Apache%20Group\Apache2\cgi-bin\maps\foo.map&VERSION=1.0.0&SERVICE=WFS&REQUEST=GetFeature&TYPENAME=bc_coastline [Example results of http request with future wfs_maxfeatures = 0 support] <?xml version='1.0' encoding="ISO-8859-1" ?> <wfs:FeatureCollection xmls... ... <gml:boundedBy> extent information ... </gml:boundedBy> <gml:featureMember> </gml:featureMember> </wfs:FeatureCollection>
Note:
See TracTickets
for help on using tickets.