Export

.asc (Cloud)

.csv

.txt

.xyz

.yxz

• Saves points and clouds inside an ASCII file

• Creates as many files as objects to export

• You can configure the file's content:

  1. Content: You can choose the columns you want to export by selecting a predefined configuration in the list or by clicking on column's headers and choosing the right definition on the menu. Only available data 100 first lines are shown. When an inspection is defined in the cloud, you can export inspection as color (in this case, the colors are determined by inspection). To do so, check the Inspection values transformed in color checkbox. You can also choose the number of decimals to export (between 0 and 6).

  2. Delimiter: Define in this part the delimiter used to separate each column

.nsd

• Saves points and clouds inside a binary file

• These files can only be read by 3DR Software

• Creates as many files as objects to export

• Cloud classification data can be exported

.pts

• Saves points and clouds inside an ASCII PTS file (Leica Geosystems format)

• Creates one file containing all clouds

.ptx

• Saves clouds inside an ASCII PTX file (Leica Geosystems format)

• Enabled only if the clouds contain scanning positions

• Creates one file containing all clouds

.las

.laz

• Saves points and clouds inside a LAS/LAZ format file (version 1.4)

• Creates as many files as objects to export

• Cloud classification data can be exported

• These formats also export the current class color for each point (optionally when real colors already exist)

.lgs

• Saves clouds (intensity or inspection values, RGB colors, Classification, setup positions and scan directions) and clipping objects

• Coordinate systems are always saved, regardless of the selection. Data will be stored in WCS and the current UCS will be flagged as "Current".

• Generated files can be password protected

• Requirement: Publisher or Publisher PRO license

.e57

• Saves clouds (including scanning directions, classification, timestamp and gridded information if available) inside an e57 file.

• This format is not designed to store the scanning directions: they will be inserted as normals.

• You can choose to export all clouds in a single file (default) or to create one file per setup/track.

• Saves perspective, cubefaces and spherical images. The images masks will not be added to the created file.

• Images and clouds will be grouped using their setup positions.

.stl

ASCII or Binary

• Saves meshes or surfacic geometric features inside a STL ASCII or Binary format file

• Creates as many files as objects to export

• Note Binary is more compact than STL ASCII format, but cannot be read by text editor

.msd

• Saves meshes or surfacic geometric features inside a MSD format file

• Creates as many files as objects to export

• These files can only be read by 3DR Software

• Keeps inspection values (not the color gradient)

.poly

• Saves meshes or surfacic geometric features inside a ASCII polyhedron format file (with topology)

• Creates as many files as objects to export

• This format is mostly used by programmers. The format is the following:

Note: -1 means no neighbor on this edge.

Note: Neighbor 0, 1 and 2 refer to a triangle number, which is neighbor on edge number 0, 1 and 2. In the previous example, you can see that the triangle T0-edge1 is neighbor of triangle T1. T1-edge2 is neighbor of triangle T0.

.ply

ASCII or Binary

• Saves meshes or surfacic geometric features inside a Polygon File format file

• Creates as many files as objects to export

• This is an indexed format similar to the .poly. It is possible to export in a binary or ASCII file

.fbx

• Saves meshes or surfacic geometric features inside a binary FBX format file

• This format can store several meshes/ surfacic geometric features

• This format gives the possibility to also export color information applied on mesh vertices (textures and real or inspection or triangle colors). The first selected mesh enables the color options available.

.obj

• Saves meshes or surfacic geometric features inside a OBJ format file

• Creates as many files as objects to export

• This format gives the possibility to also export color information applied on vertices (textures, real or inspection colors). This information is saved in MTL files. You can choose to create one MTL file for all textures or one per texture. If the objects exported have both texture and inspection color, only the texture will be exported

.glb

• Saves meshes inside a GLB format file

• This format can store several meshes

• This format gives the possibility to also export color information applied on vertices (textures, real or inspection colors). If the objects exported have both texture and inspection color, only the texture will be exported

.msh

• Saves meshes or surfacic geometric features inside a ASCII Leica format file

• Creates one file containing all meshes

.igs

.iges

• Saves chosen objects inside an IGES format file

• The exportable objects are CAD objects (Edge, Face, Shell...), clouds, polylines, geometric objects or simple points

• Creates one file containing all objects

• To export in this format, the point clouds should not be too big

.stp

.step

• Saves chosen objects inside a STEP format file

• The exportable objects are CAD objects (Edge, Face, Shell...), clouds, polylines, geometric objects or simple points

• Creates one file containing all objects

.dxf

• Saves chosen objects in Autocad .dxf format

• The exportable objects are CAD objects (Edge, Face, Shell...), clouds, polylines, meshes, geometric objects, simple points or texts

• Creates one file containing all objects

• You can:

  • choose to export meshes as a set of polylines by checking the option

  • define the distance between texts along contours lines

  • define the texts height

.ifc

.ifczip

• Saves meshes in IFC (or zipped IFC) file format ( IFC2X3 version)

• If several meshes are exported, they will be automatically grouped in a compound first

• The exported meshes will define the geometry of the IFC Site (ground mesh)

• You can override the default IFC Site origin. This IFC Site origin has to be fulfilled in the current document unit. This may be suitable with large coordinates and won't modify the georeferencing.

• Exchanges between Autodesk Revit and 3DR: Revit internal coordinates are not georeferenced:

  • If the georeferencing doesn't matter, you can keep Revit internal coordinates. Use the internal origin with orientation when exporting IFC from Revit; just export using the WCS when exporting IFC from 3DR.

  • Otherwise, you can export the IFC using a UCS defining an offset with the WCS. This offset has to be similarly defined in Revit. In other words:

    • Either the WCS stands for the georeferenced space and the UCS for the internal coordinate space

    • Or the WCS stands for the internal coordinate space and the UCS for the georeferenced space.

.xml

• Saves meshes, surfacic geometric features, multilines or points inside a LandXML file format (from Leica MS50 for example)

• Creates as many files as objects to export

.asc

Polyline

• Saves polylines or linear geometric features inside an ASCII format file

• Creates one file containing all objects

• Each polyline begins with the letter 'D' like "departure" and ends with letters 'E' (like "end") or 'F'

Example (note that first polyline is closed because the first point is repeated at the end):

D
280.905524 -311.389365 0.000000
350.905524 -241.389365 0.000000350.905524 238.610635 0.000000280.905524 -311.389365 0.000000F
D
290.905524 78.610635 0.000000
290.332831 76.287026 0.000000
288.745856 74.495706 0.000000
F

.mli

• Saves polylines or linear geometric features inside an ASCII format file

• Creates one file containing all objects

.bmp
.jpeg
.jpg
.png

• Saves images inside an image format file