FYI..... A friend of mine was parsing a gc.com GPX file using the GUI
front end. I'll leave the GPX file available for a few days. Once I
removed the offending value, it parsed ok.
Version => GPSBabel Version 1.1.1_beta09042003
Error Message => GPX: XML parse error at 18111: reference to invalid
Gpx Location => http://home.austin.rr.com/mcurry/gpx/error.gpx
Offending value =>
From: Robert Lipe <robertlipe@us...> - 2003-10-02 15:31:21
> Version => GPSBabel Version 1.1.1_beta09042003
> Error Message => GPX: XML parse error at 18111: reference to invalid
> character number
> Gpx Location => http://home.austin.rr.com/mcurry/gpx/error.gpx
> Offending value =>
This problem is known to everyone except seemingly geocaching.com,
despite numerous notifications to them. This defect in their GPX
generally croaks every GPX reader out there. It's caused by doodoo in
the logs or the cache pages. The XSD says those characters aren't valid
in those fields and will thus choke a validator or a validating parser
(like, uuuuh, most). Workarounds include editing out the offending
character or tinkering with the selection query to blow past the
offender. I've known people to go post 5 notes on a cache page just to
get the "naughty" log to roll off.
Feel free to drop a note to contact@... since I've clearly
worn out my welcome on this topic. Maybe more voices will get it heard.
FWIW, in private email to me, this and "I clicked on the program and got
a blinky black box" are about tied for the #1 support problem...