Command line mode - Revision history

Daniel at 08:26, 17 January 2026

2026-01-17T08:26:25Z

← Older revision		Revision as of 10:26, 17 January 2026
Line 103:		Line 103:
	* result is automatically saved by default (see the AUTO_SAVE command to change this).		* result is automatically saved by default (see the AUTO_SAVE command to change this).
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-OCTREE_NORMALS {radius}</code>		\|style="border-style: solid; border-width: 1px"\| <code>-OCTREE_NORMALS {radius} [-WITH_GRIDS {angle}] [-ORIENT WITH_GRIDS/WITH_SENSOR]</code>
	\|style="border-style: solid; border-width: 1px"\| ''Computes the [[Normals%5CCompute \| normals]] for all loaded clouds with the specified radius.''		\|style="border-style: solid; border-width: 1px"\| ''Computes the [[Normals%5CCompute \| normals]] for all loaded clouds with the specified radius.''

Line 123:		Line 123:
	** {local_model_type} = LS / TRI / QUADRIC		** {local_model_type} = LS / TRI / QUADRIC
	* input ''radius'' can be replaced by 'auto' to let CC try to guess a possible value (since version 2.11)		* input ''radius'' can be replaced by 'auto' to let CC try to guess a possible value (since version 2.11)

			since version 2.14 additional settings are:
			* -WITH_GRIDS {angle}
			** to compute scan grids to compute normals (with a maximum scattering angle between neighboring cells)
			* -ORIENT WITH_GRIDS / WITH_SENSOR
			** WITH_GRIDS: to use scan grids to orient normals
			** WITH_SENSOR: to use sensor(s) to orient normals

	Notes:		Notes:
Line 649:		Line 656:
	* the SF name can be used since version 2.13 only		* the SF name can be used since version 2.13 only
	* since version 2.13, it is possible to use '-1' as index to designate the default/current scalar field		* since version 2.13, it is possible to use '-1' as index to designate the default/current scalar field
			* since version 2.14, it is possible to use MIN/DISP_MIN/SAT_MIN/N_SIGMA_MIN/MAX/DISP_MAX/SAT_MAX/N_SIGMA_MAX as input values
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-SF_OP_SF {SF1 index or name} {operation} {SF2 index or name} </code>		\|style="border-style: solid; border-width: 1px"\| <code>-SF_OP_SF {SF1 index or name} {operation} {SF2 index or name} </code>
Line 747:		Line 755:
	Note:		Note:
	* since version 2.12 only		* since version 2.12 only
			\|-
			\|style="border-style: solid; border-width: 1px"\| <code>-DISTANCES_FROM_SENSOR [-SQUARED]</code>
			\|style="border-style: solid; border-width: 1px"\| ''Computes distances from every point of the cloud to the associated sensor origin (if any).''

			Options are:
			* -SQUARED: computes squared distances instead

			Notes:
			* result is automatically saved by default (see the AUTO_SAVE command to change this).
			* the default scalar field name will be 'Ranges' if not squared, or 'Ranges (squared)' otherwise. Scalar field will be overwritten if already present.
			* since version 2.14
			\|-
			\|style="border-style: solid; border-width: 1px"\| <code>-SCATTERING_ANGLES [-DEGREES]</code>
			\|style="border-style: solid; border-width: 1px"\| ''Computes compute the scattering angle from every point of the cloud (and its associated normal) w.r.t. to the associated sensor (if any).''

			Options are:
			* -DEGREES: computes angles in degrees instead of radians

			Note:
			* result is automatically saved by default (see the AUTO_SAVE command to change this).
			* the default scalar field name will be 'Scattering angles (rad)' or 'Scattering angles (deg)'. Scalar field will be overwritten if already present.
			* since version 2.14
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-M3C2 {parameters_file}</code>		\|style="border-style: solid; border-width: 1px"\| <code>-M3C2 {parameters_file}</code>
	\|style="border-style: solid; border-width: 1px"\| ''Calls the [[M3C2_(plugin) \| M3C2]] plugin (if available) on the two first loaded clouds. If a 3rd cloud is loaded, it will be used a core points. The first time, the parameters file can be created with the GUI tool (use the 'Save parameters to file' button in the bottom-left corner of the M3C2 dialog = the floppy icon). It can then be edited easily.''		\|style="border-style: solid; border-width: 1px"\| ''Calls the [[M3C2_(plugin) \| M3C2]] plugin (if available) on the two first loaded clouds. If a 3rd cloud is loaded, it will be used a core points. The first time, the parameters file can be created with the GUI tool (use the 'Save parameters to file' button in the bottom-left corner of the M3C2 dialog = the floppy icon). It can then be edited easily.''

			See [https://www.cloudcompare.org/doc/wiki/index.php/M3C2_(plugin)#Command_line]

	Note:		Note:
	* since version 2.10 only		* since version 2.10 only
			\|-
			\|style="border-style: solid; border-width: 1px"\| <code>-FACETS {options}</code>
			\|style="border-style: solid; border-width: 1px"\| ''Calls the [[Facets_(plugin) \| Facets]] plugin (if available).''

			See [https://www.cloudcompare.org/doc/wiki/index.php/Facets_(plugin)#Command_line_(since_version_2.14)]

			Note:
			* since version 2.14
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-CSF {filename}</code>		\|style="border-style: solid; border-width: 1px"\| <code>-CSF {filename}</code>
Line 771:		Line 811:
	Note:		Note:
	* since version 2.12 only		* since version 2.12 only
			* since version 2.14, the output cloud names are now {original cloud name} + '_ground_points' and {original cloud name} + '_offground_points'
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-CANUPO_CLASSIFY {classifier.prm}</code>		\|style="border-style: solid; border-width: 1px"\| <code>-CANUPO_CLASSIFY {classifier.prm}</code>
Line 848:		Line 889:
	Note:		Note:
	* since version 2.11		* since version 2.11
			* since version 2.14, secondary extensions can also be used (LAZ, etc.)
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-FBX -EXPORT_FMT {format}</code>		\|style="border-style: solid; border-width: 1px"\| <code>-FBX -EXPORT_FMT {format}</code>
Line 949:		Line 991:
	\|style="border-style: solid; border-width: 1px"\| ''Sets the default PCD file output format.''		\|style="border-style: solid; border-width: 1px"\| ''Sets the default PCD file output format.''
	Format can be:		Format can be:
	* COMPRESSED_BINARY		* COMPRESSED_BINARY (default)
	* BINARY		* BINARY
	* ASCII		* ASCII
Line 1,051:		Line 1,093:
	:<code>CloudCompare -M_EXPORT_FMT FBX -FBX -EXPORT_FMT FBX_binary -O Foot.ply -NO_TIMESTAMP -SAVE_MESHES</code>		:<code>CloudCompare -M_EXPORT_FMT FBX -FBX -EXPORT_FMT FBX_binary -O Foot.ply -NO_TIMESTAMP -SAVE_MESHES</code>
	This will open the file named 'Foot.ply' then save it in FBX binary format (same base filename, without any decoration: i.e. ''Foot.fbx'')		This will open the file named 'Foot.ply' then save it in FBX binary format (same base filename, without any decoration: i.e. ''Foot.fbx'')

	~~=Plugins=~~

	~~Some plugins have their own command line options. See for instance:~~
	* [https://www.cloudcompare.org/doc/wiki/index.php/M3C2_(plugin)#Command_line M3C2]
	* [https://www.cloudcompare.org/doc/wiki/index.php/Facets_(plugin)#Command_line_(since_version_2.14) Facets]

Daniel: /* Available options (version 2.14.alpha) */

2026-01-17T07:57:25Z

Available options (version 2.14.alpha)

← Older revision		Revision as of 09:57, 17 January 2026
Line 4:		Line 4:
	By default, this mode only opens a small console window, applies the requested actions, and eventually saves the result in a file in the same directory(ies) as the input file(s). Commands are applied in the order they are written (like a ''state machine'').		By default, this mode only opens a small console window, applies the requested actions, and eventually saves the result in a file in the same directory(ies) as the input file(s). Commands are applied in the order they are written (like a ''state machine'').

	=Available options (version 2.14.~~alpha~~) =		=Available options (version 2.14.beta) =

	{\| cellpadding="10" style="text-align:left; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #000"		{\| cellpadding="10" style="text-align:left; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #000"

Daniel at 07:57, 17 January 2026

2026-01-17T07:57:15Z

← Older revision		Revision as of 09:57, 17 January 2026
Line 1,051:		Line 1,051:
	:<code>CloudCompare -M_EXPORT_FMT FBX -FBX -EXPORT_FMT FBX_binary -O Foot.ply -NO_TIMESTAMP -SAVE_MESHES</code>		:<code>CloudCompare -M_EXPORT_FMT FBX -FBX -EXPORT_FMT FBX_binary -O Foot.ply -NO_TIMESTAMP -SAVE_MESHES</code>
	This will open the file named 'Foot.ply' then save it in FBX binary format (same base filename, without any decoration: i.e. ''Foot.fbx'')		This will open the file named 'Foot.ply' then save it in FBX binary format (same base filename, without any decoration: i.e. ''Foot.fbx'')

			=Plugins=

			Some plugins have their own command line options. See for instance:
			* [https://www.cloudcompare.org/doc/wiki/index.php/M3C2_(plugin)#Command_line M3C2]
			* [https://www.cloudcompare.org/doc/wiki/index.php/Facets_(plugin)#Command_line_(since_version_2.14) Facets]

Daniel at 07:48, 17 January 2026

2026-01-17T07:48:34Z

@@ Line 363: / Line 363: @@
 * 'N_SIGMA_MAX {N}' = mean + N * standard deviation
 |-
 |style="border-style: solid; border-width: 1px"| <code>-DENSITY {sphere radius}</code>
@@ Line 596: / Line 620: @@
 Optional settings are:
 * <code>-IN_PLACE</code> to apply the operation in place, without creating a new SF (since version 2.13)
 Notes:

Daniel at 12:34, 28 December 2025

2025-12-28T12:34:25Z

← Older revision		Revision as of 14:34, 28 December 2025
Line 645:		Line 645:
	* since version 2.13 only		* since version 2.13 only
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-SF_INTERP {SF index} {-~~DEST~~-~~IS_FIRST~~} </code>		\|style="border-style: solid; border-width: 1px"\| <code>-SF_INTERP {SF index} {-DEST_IS_FIRST} {-INTERP_NN k} {-INTERP_RADIUS r}</code>
	\|style="border-style: solid; border-width: 1px"\| ''applies the [[Scalar_fields%5CInterpolate_from_another_entity \| SF Interpolate from another entity]] algorithm to a given scalar field of the 2 first loaded clouds''		\|style="border-style: solid; border-width: 1px"\| ''applies the [[Scalar_fields%5CInterpolate_from_another_entity \| SF Interpolate from another entity]] algorithm to a given scalar field of the 2 first loaded clouds''

Line 651:		Line 651:
	The scalar-field index starts from 0. The user can use the keyword 'LAST' to designate the last scalar field.		The scalar-field index starts from 0. The user can use the keyword 'LAST' to designate the last scalar field.

	Warning: ~~for now~~ the command line ~~will~~ always ~~use~~ the same options:		Warning: before version 2.14.beta, the command line was always using the same options:
	* interpolation method: nearest ~~neighbors~~		* interpolation method: nearest neighbor
	* interpolation algorithm: normal distribution		* interpolation algorithm: normal distribution
	* radius = 1% of the destination cloud bounding-box		* radius = 1% of the destination cloud bounding-box
	* sigma = 40% of the radius		* sigma = 40% of the radius

			Since version 2.144.beta, it's now possible to specify the interpolation method:
			* '-SF_INTERP {SF index} -INTERP_NN k' to use nearest neighbors interpolation (k = number of neighbors)
			* '-SF_INTERP {SF index} -INTERP_RADIUS r' to use interpolation inside a sphere (r = sphere radius)
			(these new options must always be placed last)

	Notes		Notes

Daniel: /* Available options (version 2.14.alpha) */

2025-09-04T20:13:55Z

Available options (version 2.14.alpha)

@@ Line 320: / Line 320: @@
 * it is possible to use '-1' as index to designate the default/current scalar field
 * since version 2.13.
 |-
 |style="border-style: solid; border-width: 1px"| <code>-COLOR_INTERP</code>

Daniel: /* Available options (version 2.14.alpha) */

2025-07-13T19:14:12Z

Available options (version 2.14.alpha)

← Older revision		Revision as of 21:14, 13 July 2025
Line 167:		Line 167:
	\|style="border-style: solid; border-width: 1px"\| ''merges all loaded/generated clouds as one unique cloud.''		\|style="border-style: solid; border-width: 1px"\| ''merges all loaded/generated clouds as one unique cloud.''

	~~Note~~: result is automatically saved by default (see the AUTO_SAVE command to change this).		Notes:
			- previous clouds are unloaded from memory.
			- result is automatically saved by default (see the AUTO_SAVE command to change this).
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-MERGE_MESHES</code>		\|style="border-style: solid; border-width: 1px"\| <code>-MERGE_MESHES</code>
	\|style="border-style: solid; border-width: 1px"\| ''merges all loaded/generated meshes as one unique mesh.''		\|style="border-style: solid; border-width: 1px"\| ''merges all loaded/generated meshes as one unique mesh.''

	~~Note~~: result is automatically saved by default (see the AUTO_SAVE command to change this). This option is available since version 2.9.		Notes:
			- previous meshes are unloaded from memory.
			- result is automatically saved by default (see the AUTO_SAVE command to change this). This option is available since version 2.9.
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-SS {algorithm} {parameter}</code>		\|style="border-style: solid; border-width: 1px"\| <code>-SS {algorithm} {parameter}</code>

Daniel: /* Available options (version 2.14.alpha) */

2024-12-08T14:37:11Z

Available options (version 2.14.alpha)

← Older revision		Revision as of 16:37, 8 December 2024
Line 468:		Line 468:
	* each cloud will be replaced in memory by its cropped version (since version 2.11, the cloud is removed from memory if it's totally cropped out)		* each cloud will be replaced in memory by its cropped version (since version 2.11, the cloud is removed from memory if it's totally cropped out)
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-CROP2D {ortho_dim} {-GLOBAL_SHIFT + options} {n:number of vertices} X1 Y1 X2 Y2 ... Xn Yn</code>		\|style="border-style: solid; border-width: 1px"\| <code>-CROP2D {ortho_dim} {-GLOBAL_SHIFT + options} {n:number of vertices} X1 Y1 X2 Y2 ... Xn Yn {-OUTSIDE}</code>
	\|style="border-style: solid; border-width: 1px"\| ''Crops all loaded clouds inside or outisde a given 2D polyline. Cropping is done in a plane defined by its orthogonal dimension: X, Y or Z (i.e. coordinates along this dimension will be ignored).''		\|style="border-style: solid; border-width: 1px"\| ''Crops all loaded clouds inside or outisde a given 2D polyline. Cropping is done in a plane defined by its orthogonal dimension: X, Y or Z (i.e. coordinates along this dimension will be ignored).''

Line 484:		Line 484:

	Optional settings are:		Optional settings are:
	* -OUTSIDE: if defined only the points falling outside the input polyline will be kept (instead of inside by default).		* -OUTSIDE: if defined (after the coordinates of the vertices) only the points falling outside the input polyline will be kept (instead of inside by default)

	Note:		Note:

Daniel: /* Available options (version 2.14.alpha) */

2024-11-17T10:23:38Z

Available options (version 2.14.alpha)

← Older revision		Revision as of 12:23, 17 November 2024
Line 474:		Line 474:

	Warning, after setting the dimension, CloudCompare will expect the 2D vertices in the following order:		Warning, after setting the dimension, CloudCompare will expect the 2D vertices in the following order:
	* ~~Dim~~ = X --> YZ		* ortho_dim = X --> YZ
	* ~~Dim~~ = Y --> ZX		* ortho_dim = Y --> ZX
	* ~~Dim~~ = Z --> XY		* ortho_dim = Z --> XY

			Since version 2.14:
			* ortho_dim = Xflip --> ZY
			* ortho_dim = Yflip --> XZ
			* ortho_dim = Zflip --> YX

	Optional settings are:		Optional settings are:

Daniel: /* Available options (version 2.14.alpha) */

2024-11-17T09:53:38Z

Available options (version 2.14.alpha)

← Older revision		Revision as of 11:53, 17 November 2024
Line 468:		Line 468:
	* each cloud will be replaced in memory by its cropped version (since version 2.11, the cloud is removed from memory if it's totally cropped out)		* each cloud will be replaced in memory by its cropped version (since version 2.11, the cloud is removed from memory if it's totally cropped out)
	\|-		\|-
	\|style="border-style: solid; border-width: 1px"\| <code>-CROP2D {ortho_dim} {n:number of vertices} X1 Y1 X2 Y2 ... Xn Yn</code>		\|style="border-style: solid; border-width: 1px"\| <code>-CROP2D {ortho_dim} {-GLOBAL_SHIFT + options} {n:number of vertices} X1 Y1 X2 Y2 ... Xn Yn</code>
	\|style="border-style: solid; border-width: 1px"\| ''Crops all loaded clouds inside or outisde a given 2D polyline. Cropping is done in a plane defined by its orthogonal dimension: X, Y or Z (i.e. coordinates along this dimension will be ignored).''		\|style="border-style: solid; border-width: 1px"\| ''Crops all loaded clouds inside or outisde a given 2D polyline. Cropping is done in a plane defined by its orthogonal dimension: X, Y or Z (i.e. coordinates along this dimension will be ignored).''

			Since version 2.14, it is possible to set a Global Shift when importing the 2D vertices. It uses the same syntax as the -O option (see the -O -GLOBAL_SHIFT option).

			Warning, after setting the dimension, CloudCompare will expect the 2D vertices in the following order:
			* Dim = X --> YZ
			* Dim = Y --> ZX
			* Dim = Z --> XY

	Optional settings are:		Optional settings are: