Glad I could help - even a little. - You are correct in that many maps implementations end up writing their own throttling methods for events like "bounds_changed".
- The timeout of Google's servers in regards to kml file fetching is a frustration many face and your local caching solution sounds plausible. - Highlighting the kml feature just clicked may prove challenging. You'll probably have to just place a duplicate marker on top of the one they clicked. So no - not straightforward. - Loading feedback should be straight forward. I believe there is an event that gets triggered when the KmlLayer loads, but I can't remember for sure off the top of my head. The hard part is there is no real way other than a setTimeout to determine that the layer failed to load. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/GMjZR-mwX2cJ. 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.
