On Nov 30, 8:39 pm, Chad Killingsworth <chadkillingswo...@missouristate.edu> wrote: > > The tile latency will mask the extra CPU usage, but, why compute > > identical tile offsets in different OverlayViews ? > > I did consider this while developing, but the math for the tile bounds > calculations isn't that intensive. I opted for ease of implementation > on options such as visibility, zindex and event handling as well as > trying to keep the code easy to understand. For each draw event on the > overlay, calculating the tile coordinates and bounds was taking around > 12ms for the first time the code executed, then 1ms for each > subsequent draw event on an iPhone 3G (I used this because of the > slower processor and lower memory).
For a handful of tile layer overlays, it may not matter. I am using the same code for polys where it matters a lot. I cannot imagine the overhead of separate OverlayViews with separate event listeners for every state in the United States or even every province in Canada. I cannot imagine the overhead of individual CANVAS elements for every poly. A single common OverlayView enables polys to be combined in the same CANVAS elements. > > The tile sets may originate from different servers like: > > > www.polyarc.us/sparse > > I was considering the option of having a server proxy requests and > dynamically composite the tiles together into a single image. Great idea, especially if you have a campus WiFi network. You could cache common combinations. You could bypass the AT&T network for students on campus. > > A general solution ought to support Internet Explorer 6. It ought to > > compensate for getBounds errors at low numbered zoom levels. It ought > > to calculate tile offsets correctly for maps spanning the > > International Date Line. > > All of these points are correct - and something I plan on looking > into. Although I'm not really that thrilled with spending a lot of > work on the IE6 support. It's less than 5% of my total traffic. But a > complete solution should handle it. I agree, IE6 is a PITA but a lot of people still use it. -- 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...@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.
