Accuracy of Apple vs apps (distance & pace)?

Does anyone know why different apps using the same hardware (my iPhone) would give different results from the same run?

I tracked today’s run with my Apple Watch 3 (connected to iPhone) and with the app Weav Run, and got drastically different results - over 1/4 mile in the distance over ~3.5 miles, and :20/mile for the average pace.

I’m more inclined to believe the results from Apple, but don’t know what to make of this - both are using the same GPS data aren’t they??

Here are the two results pages (I know, super inconsistent pacing… there was one traffic light and I was trying to focus on getting a higher cadence which made everything else fall apart):

Apple

Weav Run

Posted Jun 22, 2022, 8:49 PM UTC · edited

54
pony_trekker•

The apple time is always elapsed time versus moving time.

2
Britney2007•

My brain just doesn’t think this way so excuse the dumb question but, could you explain how that affects my pace? I get stopped by a lot of lights.

1
Eikceb•

Moving time doesn’t count seconds/minutes where the GPS position doesn’t change (i.e you’re not moving), whereas elapsed time is just the time between when you pressed start and stop. Elapsed time is always greater or equal to moving time for your distance travelled. Since pace is calculated as minutes/miles, a larger numerator (number on top) for time will give you a higher (slower) pace metric.

This explains the difference in pace but less so the difference in distance. I’ve noticed this as well, and it’s likely due to the way they calculate “moving.” There is always some drift in GPS signals, so if they record you as “not moving” but you were in fact changing position, the distance recorded will be lower.

3
runrgirl25•

It depends on how the apps take the point to point GPS data and "smooth it" is what I've been told. The raw data from apple is off a couple meters/yards here and there and looks very ziggy zaggy and the individual apps use different algorithms to smooth it. Some are better than others at recognizing "corners" or curves on a track. While others will cut them if there's not a data point directly on the corner or tangenting the curve. Are you able to look at the mapped runs on each and compare how the lines are?

2