Importing Errors on Current.GPX

Your original attempt at posting the error message seems to have screwed up the forum software somewhat

You could try making a copy of current.gpx as current.xml and open it in Internet Explorer.
That will give you a 'tree' view of the file and help you decide if it really is a valid xml file. Microsoft's XML Parser will show you where the fault is, if it's a structural fault.

Unfortunately, most of Garmin's gpx files fail the official 'GPX' test (even when they're otherwise ok), because they reference the wrong schema location.
http://www.topografix.com/gpx_validation.asp

Thank you Phil,

my apologies if my original attempt at posting the error message screwed up the forum software somewhat, but I only posted it once and did not have any problems whatsoever in posting the question.

Thank you again for your help,will try XML Parser and see what I end up with.

The GeePeeEx Editor actually pinpoints the line and character number, but as I am a complete neophyte, it might take a while to really get to the bottom of it.

I have since deleted all my routes, and will retry. I have saved some information on "My favorites" from Google Maps, so maybe that's what is causing the problem.

Thanks for the help.

It was just an observation

Ok - if you've done that, there's no need to bother with the IE import - they both use the same parser.

It's unusual for the CURRENT.GPX to be corrupted. What other steps has it been through, other than just copying from the unit?

Phil,
I'm not sure he is talking about Current.gpx -- he originally said "custom.gpx"

Edit: I now see title said Current.

Sorry guys,

I did mean Current.gpx

Does that make a difference?

Thanks

X

No, Phil read it as you meant it, and he's the expert. I'm sure that he and GeePeeEx Editor can sort it out.

Did you catch his last question: " What other steps has it been through, other than just copying from the unit?"

Hi guys,

thank you for helping out. I didn't take any other steps other than copying from Garmin 760 to my hard disk.

Most of the POI's in there are from Google. I was trying to build a POI file of all the wonderful Greek places in Astoria, NY for posting here.

So, I went to Google, check the places that we usually visit (shopping, restaurants, etc) and for every place transferred to my Garmin.

Had no problems doing that. Could have I corrupted the file accidentally?

Thanks

Maybe you disconnected the Nüvi while it was still copying?

Of course, Current.gpx is rebuilt at every boot - so if you just repeat the copy operation, you should end up with a good file.

Thank you Phil,

I've tried this one as well, but finally it seems that the problem is with an invalid character in text format".

It is supposed to be character 1145.

Any idea what an invalid character could be? Maybe something in the name of the place?

Will the "&" symbol cause this problem?

Thanks again for the help.

It starting to sound like you've found a bug.

The Nüvi should be able to encode any special characters in its character set as XML. It sounds like you've found at least one that it gets wrong.

For example, it should encode ampersand as &

Thank you Phil,

I would be very happy to send you my Current.gpx if you would like to take a quick look and verify bug. It has less than 20 or so entries in it.

GeePeeEx pinpoints the character column, so I am going to start counting in Notepad. It might be easier to recreate at this point, even though I would surely like to know what is wrong with it.

Thank you again for all your help.

Yes, not a problem.

Send it to 'gpx at hornby.me.uk'

(swap the "at" for an "@")

Once again thank you so much for the help.

File e-mailed from my Gmail account.

It turned out to be easier using XVI32 from
http://www.belkaplan.de/opera/tools/xvi32.htm

I typed in the 'position in file' and ended up in the middle of a telephone number field that contained
EC 80 A8 E1 86 8E EA A4 83 E1 84 B8 04 3C

Whatever that's supposed to be...
...overtyping with spaces cures the problem.

The question is, how did those characters get there?

Interestingly, Internet Explorer manages to parse those bytes - though not as anything sensible.

Hi Phil,

thank you once again. I am not sure why the phone number ended up corrupted, but after you pinpointed the problem I went into the GPS and tried to edit the number manually. Could not even erase a single number, so I deleted the whole "Home Record".

Once the record was deleted, I was able to import the file without a hitch.

Courtesy of the all the free support I received adn the great features of GeePeeEx, I have also registered for the unlimited version of GeePeeEx.

Once again thanks for all the help.

Christos