Release Notes | Cyclone 3DR

Import

Export

Point Cloud

Files ASCII (*.asc, *.csv, *.xyz, *.yxz…)

Leica Geosystems (*.pts, *.ptx) and LGS/LGSX (*.LGS/LGSx)

Leica Nova MS50/60 (*.sdb, *.xml)

ShapeGrabber (*.3pi)

3DReshaper binary file (*.nsd)

AutoDesk DXF (*.dxf)

STL (*.stl)

Polyworks (*.psl)

Leica T-Scan + Steinbichler (*.ac)

LIDAR data (*.las; laz)

Other ASCII (*.*)

Zoller and Fröhlich *(.zfs - *.zfc)

PLY points without triangles (*.ply)

ESRI ASCII (raster format *.asc)

FARO (*.fls - *.fws)

POLYWORKS (*.psl)

E57 (*.E57 files)

LandXML files (*.xml)

Riegl (*.RDBX)

ASCII FILES (*.asc, *.csv…)

Binary files (*.nsd)

Leica Geosystems (*.pts, *.ptx, *LGSx)

E57 (*.e57)

IGES (*.igs)

LAS (*.las)

LAZ (*.laz)

Autodesk DXF (*.dxf)

Mesh

STL format (*.stl)

Binary PBI format (*.pbi)

DXF 3Dface format (*.dxf)

Ascii POLY format (*.poly)

OBJ format (*.obj)

Ascii Leica format (*.msh)

OFF files (*.off)

PLY (*.ply)

GLB format (*.glb, *gltf)

Ascii and binary STL format (*.stl)

Binary PBI format (*.pbi)

DXF 3Dface format (*.dxf)

Ascii POLY format (*.poly)

Vertices only (*.asc)

DXF polyline (*.dxf)

Ascii Leica format (*.msh)

PLY (*.ply)

LandXML (*.xml)

OBJ format (*.obj)

GLB format (*.glb)

FBX format (*.fbx)

IFC / IFCSite type (*.ifc, *.ifczip)

Contour / Section

IGES format

DXF polyline format

Binary MLI format (*.mli)

IGES format

DXF polyline format

Binary MLI format (*.mli)

ASCII formats

CAD / BIM Models

IGES

STEP

DWG

IFC

RVT

IGES

STEP

DXF

IFC (Piping models)

Project

Cyclone 3DR (*.3dr)

DXF - DWG

XML

Cyclone ModelSpace View (from IMP)

Cyclone 3DR (*.3dr)

DXF

PDF 3D

SKETCHFAB

Report

PDF

CSV

BCF

Image

BMP

JPEG

JPG

PNG

Ortho-image including georeferencing information as TXT file

JPG

JPEG

BMP

PNG

TIF (Ortho-image only)

Trajectory (mobile scanner)

Leica Geosystems (*LGSx)

Leica Geosystems (*LGSx)

Send From

Send To

Point Cloud

-

-

Mesh / Surfaces

Autodesk AutoCAD

Hexagon MinePlan 3D

Hexagon BricsCAD

Autodesk AutoCAD

Hexagon MinePlan 3D

Hexagon BricsCAD

Contour / Section / Points

Autodesk AutoCAD

Hexagon MinePlan 3D

Hexagon BricsCAD

Autodesk AutoCAD

Hexagon MinePlan 3D

Hexagon BricsCAD

CAD Model

Autodesk AutoCAD

Hexagon BricsCAD

-

Image

-

Autodesk AutoCAD (ortho-image)

Hexagon BricsCAD

Menu

Feature

Comment

Extract

Contour Lines

1 layer for standard contour lines and values.

1 layer for major contour lines and values.

Extract

Scan to Plan

1 layer per slice (floorplans or sections)

Extract

Virtual Surveyor

1 layer per layer created in 3DR Virtual Surveyor project.

Extract

Scan to Pipe

1 layer per pipe trace

Analysis

Gridded Inspection

Surface Analysis with a Grid

Points and values on grid can be directly sent to CAD SW product. Sent to active layer.

Texturing

Extract Orthoimage

Sent to active layer.

Analysis

Profile Extraction

Profile 3D Inspection

Profile 2D Inspection

1 layer for 2D Grids

1 layer for inspection objects

1 layer per section

1 layer per axis points

1 layer per axis point quotations.

Tank

2D Preview / Export

Menu

Feature

Comment

Extract

Virtual Surveyor

No selection is required for this feature. Thus, it can be used for any kind of object in a 3DR project.

Extract

Scan to Plan

Surface Modeling

Scan to Mesh

A clipping box as input is recommended to define an area of interest.

Analysis

Stockpile

Analysis

FF/FL Analysis

A maximum number of points is exposed in the first step of the workflow. It is recommanded to keep a high value to execute an accurate analysis on a dense point cloud.

Analysis

Visual Notes

No selection is required for this feature. Thus, it can be used for any kind of object in a 3DR project.

Menu

Feature

Comment

Texture

Smart Texture

Standard Texture

Edit Mask

It is mandatory to convert the images from the LGSx when a texturing workflow with images is expected by the user.

Image object usage

Group / Ungroup

In the treeview, only the converted images from the LGSx file can be grouped and ungrouped.

Menu

Feature

Comment

Analysis

Inspection Notes

Input: Inspected BIM Model

Feature to report issues from an inspection and that gives the ability to create manual notes that contains screenshots, images from disk, labels and deviation values (attached CSV), clipping object information and coordinates and orientation of viewpoint; but also, a user-defined title, an assignment (email address), a comment and a priority.

Analysis

Visual Notes

Input: BIM Model

Feature to report comments and notes based on visual analysis of a BIM design model and the captured reality. The feature gives the ability to create manual notes that contains screenshots, images from disk, distance measurements, clipping object information and coordinates and orientation of viewpoint; but also, a user-defined title, an assignment (email address), a comment and a priority.

Analysis

Clash

Input: A point cloud and a BIM Model

Feature to report clashes that contain screenshot, clash status (clash, no clash or undefined) and a comment.

All tickets refer to the same assignment (email address).

Analysis

Progress Monitoring

Input: A point cloud and a BIM Model

Feature to report the progress monitoring analysis.

Default export contains a summary (progress distribution between installed, in progress, not installed and no data).

Ability to customize the export and to create additional single tickets per analyzed element depending on their status (installed, not installed, in progress).

All tickets refer to the same assignment (email address).

Touch Mode

BIM Inspection

Input: A point cloud and a BIM Model

The “Touch Mode” BIM Inspection workflow also offers a way to create BCF issues.

The contents are similar to the notes that are exported from “Inspection notes”, which is the desktop equivalent of BIM Inspection.

Name

Menu

Feature

File extension

Contents

Example of use cases

Illustration

Class standard

File > Settings

Classification

XML

•  The list is by default defined the Hexagon standard list composed of 256 indexes. This Hexagon standard is democratized among the Hexagon products using point cloud classification and is compliant with the ASPRS definition of the first 64 indexes.

• The users can customize the name, the color the “favorite” status for each index among the 256 classes.

• The Hexagon standard list can be restored in 1-click, which is important for a unified experience between Reality Capture products and adjusted to new models.

• The list can be exported and reimported to XML.

• For the usage of Manual Classification for specific jobs, users can edit new classes (color and name) to make sure that all Cyclone 3DR projects are consistant.

• The users can adapt the names and the colors for a customer who uses a specific standard. The users can then save a XML file to save time when they need to repeat the operation for another job.

Feature code standard

Extract

Virtual Surveyor

CSV

Settings are accessible from Virtual Surveyor feature.

Two types of CSV can be managed for:

• Layers (colors + names + pixel size of assets)

• Feature Codes (layers + colors + names + beginning of index + description)

• Users must deliver topographic plans according to standards that are defined by the end customers (Department of Transportation, Municipality, Local authority, …).

• It is extremely easy to understand Cyclone 3DR template and to create a customized list of Layers and of Feature Codes in a spreadsheet from any type of text-type files.

Colormap definition

Analysis

Edit colors

Gradient

Scripting

RSI

For any colorized/inspected objects (point cloud, models, polylines), the users can edit the color gradient inside the inspection feature or from the “Edit Colors” feature.

With the Save / Load feature, it is very convenient to reuse a specific color gradient for repetittive analysis.

To build a RSI file, the best way is to create it from Cyclone 3DR user interface and to save to RSI. Users can define:

• the ranges,

• the steps,

• the colors,

• the values,

• the unit.

Regular or repetititve Design vs As-Built verification:

• Define a tolerance-standardized colormap for a specific manufacturer, or a specific type of object.

• Applications are multiple: Manufacturing, BIM, Road or Tunnel analysis, …

Report template

Report

Template Library

Scripting

MLT

 With the embedded report editor of Cyclone 3DR, there are various templates that are adapted to the different types of chapter:

• General aspects (footer, header, …)

• Analysis (Stockpile, Compare/Inspect, …)

• Image positioning

• Statistics

• Tank Inspection workflow

A dedicated help page is part of the online documentation to explain the contents of the templates.

A user might adapt a weekly scan vs as-built comparison report he has to do on a regular basis for his own customer.

Thanks to MLT files, it is easy for him to save and to reuse a template for the repetitive analysis reports.

Camera parameters

Texturing

Estimate Pose

Scripting

INCAM
EXCAM

1. INCAM Files

   • INCAM files typically contain internal camera parameters. These parameters are crucial for photogrammetry processes as they describe the intrinsic properties of the camera used to capture images.

   • Internal parameters might include focal length, principal point coordinates, lens distortion coefficients, and other calibration data that help in accurately reconstructing 3D models from 2D images.

2. EXCAM Files

   • EXCAM files generally store external camera parameters. These parameters describe the position and orientation of the camera in space relative to a given coordinate system.

   • External parameters include the camera's location (X, Y, Z coordinates) and its orientation (rotation angles or a rotation matrix). These parameters are essential for aligning multiple images or point clouds in a common reference frame.

Those files are usefull in the following cases:

• Manually defining camera parameters from a set of photos taken by a camera

• Editing camera parameters of photos taken by a not supported scanner.

The INCAM file can be generated once for all by the Calibrate Camera commands. Batch edition can also be possible through scripting.

The EXCAM file can be generated per images by Estimate Pos command.

Matrix file

Coord Sys

N points Registration

Best Fit Registration

TXT

Store the definition of a 3D transformation as a matrix in a file.

• Apply a bestfit between two objects and export the result in another software.

• Repetitive best-fit operations for the same project

Name

Application

Used scanners for training

Other recommendations

Features using class information

Indoor Generic

Indoor – All

All

Relevant for Scan to Model workflows.

Indoor Construction Site

Indoor – All

All

Relevant for “Scan to Verify” workflows for as-built verification for example.

Progress Monitoring

Outdoor for TLS

Outdoor – All

TLS

Generic classification that can be used with other sensor types.

Heavy Construction UAV

Outdoor - Heavy Construction

UAV Sensors

Recommended for Heavy Construction environment only. Can be used with other sensor types.

Relevant to execute before Virtual Surveyor, DTM

Mobile BLK Filter People

All

BLK2GO and BLKARC

Recommended with BLK2GO and BLKARC only.

Clean moving people and objects.

Road for MMS

Roads

TRK series

Recommended with all MMS sensors and useful with TLS scanners like RTC360 and BLK360 to do extraction.

Relevant to execute before Virtual Surveyor, DTM

Plant

Plant facilities, MEP environment

All

Recommended with static scanners

Relevant to execute before Scan to Pipe