This page explains the core odometer-based model behind odostrada. See the main site for the full overview.
Odometer Workflow
An Odometer Mileage Tracker
odostrada is built for people who prefer mileage records tied to real odometer readings instead of constant route surveillance.
The core model
Your first reading becomes the starting anchor for a vehicle. The next reading on that same vehicle creates the next anchor and calculates the trip distance between the two.
That is why the workflow feels different from a GPS tracker. The odometer is the backbone of the record.
Why some users trust it more
Odometer-based logging can feel easier to review later because every segment is tied to a reading you entered or captured, not an invisible route trace that ran behind the scenes.
For users who care about deliberate recordkeeping, that makes the log feel more intentional and easier to defend.
More than a simple odometer log
odostrada combines odometer capture with business-purpose tags, location tags, trip edits, trip splitting, CSV export, and fuller backup options. The point is not just to save readings. It is to turn them into structured business records.
That makes it useful for self-employed drivers who need a mileage log in miles or kilometers without giving up control of their own data.
Mileage records built around the odometer
Capture the reading. Verify the trip. Keep the record clean.