I have to write a noddy guide to uploading from Strava DIRECT from a Garmin Etrex 20/30. Can someone tell me whether the GPX files are stored in the same location as per the Dakota, ie. the /GPX/Current and /GPX/Archive directories?

Also, are they named in a similar fashion with Stopwatch- prefixes.

I can have a play later to check, but have never done it from Strava to device.

As Strava (or possibly my browser plugin) doesn't support the Etrex, when downloading to Strava direct from the device, I have to browse to GPX/Current to select the file I want.

Thanks, those are exactly the instructions I am writing. I am pretty sure that the Stopwatch files are always in archive.

Ah, ok I misunderstood the initial request (uploading from Strava vs uploading to Strava)...

The stopwatch thing doesn't sound familiar, but I don't use the archive much unless it auto archives.

Yep, to upload directly from the etrex, just browse to the GPX folder (exactly the same folder that you've put the track in that you want to follow) and, unless you've renamed it when saving it, it will be called something like TRACK_date_time. Haven't got mine in front of me now but do it all the time. The Garmin plugin doesn't work with the etrex for some reason so you always have to browse and upload as a normal file.

Edit to add you have to save the track on the etrex before you can upload it. You can't just upload the current track.

AFAIK the Garmin PLugin only works for uploading .FIT files. I only found this out after enabling the option to save tracks as both .FIT and .GPX on my Oregon whereupon it started working

ScotRoutes wrote:AFAIK the Garmin PLugin only works for uploading .FIT files. I only found this out after enabling the option to save tracks as both .FIT and .GPX on my Oregon whereupon it started working

That's odd (it is Garmin though and I always think the hardware outclasses the software... so guess I shouldn't be surprised) because AFAIK, .fit files are the compressed XML file (gpx, tcx etc.) So why they make a plugin that only reads the compressed file so then they have to uncompress it when the uncompressed file is sitting there seems a bit odd!