This is directly applicable to my current project: we're using clustering and have different styles based on an orgid (an attribute on the vector feature). When defining the style for the cluster, we're currently assuming that all features in the cluster are in the same org and we use the orgid for the first feature in the cluster. This is a safe assumption in general but obviously not for those orgs whose boundaries are coincident (though we haven't seen that in practice - yet).
Clustering based on attributes would perfectly overcome this issue. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/OpenLayers-Strategy-Cluster-and-attributive-comparisons-tp5599286p5609195.html Sent from the OpenLayers Dev mailing list archive at Nabble.com. _______________________________________________ Dev mailing list d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-dev
