@MkeRunnerGirl I've been posting about it since August and I think Fitbit sees no any issue at all. You can read a little more about my findings here:
https://community.fitbit.com/t5/Ionic/Ionic-GPS-Inaccuracies/m-p/2890584/highlight/true#M75553
The problem is using stride and steps ( somebody mentioned something like a step rate, whatever it is ) as factors when calculating the distance not just raw GPS data. Also, interesting is the fact that distance may change while coordinates obtained by GPS not ( you just standing pretty much still or GPS didn't manage to lock on yet ). It's possible that waving arms which imitates steps may add to the distance ( and use stride instead ). I don't know who came up with an idea to use stride to compute distance when there's a GPS on board, especially that if you connect GPS points and compute distance just from those you will get it correct. Moreover, when you use Bike activity, it doesn't seem to use stride to compute distance ( at least I hope so, but hey, it's Fitbit, everything possible ). Why running and walking is so broken? Nobody knows but all I know it's not an issue but feature of Ionic in eyes of the developers. Pity, because it would be enough to add an option whether you want to include stride in such computation or not.
