Yeah, I know that Google's server is the one that retrieves and processes the KML file. Then it returns to the calling page via JSON. In the JSON overlayer collection instead of multiple overlays I only see one.
I'll try entering the URL into the location box like you mentioned... which location box? the Search box you mean? On Jan 6, 3:37 pm, Rossko <[email protected]> wrote: > > Using a proxy tool I can see my KML file being read and parsed > > properly byhttp://maps.google.com/gx?q=URL_TO_MY_KMLfile. > > You're using GGeoXml. The URL above is NOT parsing your file, it is > sending the location of your file as an argument to Google's servers. > Which should then read and parse your file. So if you're checking for > accesses, there never will be an access of your KML file from your > client script. > > It is possible that the snag lies in that area (i.e in the Google > service). > To test, you can paste the full URL of your super-top-secret KML file > directly into the location box of maps.google.com, which should use > essentially the same rendering process.
-- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en.
