Due to the way the total distance metric is calculated, when the user is viewing metrics for "All Time", it will calculate the max odometer reading minus the minimum odometer reading across all years, e.g.: if the max odometer reading in February 2024 is 220000 and the minimum odometer reading dating back to February 2018 is 150000, the app will deem that the total distance traveled in February across all times is 70000 miles, and will display so in the chart. This is not a bug, but instead is a shortcoming due to how distance traveled has to be inferred from odometer readings.
-
Since odometer readings are linear, it can subject the data to skewing if the user does not drive a lot in a certain month but does drive a lot in a previous year, which in turn means that the Distance Traveled metric for All Time is not the most reliable metric; however, viewing data for a specific year eliminates this skewing since it is not affected by data of a previous year. To ensure the highest accuracy of distance traveled, you should follow the [[Best Practices|Odometer#best-practices]] when it comes inserting odometer records.
+
Since odometer readings are linear, it can subject the data to skewing if the user does not drive a lot in a certain month but does drive a lot in a previous year, which in turn means that the Distance Traveled metric for All Time is not the most reliable metric; however, viewing data for a specific year eliminates this skewing since it is not affected by data of a previous year. To ensure the highest accuracy of distance traveled, you should follow the [[Best Practices|Records/Odometer#best-practices]] when it comes inserting odometer records.
tl;dr: if you're relying on the total distance traveled metric to plan/budget future services, it is recommended that you use the metrics of the previous year instead of "All Time".
