Run Map not accurate

[gabrielei]

I recently went on a run and waited until my device said connected. After finishing, I see that the map is not accurate at all. There are parts of the run missing and it shows that I finished about 0.3 miles before my house which is also not accurate. How do I know that the time, total run and everything else is accurate if parts are missing?? 

[charleskn]

@gabrielei The good or bad news is that the GPS map issues are separate from the other tracker measurements, like steps and heart rate.

Know that with the GPS, your tracker will try to determine a stride length for you, but you can edit that manually if desired. I probably find the steps to be the most consistent measurement, and of course the one I care about the least - LOL!

My Charge 4 heart rate measurements are pretty good, most of the time, but I have had occasional issues with the tracker reading very high or low. My Charge 4 does best with steady state exercises, and less well with rapid and extreme changes in heart rate (such as with HIIT workouts). You'll see that others have had more issues here.

Reference: https://help.fitbit.com/articles/en_US/Help_article/1874.htm

As to your GPS issue, what are your tracker GPS settings? There are options, like Dynamic GPS, to allow your tracker to use the internal tracker GPS, or your phone's GPS, if you take it with you, which could save on your tracker's battery. I have had the issue where my tracker loses the GPS signal (usually running under a thick tree canopy), and when that happens, it never reconnects (depending on how long it remained disconnected). In these instances, I see the same dropouts at the same locations, over and over.

I have not explicitly told my tracker to use my phone GPS, but I do use Dynamic mode. However, when I run, I also have my Polar heart rate monitor and Polar app using my phone GPS, and Strava using my phone GPS. So far, Strava and the phone GPS has been the most robust combination.

Experiment and good luck.