Separate registration from georeferencing
Registration brings scans into agreement within a common framework. Georeferencing relates the dataset to a specified project or geographic reference. A dataset can be consistently assembled in a local system without being positioned in the coordinates required by the wider project.
State which reference is required before processing. Confirm units, orientation, vertical reference and the relationship to any existing survey or design files. If more than one coordinate version is delivered, name each clearly and document the transformation. Users should never have to guess which version belongs in a coordinated model.
Request a complete handover package
The useful package includes the data and the information needed to interpret it. Ask for a scan or coverage plan, survey dates, an exclusions register and the relevant registration report. Agree whether source scan structure and imagery are required for later review.
Include a file inventory that identifies the main project, supporting folders and any reduced or regional exports. For large projects, a clear directory structure can matter as much as the chosen format. Keep an agreed naming convention for floors and zones so recipients can find the information without relying on the survey team's memory.
Understand what the chosen format contains
In Autodesk workflows, an RCP project commonly references RCS scan data. Delivering the project file alone may therefore leave the recipient without the required content. Test the package after copying it to a separate location, with its supporting files included.
E57 is another useful exchange option, but export settings affect the delivered content. Autodesk's current documentation distinguishes options involving scan structure, edits and panorama images. Specify the required information and test a representative export in the receiving application. Do not assume that every E57 file preserves the same features.
Review the evidence behind the assembly
A registration report should help the client understand how the scans were connected and where problems may remain. Request a review focused on weak connections, isolated groups and the interfaces that matter to the work. Ask the provider to explain unfamiliar statistics in terms of the agreed acceptance criteria.
Supplement numerical evidence with targeted inspection. Open sections through floor transitions, long connections and areas where multiple scan groups meet. Where independent checks are part of the scope, include their locations and results. A single summary number should not be treated as a complete description of the dataset.
Accept the files in the intended workflow
Check the delivery using the software and hardware that the project team will actually use. Confirm that files open, zones appear in the right places and coordinates behave as expected. Verify a representative measurement and inspect whether required images or scan positions are available.
Record the delivery revision and any open issues. If a lightweight version has been created for coordination, identify the master record and explain the reduction or clipping applied. Keep the accepted package intact so that later processing does not overwrite the evidence used for the original handover.
Common questions
Does registered mean ready for any engineering use?
No. Registration describes an assembly step. Suitability still depends on coverage, reference information, checks and the requirements of the intended task. A separate drawing, model or focused verification may be needed.
Should a cloud be delivered as one file or several zones?
Choose the arrangement that supports the recipient's workflow while preserving a documented master record. Zones can simplify use, but their boundaries, coordinate consistency and relationship to the complete dataset must be clear.
Further reading
This article was rewritten in October 2026 around the subject of the original Geobiro post. The original publication date is retained; the update date identifies the current text.