<br><br><div class="gmail_quote">2011/5/5 Jeff McKenna <span dir="ltr"><<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Although there is a workaround, my personal opinion is that 6.0 shouldn't go out the door until we allow querying of the cluster object. It is only my opinion, as I can see myself having to answer these questions on the mailing list over and over again, so I am trying to avoid it. Maybe Stefanie can respond to this mailing list also?<br>
<br></blockquote><div><br>Hi Jeff,<br><br>I don't see the issue which should be fixed within the cluster layer itself. The cluster layer <b>does</b> allow querying and it provides the same objects in queries, what we can see on the map (ie. one feature per cluster). This is exacly the same behaviour as what the other layer provides currently do. What we are talking about it to make the cluster provider extraordinary in some way to provide different result sets for the querying and the normal drawing operations. Doesn't it require a new RFC to establish this environment in the MapServer codebase? Or can we fix setting the query object in a consistent way which can be utilized by the cluster provider to establish this behaviour?<br>
<br><br></div></div>Best regards,<br><br>Tamas<br><br><br><div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div>