In order to take into account the scale of the texture to be measured, r.texture allows the user to define the size of the moving window and the distance at which to compare pixel grey values. By default the module averages the results over the 4 orientations, but the user can also request output of the texture variables in 4 different orientations (flag -s). Please note that angles are defined in degrees of east and they increase counterclockwise, so 0 is East - West, 45 is North-East - South-West, 90 is North - South, 135 is North-West - South-East.
The user can either chose one or several texture measures (see below for their description) using the method parameter, or can request the creating of maps for all available methods with the -a.
r.texture assumes grey levels ranging from 0 to 255 as input. The input is automatically rescaled to 0 to 255 if the input map range is outside of this range. In order to reduce noise in the input data (thus generally reinforcing the textural features), and to speed up processing, it is recommended that the user recode the data using equal-probability quantization. Quantization rules for r.recode can be generated with r.quantile -r using e.g 16 or 32 quantiles (see example below).
Texture is a feature of specific land cover classes in satellite imagery. It is particularly useful in situations where spectral differences between classes are small, but classes are distinguishable by their organisation on the ground, often opposing natural to human-made spaces: cultivated fields vs meadows or golf courses, palm tree plantations vs natural rain forest, but texture can also be a natural phenomen: dune fields, different canopies due to different tree species. The usefulness and use of texture is highly dependend on the resolution of satellite imagery and on the scale of the human intervention or the phenomenon that created the texture (also see the discussion of scale dependency below). The user should observe the phenomenon visually in order to determine an adequat setting of the size parameter.
The output of r.texture can constitute very useful additional variables as input for image classification or image segmentation (object recognition). It can be used in supervised classification algorithms such as i.maxlik or i.smap, or for the identification of objects in i.segment, and/or for the characterization of these objects and thus, for example, as one of the raster inputs of the i.segment.stats addon.
In general, several variables constitute texture: differences in grey level values, coarseness as scale of grey level differences, presence or lack of directionality and regular patterns. A texture can be characterized by tone (grey level intensity properties) and structure (spatial relationships). Since textures are highly scale dependent, hierarchical textures may occur.
r.texture uses the common texture model based on the so-called grey level co-occurrence matrix as described by Haralick et al (1973). This matrix is a two-dimensional histogram of grey levels for a pair of pixels which are separated by a fixed spatial relationship. The matrix approximates the joint probability distribution of a pair of pixels. Several texture measures are directly computed from the grey level co-occurrence matrix.
The following part offers brief explanations of the Haralick et al texture measures (after Jensen 1996).
The computational region should be set to the input map with g.region rast=<input map>, or aligned to the input map with g.region align=<input map> if only a subregion should be analyzed.
Note that the output of r.texture will always be smaller than the current region as only cells for which there are no null cells and for which all cells of the moving window are within the current region will contain a value. The output will thus appear cropped at the margins.
Importantly, the input raster map cannot have more than 255 categories.
g.region raster=ortho_2001_t792_1m -p # set grey level color table 0% black 100% white r.colors ortho_2001_t792_1m color=grey # extract grey levels r.mapcalc "ortho_2001_t792_1m.greylevel = ortho_2001_t792_1m" # texture analysis r.texture ortho_2001_t792_1m.greylevel prefix=ortho_texture method=asm -s # display g.region n=221461 s=221094 w=638279 e=638694 d.shade color=ortho_texture_ASM_0 shade=ortho_2001_t792_1m
g.region -p rast=ortho_2001_t792_1m r.quantile in=ortho_2001_t792_1m quantiles=16 -r | r.recode in=ortho_2001_t792_1m out=ortho_2001_t792_1m_q16 rules=-
Second example: analysis of IDM (homogeneity) on a simple raster with North-South line pattern.
# import raster r.in.ascii in=- output=lines << EOF north: 9 south: 0 east: 9 west: 0 rows: 9 cols: 9 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 0 0 1 0 EOF # adjust region to raster g.region rast=lines # calculate IDM (homogeneity) in all directions r.texture -s lines method=idm out=text_lines
The following image shows the original map, the result in East-West direction and the result in North-South direction, showing how texture can depend on direction, with texture perfectly homogeneous (value=1) in the North-South direction, but quite heterogeneous in East-West direction, except for those areas where there are three columns of equal values (as size=3). The overlayed grid highlights that the texture measures output maps are cropped at the margins.
The code was taken by permission from pgmtexture, part of PBMPLUS (Copyright 1991, Jef Poskanser and Texas Agricultural Experiment Station, employer for hire of James Darrell McCauley). Manual page of pgmtexture.
Last changed: $Date: 2017-01-05 00:52:13 -0800 (Thu, 05 Jan 2017) $
© 2003-2018 GRASS Development Team, GRASS GIS 7.0.7svn Reference Manual