Okay, it seems like I was using a slightly old version of egeoxml.js, and by using the newest version this problem disappeared.
Thanks anyway, Andrew On Mar 2, 3:42 pm, AGD <[email protected]> wrote: > Oops. Here's version that passes HTML validation, same problem > though: > > http://agdarby.com/nrdc/gmap.php?state=New_Hampshire > > I assume that my polygons are OK, since the KML file works fine when I > use your viewer. Therefore, something's wrong with my use of egeoxml, > I guess. If you view the source of that page, there's hardly any > JavaScript anymore . . . . > > Any ideas? > > On Mar 2, 2:41 pm, Rossko <[email protected]> wrote: > > > >http://agdarby.com/nrdc/existing.php?state=New_Hampshire > > > The HTML is badly invalid, whether in an iframe or standalone, so that > > isn't going to help. > > > >http://agdarby.com/nrdc/states_existing/New_Hampshire.kml > > > Seems to work ok in this > > viewerhttp://greg-koppel.site88.net/maps/kml_test.html > > I'd fix the HTML and see what's left -- 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.
