> Now, since the thing actually works in IE. and best practices to make > this load faster?? Still takes quite a bit of time in IE and I'm not > sure I'm using MarkerCluster to the best of its abilities.
It won't make it go any faster overall, but it would be good practice to seperate data from presentation. Are your locations all hard coded into the webpage, or is that being generated server-side from some store? Using an AJAX technique to deliver the data seperately allows some appearance improvements - less bloat in the base page, get to see something sooner. The underlying problem is so many markers. Consider a change in the user view ; when the whole US is in view, just plot a single big marker per state with a count. Click one to zoom in to that state and display individual markers. Marker manager may be better at that sort of thing, allowing to have a set of 'state' markers that display at some zoom levels and a set of individuals to display at higher zooms - these could still be clustered. A fairly crude example http://gmaps-utility-library-dev.googlecode.com/svn/trunk/markermanager/examples/google_northamerica_offices.html -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
