InnerWeb
Skip to main content

Georeferencing in a migration: implementation notes

The IT team moving a plant structure most often gets lost not in descriptive data but in coordinates. A seemingly small transformation error or a mixed-up view means an outline in the wrong place on the plan. Below are implementation notes: what to check before writing to the production environment and in what order.

0,01 m
maximum error of the back-conversion
Source: location structure migration documentation
64
control points in the verification
Source: location structure migration documentation

What georeferencing is in a plant view

Georeferencing consists of an anchor point, rotation and scale, and together with the orthophoto it belongs to the plant view. It ties the plant plan to the real position. All outlines of buildings, lines and locations are expressed relative to it, so any change to the georeferencing shifts the entire structure beneath it.

Trap 1: deleting or replacing the view

Deleting or replacing a plant view during a structure migration removes the map calibration. This error is especially costly because it does not show in the numbers: data rows may match, while the map is empty or badly aligned.

Protection: before the migration, record the georeferencing parameters of the existing view (anchor, rotation, scale, orthophoto file) and extend the procedure with a step that checks they are present after writing.

Back-conversion test result: control points and maximum error

Back-conversion test result: control points and maximum errorBar chart: 64 control points and a maximum error of 1 centimetre.020406080valueControl points (pcs): 64 value64 valueControl points (pcs)Maximum error (cm): 1 value1 valueMaximum error (cm)
Source: Location structure migration documentation: 64 points, error 0.01 m (1 cm)

Trap 2: a transformation function different from the editor's

The migration script must calculate coordinates with the same transformation function as the editor: local metres to WGS84 with the PUWG92 correction. If the script uses a simplified formula, the outlines created by the migration will differ slightly from those drawn by hand in the editor. The difference becomes visible only when a building from the migration and one added by hand stand next to each other.

The simplest practice: the script calls the function of the same module the editor uses, instead of copying its formula.

Trap 3: coordinates stored in another view's frame

Location coordinates are sometimes stored in the frame of a different view. Before using them in a migration, check which view a row belongs to and whether that view has georeferencing. A row stored in the frame of a view without georeferencing cannot be converted to a position in the field.

Example: a team copies rows from the plant register into the structure of a new view without noticing that some items were recorded for an older, unused view. The result is locations that exist in the database but do not appear where they are expected on the map.

Verification: control points converted back

A good practice is a back-conversion test: selected control points are converted from geographic coordinates back to the plan and compared with the original. In one verification of the structure migration, outlines converted back landed on the plan with a maximum error of 0.01 m across 64 control points. A result like this gives a basis for accepting the transformation as correct.

Choose control points so that they cover the corners of the outermost buildings and points near the edge of the view, because that is where the error of rotation and scale is largest.

  • Georeferencing parameters of the existing view recorded before the migration.
  • The same transformation function as in the editor.
  • Each row checked for membership in a view with georeferencing.
  • A back-conversion test on control points, including the outermost ones.

Order of actions before writing to production

The order we recommend: a copy of the structure, trial mode with transaction rollback, review of the gate report, back-conversion test of control points, and only then the write. The migration can be repeated, so there is no pressure to write on the first run. If any gate is not green, nothing is written.

Video

Frequently asked questions

Why must the view not be replaced during a migration?

Georeferencing and the orthophoto belong to the view. Deleting or replacing it removes the map calibration, and restoring it requires re-alignment.

Which transformation should the script use?

The same one the editor uses: from local metres to WGS84 with the PUWG92 correction.

How do I check the result before writing?

Convert control points back to the plan and compare them with the original. In one verification the error was at most 0.01 m across 64 points.

Let's check the migration before writing

If your IT team is planning a plant structure migration, we will review the control points and the order of actions with them. Arrange a short technical call.

Let's talk