Gully Density

Context

• Region Australia
• Biome Temperate Dry Woodlands & Native Grasslands
• Land Use Conservation / Protected Natural Areas
• Assessment Conservation Target
• Evidence Type DegradationThreshold

Lifecycle

• Status Active
• Version 1
• Effective From 24 Mar 2026

Notes

Any active gully density > 0 m/ha is considered critical, indicating compromised ecological function and active degradation. ConsistencyResolver applied 2026-03-24 20:09 UTC: LowerThreshold 0 → (check: MinEqualsMax, rationale: The Notes indicate that any gully density > 0 is detrimental, so the threshold is an upper limit, not a lower limit. Since a MaximumOnly threshold at 0 already exists (ID=1931), the MinimumOnly threshold at 0 is redundant and causes a zero-width range. Setting LowerThreshold to null removes this conflict and resolves the issue.) ConsistencyResolver applied 2026-03-24 20:20 UTC: BenchmarkValue 0 → (check: MinEqualsMax, rationale: The Notes indicate that any gully density > 0 is detrimental, so the threshold is an upper limit, not a lower limit. Removing the BenchmarkValue from the MinimumOnly benchmark removes the zero-width range conflict and aligns with ecological interpretation.) ConsistencyResolver applied 2026-03-24 20:20 UTC: UpperThreshold → (check: MinEqualsMax, rationale: No UpperThreshold should be set on the MinimumOnly benchmark to avoid duplication and maintain the correct threshold direction.) ConsistencyResolver applied 2026-03-24 20:20 UTC: LowerThreshold → (check: MinEqualsMax, rationale: No LowerThreshold is needed on the MinimumOnly benchmark because the ecological threshold is an upper limit at 0, already represented by the MaximumOnly benchmark.) ConsistencyResolver applied 2026-03-24 20:20 UTC: BenchmarkValue → (check: MinEqualsMax, rationale: The MinimumOnly benchmark should not have a threshold value since the upper limit at 0 is already defined by the MaximumOnly benchmark (ID=1931). Clearing any BenchmarkValue or threshold fields from this benchmark removes the zero-width range conflict.) ConsistencyResolver applied 2026-03-24 20:21 UTC: BenchmarkValue → (check: MinEqualsMax, rationale: The MinimumOnly benchmark should not have a threshold value since the upper limit at 0 is already defined by the MaximumOnly benchmark (ID=1931). Clearing any BenchmarkValue or threshold fields from this benchmark removes the zero-width range conflict.) ConsistencyResolver applied 2026-03-24 20:21 UTC: UpperThreshold → (check: MinEqualsMax, rationale: No UpperThreshold should be set on the MinimumOnly benchmark to avoid duplication and maintain the correct threshold direction.) ConsistencyResolver applied 2026-03-24 20:21 UTC: LowerThreshold → (check: MinEqualsMax, rationale: No LowerThreshold should be set on the MinimumOnly benchmark to avoid duplication and maintain the correct threshold direction.) ConsistencyResolver applied 2026-03-24 20:21 UTC: LowerThreshold → (check: MinEqualsMax, rationale: No LowerThreshold should be set on the MinimumOnly benchmark because the ecological threshold is an upper limit at 0, already represented by the MaximumOnly benchmark (ID=1931).) ConsistencyResolver applied 2026-03-24 20:21 UTC: UpperThreshold → (check: MinEqualsMax, rationale: No UpperThreshold should be set on the MinimumOnly benchmark to avoid duplication and maintain the correct threshold direction.) ConsistencyResolver applied 2026-03-24 20:22 UTC: BenchmarkValue → (check: MinEqualsMax, rationale: The MinimumOnly benchmark should not have a threshold value since the upper limit at 0 is already defined by the MaximumOnly benchmark (ID=1931). Clearing any BenchmarkValue or threshold fields from this benchmark removes the zero-width range conflict.)

Related Benchmarks

Other benchmarks in the AUS-TDG-CON-GUL family.