Use this procedure to create a topographic feature classification image. Each pixel is classified into one of the following terrain types or morphometric features by setting the keyword CPTR: peak, ridge, pass, plane, channel, or pit.
This routine is obsolete and has been replaced by the TopographicFeatures task.
Syntax
ENVI_DOIT, 'TOPO_FEATURE_DOIT', CLASS_NAMES=array, CONVEX_TOL=value, CPTR={0 | 1 | 2 | 3 | 4 | 5}, DIMS=array, FID=file ID, /IN_MEMORY, KERNEL_SIZE=single scalar, LOOKUP=array, OUT_BNAME=string array, OUT_NAME=string [, PIXEL_SIZE=array], POS=array, R_FID=variable, SLOPE_TOL=value
Keywords
CLASS_NAMES
Use this keyword to specify names for each output class. CLASS_NAMES is an array of strings with [num_classes+1] elements. The first element (Class 0) is “Unclassified.”
CONVEX_TOL
Use this keyword to specify the floating-point or double-precision value for the curvature tolerance. CONVEX_TOL and SLOPE_TOL, in addition to the topographic modeling values, determine how a pixel is classified.
CPTR
Use this keyword to specify an array of long integers representing the type of output class to compute.
- 0: Peak
- 1: Ridge
- 2: Pass
- 3: Plane
- 4: Channel
- 5: Pit
DIMS
The “dimensions” keyword is a five-element array of long integers that defines the spatial subset (of a file or array) to use for processing. Nearly every time you specify the keyword FID, you must also specify the spatial subset of the corresponding file (even if the entire file, with no spatial subsetting, is to be processed).
- DIMS[0]: A pointer to an open ROI; use only in cases where ROIs define the spatial subset. Otherwise, set to -1L.
- DIMS[1]: The starting sample number. The first x pixel is 0.
- DIMS[2]: The ending sample number
- DIMS[3]: The starting line number. The first y pixel is 0.
- DIMS[4]: The ending line number
To process an entire file (with no spatial subsetting), define DIMS as shown in the following code example. This example assumes you have already opened a file using ENVI_SELECT or ENVI_PICKFILE:
envi_file_query, fid, dims=dims
FID
The file ID (FID) is a long-integer scalar with a value greater than 0. An invalid FID has a value of -1. The FID is provided as a named variable by any routine used to open or select a file. Often, the FID is returned from the keyword R_FID in the ENVIRasterToFID routine. Files are processed by referring to their FIDs. If you work directly with the file in IDL, the FID is not equivalent to a logical unit number (LUN).
IN_MEMORY
Set this keyword to specify that output should be stored in memory. If you do not set IN_MEMORY, output will be stored on disk and you must specify OUT_NAME (see below).
KERNEL_SIZE
Use this keyword to specify a kernel size for the topographic features. KERNEL_SIZE is a single scalar that sets both the x and y kernel size. KERNEL_SIZE determines the local surface-fit size used to calculate topographic modeling parameters for feature extraction.
LOOKUP
Use this keyword to specify a byte array specifying the color tables for the classification image. The LOOKUP array contains an RGB triplet for each output class. The dimensions of the array are [3, num_classes+1], and the RGB triplet is ordered [r, g , b]. The “Unclassified” class typically uses the RGB triplet [0, 0, 0] for black.
OUT_BNAME
Use this keyword to specify a string array of output band names.
OUT_NAME
Use this keyword to specify a string with the output filename for the resulting data. If you set the keyword IN_MEMORY, you do not need to specify OUT_NAME.
POS
Use this keyword to specify an array of band positions, indicating the band numbers on which to perform the operation. This keyword indicates the spectral subset of bands to use in processing. POS is an array of long integers, ranging from 0 to the number of bands minus 1. Specify bands starting with zero (Band 1=0, Band 2=1, etc.) For example, to process only Bands 3 and 4 of a multi-band file, POS=[2, 3].
POS is typically used with individual files. The example code below illustrates the use of POS for a single file with four bands of data:
pos=[0,1,2,3]
envi_doit, 'envi_stats_doit', dims=dims, fid=fid, pos=pos, $
comp_flag=3, dmin=dmin, dmax=dmax, mean=mean, stdv=stdv, hist=hist
But what if you need to create an output file consisting of data from different bands, each from different files? Library routines such as CF_DOIT and ENVI_LAYER_STACKING_DOIT can accomplish this, but they use the POS keyword differently. Suppose you have four files, test1, test2, test3, and test4, with corresponding FIDs of fid1, fid2, fid3, and fid4, respectively. In the following example, you want Band 3 from test1 in the first position, Band 2 from test2 in the second position, Band 6 from test3 in the third position, and Band 4 from test4 in the fourth position. The code should be as follows:
fid_array = [fid1,fid2,fid3,fid4]
pos=[2,1,5,3]
envi_doit, 'cf_doit', dims=dims, fid=fid_array
out_name='test_composite_file'
PIXEL_SIZE
Use this keyword to specify the pixel size of the image. PIXEL_SIZE is a two-element array of floating-point or double-precision values specifying the x and y pixel sizes, respectively.
R_FID
ENVI Classic library routines that result in new images also have an R_FID, or “returned FID.” This is simply a named variable containing the file ID to access the processed data. Specifying this keyword saves you the step of opening the new file from disk.
SLOPE_TOL
Use this keyword to specify the floating-point or double-precision value for the slope tolerance. SLOPE_TOL and CONVEX_TOL, in addition to the topographic modeling values, determine how a pixel is classified.
API Version
4.2