Hi guys, thanks for your responses. Yes, this is consistent with what I'm seeing. However, it does not stay fixed forever. I looked back at my example ID 447 again today, and again the same behavior. The first time I look at it, it's drawn incorrectly. Wait 60 seconds, reload, then it draws fine for quite some time.
I'm not sure how Google is caching a bad copy, again, the data doesn't change between requests... So this does not appear to be a problem that will just resolve itself unfortunately. Any other ideas? Should I report this as a Google Maps bug? If so, where do I do that? Thanks, Matthew On Sep 17, 7:05 pm, Mike Williams <[email protected]> wrote: > Wasn't it Grok Lobster who wrote: > > > > >I tried a half dozen or more IDs and never saw any crazy polygons. > >It's a stretch, but perhaps your video card isn't up to the task. Have > >you tried another computer and experienced the same anomaly? > > I managed to find two IDs that exhibited the problem: 400 and 650. The > problem was visible in all my browsers. The problem went away at the > same time in all my browsers. > > That's consistent with my theory that there was a bad copy in the > maps.google.com cache. If that is the case, then once the cache fixes > itself, everyone will see the correct poly. > > -- > Mike Williamshttp://econym.org.uk/gmap --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
