Corrupt xx.GPX Archive file

 

I use the archived "xx.gpx" files to go back and remember where I was on my work travels (I loose calenders). I have one GPX file that will not open in Mapsource. A Mapsource popup comes up and says "xx.gpx is not a valid Mapsource file and could not be opened."

Anyone know of anyway to recover this file?

Opening it in NOTEPAD It looks like the header info starts the same and the file ends the same as all of the other gpx files.

I wonder where I went???

Thanks,

--
Harley BOOM GTS, Zumo 665, (2) Nuvi 765Ts, 1450LMT, 1350LM & others | 2019 Harley Ultra Limited Shrine - Peace Officer Dark Blue

.

Try opening it in EPE, and see if it's corrupt there as well. If not, use Save As and call it a different name to preserve the original file. Then, try to open it in MapSource again.

--
nüvi 3790T | Those who make peaceful revolution impossible, will make violent revolution inevitable ~ JFK

It says it loaded in EPE but

It says it loaded in EPE but as it is an archived track file I don't see any information displayed in EPE.

Thanks,

--
Harley BOOM GTS, Zumo 665, (2) Nuvi 765Ts, 1450LMT, 1350LM & others | 2019 Harley Ultra Limited Shrine - Peace Officer Dark Blue

.

EPE won't display tracks. Just try what I suggested to see if it avoids the error in MapSource.

--
nüvi 3790T | Those who make peaceful revolution impossible, will make violent revolution inevitable ~ JFK

I tried a good file and my

I tried a good file and my bad file and they both load 100%, don't display anything and both give a "run-time error 52" when I try to "Save As".

--
Harley BOOM GTS, Zumo 665, (2) Nuvi 765Ts, 1450LMT, 1350LM & others | 2019 Harley Ultra Limited Shrine - Peace Officer Dark Blue

.

OK, at least you know now that the file was not caused by program errors, and is not correctable in that way. I always try work-arounds for files I want to recover. Sometimes it works, other times not.

--
nüvi 3790T | Those who make peaceful revolution impossible, will make violent revolution inevitable ~ JFK

Found a corrupt line

Thanks Juggernaut for answering. Unfortunately it kind of bugged me that 1 file out of 30 or so was corrupt. Since I could only open it in Notepad I started teaching myself a little about the track file format. I then started by extracting different groups of tracks from the file, saving it and trying to load it in Mapsource until I found the track it didn't like. Sure enough in the middle of 33 or so tracks the GPS wrote a totally incorrect line into the original file that I corrected and now I can read the whole file into Mapsource.

Like I said, it bugged me so I kept going 'til I found it. And I know more than I ever wanted to about the file format.

Thanks,

--
Harley BOOM GTS, Zumo 665, (2) Nuvi 765Ts, 1450LMT, 1350LM & others | 2019 Harley Ultra Limited Shrine - Peace Officer Dark Blue

If It Happens Again...

Google Earth can process track logs (either from your Zumo or Nuvis directly or as GPX files) and display the route(s) you travelled on the map.

It may or may not give you more infomation than Mapsource about errors in corrupted GPX files...

--
Nüvi 2595LMT

Corrupt track log

I found something similar on my 1390LMT.

First I did not even know the 1390 did track logs. But when I saw the size of the current.gpx file, I knew that must the reason for the larger file size.

When I tried Google Earth to load the file it complained about the file being corrupt. Mapsource would not load it either, but gave no reason why. GeePeeEx could not load it either but it gave me a file position for the error. With that I could examine the file, go to that position in the file. A section of the file had more than 1000 bytes with binary zeroes.
I used one of my programs to create a new file without the zeroes, and making sure the xml structure was correct.

This new file I could now get Google Earth to load and display the tracks. Mapsource still refused to load it. Now it was getting interesting. Now using another program I reformatted the gpx file into a new file which I could edit in WordPad. The original gpx file has a few very long records and no line breaks, so it's impossible to edit and make sense of. I needed a file with each level on a new line.

A trkpt structure has values for these elements:
lat, lon, ele, time, speed, course.

Starting to work on the new file I could see lot of instances where the speed node would have a timestamp value or a course value (I am pretty sure I have not been going 270 mph lately). I also found the other nodes in the trkpt structure to have bad data. The lat and lon values seemed always to be correct.

So YES, I would say that the file was majorly corrupt.

I'm guessing that Google Earth only checks the lat and lon values to be able to plot the track, while Mapsource validates the other values to be at least of the correct form.

I have cleared the track log and will check after a trip this weekend what the track log will look like after that.

I will report back of my findings.

If the same thing will happen again the track log won't be of much use for me.

JCA