As I said, http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/examplePolygons.html works. What's different about yours?
The example is available online, so strings can be pasted into decoding utilities etc and otherwise inspected. Yours aren't, the groups interface may have distorted them. I tried reconstructing them, but the inner poly was just a squiggle not a closed poly. I guess that's just a mangling, but can't check your actual string. http://groups.google.com/group/Google-Maps-API/web/why-including-a-link-is-critical The example has identical opacity etc. for both polylines, yours doesn't. But I think this may be the root - The example has the outer first, and 'winds' it clockwise. The inner comes second, and is wound counterclockwise. In yours, both wind the same way, clockwise. Guru Mike has posted erudite things on winding and holes - http://econym.org.uk/gmap/chrome.htm#winding -- 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.
