Standalone Modules

The standalone modules provide an efficient way for scripting custom workflows. After finishing a project's Analysis and Dense Cloud stage using either the SURE CLI or GUI, the modules can be employed to subsequently run the individual 2.5D and/or 3D pipeline processes.

Overview, prerequisites & parametrization

ModulePrerequisitesParametrization / control file


Analysis Dense CloudcontrolArea.txt / controlDsm.txt


Analysis Dense CloudDSMcontrolArea.txt / controlTrueOrtho.txt


Analysis Dense CloudDSMcontrolArea.txt / controlDsmMesh.txt


Analysis Dense CloudcontrolArea.txt / controlFusion.txt


Analysis Dense CloudCloud FiltercontrolArea.txt / control3DMesh.txt


AnalysisDense Cloud • Cloud Filter3D Mesh and/or DSM MeshcontrolArea.txt / controlMeshTexturing.txt


Each module executable comes with built-in information about inputs, outputs and parametrization, available by passing the "help" flag as follows:

Built-in help text
PS C:\Users\nFrames> ModuleDsm.exe --help
Command Line Parameters:
  -h [ --help ]                       Print help screen

  --log arg (=log.txt)                Path to logfile.

  --output arg (=.)                   Path to output folder.
  --controlfile arg (=controlDsm.txt) Path to ControlDsm.txt control file.
  --area arg (=controlArea.txt)       Path to controlArea.txt control file.
  --gsd arg                           Value for ground sampling distance.
  --cloud arg (=cloudlist.txt)        Path to 3D Points (.las/.laz) or mesh (.osgb) list, file or folder.
  --lidar arg                         Path to LiDAR points (.las/.laz) list,file or folder.

  --no_lidar                          Disable usage of LiDAR data (modifies controlDsm.txt)  
  --waterbody arg                     Path of the shapefile for waterbody surface.

When calling a module executable from within a SURE project folder, the input parameters - when omitted - will be set to the current project by default. Otherwise the paths to the respective inputs have to be manually specified.

The most important parameters, for example the GSD used during DSM generation, will be available directly from the module's command line interface options. More advanced configuration will be possible only in the respective control files, which can found in the project's base path.