I decided to go for a 10k today, using only my new Ionic, where I usually carry my phone. As liberating as that was, I kept feeling that the kilometres were going up slower than they usually do.
I have run this route a lot of times before, both with an iphone and an android phone to track the distance, and checking it on mapmyrun.com ever once in a while when I forgot the route, or how long it is exactly.
I hadn't checked recently, but I know that it is at least 10k, and vaguely remember it being around 11k.
However, I finished the route with a reading of 9.6k, and ran the final 400m to get the right number logged. I then checked the distance on mapmyrun, getting about 11.3k, and decided that one of the two must be wrong. The path shown in the fitbit app was more or less dead on what I had actually run, meaning that the route itself seemed to be correct.
I then realized that I could probably get a hold of the file generated by the Ionic during my run and use some online tool to tell me whether the gps was broken or something else was the problem.
I used two different sites, https://www.gpsies.com, and http://www.graphmyrun.com to analyse the TCX file, and they both said the distance was 11.15k.
This makes me happy and annoyed at the same time. I was thinking I would return my fitbit because it's gps tracking was inaccurate and useless, but it seems that it is just as accurate as I was hoping. However, it seems that my Ionic refuses to log that distance, but somehow arrives at a different result, in spite of its own GPS results.
I have read a few posts that seem to mention stride length, which I have now corrected to what I think it is. However, if this is it, I don't understand why my strides should be more reliable than the gps tracking.
Can someone help me fix this?
