07-08-2022
08:39
- last edited on
12-18-2022
22:17
by
MatthewFitbit
07-08-2022
08:39
- last edited on
12-18-2022
22:17
by
MatthewFitbit
This is not a riddle.
Today I jogged for 35 minutes/ with an average pace of 13’30” and only covered 2.66 miles.
i relied on my phone gps.
how can I improve the accuracy.
sometimes I jog and run at the same session, so stride adjustment is not an answer
Moderator Edit: Clarified subject
Answered! Go to the Best Answer.
07-08-2022 11:00
07-08-2022 11:00
@shuly Pace is minutes per mile. The notation is minutes and seconds per mile. Remember there are 60 seconds in a minute, so 13'30" is 13.5 minutes in a more mathematical notation. So if I created this dreaded math word problem, "If Shuly ran for 35 minutes at a 13'30" pace, how far did they go?", the calculated answer is 2.59 miles. As a long time user, I see this as an acceptable amount of error.
When you use your phone's GPS (or built in GPS with other devices), the distance is the GPS distance, so your Fitbit estimated stride length doesn't matter.
Does this help?
Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS
Take a look at the Fitbit help site for further assistance and information.
07-08-2022 11:00
07-08-2022 11:00
@shuly Pace is minutes per mile. The notation is minutes and seconds per mile. Remember there are 60 seconds in a minute, so 13'30" is 13.5 minutes in a more mathematical notation. So if I created this dreaded math word problem, "If Shuly ran for 35 minutes at a 13'30" pace, how far did they go?", the calculated answer is 2.59 miles. As a long time user, I see this as an acceptable amount of error.
When you use your phone's GPS (or built in GPS with other devices), the distance is the GPS distance, so your Fitbit estimated stride length doesn't matter.
Does this help?
Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS
Take a look at the Fitbit help site for further assistance and information.