kitsune-scribe replied to your photo: I really am gonna have to figure out why FitBit...
If it’s counting steps it may have adjusted the distance to account for a longer stride when running. If it’s got GPS it’s just being mean. I don’t have a Fitbit but I know a lot of lower level pedometers make you give your stride length before they’ll calculate distances.
The weird thing is that it has my stride lengths, both walking and running, and obvs. walking is shorter (my walking stride is probably wrong right now but the data I’ve entered is walking 27, running 37, and I know the 37 is accurate). So if it assumed I was walking, the distance it gives when I tell it I’ve been running should be longer, not shorter, right? (I’m genuinely asking, I am this bad at math and logic.) Because it counts steps and distance per step is further.
And if it assumed I was running, and then I told it I was running, it shouldn’t shorten the length at all. *scratches head* And I know from googlemaps that the longer distance is usually closer to correct...
I feel like there’s some logic within the FitBit programming that’s doing this, I might actually ask on the FitBit forums why it does this. I wonder if during the workout count, it’s counting all my mileage, and not just my workout mileage. It generally takes me two tenths to get dressed and out the door, so that could be it, but that seems irrational.