TRV-2026-1399Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1399 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-15T01:10:23.431504Z status: published lens: g_space sector: climate headline: Wheat yield prediction using machine learning, proximal sensing, nitrogen and climate data for Oklahoma dek: PURPOSE: Accurate in-season yield prediction is a practical prerequisite for informed nitrogen (N) management decisions in winter wheat production, yet no rigorous framework has been established and tested against the tools producers currently rely on. Our study developed and evaluated machine learning (ML) models for pre-application wheat yield prediction to support in-season top-dress N management in Oklahoma. METHODS: Four ML algorithms were evaluated using 57 site-years of multi-source data from rainfed Okla… gain_title: A machine learning model using sensor, soil, nitrogen and free climate data predicted wheat yield before nitrogen application with R² of 0.81, versus 0.12 for the INSEY benchmark. problem_title: (none) trace_subject: (none) gain_reading: A machine learning model using sensor, soil, nitrogen and free climate data predicted wheat yield before nitrogen application with R² of 0.81, versus 0.12 for the INSEY benchmark. gain_evidence: The Categorical Boosting Regression (CatBoost) model achieved the best ML performance (R²= 0.81, RMSE = 0.62 t ha−¹, and MAE = 0.42 t ha⁻¹) | substantially outperforming INSEY (R² = 0.12) under the same pre-application data constraint problem_reading: (none) problem_evidence: (none) quick_read: Researchers tested four machine learning algorithms on 57 site-years of data from rainfed Oklahoma wheat environments. Inputs included proximal-sensing NDVI at several growth stages, pre-emergence nitrogen rate, soil texture and monthly climate variables. The models were compared with the INSEY tool and with classical statistical methods. Better yield forecasts before the top-dress window could help producers decide how much nitrogen to apply, supporting productivity and nitrogen use efficiency. Because the climate inputs come from the free Oklahoma Mesonet, the approach could fit existing recommendation systems. The abstract reports model accuracy, not field outcomes from farmers actually using it to adjust nitrogen. limitation: The evidence covers rainfed Oklahoma environments, so performance elsewhere is not established by the abstract. tag: Evidence-backed gain key_points: The best model, CatBoost, reached R² of 0.81, RMSE of 0.62 t per hectare and MAE of 0.42 t per hectare. | The INSEY benchmark managed an R² of only 0.12 under the same pre-application data constraint. | The final 11-feature model relied most on February–March temperatures, evapotranspiration, water balance, pre-plant nitrogen rate and early-season NDVI. | All climate inputs are freely available via the Oklahoma Mesonet, so no extra data infrastructure is required. rundown: The study was framed around a gap: accurate in-season yield prediction is a prerequisite for nitrogen decisions in winter wheat, but no rigorous framework had been tested against the tools producers currently use. Data came from rainfed Oklahoma environments over 57 site-years. Besides the INSEY benchmark, the authors compared ordinary least squares, a linear mixed model and a generalized additive model as classical references. The authors conclude the framework can be integrated into existing nitrogen recommendation systems, combining remote sensing, climate and management data to predict yield within the application window. sources: - peer_reviewed | Precision agriculture | https://europepmc.org/article/AGR/IND609554099 | 2026-10-01 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 3b2cff5e0034afd8d3d6b6cf11983739f10d9e615346ecda73c2c737e23c26ba
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1399 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.
ace