02-26-2017 17:07
02-26-2017 17:07
Hello to all,
I notice that after tracking a walk with my GPS, my dashboard shows two different distances for the same walk (see photo) any ideas as to why?
02-26-2017 17:14
02-27-2017 05:11
02-27-2017 05:11
03-12-2017 12:14
03-12-2017 12:14
Hello @DavidTKD! Welcome to the Forums.
My suggestion would be to do the walk by selecting 'Run' option on your Fitbit. There is an issue where the Walk option does get some inconsistent information in the way the pictures you posted show. Selecting the Run option should help the information be accurate.
Let me know how it goes!
03-12-2017 15:58
03-12-2017 15:58
thanks, I'll give that a try.
03-16-2017 12:44
03-16-2017 12:44
Hey @DavidTKD, you're very welcome.
If you do give that shot, please let me know how it goes. I'd like to get much more information on this issue.
Also, if you have the time, be sure to visit our Discussion boards. There you can talk about a lot of different topics with other users.
Hope to see you around!
03-17-2017 02:58
03-17-2017 02:58
As a follow up... I select "run" now when I take my walks and it does register correctly on my dashboard. Thanks again.
David
03-17-2017 04:39
03-17-2017 04:39
@LanuzaFitbitI have gone back 5 months on my exercise records they were all "walk" Connected GPS. There was no difference on the Android map and bar. Always on the PC Dashboard Exercise maps was 0.01km less than the bar at the top. Never any drop outs.
I changed to Running Coonected GPS.. No difference, same results.
Phone: Android Xperia XP Android V7 and App 2.44.1 and firmware 17.8.301.8
03-20-2017 11:44
03-20-2017 11:44
03-20-2017 17:50
03-20-2017 17:50
@LanuzaFitbitThanks for the reply... I don't have a problem with distance.. Occasionally it drops 0.01 (10 meters) on the synced map to the server. This doesn't affect the distance recorded lifetime..
03-24-2017 13:59
03-24-2017 13:59
Hey @Colinm39!
Thanks for those pictures. I was really interested in seeing a bit more of that. It would seem, thankfully, that this is not happening to everyone and that it only occurs to some users.
While the drop is not really big, it shouldn't really affect the overall details.
Let me know if you have nay questions or need any assistance!
03-26-2017 00:57
03-26-2017 00:57
That happened to me yesterday as well. I tracked a walk and it was 6 km. But the distance on my dashboard was only on 5.4 km and I had done some steps before the walk. Very strange.
03-26-2017 01:32
03-26-2017 01:32
@aviva.sWelcome... What did the distance show in your PC Activity Log ?
I have found the Header on the Details Log of mapping/tracking is equal to what shows on the Activity Log entry. The mapping just has the error which isn't effecting the distances recorded on your lifetime achievements.
@aviva.s wrote:That happened to me yesterday as well. I tracked a walk and it was 6 km. But the distance on my dashboard was only on 5.4 km and I had done some steps before the walk. Very strange.
03-26-2017 01:46
03-26-2017 01:46
03-30-2017 14:17
03-30-2017 14:17
Hello @aviva.s!
I would like to ask you if the walk is being tracked by your Fitbit tracker? If so, what tracker is it? If it is a Charge 2, have you tried tracking the activity using the Run option? That one should prove to generate much more accurate details.
Look forward to helping you make sense of this situation.
09-05-2020 02:43
09-05-2020 02:43
Hi @LanuzaFitbit,
I am experiencing the different distances being reported on the same walk and also seemingly low distances from what I would expect.
On one route of what I would expect to be well over a mile, I have gotten the differing distances of 0.23 mi to 0.71 mi showing in the app.
I am at times pushing a stroller, so my arm isn't swinging as it typically does while walking, which I feel is reflected in a low step count. Are the number of steps calculating the distance walked even though I have my GPS tracking and a map is generated with where I walked?
To be thorough in my explanation, I start and end the "walk" exercise tracker on my fitbit. I will try using the "run" as you recommended to another user, but is this still a known issue years later?
Thanks,
Tina