Thanks! On the first load it came right up, but after reloading it a couple of times some of the tiles didn't come up (just like on mine).
So I'm convinced the problem is anytime the processing is off-loaded to the Google servers. I think my data sets are small enough that they'll work in all but the slowest computers, so I can have all the interaction be between my server and the client and leave Google's servers out of it. It looks like geoxml3 is going to be my best bet. Thanks for the quick response, Brian On Feb 9, 9:49 am, Joseph Elfelt <[email protected]> wrote: > Brian, > > Here is your sample kmz file displayed with my app (API 3.3). It > seemed reasonably fast and smooth when I tried > it.http://www.mappingsupport.com/p/gmap4.php?q=http://www.freeatvmaps.co... > > Are you seeing a significantly different response in terms of speed or > smoothness? -- 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 [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-js-api-v3?hl=en.
