Z+F
Prevu3D supports the following scanners from Z+F:
-
Z+F Imager 5010C
-
Z+F Imager 5010X
-
Z+F Imager 5016
-
Z+F FlexScan 22
Examples of Z+F software for processing:
Data Processing
Section titled “Data Processing”Terrestrial Scanner
Section titled “Terrestrial Scanner”Export Settings
Section titled “Export Settings”In order to process Z+F Terrestrial Scanner dataset inside Prevu3D, we require the following files:
- Structured E57 (Pictures are optional)
Step 1: Export Panorama Images:
-
From the main bar, select Color > Export high resolution panoramas…#
-
Export options:
-
Select
Choose from list -
Image type
jpg -
Resolution
high (width=10000)
-
-
Then select
OK

Step 2: Export E57
-
From the export project items menu, select all the items you wish to export:
-
In the Format settings tab, select the following settings:
-
Add panorama images
-
Enter your file name and file path, then select
Export

- Once exported, you will be able to upload your e57 files inside Prevu3D by following the upload workflow.
SLAM Scanner (FlexScan)
Section titled “SLAM Scanner (FlexScan)”Export Settings
Section titled “Export Settings”In order to process Z+F SLAM Scanner (FlexScan) dataset inside Prevu3D, we require the following files:
-
Pointcloud (.LAS)
-
Trajectory (.txt)
-
[Optional] Pictures
-
[Optional] Pictures Information
Step 1: Define export settings
- Select the “Settings…”

-
[Optional] Panoramas : Enabled
-
Select the Format: las
-
[Required] Track : Enabled

Step 2: Access the data
Following the export process, you may find the data inside your “export” directory

There, each FlexScan-dataset will be located in its own subdirectory

You will find the required files.

In the example below above we can see:
-
Pointcloud (.LAS) => backpack log_1_2_complete.las
-
Trajectory (.txt) => backpack log_1_2_complete_laser_0.txt
-
[Optional] Pictures => All the JPG files (backpack log_1_2_complete-idx249.jpg / backpack log_1_2_complete-idx293.jpg / backpack log_1_2_complete-idx343.jpg …)
-
[Optional] Pictures Information => All the JSON files (backpack log_1_2_complete-idx249.json/ backpack log_1_2_complete-idx293.json/ backpack log_1_2_complete-idx343.json…)