SPADE: A Large Language Model Framework for Soil Moisture Pattern Recognition and Anomaly Detection in Precision Agriculture

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2509.18123v2 Announce Type: replace Abstract: Accurate interpretation of soil moisture patterns is critical for irrigation scheduling and crop management, yet existing approaches for soil moisture time-series analysis either rely on threshold-based rules or data-hungry machine learning or deep learning models that are limited in adaptability and interpretability. In this study, we propose SPADE (Soil moisture Pattern and Anomaly DEtection), which, to the best of our knowledge, is the first LLM-based framework specifically developed for soil moisture time-series analysis. Using GPT-4.1 and domain-informed prompts, SPADE performs zero-shot joint identification of wetting events and anomalies without task-specific annotation, training, or fine-tuning. By converting time-series observations into a textual representation, SPADE identifies wetting-event timing, estimates sensor-level moisture responses, detects and classifies multiple predefined anomaly types, and generates structured, human-readable reports. SPADE was evaluated using real-world soil moisture data collected from commercial and research farms encompassing four crop types across the United States. Compared with the evaluated training-free baselines, SPADE achieved higher anomaly recall and F1-score, strong precision and recall for wetting-event detection, and high accuracy in classifying the observed anomaly types. Its structured reports summarize event timing, anomaly type, concise explanations, and sensor-level moisture responses, supporting practical interpretation of soil moisture patterns. These …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2509.18123
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.