hey guys - the problem is, 10+ second load time for building the map is never going to make anyone happy it seems like the method of having the maps summarize points is not really a high performance solution in the end. is there a way to ajax load the secondary point data so that the map build is super fast?
for an example of what i mean by "high performance" this map we built (with tiling, not points) loads hundreds of thousands of points in 3-4 seconds http://fundrace.huffingtonpost.com/ know what i mean? avaaz is fighting a similar problem here: http://www.avaaz.org/en/sept21_hosts/ its ok because the rest of th epage loads quickly, but its not relaly that ok to have a 15+ second load time On Aug 30, 5:00 pm, richard <[email protected]> wrote: > On Jul 23, 3:24 pm, Mike Williams <[email protected]> wrote: > > > > > > > It looks like you're preloading the infowindow contents before creating > > themap. Your infowindows contain huge images which are then scaled > > down. E.g. > > > http://www.sundialsociety.org.uk/images/Kent/S3009.jpg > > > is 685kb. Themapdoesn't get loaded until the "onload" event triggers, > > which occurs after all those 15 large images have been fetched. > > > You endupdisplaying the image at 300x225 pixels, so you could save a > > lot of time by creating images of that size rather than 1648x2331. On a > > slow connection that could take quite a while. > > > Skipping the preloading of the infowindow contents would also allow the > >mapto display earlier in the proceedings. The downside would be that > > there would be the normal slight delay the first time each infowindow is > > opened as the image gets fetched, rather than the current instantaneous > > photo display. > > > The underlay trick should work as long as yourmapdiv with underlay > > appears before you start preloading the infowindow contents, which > > appears to be the way you've got it configured. I don't know why that > > wouldn't work unless you repositioned yourmapdiv at the same tile that > > you added the underlay image. > > > -- > > Mike Williamshttp://econym.org.uk/gmap > > Many thanks for that Mike. I changed the width to 400 (as per the > other images in the site) and the reportedloadingtime went down from > 60-90 seconds to about 20 seconds. We are likely to haveupto 20 > sundials in one location (e.g. mass dials scratched on church walls) > in the longer term, so populating the info windows at the time they > open is probably the way to go for the future. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
