The stride length comments "worry" me. I run A LOT.. but almost all trail. Can't stand road. But with trail... there's no consistent stride length. I'll always have my phone with me, anyway.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Running with GPS. Why is the distance so inaccurate?
- Thread starter plantoschka
- Start date
- Sort by reaction score
Ran a series of tests this evening trying out some of the various different theories and combinations which had been discussed in this tread. For these tests I ran the same know one mile loop in my neighborhood 5 times trying out different combinations each time.
For these tests I used an
iPhone 6 with software version 8.3
Stainless SteelWatch with software version 1.0.1
Headphones both regular wired and bluetooth
The known 1 mile route as mapped from my computer.
Image
#1
Nike Running App on iPhone
iPhone wifi and bluetooth both ON.
Bluetooth headphones connected to iPhone
Image
Image
Image
[#2
Nike Running App on iPhone
iPhone wifi and bluetooth both OFF.
Regular wired headphones connected to iPhone
Image
Image
Image
#3
NO iPhone - powered off and not carried
Bluetooth headphones connected to Watch
Image
#4
NO iPhone - powered off and not carried
Bluetooth headphones connected to Watch
Image
#5
Nike Running App on iPhone
iPhone wifi ON
iPhone bluetooth OFF
Regular wired headphones connected to iPhone
Image
Image
Image
Thank you for testing. Really hoped 1.01. would fix this problem. I usally run 6 km.
Runtastic: 6,05 KM
Nike+: 6,02
Apple Watch: 5,45 KM
I'm hopeful it still will. We all only got 1.01 yesterday so I had yet to have any opportunity to "learn" prior to those tests. Also the setting dhy8386 mentioned might make a difference too.
Checked after you mentioned it ... My Motion Calibration & Distance was OFF on my iPhone (Settings > Privacy > Location Services > System Services). I have now switched that to ON hopefully that will makes a difference after it has some opportunity to "learn" with it ON.
Actually, perhaps the update wiped any previous data that was "learned" since it was deemed to be inaccurate. Maybe it will take a couple more runs to recalibrate it??? I'll see in the AM and will give it 3 tries again. Hopefully by #3 it will have it pretty close to the actual distance.
This morning was my first run with 1.0.1 and I did notice there was a notification when starting an "Outdoor Run" that reiterated doing a 20 min run with your phone to calibrate the distance. This would lead me to think that all previous data was likely wiped from the device with the update. Anyway, here are my previous findings and current:
1.0.0
Run 1 (using a time goal): 2.28 mi
Run 2 (using distance goal set to 2.30): 2.32 mi
Run 3 (open goal, not connected to phone): 2.27 mi
1.0.1
Run 1 (open goal, with phone): 2.31 mi
Again, the actual distance of this particular route is 2.38 mi confirmed via MapMyRun's online pin drop map tracker. Runs are all at or just over 20 mins to meet Apple's "requirement."
This seems to be heading in the right direction. At least we're >.10 mi over the actual distance now. A couple more hundredths of a mile and we will definitely be close enough.
I'll continue the same route for the next couple runs to make sure it is fully calibrated since the update and will also try using a distance goal to see if that changes it's attentiveness to the distance.
My last test will be to wear my old TomTom Cardio Multi-Sport watch on the other wrist and see what that says in comparison since it connects directly to the GPS satellites.
Anyone else find their distance to be "improved" at the very least?
1.0.0
Run 1 (using a time goal): 2.28 mi
Run 2 (using distance goal set to 2.30): 2.32 mi
Run 3 (open goal, not connected to phone): 2.27 mi
1.0.1
Run 1 (open goal, with phone): 2.31 mi
Again, the actual distance of this particular route is 2.38 mi confirmed via MapMyRun's online pin drop map tracker. Runs are all at or just over 20 mins to meet Apple's "requirement."
This seems to be heading in the right direction. At least we're >.10 mi over the actual distance now. A couple more hundredths of a mile and we will definitely be close enough.
I'll continue the same route for the next couple runs to make sure it is fully calibrated since the update and will also try using a distance goal to see if that changes it's attentiveness to the distance.
My last test will be to wear my old TomTom Cardio Multi-Sport watch on the other wrist and see what that says in comparison since it connects directly to the GPS satellites.
Anyone else find their distance to be "improved" at the very least?
Getting Closer!
So today's run was interesting as it inched closer to the actual distance. Here are my total findings so far...
1.0.0
Run 1 (using a time goal): 2.28 mi
Run 2 (using distance goal set to 2.30): 2.32 mi
Run 3 (open goal, not connected to phone): 2.27 mi
1.0.1
Run 1 (open goal, with phone): 2.31 mi
Run 2 (distance goal, with phone): 2.33 mi
Again, the actual distance of this particular route is 2.38 mi confirmed via MapMyRun's online pin drop map tracker. Runs are all at or just over 20 mins to meet Apple's "requirement."
These are all running on the same path the whole way so there's really no deviation from the route to create any "extra" distance. I think being within 0.05 mi is getting close enough, much better than 0.10 for sure! We'll see what run 3 with a 20 min time goal set will do and then without the phone...
So today's run was interesting as it inched closer to the actual distance. Here are my total findings so far...
1.0.0
Run 1 (using a time goal): 2.28 mi
Run 2 (using distance goal set to 2.30): 2.32 mi
Run 3 (open goal, not connected to phone): 2.27 mi
1.0.1
Run 1 (open goal, with phone): 2.31 mi
Run 2 (distance goal, with phone): 2.33 mi
Again, the actual distance of this particular route is 2.38 mi confirmed via MapMyRun's online pin drop map tracker. Runs are all at or just over 20 mins to meet Apple's "requirement."
These are all running on the same path the whole way so there's really no deviation from the route to create any "extra" distance. I think being within 0.05 mi is getting close enough, much better than 0.10 for sure! We'll see what run 3 with a 20 min time goal set will do and then without the phone...
Getting Accurate!
Inching closer to the actual distance...perhaps it's safe to say "close enough" but a run without the phone will be the final test! Here are my latest findings...same route, etc...
1.0.0
Run 1 (using a time goal): 2.28 mi
Run 2 (using distance goal set to 2.30): 2.32 mi
Run 3 (open goal, not connected to phone): 2.27 mi
1.0.1
Run 1 (open goal, with phone): 2.31 mi
Run 2 (distance goal, with phone): 2.33 mi
Run 3 (distance goal, with phone): 2.35 mi
Again, the actual distance of this particular route is 2.38 mi confirmed via MapMyRun's online pin drop map tracker. Runs are all at or just over 20 mins to meet Apple's "requirement."
Being only 0.03 mi under the mapped distance is probably close enough at this point. Will post one last run once I record one without the phone's assistance, we'll see how that does... Anyone else seeing any improvement since the update?
Inching closer to the actual distance...perhaps it's safe to say "close enough" but a run without the phone will be the final test! Here are my latest findings...same route, etc...
1.0.0
Run 1 (using a time goal): 2.28 mi
Run 2 (using distance goal set to 2.30): 2.32 mi
Run 3 (open goal, not connected to phone): 2.27 mi
1.0.1
Run 1 (open goal, with phone): 2.31 mi
Run 2 (distance goal, with phone): 2.33 mi
Run 3 (distance goal, with phone): 2.35 mi
Again, the actual distance of this particular route is 2.38 mi confirmed via MapMyRun's online pin drop map tracker. Runs are all at or just over 20 mins to meet Apple's "requirement."
Being only 0.03 mi under the mapped distance is probably close enough at this point. Will post one last run once I record one without the phone's assistance, we'll see how that does... Anyone else seeing any improvement since the update?
Mind seem to be getting closer to accurate as well. My run from yesterday of almost an hour was 6.23 miles according to Nike+ Running on my iPhone 6. My Watch workout set to Outdoor Run No Goal reported a total distance of 6.06 miles which averages out to a variation of less than 0.03 per mile. I'm still hopeful it continues to "learn" and get even a little more accurate but we will see.
Yesterday was my 5th run since updating to 1.01 but all different distances and routes so far. Intending to run the same 4 mile route multiple days in a row now and see how it does.
So here's something that's kinda interesting from my run today...I did a time goal to see if that made a difference and it was less accurate than before...as stated in my other posts the route is 2.38 mi.
1.0.0
Run 1 (using a time goal): 2.28 mi
Run 2 (using distance goal set to 2.30): 2.32 mi
Run 3 (open goal, not connected to phone): 2.27 mi
1.0.1
Run 1 (open goal, with phone): 2.31 mi
Run 2 (distance goal, with phone): 2.33 mi
Run 3 (distance goal, with phone): 2.35 mi
Run 4 (time goal, with phone): 2.31 mi
So it seems more accurate than 1.0.0 was but not as accurate when using a distance goal...perhaps it communicates more with the phone when it is set to a distance goal??? I'll try one more before disconnecting from the phone.
I went on my first run with my SS watch today and the accuracy was off my half a mile. My wife was running with runtastic tracking our progress and I was using the running workout.
I had my iPhone 6 with me so I was confused why it would be so off.
I came home and found this article about calibrating the runs and noticed step 3 in this list was disabled on my phone.
http://www.idownloadblog.com/2015/0...ow-to-calibrate-apple-watch-workout-activity/
Any one else having the same issue may want to look at their settings. There are some people that have very accurate results.
The other thing was that I was pushing a stroller so using arm swings was not a possible way to measure distance.
Why not just use the GPS if the phone is with you? I always run with my phone in case of emergencies but like the idea of looking at wrist for updates on my pace / distance.
I can't wait for OS2.0 so I can just use runtastic pro natively on the watch and have it update my rings.
I had my iPhone 6 with me so I was confused why it would be so off.
I came home and found this article about calibrating the runs and noticed step 3 in this list was disabled on my phone.
http://www.idownloadblog.com/2015/0...ow-to-calibrate-apple-watch-workout-activity/
Any one else having the same issue may want to look at their settings. There are some people that have very accurate results.
The other thing was that I was pushing a stroller so using arm swings was not a possible way to measure distance.
Why not just use the GPS if the phone is with you? I always run with my phone in case of emergencies but like the idea of looking at wrist for updates on my pace / distance.
I can't wait for OS2.0 so I can just use runtastic pro natively on the watch and have it update my rings.
Thanks for sharing the link, unfortunately I've had step 3 on this whole time and my watch still seems to be slightly off...now, we're talking between .07 and .03 mi most of the time so it's not a huge amount difference. Will be interesting to see if this continues to improve in any way... I'm looking forward to OS2.0 as well but I bet that will also finally fix this accuracy issue with their native app as well...LOL, you know that's when it will work perfectly, right when we're ready to move on...ha...
Going for another run this evening and will post if there's any improvement in my accuracy. I will say though, cycling is much more accurate. I went on a ride over the weekend and the watch was basically spot on with my bike computer.
I'll try to get a 4 mile run in this afternoon. I have not run again since enabling that option. I'll again let my wife track with runtastic and I'll track just using watch+phone and see if it looks like it started using the gps on the phone. With a stroller the watch will never get the info need from a regular arm swing.
Thank you! My watch doesn't seem to calibrate checked and that setting was off, not sure why. I have been using Runkeeper in tandem and the watch was always off.