Did the same recovery run as Wednesday, albeit at 8min/mile
Fitbit this time gave 4.70 miles (as opposed to 4.74). I used IPBike which gave 4.737
Both Fitbit tracks look very similar at a quick glance but there must have been some subtle differences.
I measure the route with Google maps and it said 4.7 miles, I used hillmap.com to click out the the path and it gave 4.7 and since the path wasn't exact on the curves that should eb rounded up very slightly, about 4.1 to 4.2 would be my guess.
Bit of a mixed bag here, the runtastic track is clearly poor but only one sample. There was a bit of a variance in the 2 fitbit tracks. IPBike does indeed seem better than runtastic with a faster polling rate and a distance very similar to the fitbit's first track.
however, this is a road running course so the curves are wide and gentle and the corners hard 90* turns and infrequent, so relatively easy for most trackers. Also when running in straight lines is the kind of condition that makes GPS trackers over read the distance since any noise/deviation from the true straight line will add to the distance.
I might test how ipbike does on my forest trails, it could be similar to the fitbit if it uses the same polling rate. The UI on ipbike definitely sucks and since it is biking app it doesn't really have the features I want for running (e.g. 1 miles paces etc).
I still think endomono has the best UI/features, just wish the polling rate was higher.
