> > > From: bratliff > > > Slightly off topic, it is too bad neither VML nor > > > CANVAS has the ability to cache the building of > > > the same shape from a previous run.
> > From: Michael Geary > > Very true. PolyGonzo does a bit of caching here to > > partially make up for this. When it runs the loop to > > convert the lat/longs to pixel positions, it saves the > > results for each zoom level. If you pan the map, or > > zoom in or out and then return to the same zoom > > level again, it doesn't recalculate the pixel positions > > but uses the ones it has already calculated. > From: bratliff > In the same session you can have a separate DIV for > each zoom level with just one visible. Across sessions > each DIV is rebuilt from scratch. That's a good idea. We didn't do that yet because it didn't seem necessary for our use case with the election maps, since the source data for the polygon coloring was changing fairly frequently. > I believe Google avoids rendering the off-screen portions > of large polys. Are you doing anything similar? Yes, for the GOverlay version, we create the canvas element (or a div element for VML) at a size that covers the visible portion of the map plus a bit extra around the edges (1/3 of the map width or height) to allow for panning. For the static map version, it's exactly the size of the visible map. -Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
