Fusion MapGuide selection is slow
|Reported by:||chrisclaydon||Owned by:||madair|
|External ID:||1161170||Operating System:||All|
Fusion currently determines selected features by making multiple requests to the MapGuide feature service. This works, but is slow and inefficient. MapGuide provides the QueryMapFeatures API on the Rendering Service to allow all the processing to be handled on the server side instead. The only shortcoming of this API is that it will only return properties for a single feature. This may be addressed in MapGuide in the future at some point, which would make things simpler in Fusion.
In the meantime, QueryMapFeatures can still be used to determine the selected features, and the Feature Service can then be used to retrieve their properties. The flow through the code can also be modified to render the selection in the map as soon as we know the selected features, rather than waiting for all the properties to be retrieved too, which can take some time.
The result would be a much faster perceived and actual response to a selection request.