TRV-2026-1839Certified recordPeer-reviewed

Citizen science-Large Language Model alliance for automatic assessment of river hydromorphology

Hydromorphological assessment is a fundamental component of river ecosystem evaluation and management, yet standardized field protocols such as the River Habitat Survey (RHS) require trained personnel and substantial field effort. This study investigates whether multimodal large language models (LLMs) can support preliminary hydromorphological screening based solely on photographic documentation of river reaches originating from citizen science datasets. A dataset of 60 river sections previously assessed using t…

Media & Arts · The Trace — both readings · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — gain

A multimodal LLM given photographs of river reaches captured broad gradients of habitat quality and status class, offering a rapid screening aid for prioritizing sites for detailed field survey.

Current reading — problem

The same LLM approach underestimated human modification of river channels and could not reliably infer submerged channel features, so it cannot replace standardized field surveys for regulatory assessment.

What this doesn’t fix

The approach showed only moderate agreement, tested 60 reaches, and could not reliably infer submerged channel features from photographs, so it cannot replace field surveys for regulatory assessment.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1839, v1: “Citizen science-Large Language Model alliance for automatic assessment of river hydromorphology.” Truvace, 2026-10-18. /record/TRV-2026-1839 (accessed at citation time). sha256 00a6710bb82dde13…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv100a6710bb82d…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1839 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.