If that's really what it says, the error Earth is returning is correct; there is an invalid entity encoding at the end of that key. That's a site problem, not an Earth one.
I suspect that what has happened is that the XML actually says & (like it should) and that we are only seeing the raw & because something somewhere along the line has interpreted it.
My KML file has & just fine but I'm still getting the "junk after document element" error.
Most users here seem to be experiencing the "junk after document element" problem rather than problems with uploading GPX files.
As I have previously diagnosed, when you use the URL that is in the NetworkLink with wget (of course, you need to hand-append the BBOX= to make it into a valid URL to GET) then you end up with a file that contains 2 (yes 2) XML documents. The first one seems perfectly valid. The second one contains the text that I have included in a previous post in this thread. It is this second XML document that constututes the "junk after document element" and is what is causing the problem in GE. The only place this XML can originate from is the geocaching.com web server.
It is curious that the coordinates in the second document are always the same (-122.34902, 47.620382, 0).
This just happens to be EXACTLY the coordinates of the Space Needle in Seattle, Washington!
There appears to be an event happening at this location on November 11 but, even more coincidentally, the notice for this event was published on October 26. This is the date when I (at least) started noticing the problems after it had prevously been working just fine.
Please can someone look at why the geocaching server might be producing a response that contains two documents?
Chris