Opened 17 years ago
Closed 17 years ago
#2353 closed defect (fixed)
support maxfeatures for GetObservation requests
Reported by: | tomkralidis | Owned by: | tomkralidis |
---|---|---|---|
Priority: | normal | Milestone: | 5.2 release |
Component: | SOS Server | Version: | svn-trunk (development) |
Severity: | normal | Keywords: | |
Cc: | assefa, mapserverbugs |
Description
SOS is in the same predicament as WFS w.r.t. voluminous XML responses.
Supporting ows|sos_maxfeatures would be valuable for service providers to control output for GetObservation requests/responses.
Subsequently, msSOSGetCapabilities should check if MAP/WEB/METADATA/???_maxfeatures is set. If it is, then the following will be written out under ows:OperationsMetadata.
<ows:Constraint name="DefaultMaxFeatures"> <ows:Value>$mf</ows:Value> </ows:Constraint>
...where $mf is the value of MAP/WEB/METADATA/???_maxfeatures
Change History (1)
comment:1 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
- implemented in r6971. If sos_maxfeatures is set, msSOSGetObservation() breaks when threshold is reached. Also, msSOSGetCapabilities outputs an ows:Constraint element
- HISTORY.txt updated
- msautotest: no applicable changes required
- documentation: sos_maxfeatures added to http://mapserver.gis.umn.edu/docs/howto/sos_server
Note:
See TracTickets
for help on using tickets.