Why does a GPS tracker read fewer kilometres than the road?
A tracker does not measure distance along the road. The platform joins the records with straight lines and adds them up. On a straight road that sum is exact. When a bend falls between two records, the straight line cuts the corner and the kilometres are lost for good.
The longer the gap between records, the more each corner costs. A 30-second interval on a city route with one street corner per kilometre can lose around 6 % of the distance. A long, gentle highway loses almost nothing with the same rule.
How does the planner calculate the gap?
It drives a repeating road of straights and bends, logs a record whenever one of your triggers fires, and compares the sum of straight lines with the road. It repeats this for 24 evenly spread start points and averages them.
- The corner factor 0.188 for 90° is the exact average of the cut corner when the bend falls anywhere between two records. The tests of this page check the simulation against it and against the arc formula.
- Speeds set the spacing of time-based records: cruise speed on straights, turn speed in the bend.
- All device values are inputs or page settings that Tracom staff can update.
Which trigger closes the gap for the fewest records?
A shorter interval adds records everywhere, including on straight road where they change nothing. A heading-change trigger adds records only in the bends, where the distance is lost.
Time only
Rule A
- Corner cutting
- High on city routes
- Records
- Same on every km
- Set by
- Interval
Time and heading
Rule B
- Corner cutting
- Small
- Records
- Extra only in bends
- Set by
- Interval and angle
Distance
Rule C
- Corner cutting
- Low at short spacing
- Records
- Same on every km
- Set by
- Metres
When you order or configure trackers, ask which reporting triggers the model supports and their ranges: time, distance, heading change and the stopped interval. The interval alone does not decide the mileage.
Can the tracker read more than the road?
Yes, when it stands with the ignition on and nothing freezes the position. Each parked record lands a few metres from the last one, and the platform adds those jumps as distance. Generators, pumps and vehicles that idle for hours collect the most.
A stop filter in the device or platform holds the position when the ignition is off, the speed is near zero or the motion sensor is still. With it, parked records add no distance.
How do you test the setting on a known route?
Pick a measured route
Use a loop with known length and real bends, for example a site road or a city block.
Drive it with the current rule
Note the tracker distance from the platform report for the trip.
Change one trigger
Send the new heading or interval setting and drive the same loop again.
Compare and keep the record
Write both results in the configuration sheet with the date and firmware.
Assumptions and limits
- The road is modelled as equal bends spread evenly. Real routes mix bends, so treat the result as a planning estimate.
- Speed is constant on straights and in bends. Braking before a bend is not modelled.
- Satellite position error while moving is not added. On open roads it changes the sum far less than corner cutting.
- Data volume counts records only, not heartbeats, events or video.
- Odometers have their own tolerance. Compare with a measured route, not only with the dashboard.
This page does not certify the distance a device records. For a contract or a dispute, test the configured device on a measured route and keep the log.