12-29-2022 14:33 - edited 12-29-2022 17:18
12-29-2022 14:33 - edited 12-29-2022 17:18
The map I got from my Charge 5 for today's run was horribly off. See image - the dotted green line is my actual route, with the red one being the map from FitBit. I don't expect great things from something the size and price of this device, but this is pretty bad. I've already done a restart - what else should I try in order to get a better track next time I'm out?
I'm also thoroughly confused by the data. Despite seeing huge corners cut away from my route, I got a pace that was almost a minute faster than my average. I like to think that I'm improving, but I'm pretty certain I didn't get that much faster in such a short time.
Edit: Even weirder, I downloaded the .tcx file and the spacing of my half mile lap points seems really inconsistent. In particular, see the long straightaway.
Edit 2: I just used Google Earth to measure the route. It shows 6.87 miles vs 7.75 reported by my Charge 5. So I'm even more confused about what's happening because the track shown on the map cuts a lot of corners and thus should be shorter.
12-29-2022 16:02
12-29-2022 16:02
Straight lines between waypoints indicate that between these waypoints the GPS was lost. On this course, I see you've lost your GPS connection a number of times. If you didn't use Charge 5 (no altimeter) you could check the elevation which would also show the gaps when GPS wasn't working. If you want to make sure, you may open the activity in the web dashboard and scroll through the timeline (on the pace chart). You will see the location marker moving on the map and disappearing when GPS is lost.