@recollir@BenjaminHan Possibly; back when I used Strava, what's wasn't an irregular thing, and then I'd compare it to the watch's track which was always solid.
I’m actually quite curious how the two apps, which (I imagine) work from the same GPS information, can get such different results.
I am also guilty of finishing a run without checking if I've hit my target distance. Such is life. 🤣
@WTL@recollir I think I have only myslef to blame: 10k = 6.21317 miles, and I stopped the watch at 6.20, and that’s what my watch recorded, but #Strava reported 6.21 (?), and neither recognized it’s a 10K run…
More bizarre to me is how Strava interprets the elevation gain: see below from my recent #halfMarathon PR run. The route is pretty flat, so my #AppleWatch is definitely the correct one. Funny thing is this doesn't happen every time. Any idea?
@WTL@recollir Right after posting this, I noticed after tapping the three dot icon on the upper right in #Strava, I got this option “adjust elevation”. This appeared to fix the problem, although the result still doesn’t match #Applewatch’s.
@BenjaminHan@WTL I haven’t seen this kind of discrepancy yet. I guess you would want to download the GPX file from Strava and take a look at it… (there are some apps to extract GPX info from the fitness app as well (though you might have “other means” 😜). With the different GPX files you could compare their data (it is just XML anyway) or upload them to different other sites to see what they make out of them. Gaia, GPX studio, …
Add comment