i've got exactly the same issue and tried the same steps with the same results (i could have written the op word for word!). not sure how to proceed from where i am (i.e. stuck).
one thing i've noticed that the file in garmin connect cannot be exported as a tcx file for manual upload to strava (other rides can) - it displays a http 500 error. can it be a problem on garmin connect side?
Dear,
Can you instead of sending me generic reply's who are only annoying and irritating me more just treat my query and solve it? Its now been over three days I have already found easily ten people having the same propblem. Starting to get vocal on the internet. What must we do to actually get treated correctly as a paying customer and not been just send generic copy paste answer? Must we get very vocal on facebook and twitter or can you just look into the issue correctly?
Kind regards
a probably soon to be former client who is getting close to recommend that to his friends to.
+1 here, ticket raised, bit frustrating!
I've fixed Strava upload, at the expense of lost cadence / HR in Strava. Not really an issue as this is available to me in RWGPS / GC (even though I used a Wahoo...).
Sorry I don't have time to write a full method however here is a summary:
1. Combine multiple FIT files and eventually get this into RWGPS (or maybe it was GC first - did this yesterday).
2. Export as GPX
3. Used https://simple-gpx.herokuapp.com with 2m resolution to reduce GPX to around 1.9MB (this stripped cadence/HR - will look at writing my own tool in the future or talking to Phil...)
4. Attempted Strava upload - again reported file already existed (ticket etc. raised yesterday)
5. Offset all timestamps by 1 hour. THIS SOLVED IT. I'm sure there must be an online tool to do this, I didn't have time to find one but this isn't too tricky in Python,
Here is my simple script for doing the conversion:
Its the sheer data size that gives the problem,
Quite some people rode it as one ride without sleep ;), I must admit I had one long beauty sleep after 700K.
How big is the actual file you're uploading to strava?
Sounds like strava has a poorly thought through max file upload size. Probably from the same sort of thinking that causes a lot of garmins to not like longer rides. "But who would have a ride that long? Noone does a 1200km ride and upload it in one go..."
J
RWGPS is showing something very odd with my files: my full PBP file which I combined using fitfiletools (https://ridewithgps.com/trips/39041788) is only showing data for the first 1101km - which is where I stopped my ride, but the map shows a track all the way back to the start.
If I upload separately, it shows https://ridewithgps.com/trips/39042179 and https://ridewithgps.com/trips/39042154
Weird.
Interestingly my Strava stats are showing my multiple PBP attempted uploads in my total distance for this year, but they're not appearing anywhere on my profile.It's also giving "--" for longest ride.
Quite some people rode it as one ride without sleep ;), I must admit I had one long beauty sleep after 700K.
The garmin file is 8MB and doesn't want to go through, My fittools created halves are 6.7MB each but sail through fine.
.fit files seem to be pretty damn efficient then. Just noticed the .fit file for last weekend's 300 is 1.8M, where as the GPX is 14M.
.fit files seem to be pretty damn efficient then. Just noticed the .fit file for last weekend's 300 is 1.8M, where as the GPX is 14M.
I wonder what arbitrary dice roll strava used to decide on the upload limit...
J
* do you have a power meter
* do you have Di2 (or eTap)
.fit files seem to be pretty damn efficient then. Just noticed the .fit file for last weekend's 300 is 1.8M, where as the GPX is 14M.
Surely there’s no need for the GPX file to be anything like that big, even for a 1200km ride? Is it not possible to run it through eg Phil W’s simplegpx tool to strip out extraneous data?
Except when it is...
I wonder what arbitrary dice roll strava used to decide on the upload limit...
GPX files are uncompressed XML, that is always going to be big (it compresses well though).
@Hofnar with your workaround you get two (or three) separate rides in Strava I suppose? It doesn't get merged into one 1200km ride?
Solution gained.
I posted a message and request for help on the Garmin Forum and a very kind person of the name 'OnlyTwo' had a look and re-sized the file for me (10Mb down to 1.3Mb) and it has uploaded to Strava with no issues. I have no idea what 'OnlyTwo' did, but I am very grateful to them.
Sorry that so many of us seem to be having similar issues.
I must be dense this morning, but what is R-R data?
If you have trouble uploading, pm me and I'll give you my email so I can try to condense your file with my program (it's rather user-unfriendly at the moment).
zigzag - I had the same issue. Under My Stats on Strava there is a button to Refresh Stats - this solved it for me
zigzag - I had the same issue. Under My Stats on Strava there is a button to Refresh Stats - this solved it for me
nice one - refreshing stats solved it for me too - thanks!
Quite some people rode it as one ride without sleep ;), I must admit I had one long beauty sleep after 700K.
The garmin file is 8MB and doesn't want to go through, My fittools created halves are 6.7MB each but sail through fine.
.fit files seem to be pretty damn efficient then. Just noticed the .fit file for last weekend's 300 is 1.8M, where as the GPX is 14M.
I wonder what arbitrary dice roll strava used to decide on the upload limit...
J
what i'm puzzled about is why it managed to upload a much longer ride before (with the extra sensor data as well), but got stuck this time. unless they changed/reduced their timeout limits recently.
Ok, I've added the ability to add or subtract one minute from all the timestamps in a GPX track.
https://simple-gpx.herokuapp.com/
In one hit, you will be able to use my web utility to get around Strava duplicate rejection, and simplify the data to the point it doesn't time out. Again if you want to retain power, cadence, HR, electronic shift data data look elsewhere.
Use 1 metre accuracy, retain timestamps and elevation boxes ticked. Choose timestamp shift amount from new dropdown.
A trackpoint every 4 metres is somewhat excessive :-)
1/sec is pretty standard for recording power etc. Pretty sure TrainerRoad advise against anything else as it messes up analytics.
Currently paying for TrainingPeaks TrainerRoad and Strava. Strava is the only one that has messed up badly. Renewal is next month. Good chance to save a few quid.
PM me if it doesn't, so far my program to condense from 1/s to 1/3s worked for all .fit files that came directly from a GPS (Strava did not accept the one that came from ridewithgps).