Thank you for the feedback! I figured it out 1 hour ago. It is precisely what you describe.
When you initialize the KML layer, you send a link to the Google Maps API with the location of the KML file. Because KML layer is generated serverside (when many markers) the Google servers of course need to be able to access the link. And a localhost link does not work of course. :) .nikolajp On Sep 29, 1:20 pm, Rossko <[email protected]> wrote: > If you are using the KmlLayer facility, you need to know that it runs > at Google's servers. Google needs to be able to access the KML file, > it won't work with 'local copy'. -- 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.
