There's a bit of insight into how KML tile-based display works here: http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/d7a3e542c09200aa/51ae45bfed902d36 we might guess that different browsers on differently loaded PCs could construct different URLs for the same tile image, the IDs could possibly be in a different order depending on the order in which the API completes multiple almost-simultaneous KmlLayer setups?
More guessing, Google's server may render new tiles for different URL requests even if the logical content should be the same. Really, Google _should_ construct new tiles to honour the layer ordering. It has been noted before that KML rendering is ruthlessly picky about response times when fetching images and KML files. Maybe your own server or network load went up a few weeks back, maybe Google tightened the timeouts. It may well be your redirect is adding lag. -- 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-v3@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.
