Rasterize - Revision history

Daniel at 21:01, 13 April 2026

2026-04-13T21:01:59Z

← Older revision		Revision as of 23:01, 13 April 2026
Line 41:		Line 41:
	** the median SF value		** the median SF value
	** or the inverse variance		** or the inverse variance
	* '''since version 2.6.2 the user can choose the 'active layer' that will be projected. The default layer is 'height grid values' (i.e. the coordinate of the points along the projection dimension) but it can now be any scalar field associated to the selected cloud, the hillshade layer, etc.'''		* '''since version 2.6.2 the user can choose the 'active layer' that will be projected. The default layer is 'height grid values' (i.e. the coordinate of the points along the projection dimension) but it can now be any scalar field associated to the selected cloud, the hillshade layer, the X-ray layer, etc.'''

	Once the base parameters are properly set, the user must click on the 'Update grid' button to make CloudCompare actually compute the grid and display it.		Once the base parameters are properly set, the user must click on the 'Update grid' button to make CloudCompare actually compute the grid and display it.
Line 184:		Line 184:
	[[Image:Cc_colored_contour_lines.jpg\|frame\|center]]		[[Image:Cc_colored_contour_lines.jpg\|frame\|center]]

	== Hillshade ==		== Hillshade / X-ray ==

	Since version 2.6.3, the Rasterize tool can generate an hillshade layer:		Since version 2.6.3, the Rasterize tool can generate an hillshade layer:
Line 190:		Line 190:

	Once the grid has been generated:		Once the grid has been generated:
	* click on the 'Hillshade' tab		* click on the 'Hillshade / X-ray' tab
	* set the right parameters (sun position)		* set the right parameters (sun position)
	* click on ~~generate~~		* click on 'Generate hillshade'

	Note that ~~this layer~~ will disappear each time the 'Update grid' button is clicked		Since version 2.14, the Rasterize tool can generate an X-ray layer, with a very similar process:
			[[Image:X-ray.jpg\|frame\|center]]

			Once the grid has been generated:
			* click on the 'Hillshade / X-ray' tab
			* click on 'Generate X-ray scalar field'

			Note that these layers will disappear each time the 'Update grid' button is clicked

Daniel at 22:04, 3 December 2024

2024-12-03T22:04:34Z

← Older revision		Revision as of 00:04, 4 December 2024
Line 35:		Line 35:
	*** median value of all points falling in this cell		*** median value of all points falling in this cell
	*** inverse variance: the height or scalar value of each cell is equal to a weighted average of the points falling inside the cell. The weights are equal to the inverse variance (= 1/std_dev^2). Standard deviation values (std_dev) are obtained from an already existing scalar field, which must be selected by the user.		*** inverse variance: the height or scalar value of each cell is equal to a weighted average of the points falling inside the cell. The weights are equal to the inverse variance (= 1/std_dev^2). Standard deviation values (std_dev) are obtained from an already existing scalar field, which must be selected by the user.
			* similarly, if the 'project SF(s)' option is checked, scalar field values can be 'projected' onto the raster as well. When multiple points/SF values fall inside the same raster cell, CC can extract the single SF value for this cell as:
			** the minimum SF value
			** the average SF value
			** the maximum SF value
			** the median SF value
			** or the inverse variance
	* '''since version 2.6.2 the user can choose the 'active layer' that will be projected. The default layer is 'height grid values' (i.e. the coordinate of the points along the projection dimension) but it can now be any scalar field associated to the selected cloud, the hillshade layer, etc.'''		* '''since version 2.6.2 the user can choose the 'active layer' that will be projected. The default layer is 'height grid values' (i.e. the coordinate of the points along the projection dimension) but it can now be any scalar field associated to the selected cloud, the hillshade layer, etc.'''

Daniel: /* Cloud */

2024-02-04T15:00:08Z

Cloud

← Older revision		Revision as of 17:00, 4 February 2024
Line 112:		Line 112:
	Several additional scalar fields can be generated:		Several additional scalar fields can be generated:
	* 'population': number of input points falling in each cell		* 'population': number of input points falling in each cell
	* 'min ~~height~~': minimum height of the points falling in each cell		* 'min': minimum height of the points falling in each cell
	* 'average ~~height~~': average height of the points falling in each cell (''may be redundant with the default 'height' scalar field'')		* 'average': average height of the points falling in each cell (''may be redundant with the default 'height' scalar field'')
	* 'max ~~height~~': maximum height of the points falling in each cell (''may be redundant with the default 'height' scalar field'')		* 'max': maximum height of the points falling in each cell (''may be redundant with the default 'height' scalar field'')
	* '~~average height': average height of the points falling in each cell (''may be redundant with the default 'height' scalar field'')~~		* 'std. dev.': standard deviation of the height values of the points falling in each cell
	* 'height std. dev.': standard deviation of the height values of the points falling in each cell		* 'range': range of the height values of the points falling in each cell
	* '~~height~~ range': range of the height values of the points falling in each cell		* Since version 2.13:
			** 'unique val.': the number of uniques values inside each cell
			** 'median': median value
			** 'percentile' + percentage: highest value of the given percentage of points (sorted)

			Since version 2.13, it is now also possible to choose whether the above statistics should be applied to 'height' values, all the 'scalar fields' or both (with checkboxes).

	=== Raster ===		=== Raster ===

Daniel: /* Interpolate scalar fields */

2024-02-04T14:54:13Z

Interpolate scalar fields

← Older revision		Revision as of 16:54, 4 February 2024
Line 88:		Line 88:
	* by keeping the average SF value of all the points falling in this cell		* by keeping the average SF value of all the points falling in this cell
	* by keeping the maximum SF value of all the points falling in this cell		* by keeping the maximum SF value of all the points falling in this cell
			* since version 2.13:
			** median value
			** inverse variance

	Note: interpolated scalar fields can only be used when exporting the raster grid as a new cloud or as a raster file in a formats that supports real-valued layers.		Note: interpolated scalar fields can only be used when exporting the raster grid as a new cloud or as a raster file in a formats that supports real-valued layers.

Daniel: /* Interpolating empty cells */

2024-02-04T14:52:49Z

Interpolating empty cells

← Older revision		Revision as of 16:52, 4 February 2024
Line 56:		Line 56:
	=== Interpolating empty cells ===		=== Interpolating empty cells ===

	The 'interpolate' option consists in a linear interpolation with the nearest non-empty neighboring cells. This can give very good results in the presence of small holes. However it can be less realistic on ~~big~~ holes. '''The biggest limitation is that it's limited to the convex hull of the non-empty cells'''. Therefore a custom value must still be specified (in the field below the 'Fill with' drop-down list) to fill the remaining empty areas (if any).		''Interpolate''

			The 'interpolate' option consists in a linear interpolation with the nearest non-empty neighboring cells. It relies on Delaunay triangulation.

			This can give very good results in the presence of small holes. However it can be less realistic on large holes. '''The biggest limitation is that it's limited to the convex hull of the non-empty cells'''. Therefore a custom/default value must still be specified in the field below the 'Fill with' drop-down list to fill the remaining empty areas (if any).

	[[Image:Cc_rasterize_interpolation_small.jpg\|frame\|center\|Interpolation principle]]		[[Image:Cc_rasterize_interpolation_small.jpg\|frame\|center\|Interpolation principle]]

			''Kriging''

			It is now possible to use a Kriging algorithm to fill the empty cells. While this option may take more time to compute, it allows to interpolate cells all over the raster grid and not only inside the non-empty cells convex hull.

			[[Image:Rasterize_kriging.JPG\|frame\|center\|Kriging interpolation option]]

	=== Grid position ===		=== Grid position ===

Daniel: /* Generating a raster grid */

2024-02-04T14:42:41Z

Generating a raster grid

← Older revision		Revision as of 16:42, 4 February 2024
Line 29:		Line 29:
	* the projection direction (X, Y or Z - default: Z)		* the projection direction (X, Y or Z - default: Z)
	* how the 'height' of each cell grid will be computed:		* how the 'height' of each cell grid will be computed:
	** minimum ~~height~~ of all points falling in this cell		** minimum value of all points falling in this cell
	** average ~~height~~ of all points falling in this cell		** average value of all points falling in this cell
	** maximum ~~height~~ of all points falling in this cell		** maximum value of all points falling in this cell
			** since version 2.13:
			*** median value of all points falling in this cell
			*** inverse variance: the height or scalar value of each cell is equal to a weighted average of the points falling inside the cell. The weights are equal to the inverse variance (= 1/std_dev^2). Standard deviation values (std_dev) are obtained from an already existing scalar field, which must be selected by the user.
	* '''since version 2.6.2 the user can choose the 'active layer' that will be projected. The default layer is 'height grid values' (i.e. the coordinate of the points along the projection dimension) but it can now be any scalar field associated to the selected cloud, the hillshade layer, etc.'''		* '''since version 2.6.2 the user can choose the 'active layer' that will be projected. The default layer is 'height grid values' (i.e. the coordinate of the points along the projection dimension) but it can now be any scalar field associated to the selected cloud, the hillshade layer, etc.'''

Daniel: /* Grid position */

2022-02-19T13:12:16Z

Grid position

← Older revision		Revision as of 15:12, 19 February 2022
Line 63:		Line 63:
	[[Image:Cc_rasterize_bb_edit_dialog.jpg\|frame\|center\|Grid extents setup dialog]]		[[Image:Cc_rasterize_bb_edit_dialog.jpg\|frame\|center\|Grid extents setup dialog]]

	Warning: the Rasterize tool uses the '[https://www.usna.edu/Users/oceano/pguth/md_help/html/PixelIsWhat.html pixel-is-~~point~~]' convention (the grid min corner coordinates correspond to the lower left grid cell '''center''').		Warning: the Rasterize tool grid uses the '[https://www.usna.edu/Users/oceano/pguth/md_help/html/PixelIsWhat.html pixel-is-area]' convention but the grid itself is centered on the boundary pixel centers. The grid min corner coordinates correspond to the lower left raster cell '''center''', and the grid max corner coordinates correspond to the upper right raster cell '''center''':

			[[Image:Raster_grid.jpg\|frame\|center\|Raster grid]]

	=== Interpolate scalar fields ===		=== Interpolate scalar fields ===

Daniel: /* Grid position */

2022-02-19T12:42:54Z

Grid position

← Older revision		Revision as of 14:42, 19 February 2022
Line 63:		Line 63:
	[[Image:Cc_rasterize_bb_edit_dialog.jpg\|frame\|center\|Grid extents setup dialog]]		[[Image:Cc_rasterize_bb_edit_dialog.jpg\|frame\|center\|Grid extents setup dialog]]

	Warning: the Rasterize tool uses the 'pixel-is-point' convention (the grid min corner coordinates correspond to the lower left grid cell '''center''').		Warning: the Rasterize tool uses the '[https://www.usna.edu/Users/oceano/pguth/md_help/html/PixelIsWhat.html pixel-is-point]' convention (the grid min corner coordinates correspond to the lower left grid cell '''center''').

	=== Interpolate scalar fields ===		=== Interpolate scalar fields ===

Daniel: /* Grid position */

2022-02-19T12:41:16Z

Grid position

← Older revision		Revision as of 14:41, 19 February 2022
Line 62:		Line 62:

	[[Image:Cc_rasterize_bb_edit_dialog.jpg\|frame\|center\|Grid extents setup dialog]]		[[Image:Cc_rasterize_bb_edit_dialog.jpg\|frame\|center\|Grid extents setup dialog]]

			Warning: the Rasterize tool uses the 'pixel-is-point' convention (the grid min corner coordinates correspond to the lower left grid cell '''center''').

	=== Interpolate scalar fields ===		=== Interpolate scalar fields ===

Daniel at 09:52, 22 April 2016

2016-04-22T09:52:49Z

← Older revision		Revision as of 11:52, 22 April 2016
Line 32:		Line 32:
	** average height of all points falling in this cell		** average height of all points falling in this cell
	** maximum height of all points falling in this cell		** maximum height of all points falling in this cell
	* '''since version 2.6.2 the user can choose the 'active layer' that will be projected. The default layer is 'height grid values' (i.e. the coordinate of the points along the projection dimension) but it can now be any scalar field associated to the selected cloud'''		* '''since version 2.6.2 the user can choose the 'active layer' that will be projected. The default layer is 'height grid values' (i.e. the coordinate of the points along the projection dimension) but it can now be any scalar field associated to the selected cloud, the hillshade layer, etc.'''

	Once the base parameters are properly set, the user must click on the 'Update grid' button to make CloudCompare actually ~~computed~~ the grid and display it.		Once the base parameters are properly set, the user must click on the 'Update grid' button to make CloudCompare actually compute the grid and display it.

	'''Each time a parameter is modified, the 'Update grid' button will appear in red. The user has to click on it to actually apply the changes.'''		'''Each time a parameter is modified, the 'Update grid' button will appear in red. The user has to click on it to actually apply the changes.'''
Line 42:		Line 42:
	=== Empty cells ===		=== Empty cells ===

	If no ~~points fall~~ inside a given cell, this cell will be considered as 'empty'. ~~Empty~~ cells are not visible when displayed ~~by CloudCompare~~ in the 3D view. They generally have a dedicated 'NaN' or 'empty' value when exported to a raster file (depending on the format).		If no point falls inside a given cell, this cell will be considered as 'empty'. By default empty cells are not visible when displayed in the tool's 3D view. They generally have a dedicated 'NaN' or 'empty' value when exported to a raster file (depending on the format).

	It is possible ~~to tell CloudCompare~~ to fill ~~those~~ cells in various ways:		It is possible to fill these cells in various ways:
	* use the minimum height of the whole grid		* use the minimum height of the whole grid
	* use the average height of the whole grid		* use the average height of the whole grid
Line 53:		Line 53:
	=== Interpolating empty cells ===		=== Interpolating empty cells ===

	The 'interpolate' option consists in a linear interpolation with the nearest non-empty neighboring cells. This can give very good results in the presence of small holes. However it can be less realistic on big holes. The biggest limitation is that it ~~doesn~~'~~t work outside~~ the convex hull of the non-empty cells. Therefore a custom value must be specified (in the field below the 'Fill with' drop-down list) to fill ~~these~~ areas (if any).		The 'interpolate' option consists in a linear interpolation with the nearest non-empty neighboring cells. This can give very good results in the presence of small holes. However it can be less realistic on big holes. '''The biggest limitation is that it's limited to the convex hull of the non-empty cells'''. Therefore a custom value must still be specified (in the field below the 'Fill with' drop-down list) to fill the remaining empty areas (if any).

	[[Image:Cc_rasterize_interpolation_small.jpg\|frame\|center\|Interpolation principle]]		[[Image:Cc_rasterize_interpolation_small.jpg\|frame\|center\|Interpolation principle]]
Line 76:		Line 76:
	=== Resample input cloud ===		=== Resample input cloud ===

	This option tells CloudCompare to keep in each grid cell the point which is the closest to the cell center (~~in 2D)~~ instead of ~~generating of using~~ the cell center itself. This way it is possible to subsample the cloud in a semi-gridded pattern. If the grid is to be exported as a cloud, all the input cloud features (colors, normals, etc.) can be properly exported as well.		This option tells CloudCompare to keep in each grid cell the point from the input cloud which is the closest to the cell center (instead of the cell center itself). This way it is possible to subsample the cloud in a semi-gridded pattern. If the grid is to be exported as a cloud, all the input cloud features (colors, normals, etc.) can be properly exported as well.

			Since version 2.7 the resample option can now be used with the 'average height' projection. In this case only the 2D coordinates of the original point are kept (''the point which is the closest to the cell center'') and the height is replaced by the average cell height.

	== Export ==		== Export ==
Line 150:		Line 152:

	[[Image:Cc_colored_contour_lines.jpg\|frame\|center]]		[[Image:Cc_colored_contour_lines.jpg\|frame\|center]]

			== Hillshade ==

			Since version 2.6.3, the Rasterize tool can generate an hillshade layer:
			[[Image:Cc_rasterize_hillshade.jpg\|frame\|center]]

			Once the grid has been generated:
			* click on the 'Hillshade' tab
			* set the right parameters (sun position)
			* click on generate

			Note that this layer will disappear each time the 'Update grid' button is clicked