Changes between Initial Version and Version 2 of Ticket #2459


Ignore:
Timestamp:
06/24/14 20:33:25 (11 years ago)
Author:
jng
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2459

    • Property Resolution → fixed
    • Property Status new → closed
    • Property Priority low → high
    • Property Severity trivial → critical

  • Ticket #2459 – Description

    initial v2  
    1515The problem is when a click could select more than one layer, the attributes may be collected for the wrong layer, even if that layer has candidate matching features. When MAXFEATURES=1 and we requested LAYERNAMES=Trees,Parcels and a selection image/XML of Parcels is returned, at this point we only want to collect attributes from Parcels instead of '''Trees and Parcels'''.
    1616
    17 Basically when we have a MgFeatureInformation, we want to use the layer names within its MgSelection for collecting the matching attributes instead of using the layer names from the original request.
     17Basically when we have a MgFeatureInformation, we should use its MgSelection to drive the whole attribute collection process instead of reissuing the same request parameters to QueryFeatureProperties() and hoping its set of attributes will match up with the rest of the response.