Originally Posted by
northerntier
Obviously there would be thresholds, just like with auto-pause features. This is not rocket-science. I don't even need GPS. Here's one heuristic: after my sensors stop talking to the phone for 10 minutes, go back to the last time they recorded a move and call that the end of the ride. Poof, done.
No, I assume the real reason this doesn't exist is there aren't enough nutso commuters like me that want to track every ride and are too lazy to press the start/stop button.
I've got every ride of mine in the last decade in a database. About 3500 for around 33,000 miles, 10,000 of them touring miles :-).
(I do realize that these are low numbers for some of you.)
So on your route to wherever you're going, you get a flat tire. For whatever reason, it takes you longer than 10 minutes to fix it. Your computer doesn't get any signals from the sensor(s) and ends the ride. You fix the flat and move on and the computer starts another ride. As you continue, you pass a convenience store and decide to stop and get a cup of coffee. You go to the bathroom while you're there and stay more than 10 minutes. Computer ends the ride and starts another one when you continue. You now have turned one ride into three. If you've ever done any software development, the first thing you quickly learn is that theory is much, much easier than implementation.