No, it's not about the .kml: I've changed the endpoint but it still doesn't work.
I don't see anything also if I put a legit kml URL in <href>. Another thing I can't explain is in the web server log. If I browse to http://maps.google.com/?q=http://ousia.mine.nu/hen.kml I read only the *two* expected calls in my log: the first is the get (of course by Google servers) of http://ousia.mine.nu/hen.kml the second is the get (with BBOX in the query string) of the <href> in hen.kml If I browse to http://ousia.mine.nu I read in the log: the gets (by my browser) to retrieve the index page and the resources (as expected) the get (by Google server) to retrieve the hen.kml (as expected) two gets (by Google server) to retrieve the <href> of hen.kml (these gets no not have BBOX in the query string) and then, in the same second, a lot (at least 15) gets (by 66.249.82.65, a Google server) to retreive - again ! - the hen.kml Again, I can't understand what's going on. Any ideas? On Sep 3, 6:15 pm, Joseph Elfelt <[email protected]> wrote: > The networklink in your kml file now says: > <href>http://ousia.mine.nu/hen/get_kml</href> > > I do not believe that is a valid URL to a KML file. A valid URL would > end in .kml > You appear to be trying to run some kind of code with that line so it > is little wonder that it does not work > > Just for fun, try entering a legit kml URL in your <href> tag -- 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.
