Full-body Scans
There are many possibilities how to use RealityScan with different full-body scanners. They all depend on user's needs and scanner parameters.
Scanning options
Scan requirements:
-
( 1 ) Scan with a fixed coordinate system:
the distance measured in the 3D scan has to represent the distance in the real world
-
( 2 ) Scan with an arbitrary coordinate system:
the distance measured in the 3D scan does not need to represent the distance in the real world
Types of scanners:
-
( a. ) Fixed-camera setup:
no camera is moved, rotated or changes its focal length and parameters of each camera remain the same across multiple scans, there is a completely fixed camera setup
(Camera movement of even 1 millimeter or camera rotation of 1/10 degrees is visible in an image. Therefore, the camera setup has to be fixed really firmly.)
-
( b. ) Bending-camera setup:
cameras can move a little bit, there is not a completely fixed camera setup
Scans' usage:
-
( i. ) Operator-based:
each scan is processed by an operator separately
-
( ii. ) Automatic:
each scan is processed automatically and possibly post-processed later
Possible approaches
With a suitable combination of the options described above, there are 8 different approaches how to use RealityScan in processing of full-body scans:
-
( 1.a.i ) Scans with a fixed coordinate system created using Fixed-camera setup with Operator-based processing:
- preservation of model position and distances in scans is required
- RealityScan workflow with XMP metadata is used
- scans are processed in the user interface (UI)
-
( 1.a.ii ) Scans with a fixed coordinate system created using Fixed-camera setup with Automatic processing:
- preservation of model position and distances in scans is required
- RealityScan workflow with XMP metadata is used
- scans are processed in the command-line interface (CLI)
-
( 1.b.i ) Scans with a fixed coordinate system created using Bending-camera setup with Operator-based processing:
- preservation of model position and distances in scans is required
- RealityScan workflow with flight-log data is used
- scans are processed in the user interface (UI)
-
( 1.b.ii ) Scans with a fixed coordinate system created using Bending-camera setup with Automatic processing:
- preservation of model position and distances in scans is required
- RealityScan workflow with flight-log data is used
- scans are processed in the command-line interface (CLI)
-
( 2.a.i ) Scans with an arbitrary coordinate system created using Fixed-camera setup with Operator-based processing:
-
( 2.a.ii ) Scans with an arbitrary coordinate system created using Fixed-camera setup with Automatic processing:
-
( 2.b.i ) Scans with an arbitrary coordinate system created using Bending-camera setup with Operator-based processing:
-
( 2.b.ii ) Scans with an arbitrary coordinate system created using Bending-camera setup with Automatic processing:
In these 4 cases, only manual processing of scans in the user interface (UI) can be used, which is for approaches ( 2.a.i ) and ( 2.b.i ) described in more detail in the Quick Start tutorial.
Automatic processing of scans in the command-line interface (CLI) in approaches ( 2.a.ii ) and ( 2.b.ii ) is not used because none of the available data and metadata can be reused suitably.