Fantastic, thanks for following up with the information on this item.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
mapguide-users mailing list
mapguide-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo
The just released 3.1.2 introduced new webconfig.ini properties for you to
apply global limits:
GlobalMaxFeatureQueryLimit (for SELECTFEATURES)
GlobalMaxMapFeatureQueryLimit (for QUERYMAPFEATURES)
GlobalGetWfsFeaturesLimit (for WFS GETFEATURES)
GlobalGetWmsFeatureInfoLimit (for WMS GETFEATUREINFO)
Thanks again Jackie. Not a major issue but it does offer more control over
default output.
To prevent breaking existing client viewers that rely on this information,
the default setting could be left to output the bounds data, with a
server-side variable that disables it if desired. As you said, p
Support for omitting bounds information in QUERYMAPFEATURES:
a) Is an API change
b) Would break our existing client viewers that relied on this information
(eg. Zoom to selected feature) if omitted by default. It would also require
some modification from our viewers to gracefully operate in the
Thank you Jackie. I suspected that was the case, as I looked in many places
for evidence of that parameter, although I did not consider the
webconfig.ini.
On a related note, it would be nice to turn off sending Bounds as part of
the Feature data provided in the JSON to mapagent.fcgi request, i.e.
No server-side limiting mechanism exists at the moment.
This is actually something worth implementing, but I'm not sure if a global
serverconfig.ini value is the place to put it. It's probably actually a web
tier limit (specified in webconfig.ini) that should be applied for mapagent
operations tha
Hello,
From a previous post on the matter, the final word was that there is no
server-side mechanism to limit the number of map features selected:
http://osgeo-org.1560.x6.nabble.com/Limiting-number-of-results-from-Maestro-QueryFeatureSource-or-mapagent-SELECTFEATURES-td5135715.html
Have there b
