Re: [Gpsbabel-misc] Google Earth Error

[Robert L. <rob...@gp...>]

On Thu, Aug 5, 2010 at 12:52 PM, Maarten Sneep <maa...@xs...>wrote:

> Please reply to the list.
>
> On 5 aug 2010, at 19:44, Paul McCarty wrote:
>
> > When I use a Garmin MapSource - gdb as the input file to convert to
> Google Earth (Keyhole) Markup Language I get a “translation successful”.
> >
> > gpsbabel -w -t -i gdb,ver=3 -f C:/Documents and Settings/Paul
> McCarty/Desktop/Philmont2.gdb -o
> kml,lines,points,line_width=6,line_color=99ffac59,floating,extrude,track,trackdata,trackdirection,units=s,labels,max_position_points=0
> -F C:/Documents and Settings/Paul McCarty/Desktop/Philmont2010.kml
> >
> > Translation successful
> >
> >  When I try to open the new file in Google earth I get the attached error
> message.
> >
> > I don’t know what other information you may need. I hope that this
> cleared just a little bit of the fog in your crystal ball.
>
> No, this didn't help one bit. A fragment of the resulting kml file might be
> useful. A link to the offending gdb file might be helpful in trying to
> reproduce the issue. Which version of GPSPabel do you use.


While Maarten's suggestions on how to ask effectivel questions are all
spot-on, my crystal ball has  stronger super powers.  In it, I see input
that needs to be entity encoded (such as an ampersand or angle brackets) and
GPSBabel 1.4.1.

>From the last time we had this discussion -

Problem lines in the resulting kml file look like this:
> <description><![CDATA]<a
> href="http://radreise-wiki.de/Paris-Leuven-Venlo-Wesel#Binche
> ">Paris-Leuven-Venlo-Wesel</a>]]</description>
>

Two unfortunate typos make this fail.  You can manually fix the files
manually with a text editor.  Just replace "CDATA]" with "CDATA[" and "]]<"
with "]]><"

I've fixed this in the source; it'll be in the next beta or official release
I make.  I haven't set a schedule for that as this seems to be the only real
ankle-biter in 1.4.1 and it's affected a low number of users.

RJL