InnerWeb
Skip to main content

Case: transmitter recorded inside a warehouse instead of beside the road

Every delivery passing one point on the plant road drew a short jump into the warehouse and back on the map. Physically the transmitter hung by the road, but in the database it had a position inside the building. We show how the logistics coordinator and the administrator together established which transmitter of the pair was active and what they corrected.

2
database rows for one physical point in the described setup
Source: karta
0
route points in the spare row
Source: karta

Situation: deliveries with a bounce into the warehouse

The logistics coordinator at a production plant noticed a regular pattern on the delivery map. A vehicle drives along the road, at one point the line jumps into the interior of the warehouse and immediately returns to the road. This repeated on every trip along the same route.

The regularity was the first clue. Random reading errors produce scattered bounces in different places. A repeated jump to the same place means the system consistently believes in the wrong position of one specific transmitter.

Mechanism: how a wrong position draws a jump

A delivery route is a path between the positions of transmitters detected by the phone. If a transmitter mounted by the road has a position inside the warehouse in the database, every delivery that detects it draws a jump to that place and back.

That is why the solution lies in the database and not in the field. The device does exactly what it should: it broadcasts its identifier. The error sits in the identifier-position pair.

An additional trap concerns names. The name of a transmitter shown on the map comes from the location assigned to it, not from the transmitter itself. If the location had earlier been chosen as the warehouse, the name also suggests the warehouse, which makes it harder to guess that the transmitter hangs somewhere else.

Two rows for one point: active and dormant

Searching the database revealed a second surprise. One physical navigation point had two transmitter rows in the database with a shared minor number and different major numbers. Only one of them was actually detected, the other was a dormant spare.

Such a configuration is legitimate and sometimes deliberate, for example when a transmitter was replaced with a unit using another major. The problem appears when someone corrects the position of the row that is not the live one. The fix then lands on the spare record and nothing changes on the map.

How to establish which of the pair is active

The number of route points recorded for each of the two transmitters decides. The active one has many, the spare has zero. This is an objective criterion, independent of descriptions in the database or of the memory of the people who installed the equipment.

Querying the number of route points per transmitter takes a moment and eliminates guesswork. Only after that is it known which row may be edited.

Solution: correcting the right row

Having the list of pairs, the administrator chose the row that has a point history and moved its position on the map so that it lies by the road where the transmitter actually hangs. The dormant row was left untouched.

Correcting the stored position removes the jump for all future deliveries. No one had to be sent into the field and nothing had to be reprogrammed.

The plant also agreed to keep the spare rows in the database. Inactive spare transmitters are not deleted, because they may start transmitting again someday. Instead, a zero can be appended to the name of the spare so that the pair can be told apart.

  • Recognise the repeated pattern: the same jump to the same place.
  • Find all rows in the database with the same minor.
  • Count the route points of each row and identify the active one.
  • Move the position of the active row to the real place by the road.
  • Mark the spare row in its name, do not delete it.

Result and limitations

After the correction, new deliveries passed the point without a bounce. The line stayed continuous and matched the actual road, so the coordinator could again trust the map as evidence of travel time.

There is one limitation that should be flagged to the users of the reports. Route points are immutable records of the moment the signal was received, so correcting a transmitter does not rewrite history. Deliveries made before the fix keep the jump in the preview. A report covering the period before and after the change should carry the date of the correction.

If after the correction the jump does not disappear and the transmitter has only one row, check whether you are not dealing with a physical duplicate of the identifier. We describe that case separately.

Conclusions for the logistics coordinator

A repeated jump to the same place is a sign that the data of one transmitter is at fault. The key is to identify the active row by the number of route points, not by its name.

Before anyone changes a position, they should check whether the transmitter has a duplicate in the database. A change made on the spare record is ineffective and gives a false sense that the matter is solved.

Video

Frequently asked questions

How do I know which row of a transmitter is active?

Count the route points recorded for each of the pair. The live one has many, the spare has zero. Do not rely on names or descriptions in the database.

Can I delete the spare row?

This is not recommended. An inactive transmitter may start transmitting again. Instead of deleting it, add a zero to its name to tell the pair apart.

Where does the transmitter name on the map come from?

From the location assigned to the transmitter, not from the device itself. Changing the location therefore changes the displayed name.

Will the correction fix old deliveries on the map?

No. Route points are immutable records, so deliveries made before the correction keep the jump in the preview.

Does your delivery map show route jumps?

We will review transmitter pairs in your database with you and point out the rows to correct. Book a conversation about auditing location data.

Let's talk