On Oct 20, 2:44 pm, matthewmabon <[EMAIL PROTECTED]> wrote: > > Thanks both for the support so far. the KML file has remained > unchanged from its previously working state so the validity of the > KML's cant be to blame i shouldnt have thought!
Why not?! If Google have beefed up their validation to use the OGC 2.2 standard rather than their proprietory 2.1 version, then there could well be problems with your data. Surely the thing to do is to make your data 2.2-compliant? The GGeoXml parser is server-side, not client side, so if it's not a client problem (and you've tried many different API versions) it must be an issue with Google's server interpreting your data. What is a little disappointing is that there appears to be no way to determine whether GGeoXml has encountered an error: it returns a valid, but empty, overlay so that GGeoXml.loadedCorrectly() returns true. Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
