The entire map is 8,000+ miles of ATV trails covering the state of Utah and would be on the order of 50MB to 100MB (as a zipped KMZ). That's why I'm only dynamically serving up what the visitor is currently looking at (with the options they currently have selected to be included in the view).
Thanks for the heads up on viewing the headers with wget, that is very helpful. I've turned back on the caching, and I'll leave it on and see what happens, but it doesn't seem to make any difference. Chrome and Safari seem much more consistent in downloading all of the tiles. The problem is definitely not with the Google servers getting my KMZ file, it's with the tiles getting generated or getting back to the client. Here is a debug URL that makes this very clear: http://www.freeatvmaps.com/atv-trails/straight-canyon-crawford-pass-loop/polydebug/ At that URL I've added a transparent polygon that covers the entire viewport. It is very easy to see which tiles load and which don't. If there was a problem with the Google servers getting the KMZ file from my server (or with caching) none of the tiles would come through. They're getting the file, and parsing it completely, but not all of the tiles are getting back to the client (with FF and IE being the worst offenders or most susceptible). Thanks! I really appreciate the thorough help and insights. -- 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.
