[mapserver-users] Re: Limiting the execution time of mapserver
Tom.Kralidis at ec.gc.ca
Tue Jun 22 15:32:16 EDT 2010
Another option is using WEB.METADATA.wfs_maxfeatures, which MapServer
will truncate to when doing WFS GetFeature responses. This is then
advertised in the WFS Capabilities XML (ows:Constraint
name="DefaultMaxFeatures"). This also gets automagically passed to the
underlying SQL statement, shapefile data fetch, etc., on WFS GetFeature.
Thus you can use this to control output, so that the client never gets
more than x features back.
The client, in their WFS GetFeature requests, can then use the parameter
startindex=n (where n is an integer of the start position of the result
set) to page through the results accordingly.
> -----Original Message-----
> From: mapserver-users-bounces at lists.osgeo.org
> [mailto:mapserver-users-bounces at lists.osgeo.org] On Behalf Of
> Andy Colson
> Sent: Tuesday, 22 June 2010 15:19
> To: mattmendick
> Cc: mapserver-users at lists.osgeo.org
> Subject: Re: [mapserver-users] Re: Limiting the execution
> time of mapserver
> On 6/22/2010 2:13 PM, mattmendick wrote:
> > Thanks for the reply - where would you put this limit
> statement? I've
> > tried putting it in the DATA section, like so:
> > DATA "wkb_geometry from (select * from parcels LIMIT 100)
> as subquery
> > using unique ogc_fid using srid=4326"
> I was thinking this one...
> > And none of these seem to work - am I putting the limit
> statement in
> > the right spot?
> Bummer... I was only guessing, I have never tried it before,
> maybe the query get's re-written (appending where clauses and
> what not) and the limit gets lost. Sorry 'bout that.
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
More information about the mapserver-users