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. "Feature":[{"Bounds":["-12945413.350013612 5407462.6793876747 -12945104.670435043 5407572.3364841882"] According to this RFC you implemented, it seems there is a hook in the MgBatchPropertyCollection for bIncludeFeatureBBOX: https://trac.osgeo.org/mapguide/wiki/MapGuideRfc126 However it does not appear that the mapagent.fcgi behavior can be adjusted on either client-side or server side. Removing bounds information would reduce the JSON overhead anywhere from 10%-50% depending on the requested layer feature data. Just an additional consideration related to the first one. -- 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/mapguide-users