52/100

Moderate evidence

GainPublished recordLifestyleGood Space

Research on the optimal modeling path for inversion of Pb content in rice leaves based on hyperspectral data of ground objects and machine learning and cross-scale remote sensing monitoring

Truvace record
TRV-2026-1188raw data (JSON)
Version
v2Revised
First published
Evidence type
Benchmark or lab evaluation
Sources
1 sourcePeer-reviewed
sha256
20f997292914…check it

Real-time and accurate monitoring of heavy metal concentrations in rice is essential for ensuring food safety and supporting the safe utilization of contaminated agricultural land. Hyperspectral technology offers advantages such as rapid, nondestructive, cost-effective, and environmentally friendly monitoring. This study developed multiple models for estimating Pb content in rice leaves, compared their performance, and identified stable modeling pathways for continuous regional monitoring using hyperspectral rem…

The gain

The best-performing model, combining the Whale Optimization Algorithm with PLS, estimated lead content in rice leaves with a validation R2 of 0.7452.

Sources

1 on file
  1. Environmental Monitoring and Assessmentdoi:10.1007/s10661-026-15959-x
    Peer-reviewed2026-09-23

Cite this record

v2

Truvace Impact Record TRV-2026-1188, v2: “Research on the optimal modeling path for inversion of Pb content in rice leaves based on hyperspectral data of ground objects and machine learning and cross-scale remote sensing monitoring.” Truvace, 2026-11-04. /record/TRV-2026-1188 (accessed on the day you copy it). sha256 20f997292914ef57…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv220f997292914…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  2. Publishedv10a9e434cf1a2…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1188 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.