Thanks Brendan, FireHawk, and Zipp for your suggestions.
Here's an update, I installed both Firefox 4 and Chrome 10 and
confirmed the problem "Google Error - 400 Bad Request" does NOT exist
with Chrome or Firefox, but was still present on IE 8. Given that I
was installing all the latest browsers, I decided to install IE 9 and
the problem was not present with IE 9 either. However, there's an
interesting observation regarding performance, both Firefox and Chrome
imported my ~ 200 <Placemark> KML file in less than 1 second, whereas
both IE 9 and 8 took ~ 15 seconds to do the same import. I cannot
imagine what is going on inside IE 8/9 that is taking so long, but it
is consistent and happens on many different PCs, whereas Chrome/
Firefox its always < 1 second. Unfortunately, most of the 200 or so
"users" have plain ole PCs with IE, thus they run into very long load
times to look at these maps. Anyhow, thanks to you the original
problem is resolved.
Thanks - mike
PS Brendan - Unfortunately I cannot share the KML ... the "user group"
considers name, address, phone number info contained in the KML
confidential. As an FYI the KML is generated via a 2000 line Excel
macro that accepts an Excel workbook (and a separate GPS relocation
correction workbook, GPS relocations are needed due to the remote
locations which have many long/lat errors). Given name, address,
phone, email heading names ... the macro generates KML which works
great. GE is definitely very cool, prior to this the user group was
maintaining maps by hand and they where never right due to human
transcription/mapping errors.
On Mar 30, 5:50 pm, Brendan Kenny wrote: