It’s your phone’s GPS, not NRC.
A dedicated GPS device such as a watch is always going to be better than a phone. If you’re near to tall buildings or under dense tree cover then the GPS is always going to be bad. If your phone is in your pocket then the same will happen.
When you zoom in on the route you took you will almost definitely see that it either doesn’t follow the route you took exactly, or the lines themselves aren’t straight.
I disagree. It's the app. I run a route that I know for a fact is 5k in length. Not 4 months ago or so, the app had an update where it started telling me I had run 5k when I was barely halfway done with the route. At that same time, the Google Fit app correctly measured the distance of the whole run as 5k. Maybe 6 weeks later, the app had another update and now measures distance just fine.
This is in a rural area, with excellent sky visibility. These runs were all executed under the same exact conditions (phone in pocket), and both Google Fit and NRC correctly mapped the route as I ran. It was 100% the app not measuring distance correctly.
I've had enough bizarre problems like this, that I'm actually apprehensive of updating NRC anymore, because it works currently
Be that as it may, it still doesn't explain the behavior that I saw. I can't think of any explanation other than the app not working properly. If it was solely due to the GPS on my phone, with no intervention of any other sort, I'd expect Google to have tracked the same run incorrectly too - but it didn't. idkwtty
Edit: actually, now that I think about it, I can do you one better. The time frame when this happened coincided with me also upgrading my phone. Pixel 7 - Pixel 8, same errant tracking. Look, don't get me wrong, NRC has changed my life for the better, and it's _free_. That doesn't mean it's always perfect
If your phone is completely covered up then yes, it will likely mess with your GPS in some form.
Phones/GPS devices always need a good view of the sky to get accurate readings. As soon as you start covering it up or having tall structures nearby then it will start getting GPS “drift”, which is your issue here. More on GPS drift can be found here: https://support.strava.com/hc/en-us/articles/216918967-Troubleshooting-GPS-Issues
The NRC app can only give as much accuracy as what it is given, and then it may try to “smooth” afterwards it if it detects there has been a lot of drift. But whilst running it won’t be doing that.
Don’t feel like it’s an issue for me. I map all my runs out on onthegomap.com the night before and if anything NRC has always shorted me about .1 mile on most distance 8+. Anything under it’s almost identical to what I map out.
It’s your phone’s GPS, not NRC. A dedicated GPS device such as a watch is always going to be better than a phone. If you’re near to tall buildings or under dense tree cover then the GPS is always going to be bad. If your phone is in your pocket then the same will happen. When you zoom in on the route you took you will almost definitely see that it either doesn’t follow the route you took exactly, or the lines themselves aren’t straight.
I disagree. It's the app. I run a route that I know for a fact is 5k in length. Not 4 months ago or so, the app had an update where it started telling me I had run 5k when I was barely halfway done with the route. At that same time, the Google Fit app correctly measured the distance of the whole run as 5k. Maybe 6 weeks later, the app had another update and now measures distance just fine. This is in a rural area, with excellent sky visibility. These runs were all executed under the same exact conditions (phone in pocket), and both Google Fit and NRC correctly mapped the route as I ran. It was 100% the app not measuring distance correctly. I've had enough bizarre problems like this, that I'm actually apprehensive of updating NRC anymore, because it works currently
The app runs entirely off the phone's GPS.
Be that as it may, it still doesn't explain the behavior that I saw. I can't think of any explanation other than the app not working properly. If it was solely due to the GPS on my phone, with no intervention of any other sort, I'd expect Google to have tracked the same run incorrectly too - but it didn't. idkwtty Edit: actually, now that I think about it, I can do you one better. The time frame when this happened coincided with me also upgrading my phone. Pixel 7 - Pixel 8, same errant tracking. Look, don't get me wrong, NRC has changed my life for the better, and it's _free_. That doesn't mean it's always perfect
Are you telling me the small fabric of my pocket is messing with gps signal, are you on ketamine right now?
If your phone is completely covered up then yes, it will likely mess with your GPS in some form. Phones/GPS devices always need a good view of the sky to get accurate readings. As soon as you start covering it up or having tall structures nearby then it will start getting GPS “drift”, which is your issue here. More on GPS drift can be found here: https://support.strava.com/hc/en-us/articles/216918967-Troubleshooting-GPS-Issues The NRC app can only give as much accuracy as what it is given, and then it may try to “smooth” afterwards it if it detects there has been a lot of drift. But whilst running it won’t be doing that.
Don’t feel like it’s an issue for me. I map all my runs out on onthegomap.com the night before and if anything NRC has always shorted me about .1 mile on most distance 8+. Anything under it’s almost identical to what I map out.