> I have > the data which is related to a particular cluster stored in an string > array.
I don't really understand what you mean by 'cluster' in this context. MarkerClusterer manages your markers for you; you create a bunch of markers and pass them to MC. MC then decides which markers are in view, which need to be grouped into clusters, which don't. Every time the view changes, this is recalculated. Clusters can form and break up as views change. There's no sense in some chunk of data permanently associated with a transient cluster. If you want to display a bunch of info about the markers that make up an MC cluster, you identify that at the time you want it e.g. on a click. You identify each of the markers comprising the (current) cluster and retrieve the info about each, and assemble the whole as you see fit. Perhaps each of your marker objects would have a unique ID property that you can use to index into an array. Or, perhaps each of your marker objects would have the actual data needed attached as a property. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
