Editing track leads to it not being recognized by Garmin Connect

One more that I have found:

If I use Basecamp to remove the first few track points in a track (while I was fussing around the car before starting my bike ride) then Basecamp will change the name to something other than the new start time in the gpx file. Garmin Connect will then not accept the file.

I cannot reproduce this. The name of the track doesn't get changed by BaseCamp when removing track points (or at least I could not get it to).

Could you provide a sample track and the exact steps to reproduce this?

I will also be moving this to a separate thread.

Here is a recent file. It is original. The behavior is not quite the way I described it but is still a problem nonetheless.

I open the file on my GPS (Garmin Oregon 450) in Basecamp and remove the first two data points where I have not moved yet.

Then I open Garmin Connect and try to upload the file manually. I get an error with no reason given.

If I try to upload the file without the changes (without removing the first two points) then there is no problem.

The name of the file is not changed by Basecamp but somehow makes the file unable to load into Garmin Connect.

Have you been able to duplicate this problem yet?

I apologize for the late response.

I cannot reproduce the issue with your track. I loaded it up in BC 3.2.1, removed the first two points (the ones with 0 length) and could upload it just fine.

Were you using BC 3.2.1?

Be advised though that currently BaseCamp will strip heart-rate and cadence data. This should be fixed with the release of BC 3.2.2 (which will be released "soon").

Yes, I am using 3.2.1. Thanks for trying.

Yes, I am using 3.2.1. Thanks for trying.

That is odd. Have you tried this again? GarminConnect seemed to have gotten a few updates recently. Maybe they fixed the issue?

If it still doesn't work, can you send me the gpx file that it fails to accept?

Here is one. It has already been uploaded to my account so Garmin Connect will not allow me to upload it again. I get the message that it has already been uploaded. I did this twice to make sure the file was OK. Then I removed the first two points and tried again. This time I got the message that an error had occurred. Give it a try.

Thanks

I'm experiencing a similar error when uploading to Garmin Connect. The error reads "An error occurred with your upload. Please try again"

I use Base Camp to connect, download and edit the data, stripping out the dead time before and after the activity. The track is then saved as a gpx then uploaded to Garmin Connect where the error occurs.

My workaround is to open the exported file in Map Source and save as a gpx without any modification. Doing this is successful with Garmin Connect. This is a workaround I'd rather not do. Can you please help?

I'm using a GPSMAP 62S 3.4, Base Camp 2.3.0.0, Map Source 6.16.3.

I've uploaded 3 files named according to the source as discussed.

Hello Forkbender,

The problem is not in the editing of the files in Basecamp.
Neither the Original nor Basecamp gpx files would load into Garmin Connect for me.
The MapSource gpx file loaded into GC just fine.

The problem was in the first line of the xml file headers. If you right click a gpx file and pick "Open With > Word Pad" you will see the xml file that makes up the gpx file.

MapSource has the first line correct.
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>

Original.gpx (from BaseCamp I assume) and BaseCamp.gpx (edited in BaseCamp) are incorrect with
<?xml version="1.0" encoding="utf-8"?>
They are both missing standalone="no"

If you add standalone="no" in with spaces on each side just like MapSource, the gpx files Original and BaseCamp load just fine into GC.

The problem appears to be in the BaseCamp software code when you do a Save As to a GPX file. I do not use BaseCamp but if there is the option in BaseCamp to do a Save As to a TCX file you might try that and see if the first line comes out correctly and loads into GC.

Thanks for the response, Don,

I've been reviewing everything else in the xml file for just such an error. This got me thinking about how exact the syntax needs to be with xml, even as much as case context.

What I noticed is the in both the original.gpx and basecamp.gpx is the the first line contains <?xml version="1.0" encoding="utf-8"?> where utf is lower case. On a hunch, I changed this to uppercase and reading <?xml version="1.0" encoding="UTF-8"?>. I didn't add the standalone attribute so that it would test independently.

Garmin Connect accepted the file with the change to uppercase. Thanks so much for your help. If someone from Garmin is reading, would you please confirm this and hopefully change it in the next version.

Thanks,

Wayne