You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #1949 it would be nice if OpenTracks could determine the bicycle wheel circumference on its own, so that I did not have to remember and type it when switching bicycles.
There could be a menu item that is available during a recording or , to calibrate the wheel size. The user would have to activate it manually. The result would apply to the entire current recording and any subsequent recordings.
Alternatively, near the start of a GPS based recording, OpenTracks can detect when I have been riding straight on a level surface for a few tens or hundreds of meters. If the calculated wheel circumference differs from the configured one, it would display a message with the options "adjust" or "ignore". I think that this would be problematic in various respects: What exactly is "near the start"? What if one starts at a steep hill or in an area of bad GPS reception? What if the display was already turned off?
The text was updated successfully, but these errors were encountered:
Seems like a big feature for an edge case, better proposal for now is to add an ability to save different bikes configurations and allow to change them with 2 taps on the main screen. Not only the circumference, but maybe also specific sensors.
Related to #1949 it would be nice if OpenTracks could determine the bicycle wheel circumference on its own, so that I did not have to remember and type it when switching bicycles.
There could be a menu item that is available during a recording or , to calibrate the wheel size. The user would have to activate it manually. The result would apply to the entire current recording and any subsequent recordings.
Alternatively, near the start of a GPS based recording, OpenTracks can detect when I have been riding straight on a level surface for a few tens or hundreds of meters. If the calculated wheel circumference differs from the configured one, it would display a message with the options "adjust" or "ignore". I think that this would be problematic in various respects: What exactly is "near the start"? What if one starts at a steep hill or in an area of bad GPS reception? What if the display was already turned off?
The text was updated successfully, but these errors were encountered: