Improved stop detection and distance calculation with a speed sensor
First of all, Locus is amazing, keep up the great work!
I use Locus to record rides with my road bike and noticed two things:
First, it seems like the total distance of a ride is computed with the recorded gps location points, is that right? If so, I would love to see that the distance is computed from the speed sensor data (with the comulative wheel revolutions parameter and the wheel circumference). This has obvious advantages: The distance will be much more accurate, and the update frequency of the gps points could be reduced without sacrificing accuracy, while saving battery life.
Secondly, I noticed that the stop detection seems to depend on the gps location, correct? If that is the case, one might get an unreliable stop detection if the gps is inaccurate, and a lot of false positives. In my option, it would be a much better solution to use the speed sensor for the stop detection. If the wheel stops spinning, the bike is standing and the activity should be paused. Again this has advantages: It is way more precise than using gps location updates, and thus delivers a more accurate moving average speed.
Again, I really love Locus, but these two improvements would make it the perfect cycling computer for road cyclists, making the accuracy of the track recording competitive with high end dedicated cycling computers!