Registration / QA / exchangeDATA 04

Point-cloud processing that makes the dataset reviewable and ready to move.

Processing should preserve traceability from scan positions to the delivered dataset while making the information practical for the receiving team to open, navigate, and reference.

DIRECT
ANSWER

What does this service do?

Point-cloud processing aligns individual scan positions into a coordinated dataset, reviews the registration and control, manages noise and organization, and prepares agreed files for downstream software. A registered point cloud is the starting reference for many CAD and BIM tasks. It does not prove that every required surface was captured.

USE / FIT

Start with the project condition

When this workflow earns its place.

Match the method to the uncertainty or decision it must resolve. Equipment and output follow from that use.

01

Raw FARO scans need registration

Build and review a scan network in FARO SCENE using methods appropriate to the project.

02

A dataset will not fit the workflow

Convert, segment, decimate, crop, or index data around the receiving software and use.

03

Coordinates are unclear

Document origin, units, orientation, control relationship, transformations, and export settings.

04

The model team needs a clean handoff

Package referenced files, naming, scope notes, and representative QA material together.

Before productionSCOPE INPUTS

Four decisions that keep the data useful.

01Source
Scanner format, software/version, scan count, imagery, targets, control, and prior processing.
02Registration
Target-based, cloud-to-cloud, visual, control-constrained, or combined relationships.
03Data management
Clipping, filtering, segmentation, resolution, scan structure, naming, and archive needs.
04Destination
E57, RCP/RCS, LAS/LAZ, software-native data, viewer, or another tested exchange.

Controlled sequenceDATA 04

From requirement to reviewed handoff.

  1. 01

    Inventory

    Inspect source files, scan structure, notes, control, and expected coordinate basis.

  2. 02

    Register

    Develop scan relationships with suitable target, visual, cloud-to-cloud, or survey methods.

  3. 03

    Interrogate

    Review weak links, residuals, overlap, local fit, control, and network geometry.

  4. 04

    Clean

    Apply agreed noise removal, clipping, classification, or privacy treatment without hiding uncertainty.

  5. 05

    Organize

    Set naming, groups, regions, coordinate notes, origin strategy, and manageable dataset divisions.

  6. 06

    Exchange

    Export, index, test, and package data for the receiving application.

Project-definedOUTPUTS

Files are selected for the receiving workflow.

No format or derived deliverable is automatic. The project scope confirms coordinates, detail, organization, software version, and the intended use.

01

E57

Vendor-neutral exchange that can preserve structured scan positions depending on export and importer.

02

RCP / RCS

Autodesk-indexed project and scan files for ReCap-supported applications.

03

LAS / LAZ

Common point-record formats, with LAZ providing lossless compression.

04

Native / viewer package

SCENE project or viewer-ready data when licensing, scope, and receiving needs permit.

QA / REVIEW

A single mean error value is not a complete registration review.

Review should consider network shape, redundant relationships, local fit in decision-critical areas, target quality, control behavior, scan movement, and coverage. The relevant evidence depends on the registration method and project use.

Scope boundariesREAD BEFORE USE

What the workflow does not automatically establish.

  • Processing cannot create geometry that was not captured.
  • Aggressive filtering or decimation can remove decision-relevant detail.
  • Coordinate conversion without a verified basis can produce plausible but incorrect alignment.
  • File compatibility varies by application and version; representative testing is part of a responsible handoff.

Technical answersFAQ

Questions project teams ask before they commit.

What is point-cloud registration?

Registration is the process of placing separate scan positions into one coordinated spatial relationship using targets, shared geometry, visual positioning, survey control, or a combined method.

What is a registered point cloud?

It is point data from multiple capture positions that has been aligned in one coordinate framework and approved under the project’s review method.

What is the difference between E57 and RCP/RCS?

E57 is a vendor-neutral exchange format. RCP is an Autodesk project index that can reference one or more RCS scan files. The best choice depends on the receiving application, scan structure, coordinates, and performance needs.

Can any point cloud be converted to ReCap?

Many common formats can be indexed, but source structure, size, coordinates, scanner imagery, units, and the specific software version should be checked before committing to a workflow.

Next coordinatePROJECT / SCOPE

Define the site. Define the output. Then plan the capture.

Tell us what your team needs to decide, the conditions you need documented, and the software the information must enter.