Other (not-implemented) metrics

[marcosci]

To keep it a bit more organized, here a single list with the metrics we are currently missing.

Cell-aggregation metrics

• Adding cell-level aggregation metrics #288

Contrast metrics

• https://fragstats.org/index.php/fragstats-metrics/contrast-metrics

Patch level

• Proximity index (Responsible: 👻) -> Needs user to specify search radius
• Similarity index (Responsible: 👻) -> Needs user to input similarity table

Class level

• Linearity index distribution (Responsible: 👻) -> Not in FRAGSTATS manual
• Connectance (Responsible: @marcosci ) -> Needs nearest neighbor distances, so we wait until we have a good solution for ENN
• Proximity index distribution (Responsible: 👻) -> Needs search radius
• Similarity index distribution (Responsible: 👻) -> Needs similarity table
• Linearity index distribution (Responsible: 👻) -> Not in FRAGSTATS manual
• MFRAC (Responsible: 👻)

Landscape level

• Linearity index distribution (Responsible: 👻) -> Missing in FRAGSTATS manual
• Proximity index distribution (Responsible: 👻) -> Needs search radius
• Similarity index (Responsible: 👻) -> Needs similarity table
• Connectance (Responsible: @marcosci )

[aavotins]

One of the advantages of Fragstats is the ability to define different interactions between classes when calculating, e.g. core areas or edge contrasts. It seems that {landscapemetrics} is currently only able to use a single value instead of a (contrast oor edge depth) matrix. For example, functions lsm_c_tca, lsm_p_core. Is it planned (and is there any idea of timing?) to implement edge depth and contrast matrix metrics between classes? Or pmaybe there are some building blocks for this, that I have missed?

[mhesselbarth]

All edge metrics have a edge_depth which allows to specify how many rows of cells are considered "edge". You can use show_cores(x, edge_depth=1) vs. show_cores(x, edge_depth=3) to get a visualization of this.

As for the contrast matrix, I don't think this will be implemented soon due to missing time.