Agriculture and agronomy (applied): ML domain track
You already work with seasons, fields, sensors, and messy observational records. This track orders the shared Road to ML spine for applied agriculture and agronomy-style analysis. It teaches methods. It does not prescribe farm practices. It does not guarantee yield, compliance, or a hire.
Core idea. Keep domain judgment about crops, livestock, soil, and weather context. Add Python, regression or classification, time series, and honest metrics. Methods live in Modules 00–25.
Who this is for
- Agriculture, agronomy, and agri-engineering learners
- Practitioners analyzing stations, IoT sensors, or remote-sensing derived tables
- Analysts who need forecasting habits without jumping straight to deep models
What you already bring
- Comfort with seasons, growth stages, and field variation (even if informal)
- Respect for missing data, sensor drift, and site differences
- Stakeholder questions that need clear uncertainty talk
ML problem types you will meet
- Time series forecasting and anomaly detection on sensor or station streams
- Regression on continuous yield or quality-style variables
- Classification of stress, quality, or event labels from features
- Careful train/test splits that respect time and location
- Communication of error so decisions are not oversold as prescriptions
Gaps this track closes
- Module 01
- Modules 02–05
- Module 15
- Module 03 or Module 04 by task
- Module 21
- Module 19 when archives are tabular
Related resources
- Data Validation. Sensors drift. Validate before you trust a forecast.
- Ethics in ML. Field and farm data still need careful use framing.
- Common Errors. Leakage and shuffle mistakes hit seasonal data hard.
- Model Explainability Cheatsheet. Quick sheet beside Module 21.
- Stakeholder Communication. Uncertainty talk without agronomic prescriptions.
Role emphasis (not destiny)
| Emphasis | Role | Why |
|---|---|---|
| Primary | Data Scientist | Models plus evaluation on observational field data |
| Alternate | ML Engineer | When models must run in a monitoring or ops pipeline |
See Career Paths and Career Roadmap Guide. Treat times as emphasis maps only.
Intensity maps
Research support (tier B)
- Module 00 if needed
- Module 01
- Module 02
- Module 03 or Module 04
- Module 05
- Module 15
- Module 21
- Time-aware practice via Module 15 or a Module 16 project you adapt carefully
Job-oriented study (tier B toward C)
- Complete Research support
- Add Module 19 and Module 07
- Add Module 13–14 only for production monitoring roles
- Keep deep learning optional until baselines and Module 15 habits are solid
Ordered study checklist
- Pick intensity map
- Finish Module 01 with a public agricultural or sensor CSV
- Write a time-based (and site-aware) split before any fancy model
- Finish Module 05 and Module 15 for ordered data
- Practice one forecast or anomaly plot with error described in plain words
- Document what the model must not be used for (agronomic prescription, guaranteed yield)
Start here
Open Module 00 README if you need math or environment help. Otherwise open Module 01 README.
Honesty and traps
- Educational content only. Not farm advice, chemical recommendations, or regulatory compliance guidance.
- Random shuffles destroy time series truth. Prefer time order.
- Spatial leakage is real when nearby fields share train and test.
- Vendor “AI for yield” marketing is not a methods curriculum.
Try next: Open Module 15: Time Series Analysis after Modules 01, 02, 05, and one supervised module (03 or 04).