Use the Compute Cutlines command to compute the cutlines for the selected input images using a method you select. Each method is described in the following table.
| Name | Description |
|---|---|
| Minimum Squared Difference | Suitable for use with most mosaicking projects and, in most cases, produces the cleanest cutlines.
A cutline is determined in each overlapped area between two adjacent images, with minimum squared differences of gray values at the same locations of the region in all image channels. |
| Minimum Difference | Suitable for most mosaicking projects.
A cutline is determined in each overlapped area between two adjacent images, with minimum differences of gray values at the same locations of the region. |
| Minimum Relative Difference | Similar to Minimum Difference, but provides better output in cases where similar sections of data appear dissimilar in various images. |
| Edge Feature | Provides better output in urban-area mosaicking, or in images containing many linear features.
The objective is to avoid placing cutlines across linear features. |
| Maximum Data | Places cutlines on the boundary of the real image pixels, meaning that NoData pixels will be ignored when the image boundary is determined. |
| File Extent | The cutline will be the extents of the input image or images and will not exclude NoData pixels during cutline generation. |
| Auto Constrain | Automatically constrain cutlines to the more central portions of the images.
If there is a large amount of overlap between images, Auto Constrain can be useful in limiting the data being considered for cutline generation to areas closest to the center of the images.
Note: Auto Constrain cannot be used with File Extent.
|
© PCI Geomatics Enterprises, Inc.®, 2026. All rights reserved.