InnerWeb
Skip to main content

Correcting transmitter position after installation: implementation notes

After installation it turns out that the saved position of a transmitter differs from the place where it hangs. The order of the correction decides whether route history and the audit log stay readable. Below are the steps, the pitfalls and the conditions.

Rules that follow from how the system works

Three properties of the system set the order of the correction. First: the transmitter position is saved in centimetres as x, y, z coordinates, and the map displays them after conversion to metres. Second: saved route points are immutable snapshots taken at the time of reading, so a correction does not rewrite deliveries already recorded, only future ones. Third: edits made in the admin application go to the audit log, while changes made outside it bypass the log.

These rules mean that the correction is made in the application, with a recorded reason and a marked time boundary after which the data is correct.

Step 1: confirm it is the position, not the identifier

Before correcting the coordinates, check whether the cause is not a duplicated identifier. Two physical transmitters with the same identifier, hung in distant places, cannot be told apart, and changing the saved position only moves the problem to the other place. Compare the deviating route point with the previous and next points of the same tracker: the previous point shows where the vehicle was.

Example: distance of the saved position from the actual one, before and after the correction

Example: distance of the saved position from the actual one, before and after the correctionBefore and after chart: the distance of the saved transmitter position from the actual one drops after the correction.010203040mBefore correction (Transmitter A): 18 m18 mAfter correction (Transmitter A): 0.5 m0.5 mTransmitter ABefore correction (Transmitter B): 35 m35 mAfter correction (Transmitter B): 0.5 m0.5 mTransmitter B
  • Before correction
  • After correction
Source: Sample calculation: assumed distances illustrating the effect of the correction, not data from a deployment

Step 2: measure the actual position

Measure the mounting place against a reference point, for example a pole or a wall, and convert it to centimetre coordinates in the map system. Enter the mounting height. Avoid reading coordinates by eye from the map, because an error of several metres produces a route deviation almost as large as the original mistake.

Step 3: record the correction in the application with a reason

Edit the transmitter in the admin application, so that the change reaches the audit log. In the service note record the old and new coordinates, the reason and the work order number. A change made in the database outside the application bypasses the log and makes it impossible to establish later who made it and when.

Step 4: mark the data boundary before and after the correction

Route records from the period before the correction stay in the history with deviations. Note the date and time of the correction and the transmitter identifier, so that an analyst knows that data from before this moment may contain deviations. In this way the audit evidence does not change after the fact, and it remains understandable to someone who reads it later.

Step 5: verify on the control route

After the correction, walk or drive the control route and check that there is no longer a deviation at the transmitter location. Only the result on the map closes the work order. If the deviation persists, return to step 1: a second transmitter with the same identifier may be hanging somewhere else.

Pitfalls and conditions

The most common pitfalls are correcting coordinates without checking for a duplicate, entering metres in a centimetre field, and editing outside the application. A condition for an efficient correction is a transmitter register with the reference point and the mounting height, because without them every measurement has to start from zero.

If there are many corrections, it is a sign that the installation process needs improvement: an installation card with labelled units and a uniqueness check of identifiers before the work order is closed reduce the number of corrections.

After a series of corrections, prepare a short summary for the maintenance team: how many transmitters were corrected, what the causes were and how the installation card was changed. The summary is recorded in the register as a review entry. In this way later installations benefit from earlier experience, and the number of corrections after installation falls over time, which is visible in the audit log.

  • Correcting coordinates without checking for a duplicated identifier.
  • Metres entered in a centimetre field.
  • Editing outside the admin application.
  • No note with the correction date, so it is not known from when the data is correct.

Video

Frequently asked questions

Does a position correction change existing routes?

No. Saved route points are immutable snapshots taken at the time of reading, so the correction affects future trips. Record the correction date to tell data from before and after apart.

In what units is the position entered?

In centimetres as x, y, z coordinates. The map displays them after conversion to metres, so a unit mistake shifts the transmitter by an order of magnitude.

Why must the correction be made in the application?

Only edits made in the admin application reach the audit log. Changes made outside it bypass the log, and their author cannot be established.

What if the route deviation persists after the correction?

Check whether there is a second transmitter with the same identifier. A coordinate correction will not help when the duplicate hangs in another place.

Put transmitter corrections in order

We will help you set up a correction procedure with a service note and a control route. Book a conversation with the InnerWeb team.

Let's talk