Orthophoto/DSM

Produce interoperable raster layers for visualization and analysis in third-party GIS/CAD software or image processing tools.

Note: When using tiling, orthophoto/DSM productions generate one file per tile. You can use the command Merge orthophoto parts (available once ContextCapture production is complete) to create a single merged file for the orthophoto and for the DSM.

DSM output formats

TIFF/GeoTIFF: standard raster format with georeferencing information.
ESRI ASCII raster/ASC: common ASCII format for grid exchange.
XYZ: basic ASCII format with 3 columns, each line containing the X, Y and Z coordinates.

The reference 3D model geometry must be available to process DSM.

Orthophoto output formats

TIFF/GeoTIFF: standard raster format with georeferencing information.
JPEG: standard compressed image format.
KML Super-overlay: hierarchical image file format suited for real-time 3D display of very large orthophotos in Google Earth.

Options

Sampling distance: sampling distance option. Unit depends on the selected Spatial reference system.
Maximum image part dimension (px): define the maximum tile size for the resulting raster file.
Projection mode: define how the 2D data layer is processed from the 3D model (Highest point or Lowest point).
Orthophoto/DSM: enable or disable the corresponding production.
Color source:
Optimized computation (visible colors): the best photos with visible colors band are selected according to the actual projection.

Optimized computation (thermal): the best photos with thermal band are selected according to the actual projection.

Reference 3D model visible color: keep the internal reference 3D model with visible colors as is (mush faster).

Reference 3D model (thermal): keep the internal reference 3D model with thermal band as is (mush faster).
No data: pixel value or color representing no information.

The reference 3D model texture and geometry must be available to process orthophoto.

About LOD naming convention

3D mesh productions with LOD use a specific naming convention for node files according to tile name, level of detail resolution, and node path (for LOD trees).

For a node file "Tile_+000_+003_L20_000013.dae", the meaning is the following:

Tile_+000_+003: tile name.

L20: normalized level of detail which is related to ground resolution.

Table 1. Level of detail and ground resolution correspondence table (sample)
Level of detail	Ground resolution (meter/pixel or unit/pixel)
12	16
13	8
14	4
15	2
16	1
17	0.5
18	0.25
19	0.125
20	0.0625

000013: optional node path, only included for LOD tree.

Each digit of the node path corresponds to a child index (zero-based) in the tree. For quadtree and octree productions, the child index unambiguously indicates the quadrant/octant of the child node.

Table 2. Example of node files for a production with LOD of type simple levels

Table 3. Example of node files for a production with LOD of type quadtree