InnerWeb
Skip to main content

Moving a location structure from another system: integrator's guide

A plant that already keeps a location register in another system does not have to enter it into the InnerWeb map from scratch. An integrator can move the structure with a script, but only if the script keeps the identifiers, calculates coordinates with the same function as the editor and checks the result before anything is written. Below we describe the successive steps: backup, rollback trial and write.

0.01 m
maximum error on 64 control points in one verification
Source: internal card

Step 1: understand where the georeferencing lives

Before you start moving rows, establish what a view is in the target model. The georeferencing (anchor point, rotation, scale) and the orthophoto belong to the plant view. Deleting or replacing such a view during a structure migration removes the map calibration, and restoring it requires new measurements. This is the most expensive mistake you can make, so the first rule is: a migration does not delete or replace views that carry georeferencing.

It is also worth remembering that the level named hall means a plant division or view, and buildings are areas inside it. The source register may name these concepts differently, so before moving the data build a mapping table of concepts: what in the source system corresponds to a view, a building, a line and a location.

Step 2: keep the identifiers and number new items separately

Data from the existing system is moved with its identifiers preserved, and new lines and locations receive numbers from a separate range. This way the mapping of old items to new ones stays reproducible: for every row in the target system you know where it came from, and for items added during the migration it is clear that they are new.

When you choose the number range for new items, leave a clear margin above the largest source identifier and record the range in the migration documentation. Changing the range after the fact makes a later audit harder.

Sample breakdown of migration time for one plant

Sample breakdown of migration time for one plantBar chart: sample hours of the migration steps, from 4 to 16 hours05101520hrsMapping concepts: 8 hrs8 hrsMapping conceptsScript and control points: 16 hrs16 hrsScript and controlpointsRollback trial: 4 hrs4 hrsRollback trialWrite and verification: 6 hrs6 hrsWrite andverification
Source: Sample calculation: planning assumptions, not data from a specific client

Step 3: calculate coordinates with the same function as the editor

The migration script must calculate coordinates with the same transformation function as the editor: from local metres to WGS84, with the PUWG92 correction. A custom, simplified formula in the script will drift away from the editor, and the outlines will be shifted relative to the plan. Check the result on control points converted back: in one migration verification, outlines converted back hit the plan with a maximum error of 0.01 m across 64 control points.

Before using the coordinates, also check which view a row belongs to. Location coordinates may be stored in the frame of a different view, and using them without checking whether that view has georeferencing places objects in the wrong position.

Step 4: take a backup and run a rollback trial

A structure migration can first be run in rollback-trial mode, in which the transaction is undone at the end, and only then in write mode. A backup of the structure is made before writing, and the migration itself is repeatable, so it can be run again after corrections. A rollback trial performs all the steps and checks but reverts the changes at the end, so the team sees the full report with no risk to the data.

When you review a trial, read the report of the gates rather than only the success message. If any gate returns a value other than zero, do not proceed to writing. The details of the consistency gates are described in a separate checklist.

Step 5: write and verify after the migration

Write only after a clean trial. After writing, open the map and compare several objects with the source plan: building outlines, line assignments, floors. Floor rows are created only for buildings with more than one level, because a building with a single ground floor gets no floor row. Otherwise the level panel would show the floors of other buildings.

Keep the pre-migration backup until the plant's users accept the result. For a group migrating several plants, the same script and the same procedure are repeated at each of them, which is one of the reasons why subsequent migrations go faster.

Video

Frequently asked questions

Can I run the migration without a trial?

Technically yes, but it is a bad idea. A rollback trial shows the full report with no risk to the data, and it is cheaper than correcting a faulty write.

What if the source register has no georeferencing?

First calibrate the plant view in InnerWeb: anchor point, rotation and scale. Only then migrate the objects with their local coordinates.

Can you trace where a location came from after the migration?

Yes, if the source identifiers were kept and new items were numbered from a separate range. The mapping is then reproducible.

Do you have a location register in another system?

We will assess with you how to move it into the plant map without losing the calibration and with a reproducible mapping of items.

Let's talk