Well, in my tests I have found that reversing the order of the co-
ordinates in a KML file has no effect, but creating the polygons
directly in JavaScript with the inner (or outer) polyline reversed
does resolve the issue. I don't know why this would be, but it
effectively renders the innerBoundaryIs element in the KML
specification unusable if you want to support WwebKit browsers. I have
abandoned KML now for this reason.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
