Hi,
I merged a garmin fit-file with a tcx export from my bosch e-bike to include the power- cadence-Data. It works fine, but the output fit-file include wrong speed-data.
First i thought the tool tryied to calculate miles to metric km/h, but the input data was already in km/h?
Can someone confirm or explain this behaviour? Is this a bug or a feature?:)
For example the the statistics from input-file = max speed: 43,3km/h in output-file = max-speed: 111,6km/h
The konditions: exclude all position and elevation data from the other tcx file, only use trackpoints with position from the garmin fit-file.
Kind reguards
Chris
Recalculate wrong Speed-Data
Re: Recalculate wrong Speed-Data
Hi Chris -
The speed in the output file is determined by the distance. Remember this equation:
Distance = Rate * Time
What the tool does is it takes the distance between each and every point (and the time), and it calculates the speed between each point. As you may have noticed, there are 3 different ways to embed distance in your final file:
1) Omit Distance.
2) Use Embedded distance from your original files
3) Have my tool calculate distance based on the distance between each point.
For your purposes, you're going to want to use the #2 option (Use Embedded distance). It sounds like the other options you selected were correct.
With regard to the confusion about distance conversions: All GPS files are always in metric (km/h). However, for the sake of displaying the values, the tool will show imperial units (miles, feet, etc..)... however if you're seeing feet and miles, the tool is just inserting the metric values behind the scenes.
Hope that helps, but if it doesn't use the contact form and send me your files.
The speed in the output file is determined by the distance. Remember this equation:
Distance = Rate * Time
What the tool does is it takes the distance between each and every point (and the time), and it calculates the speed between each point. As you may have noticed, there are 3 different ways to embed distance in your final file:
1) Omit Distance.
2) Use Embedded distance from your original files
3) Have my tool calculate distance based on the distance between each point.
For your purposes, you're going to want to use the #2 option (Use Embedded distance). It sounds like the other options you selected were correct.
With regard to the confusion about distance conversions: All GPS files are always in metric (km/h). However, for the sake of displaying the values, the tool will show imperial units (miles, feet, etc..)... however if you're seeing feet and miles, the tool is just inserting the metric values behind the scenes.
Hope that helps, but if it doesn't use the contact form and send me your files.
