Hi there,
when tracking my rides with Apple Watch, the data recorded is a plausible and consistent match with other resources, e.g. komoot pre ride track planning.
Importing the recorded track however, has a strange impact especially on altitude information. A track with 300 meters of altitude difference (Apple, komoot, paper map) e.g. easily gets imported as 600+ meters in Strava. This gives a wrong information for the training status and kind of nags on my credibility with those who joined me for the ride 😉 😉
Why doesn‘t Strava simply take the well recorded data from Apple, but applies some additional magic during import, that actually goes so significantly wrong?
thanks a lot!
Thomas