All of those involve named locations with wrong coordinates, a mistake that's bound to happen.
However, this wasn't a case of a name being associated with the wrong location. I was simply following the trail, not using the phone to navigate at all. Besides, trying to use it to navigate to the forest that you're already in wouldn't work very well!
Rather, apparently Google Timeline stored a name instead of coordinates in a situation where that makes no sense at all. It's a forest, it doesn't have a precise x, y!
If my Fitbit is in the ballpark I would need a lot more than that.
It seems to run about 200 calories/mile. (Note: I'm hiking in mountains and the lowest trailhead is over 7,000' and carrying a daypack. A walk in the park would no doubt use less.)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.