Map
Draw each field once. The app loads what the public datasets for its country hold: soil type, slope, watercourses within fifty metres, and designations such as a nitrate vulnerable zone. Those four layers make up the field profile. A field can be split into zones for sub-field work.
A mapped farm with fields, a watercourse buffer and a designation.
Model
For every field, every day, the app models the weather, soil temperature, evapotranspiration and crop growth stage from public data. The models are documented in Models. Each modelled value is labelled modelled and names the model behind it. The weather archive and forecast, the elevation and the planting record are combined into one feature snapshot per field per day. The four models read from it. The field view shows what they return.Measure
Where the model isn’t good enough, a sensor replaces it with a reading from that field. Use an AgriHub360 Sensor or bring your own sensor. A measured value is labelled measured, with the device and the time it came from. The app shows it next to the modelled value it replaced. The reading and the modelled value meet on the field timeline. Each field gets one chart comparing the two.
The modelled value and the measured value on one chart for one field.
Act
The app gives you the rate and the date. You record the application as you do it, in the field, with or without signal. The record feeds the RB209 nutrient plan, the NVZ and Nmax checks, the SFI evidence and the spray log with its MAPP check. The compliance pack is built from the record, in the shape each regime asks for. Each application and each spray goes into its own log. The nitrogen checks, the plan and the SFI evidence read from the logs. The pack is built from all four as a PDF or a share link.
From the application record to the four logs to the compliance pack.