Renaming the file to .kml should be the easiest option. If it doesn't work, post back with a link to a demo page that uses the .kml file that doesn't work.
Also try deleting the comments on lines 2-4 of your file. On Thursday, 5 April 2012 02:04:53 UTC+10, rmcguire wrote: > > where do I set the content type at.....this just doesn't make sense > why this stopped working? > > On Apr 4, 7:37 am, rmcguire <[email protected]> wrote: > > which comments between the kml tags? > > > > On Apr 4, 4:53 am, "Enoch Lau (Google Employee)" <[email protected]> > > wrote: > > > > > > > > > It's not required that the file extension be .kml. But if it does not > end > > > in .kml, you can say that it is a KML file by specifying the > content-type. > > > If the content-type is not set and the file extension is not .kml, we > try > > > to guess whether it is a KML file by looking at the first little bit > of the > > > document - which is why removing the comments would help. > > > > > On Wednesday, April 4, 2012 8:05:36 PM UTC+10, [email protected]: > > > > > > On Apr 4, 12:11 am, "Enoch Lau (Google Employee)" > > > > <[email protected]> wrote: > > > > > We took a look and it appears that this file wasn't detected as a > valid > > > > KML > > > > > file by the rendering engine. To fix this, you could: > > > > > > > - Remove the comments between the kml & kml tags at the top of > the > > > > file > > > > Why would comments cause validation to fail? > > > > > > > - Rename to .kml > > > > This has never been required before. My server doesn't let me > > > > serve .kml; .xml files have always worked fine with Google Maps > > > > before. > > > > > > > - Set the content type to be Content-Type: > > > > > application/vnd.google-earth.kml+xml > > > > again, this is a change; plain xml has always worked before now (and > > > > continues to I believe) > > > > > > -- Larry > > > > > > > To assist with debugging, KmlLayer now has a status property: > > > > > https://developers.google.com/maps/documentation/javascript/reference... > > > > > In this particular instance, the status was INVALID_DOCUMENT. > > > > > > > Enoch > > > > > > > On Friday, 30 March 2012 00:06:27 UTC+11, rmcguire wrote: > > > > > > > > Could someone please look at my page at > > > > > >www.meadowlarkco.com/regulationsmap2.html > > > > > > and tell me why my borders around my states aren't showing up > and > > > > > > hence why my infowindows don't display? > > > > > > > > thanks- Hide quoted text - > > > > > - Show quoted text -- Hide quoted text - > > > > - Show quoted text - -- 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/-/723NRJ7mda8J. 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.
