Large-scale segmentation using MeanShift


This application chains together the 4 steps of the MeanShift framework, that is the MeanShiftSmoothing, the LSMSSegmentation, the LSMSSmallRegionsMerging and the LSMSVectorization.

This application can be a preliminary step for an object-based analysis.

It generates a vector data file containing the regions extracted with the MeanShift algorithm. The spatial and range radius parameters allow adapting the sensitivity of the algorithm depending on the image dynamic and resolution. There is a step to remove small regions whose size (in pixels) is less than the given ‘minsize’ parameter. These regions are merged to a similar neighbor region. In the output vectors, there are additional fields to describe each region. In particular the mean and standard deviation (for each band) is computed for each region using the input image as support. If an optional ‘imfield’ image is given, it will be used as support image instead.


Input Image -in image Mandatory
The input image can be any single or multiband image. Beware of potential imbalance between bands ranges as it may alter euclidean distance.

Spatial radius -spatialr int Default value: 5
Radius of the spatial neighborhood for averaging. Higher values will result in more smoothing and higher processing time.

Range radius -ranger float Default value: 15
Threshold on spectral signature euclidean distance (expressed in radiometry unit) to consider neighborhood pixel for averaging. Higher values will be less edge-preserving (more similar to simple average in neighborhood), whereas lower values will result in less noise smoothing. Note that this parameter has no effect on processing time.

Minimum Segment Size -minsize int Default value: 50
Minimum Segment Size. If, after the segmentation, a segment is of size strictly lower than this criterion, the segment is merged with the segment that has the closest sepctral signature.

Size of tiles in pixel (X-axis) -tilesizex int Default value: 500
Size of tiles along the X-axis for tile-wise processing.

Size of tiles in pixel (Y-axis) -tilesizey int Default value: 500
Size of tiles along the Y-axis for tile-wise processing.

Output mode -mode [vector|raster] Default value: vector
Type of segmented output

  • Segmentation as vector output
    In this mode, the application will produce a vector file or database and compute field values for each region

  • Standard segmentation with labeled raster output
    In this mode, the application will produce a standard labeled raster.

Segmentation as vector output options

Support image for field computation -mode.vector.imfield image
This is an optional support image that can be used to compute field values in each region. Otherwise, the input image is used as support.

Output GIS vector file -mode.vector.out filename [dtype] Mandatory
The output GIS vector file, representing the vectorized version of the segmented image where the features of the polygons are the radiometric means and variances.

Standard segmentation with labeled raster output options

The output raster image -mode.raster.out image [dtype] Mandatory
It corresponds to the output of the small region merging step.

Temporary files cleaning -cleanup bool Default value: true
If activated, the application will try to clean all temporary files it created

Available RAM (MB) -ram int Default value: 256
Available memory for processing (in MB).


From the command-line:

otbcli_LargeScaleMeanShift -in QB_1_ortho.tif -spatialr 4 -ranger 80 -minsize 16 -mode.vector.out regions.shp

From Python:

import otbApplication

app = otbApplication.Registry.CreateApplication("LargeScaleMeanShift")

app.SetParameterString("in", "QB_1_ortho.tif")
app.SetParameterInt("spatialr", 4)
app.SetParameterFloat("ranger", 80)
app.SetParameterInt("minsize", 16)
app.SetParameterString("mode.vector.out", "regions.shp")


See also