I've been having an issue with distances recorded on my runs. My typical runs are recorded using my S2 Nike watch and NRC+ on my iPhone 6.
Recently, I had changed up my regular running paths and had a very fast time (for me). I just thought I was getting faster, but alas, it was not the case. Depending on how the run is recorded, the distances recorded can be up to 15% more than reality. For instance, on a 3.1 mile route, the AW records the distance as 3.53 miles. So instead of displaying an 8:45 pace or so, I get rewarded with a 7:45 pace ... give or take.
Anyways, I figured out the combinations used that result in the inaccurate distances and which combinations gives me accurate distances. It mostly depends on whether I start the run using my AW or my iPhone.
Here are my findings. I wonder if anyone has the same experiences that I've been seeing.
Typical Route (between 3.05 and 3.15 miles, depending on the mapping website)
I mapped out my route using RunMyRoute.com and also Google Maps walking directions. They're both around 5k (3.11 miles).
1st Run - NRC+ on both the AW and iPhone - run started on the AW
The above map was taken from my SmashRun account. NRC+ recorded this run as 3.53 miles. As you can see, the map route is exactly the same as the reference map above.
2nd Run - AW Workout (carrying iPhone) - run started on AW
This map was taken from the Workouts app on the iPhone. The run was recorded as 3.58 miles. You can also see that the map route matches the reference map.
3rd Run - NRC+ on both the AW and iPhone - run started on iPhone
This map also comes via SmashRun and was recorded properly as 3.1 miles. You can see that it matches the reference map.
Theory
Based on how the AW is supposed to work with the iPhone connected, I surmise that the iPhone is the source for the GPS data in all three of these runs. This would make sense.
However, I believe that the iPhone and AW are using different maps when calculating distances. I'm not sure why this would be the case, as the exact longitude and latitude positions are available and both the AW and iPhone should have sufficient processing power to calculate distance between two GPS data points in real time.
The fact that I get the same, inaccurate distance when I use the AW workout and AW-NRC is also telling.
Question
Right now, this issue doesn't really impact me, as long as I always remember my iPhone and it's charged up. To get elevation data using NRC+, you have to start the run on the iPhone anyways.
Question is whether anyone else notices this. There are plenty of folks on the internet that claim the AW GPS is inaccurate, but I've not come across anyone with my particular issue. I'm wondering if anyone in the MR family is seeing this too, and if they've come across a solution.
Recently, I had changed up my regular running paths and had a very fast time (for me). I just thought I was getting faster, but alas, it was not the case. Depending on how the run is recorded, the distances recorded can be up to 15% more than reality. For instance, on a 3.1 mile route, the AW records the distance as 3.53 miles. So instead of displaying an 8:45 pace or so, I get rewarded with a 7:45 pace ... give or take.
Anyways, I figured out the combinations used that result in the inaccurate distances and which combinations gives me accurate distances. It mostly depends on whether I start the run using my AW or my iPhone.
Here are my findings. I wonder if anyone has the same experiences that I've been seeing.
Typical Route (between 3.05 and 3.15 miles, depending on the mapping website)
I mapped out my route using RunMyRoute.com and also Google Maps walking directions. They're both around 5k (3.11 miles).
1st Run - NRC+ on both the AW and iPhone - run started on the AW
The above map was taken from my SmashRun account. NRC+ recorded this run as 3.53 miles. As you can see, the map route is exactly the same as the reference map above.
2nd Run - AW Workout (carrying iPhone) - run started on AW
This map was taken from the Workouts app on the iPhone. The run was recorded as 3.58 miles. You can also see that the map route matches the reference map.
3rd Run - NRC+ on both the AW and iPhone - run started on iPhone
This map also comes via SmashRun and was recorded properly as 3.1 miles. You can see that it matches the reference map.
Theory
Based on how the AW is supposed to work with the iPhone connected, I surmise that the iPhone is the source for the GPS data in all three of these runs. This would make sense.
However, I believe that the iPhone and AW are using different maps when calculating distances. I'm not sure why this would be the case, as the exact longitude and latitude positions are available and both the AW and iPhone should have sufficient processing power to calculate distance between two GPS data points in real time.
The fact that I get the same, inaccurate distance when I use the AW workout and AW-NRC is also telling.
Question
Right now, this issue doesn't really impact me, as long as I always remember my iPhone and it's charged up. To get elevation data using NRC+, you have to start the run on the iPhone anyways.
Question is whether anyone else notices this. There are plenty of folks on the internet that claim the AW GPS is inaccurate, but I've not come across anyone with my particular issue. I'm wondering if anyone in the MR family is seeing this too, and if they've come across a solution.
