Symptom: a route that jumps away and returns
A route on the online delivery map is not a GPS trace. It is a path that connects the positions of transmitters the phone detected along the way. That is why any error in transmitter data shows up immediately as geometry: the line makes an unnatural angle, runs off to the side and returns to the same spot.
At the plant in question the report was as follows: for some trips the map showed a point several hundred metres away from the road, and the next point was back on the road again. A driver could not cover such a distance in a few seconds, so from the start it was clear that the problem lay in the data, not in the vehicle's movement.
The team did not start by replacing hardware or clearing the cache. It started with the question: which transmitter is the common factor behind all the jumps?
Why two transmitters can look like one to the system
A transmitter is recognised by a pair of numbers: major and minor. The system does not see which physical unit sent the signal, only the identifier. If two devices several hundred metres apart broadcast the same major:minor pair, the system treats them as one transmitter.
The effect is predictable. A phone near the first transmitter records a route point placed at the location assigned to that identifier in the database. A phone near the second one does the same, but the database knows only one location. One of the two locations will therefore always be wrong, and the route of a vehicle moving between them starts to jump.
One consequence is worth remembering: changing the stored position does not fix anything in such a situation. The error just moves to the other place, because two physical devices still share one identifier.
Bounces caused by one transmitter in the scan
Diagnosis step by step on route data
The true position of a device is established from neighbouring route points. A point that jumps away from the previous one and to which the next point returns is an artefact. The previous point shows the actual place of the vehicle.
The administrator applied a simple detection rule: a bounce is a point more than 55 units away from the previous one, after which the next point returns close to the previous one, meaning closer than 21 units. The scan covered over one million route points from 14 days, so the result did not depend on a single trip.
Ranking transmitters by number of bounces
After the bounces were found, each one was assigned to the transmitter that caused it. The result was a ranking: a few transmitters at the top with many bounces and a long tail of single cases.
This is an important warning against jumping to conclusions. Many apparently guilty transmitters are merely the return points of one real culprit. In one scan, 151 of 651 bounces disappeared after silencing a single transmitter. That is why the first action is to silence the leader of the ranking, not to correct the whole list in bulk.
Telling a duplicate apart from a vehicle that stopped
A vehicle that stopped and then set off from a different place is not evidence of a duplicate. The time gap between the points decides. Real duplicates had a gap on the order of 5 seconds, too short to cover 400 to 650 m. If the gap is an hour, the bounce may simply be an ordinary trip.
Action: silencing the duplicate without losing data
The duplicate was silenced by changing its major number to a value that no device transmits. Position, minor and location stayed in the database, so reversing the operation means changing one number. Nobody deleted records, rewrote history or touched the maps.
The administrator was aware of the cost of this method: both transmitters of the pair drop out of positioning until a site visit. Position is therefore temporarily less precise in that spot, but the routes stop lying. In practice the plant chose this solution, because the loss of one point on the road is milder than jumps of several hundred metres.
The permanent fix requires a service visit: one of the two devices receives a new, unique identifier, which is saved in the database together with the correct position.
- Select the transmitter with the largest number of bounces from the ranking.
- Change its major to a value that no device transmits.
- Leave minor, position and location unchanged so that the change can be reversed.
- Synchronise the positioning cache without clearing it entirely.
- Plan a site visit and give the second device a new, unique identifier.
Verification after the change
After the identifier change the positioning cache has to be synchronised, but without clearing it entirely, so as not to disturb the other transmitters. The team then checked two facts in the data.
First, the silenced transmitter no longer records new route points. Second, the remaining transmitters keep recording them at the normal rate. Had the second condition failed, the synchronisation would have hit the whole infrastructure.
It is also worth remembering that route points are immutable records of the moment the signal was received. Trips made before the correction keep the jump in the preview. This is not a bug but a property of the system: history is meant to reflect what the system recorded at the time.
Conclusions for the location system administrator
The most important lesson: a route jump is a signal about data quality, not a failure. The diagnosis rests on route data rather than hunches, and the first step is a ranking of transmitters by bounces.
The second lesson concerns prevention. The uniqueness of the major:minor pair must be checked at every installation. We describe the numbering rules in the recommendations on transmitter numbering and naming, and the methods for detecting duplicates from data in a separate best-practices guide.
The third lesson: a temporary fix and a permanent fix are two different tasks. Silencing closes the problem on the map within a few minutes, the service visit closes it physically.
Checklist
Video
Frequently asked questions
Does a route jump mean the system has failed?
No. Most often it points to a data problem with a transmitter, for example a duplicated identifier or a wrong position. The system draws exactly what the database says.
Is it enough to correct the transmitter position in the database?
Not for a physical duplicate. Two devices share one major:minor pair, so the correction only moves the error to the other place. One of the two identifiers has to be changed.
Does silencing delete data?
No. Only the major number changes. Position, minor and location stay, and reversing the change means changing one number.
Will old routes be corrected?
No, because route points are immutable records of the moment the signal was received. Reports covering the period before the change should carry a note.
Want to check the quality of transmitter data at your plant?
Let's talk about auditing routes and transmitter numbering. We will show how to detect duplicates in your data.
Let's talk