Fantastic--thanks Jackie!
Is it possible to somehow push this limit all the way through to the server
side? Perhaps I'd better explain what I'm trying to do.
We have a rather large map (500+) layers and are trying to tune it to
improve performance. As part of this, I've written a script (using
There is no server-side limiting mechanism at the moment. The limiting
mechanism is purely on the MaestroAPI side.
Having said that, if you're using MGOS 2.5 or newer, feature query responses
are now chunked meaning content will be written out to the wire as the
server-side feature reader is
Hi all,
Is there a way to limit the number of features returned the MaestroAPI
HttpServerConnection.FeatureService.QueryFeatureSource method? It looks like
this accesses the mapagent SELECTFEATURES operation which does not appear to
have a maxFeatures parameter. Are there any FDO query
Hi John,
I thought in the past I had put in a variant of QueryFeatureSource that lets
you specify an upper limit on the number of features.
Well that's not the case, so I've made a ticket for this
(http://trac.osgeo.org/mapguide/ticket/2435). It is something we should have
in the Maestro API.
