lsm_c_para_sd: PARA_SD (class level)

Description Usage Arguments Details Value References See Also Examples

Description

Standard deviation perimeter-area ratio (Shape metric)

Usage

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
lsm_c_para_sd(landscape, directions)

## S3 method for class 'RasterLayer'
lsm_c_para_sd(landscape, directions = 8)

## S3 method for class 'RasterStack'
lsm_c_para_sd(landscape, directions = 8)

## S3 method for class 'RasterBrick'
lsm_c_para_sd(landscape, directions = 8)

## S3 method for class 'stars'
lsm_c_para_sd(landscape, directions = 8)

## S3 method for class 'list'
lsm_c_para_sd(landscape, directions = 8)

Arguments

landscape

Raster* Layer, Stack, Brick or a list of rasterLayers.

directions

The number of directions in which patches should be connected: 4 (rook's case) or 8 (queen's case).

Details

PARA_{SD} = sd(PARA[patch_{ij}]

where PARA[patch_{ij}] is the perimeter area ratio of each patch.

PARA_SD is a 'Shape metric'. It summarises each class as the standard deviation of each patch belonging to class i. The perimeter-area ratio describes the patch complexity in a straightforward way. However, because it is not standarised to a certain shape (e.g. a square), it is not scale independent, meaning that increasing the patch size while not changing the patch form will change the ratio.

Units

None

Range

PARA_SD >= 0

Behaviour

Equals PARA_SD = 0 if the perimeter-area ratio is identical for all patches. Increases, without limit, as the variation of the perimeter-area ratio increases.

Value

tibble

References

McGarigal, K., SA Cushman, and E Ene. 2012. FRAGSTATS v4: Spatial Pattern Analysis Program for Categorical and Continuous Maps. Computer software program produced by the authors at the University of Massachusetts, Amherst. Available at the following web site: http://www.umass.edu/landeco/research/fragstats/fragstats.html

See Also

lsm_p_para, sd,
lsm_c_para_mn, lsm_c_para_cv,
lsm_l_para_mn, lsm_l_para_sd, lsm_l_para_cv

Examples

1

r-spatialecology/landscapemetrics documentation built on May 20, 2019, noon