Thanks Larry for checking on this. Actually its still not working. I should have been more specific about which KMLs aren't working. The Hiking and the Equestrian KMLs aren't loading. Last week on Friday Hiking magically started working, but now it is not. They all worked fine up until last week. I've tried changing between the different versions 3.2 --> 3.5. It wouldn't even load the map using 3.2 and I didn't notice a difference between 3.3, 3.4 and 3.5.
Here are the KML locations -- http://daviscountyutah.gov/trails/trailheads17.kml http://daviscountyutah.gov/trails/trails_proposed4.kml http://daviscountyutah.gov/trails/trails_equestrian.kml http://daviscountyutah.gov/trails/trails_hiking.kml http://daviscountyutah.gov/trails/trails_motorized.kml http://daviscountyutah.gov/trails/trails_class1d.kml http://daviscountyutah.gov/trails/trails_class2.kml http://daviscountyutah.gov/trails/trails_class3.kml Larry was it taking a long time for the Overlays to load? They used to load almost immediately now it takes 20 seconds or so. Thanks for your help! On May 16, 2:15 pm, "[email protected]" <[email protected]> wrote: > On May 16, 12:25 pm, daviscounty <[email protected]> wrote: > > > I am using Google maps to trail data and am loading routes exported > > out of ArcMap using' Export to KML'. I've had this > > working for 6 months, but last week I noticed that the maps was > > loading really slowly and the kml overlays even slower. Some were not > > showing at all. I double checked that the my map links were correct > > and up to date, and double checked that the code hadn't changed. > > > I looked on friday and one of the KMLs that wasn't loading seemed to > > work, and just checked > > again, now it doesn work. Here are a couple of links: > > > -http://daviscountyutah.gov/trails/ > > That seems to be working for me, I was going to suggest you try v3.4 > rather than the "nightly" development version (add v=3.4 to the URL > that includes the API), but I see you are doing that. Is that what > fixed it? > > Larry > > > > > Is there something going on with Google's servers that I am unaware > > of? Was there an update that I need to take into account to handle > > things differently when loading kml overlays? > > > Thanks for your help! > > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
