I think the problem is that the QueryFeatureProperties() API which v2.6 QUERYMAPFEATURES currently uses to assemble the response does not seem to produce the same expected set of data as QueryFeatures() even though we pass the same set of parameters to both.
I've been testing on the Sheboygan map where Parcels and Trees are selectable, and I've been getting cases where selecting a parcel gives me a selected parcel image, but no attributes because QUERYMAPFEATURES was fetching the attributes of a selected tree and vice versa. Rather than try to bash an existing QueryFeatureProperties API into shape with a metaphorical hammer to make it do something I'm starting to think it wasn't originally designed for, I've tried to write the feature attributes into XML response directly from the MgSelection of the MgFeatureInformation we get. This is proving to be a more reliable approach, and I don't get the symptoms that I have been getting before. The patch is here (http://trac.osgeo.org/mapguide/ticket/2459). I've submitted to -internals for review. It will land in trunk/2.6 by the end of the week if the patch is okay and/or nobody has made any comments by then. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Fusion-2-6-AIMS-2015-ZoomToSelection-Problem-tp5145845p5146423.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
