FARO Connect Overview

The Reprocess SLAM workflow allows you to define advanced processing parameters to help processing in more challenging capture environments. Typically, you already have processed data using the different preset capture environments, available in the Default workflow at project creation. If this has not provided an acceptable outcome, this workflow allows you to modify parameters before reprocessing SLAM.

The Alignment workflow allows you to align multiple point clouds by providing several tools to manually select and match common user selected points between scans.

A fine alignment process is also available, and this requires that all required scans are closely aligned at the start of the process.

Note: When capturing the data, it is essential that there is at least 30% overlap between captures.

There are five Registration workflows which allow you to easily align two datasets together, by either:

• using common extracted reflective targets or user measured reference targets, present in both scans
• using extracted reflective targets or user measured reference targets together with the imported georeferenced Control Points of the captured reflective or reference targets.

The Reflective Target Alignment, Reflective Target Georeferencing, and Stop and Go Alignment workflows, use a rigid transformation, meaning the point cloud is transformed using a rigid translation and rotation matrix to best fit the control points from the reference scan.

The Stop and Go Georeferencing workflow can use either a rigid transformation, or non-rigid transformation, meaning the original data is reprocessed using the SLAM algorithm to ensure that the trajectory matches the control points.

There are three analysis workflows that can be applied to project dataset, depending upon you output needs.

• Change Detection

When a project has scans (.laz) of the same location, captured at different points in time, using the Change Detection workflow, the point clouds can be compared to establish differences and changes. The output point cloud colorizes objects or surfaces to indicate the changes that have occurred during the period between scans.

• Floorslices

Allows the user to create a scaled .png of a slice through the point cloud at a set height above the floor.

• Static Scans with Flash

This workflow analyses Orbis scans and automatically generates static scans at the positions where the person capturing the scan stopped. The generated scans are enhanced with Flash and color data.

Flash technology enables user to have a similar outcome as any known static scan together with the ability to measure directly on high-resolution panoramic images.

After you have processed data and confirmed the output, you can apply additional filters to further thin and clean the data. For this purpose, the following workflows are available:

• Noise reduction

With this filter you can improve the point cloud by removing outlying data points.

Example: Noise reduction Filter

• Outlier

With this filter, you can remove outlying data points from the point cloud. Outlying points can be caused by rain or dust or by partial reflections from edges.

Example: Outlier Filter

• Range

With this filter, you can remove less dense and lower accuracy points that exist furthest from the scanner. The points are filtered with respect to their distance from the trajectory.

Example: Range Filter

• Thinning

This filter creates a uniform point cloud and reduces the number of points to reduce the thickness of scanned surfaces based upon either a 2D or 3D grid method defined by the user.

Example: Thinning filter

• Transient

This filter is useful to identify temporary points caused by people or vehicles that are moving past the scanner during acquisition.

Example: Transient Filter

 

Users can post process images captured during scanning after importing, using Vision tools:

• Calculate Vision Camera Positions computes the exact position and orientation (Pose) of the camera when the images were taken, which is required to align the point cloud data and the images. This workflow outputs a .gs-vision file.
• Colorize Cloud Using Vision extracts the color information from the equirectangular images and applies it the to the point cloud data, outputting a colorized .laz file with RGB information.

Users can export project artifacts to various formats, allowing them to be imported into other applications, such as FARO SCENE:

• Point cloud .laz can be exported to .e57, .las, .laz, .ply or .txt
• Control points and reference points can be exported to .txt
• Static scans can be exported to .e57 structured format, which can then be imported and analyzed in FARO SCENE.
• Dataset to. E57 format is a specific export  that includes your Flash scans as well as embedded high-resolution images and the mobile point cloud bundle in a single file. Users can load the exported .e57 file into other software products, for example FARO SCENE.