Hi Bob,
I've attached an image so you can see my experiences. Obviously here we are playing with different devices so to draw likeness is guesswork at best. But this is the solution I found to my Strava Random elevation woes. Thing is I know the Garmin810 was writing the file in Raw data and using its own interpretation of it for elevation calculation. Indeed Training peaks would actually read lower than garmin so my guess is Garmin probably Chopped out the micro ups and downs. TrainingPeaks was using some form of algorithm based on continual increase. Again just chopping out the up one down two up thee feet type data whereas strava just added the whole lot together and produced an elevation profile from that.
The only thing I can think is that in the Files its now reading from there is an elevation gained constant written at the end of the activity. When I had to chop my Wattage data out of a TCX/GPX(I forget) it had a max and average watts value in there so I'm thinking something similar. Trouble is the FIT file is gibberish so I can read that.
I did however copy and paste my Fit file off the device and upload that directly to Strava via upload from file. It hit me with the same value as the device did. It must be writing to a constant somewhere in the file.
Whatever you have as your elevation on your device in the ride history will be the correct one. I would go from there as the correct value. I know training Peaks allows you to edit the Elevation Gained value and thats what I have been doing for proper tracking and then ignoring strava until now.
What does the dive write to in default. Is it a .fit file in your rides folder on the device's memory?
I've attached an image so you can see my experiences. Obviously here we are playing with different devices so to draw likeness is guesswork at best. But this is the solution I found to my Strava Random elevation woes. Thing is I know the Garmin810 was writing the file in Raw data and using its own interpretation of it for elevation calculation. Indeed Training peaks would actually read lower than garmin so my guess is Garmin probably Chopped out the micro ups and downs. TrainingPeaks was using some form of algorithm based on continual increase. Again just chopping out the up one down two up thee feet type data whereas strava just added the whole lot together and produced an elevation profile from that.
The only thing I can think is that in the Files its now reading from there is an elevation gained constant written at the end of the activity. When I had to chop my Wattage data out of a TCX/GPX(I forget) it had a max and average watts value in there so I'm thinking something similar. Trouble is the FIT file is gibberish so I can read that.
I did however copy and paste my Fit file off the device and upload that directly to Strava via upload from file. It hit me with the same value as the device did. It must be writing to a constant somewhere in the file.
Whatever you have as your elevation on your device in the ride history will be the correct one. I would go from there as the correct value. I know training Peaks allows you to edit the Elevation Gained value and thats what I have been doing for proper tracking and then ignoring strava until now.
What does the dive write to in default. Is it a .fit file in your rides folder on the device's memory?