BaseCamp does not show which GPX file is corrupt

Former Member over 13 years ago

Sometimes a GPX file in a GPS gets corrupted. BaseCamp for Mac detects this, does not read the file and gives an warning pop-up to me

But this error only tells me that there is a problem with a file, not which file. So how do I know which file to remove?

Please show the directory and filename which file gives the error.

BaseCamp for Windows how ever does show the directory/filename, only BC for Mac leaves me in the clouds ;)

I can simulate a bad GPX file by transferring a Geocache wireless by Ant from my Montana 650 to my GPSmap62st. ANT received files are not readable by BC Mac/Windows or MapSource, but the GPSmap62 has no problem with the data. I created a notification of this behavior already to the 62/78 beta team.

0 PSEABOLT over 13 years ago

I have used Apple disk utility to repair the volume on my Dakota a couple of time. Worked for me both times but I was dealing with low value data. You might want to get a second opinion before you try. Note my problem was different, the volume would not mount until I ran disk repair on the Dakota.

0 Former Member over 13 years ago

I have no disk problems ;) I have "corrupted" GPX file problems ;)

The first post has now the gpx files

0 azdrmn over 13 years ago

Sometimes a GPX file in a GPS gets corrupted. BaseCamp for Mac detects this, does not read the file and gives an warning pop-up to me

But this error only tells me that there is a problem with a file, not which file. So how do I know which file to remove?

Please show the directory and filename which file gives the error.

BaseCamp for Windows how ever does show the directory/filename, only BC for Mac leaves me in the clouds ;)

I can simulate a bad GPX file by transferring a Geocache wireless by Ant from my Montana 650 to my GPSmap62st. ANT received files are not readable by BC Mac/Windows or MapSource, but the GPSmap62 has no problem with the data. I created a notification of this behavior already to the 62/78 beta team.

BaseCamp for the Mac has always printed GPX format errors to the console. That should include the file, line and char # on that line.

0 Former Member over 13 years ago

I don't know anymore if I was looking at BC 3.3.2 or 4.0.0.x but with these files BC for Mac it did not show the file information with me.

62-78 beta team has the files also, and they did confirm me that something was wrong, which they will fix.