Blaze and distance on GPS completely screwed

[SunsetRunner]

For a bit more than week tracking a run via Fitbit App and GPS results into completely odd results.

The distance and km marks calculated on the map are such that it suddenly is around 40% longer distance than in real.. So for a calculated 10km run the steps recorded were 7988 - lets make it 8000. That would mean that (if Fitbit would calculate things from any entered stride length that number would have to be 1.25m .... that never has been entered anywhere - I had 90cm for running and 70cm for walking.

That all doesnt make sense to me. So if the distance doesnt get calculated based on entered stride length then this means that GPS suddenly doesnt work anymore - and hey I am running always the same track in a park and the weather was great.

Result is that for Fitbit I turned into a high efficiency runner telling me that I finished a km in 5min 15sec average... would be nice but I am a slow runner actually.... 

I really would like to see the following:

1. correct tracking of path and overall distance with the km marks set correctly

2. Fitbit blaze counting the steps because dependent on geography and human nature stride lengths will alter during a run especially when running uphill for a while where one might reduce stride lengths. Blaze should be good in counting steps and GPS should be good to track distance - what'S the problem to get that in good sync?

I hope somebody can solve that mystery for me

[SunsetRunner]

ok - I did some more analysis - I zoomed into the track map and noticed that the track gets recorded as an extreme zigzag around the path I am running at.... so maybe it is a problem with GPS tracking on iphone. when calculating distance around that zigzag course it would be no wonder that the distance calculated is so much off. But I wonder why it is that accurate the last days.... hmmmm

[AlejandraFitbit]

A warm welcome to the Community @SunsetRunner and thanks for troubleshooting this by yourself.

As you discovered, your GPS distance will be calculated by your phone's GPS. If you are having issues with it, I recommend taking a look at this post to troubleshoot this problem. Also, here you will be able to see some instructions to follow in order to update your stride length information.

I hope this helps, let me know the outcome. 

[SunsetRunner · Accepted solution]

ok - it works again - I restarted my iphone and made another run - and it worked again. I dont know whether the restart was really fixing it or whether it was the way the iphone was attached to me... again not 100% sure whether this happened for ALL wrongly recorded runs - but I had the phone in the side pocket of my jacket - now as it was warmer again I was wearing it at the arm again.

At least I know what to try first next time.... restart phone - wear on arm.....

Thx

[VictorHyman]

I have the same issue and it is generally worse on longer runs. I find frequently that that my GPS based pace is suddenly off way too fast and when I look at the map after my run the the KM markers are not evenly paced. I've run a second GPS running app (My Asics) at the same time as I'm using my Blaze's Connected GPS and the other app appears to be more accurate.