Hi Jeff,<br><br> 'Cluster:FeatureCount' would be added to the CLUSTER layer as an additional attribute. In this regard it can be used as the text data when labelling the features, I imagine something like:<br><br>LAYER<br>
TYPE POINT<br> NAME cluster<br> CONNECTIONTYPE CLUSTER<br> PROCESSING "SOURCELAYER=layername"<br> CLASS<br> EXPRESSION ([Cluster:FeatureCount] > 1)<br> TEXT ([Cluster:FeatureCount])<br> LABEL<br>
...<br> END<br> END<br> ...<br>END<br><br>I would prefer this option to work even with the STYLEITEM "AUTO" setting, where the styles for the source layer would be retrieved only for the individual shapes not for the clustered shapes. I hope I can provide a working example soon.<br>
<br>Best regards,<br><br>Tamas <br><br><br><br><div class="gmail_quote">2011/2/14 Jeff McKenna <span dir="ltr"><<a href="mailto:jmckenna@gatewaygeomatics.com">jmckenna@gatewaygeomatics.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello Tamas,<br>
<br>
This is a very interesting proposal. I often have a hard time to picture these changes beforehand, but I am trying to now and I have a question: when it comes to clustering, I think a common need is also to label the number of clustered points...and since you'll know how many features are combined according to your proposal (I see 'Cluster:FeatureCount' mentioned in the RFC) I believe we must also expose this clustercount in the label object. How I am not sure, but to me this will be a common need. Or is this mentioned in the RFC already?<br>
<br>
-jeff<div class="im"><br>
<br>
<br>
<br>
On 11-02-10 6:02 PM, Tamas Szekeres wrote:<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
Hi Devs,<br>
<br>
In reference to the feature request from WhereGroup<br></div>
<<a href="http://www.wheregroup.com/en/welcome" target="_blank">http://www.wheregroup.com/en/welcome</a>> we did some refinement in the<div class="im"><br>
specification and I've created MS-RFC-68<br>
(<a href="http://trac.osgeo.org/mapserver/browser/trunk/docs/en/development/rfc/ms-rfc-68.txt" target="_blank">http://trac.osgeo.org/mapserver/browser/trunk/docs/en/development/rfc/ms-rfc-68.txt</a>)<br>
which contains a reasonable implementation to this option without<br>
requiring significant modifications in the MapServer codebase and the<br>
current processing chain. With regards to the timing, I already have<br>
some working code in place which could be finished by the time of the<br>
feature freeze of MapServer 6.0 we are targeting now (feb. 28).<br>
<br>
</div></blockquote><div><div></div><div class="h5">
<br>
_______________________________________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
</div></div></blockquote></div><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>