Error Exporting to File

Update: Tried installing basecamp on a different computer and having the same problem. On the first export, basecamp will generate a gpx file (that seems to contain corrupt data). On the second and subsequent exports I receive the "error exporting to file" dialogue. :(

Seems to work OK for me on my 2007 iMac running OS X 10.8.3 using BaseCamp 4.1.1.0.

What version of BaseCamp are you using?
What version of OS X are you using?

How have you determined that the data within the export file is corrupt?

Have you tried selecting different data or even just starting with a single data point of a single type?

Hi Jack,

Basecamp 4.1.1
OSX 10.8.2

I think I have isolated two separate problems.

First, when I select "Export Selected User Data" the save dialog automatically highlights the previously exported gpx file and the export fails every time. If I click around and unhighlight this previous export, the new export works fine. It's as if by default basecamp is trying to write a gpx file into another gpx file. Clearly a bug in basecamp...

The second problem is that when I upload a track to Strava, I get an alert that says "Error Processing Activity." Now I did have one or two exports that were processed correctly on Strava and I believe they were both exports of "Activity Logs" rather than saved tracks. I opened the gpx files of an activity log next to a saved track and discovered that activity logs contain time data but saved tracks do not. Not sure why Garmin strips time data when you save a track, but this may be the problem.

Hi Jack,

Basecamp 4.1.1
OSX 10.8.2

I think I have isolated two separate problems.

First, when I select "Export Selected User Data" the save dialog automatically highlights the previously exported gpx file and the export fails every time. If I click around and unhighlight this previous export, the new export works fine. It's as if by default basecamp is trying to write a gpx file into another gpx file. Clearly a bug in basecamp...

The second problem is that when I upload a track to Strava, I get an alert that says "Error Processing Activity." Now I did have one or two exports that were processed correctly on Strava and I believe they were both exports of "Activity Logs" rather than saved tracks. I opened the gpx files of an activity log next to a saved track and discovered that activity logs contain time data but saved tracks do not. Not sure why Garmin strips time data when you save a track, but this may be the problem.

I agree that there is a problem with "Export Selection" to a file but mine is a little different than yours.
I am using WinXP SP3 & BaseCamp v4.1.2.

In My Collection I have a folder named RACES.
In RACES I have a folder named 50 MILES.
In 50 MILES I have several races as Lists named Shanghai, Prescott, etc.
Each of these Lists has several separate loops named Loop1, Loop2, etc

When I select the entire list of Shanghai, etc the "Export Selection" is not available. Only Export 'Shanghai' is available and I get a good GPX file of the entire race with all waypoints and loops.

Now comes the problem I have.
When I select a single loop1 from Shanghai or any other race then "Export Selected" becomes available and I get a file with NO EXTENSION.
A totally unusable file. Is that similar to what you get?
I did add .gpx to it and it became usable but that should not be the way it works. "Clearly a bug in basecamp..." like you said. :D

About your 2nd problem with saved files from your device that have no timestamps. You are correct, files must have timestamps to be loaded into Strava or Training Center or Garmin Connect etc.
On older devices like GPSMAP, the timestamps are stripped and points filtered to 250 or 500 to make smaller files to improve the number of tracks you can save. Like you already found out, the Activie Log has all the timestamps and points and will load just fine.
My remedy is I never save my ride on my GPSMAP. I download the Active Log and then clear the tracklog for the next ride.

Hm, nope, not the same problem. Yes, the file extension should definitely be there by default. :)

...I think I have isolated two separate problems.

First, when I select "Export Selected User Data" the save dialog automatically highlights the previously exported gpx file and the export fails every time. If I click around and unhighlight this previous export, the new export works fine. It's as if by default basecamp is trying to write a gpx file into another gpx file. Clearly a bug in basecamp...

The second problem is that when I upload a track to Strava, I get an alert that says "Error Processing Activity." Now I did have one or two exports that were processed correctly on Strava and I believe they were both exports of "Activity Logs" rather than saved tracks. I opened the gpx files of an activity log next to a saved track and discovered that activity logs contain time data but saved tracks do not. Not sure why Garmin strips time data when you save a track, but this may be the problem.

Addressing the 2nd problem (no timestamp on saved tracks): Alas, that is a device specific problem. My guess is that the hardware guys were trying to save space back when memory was expensive for devices. In any event if you get a copy of GPSBabel from www.gpsbabel.org AND download the entire User Manual in PDF format AND then look at page 137 you will see there is a way to add fake timestamps to your saved tracks. I've not done it on the Mac but I did it a lot on my Windows machine. Should work. GPSBabel can do some really neat stuff if you take the time to learn it.

As for the 1st problem: if I do a sequential export of the same user data, e.g., "track 001" it will suggest the same name but when I actually attempt to export it again the operating system will come back with a message asking me if I want to overwrite the file. If, on the other hand I select "track 002" after exporting user data "track 001" my system will suggest "track 002" as the file name not "track 001" as yours does. Sorry, I am clueless why yours is doing that. I might suggest a disk permissions repair and perhaps a reinstall of Basecamp but they are just guesses.

As for the corrupted data, double click on the track you want to export and look into its details. Check the track points list for rows with empty time and speed (ignore the last point). Delete those empty points. Export the data. Problem fixed.