These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Weather Station / Advisory
- Features
- Weather observations
Weather observations
Record station rainfall against the alert threshold for each field operation and submit it for review before an advisory goes out.
OverviewDraft Observations×
Weather Station / Advisory · Weather observations
New
Draft Observations
Submission waits for the farm coordinator
| Station | Observed at | Rainfall inches | Alert threshold | Parent | Revision | |
|---|---|---|---|---|---|---|
| STT-836 | 10 Oct | 740 | 180 | FO-85542 | 90 | |
| STT-986 | 05 Oct | 700 | 290 | FO-48117 | 250 | |
| STT-355 | 15 Oct | 710 | 180 | FO-89539 | 210 | |
| STT-674 | 22 Oct | 560 | 640 | FO-31522 | 570 | |
| STT-431 | 04 Oct | 600 | 130 | FO-36539 | 820 |
6 of 6 records
STT-836Weather observations · WO-84992
Observed at10 Oct
Rainfall inches740
Alert threshold180
ParentFO-85542
Revision90
What you can do
Tie each reading to the work it affects
A weather observation records what a station measured and why it matters for a specific field operation. The farm coordinator enters the station, the observation date, the rainfall in inches and the alert threshold that applies to the planned work. A fungicide that needs a dry day after application might carry a threshold of 0.25 inches; a reading above that line means the spray should move.
Observations start as Draft and are submitted for review. A Domain Reviewer approves or rejects each one and the decision date is recorded. Only an approved observation becomes the reviewed weather advisory for the farm. The observation also carries a revision number, so the advisory that went out can always be traced to the reading the reviewer actually saw.
How the work is organized
- Record against the operation. Each observation names the field operation it supports and its organization, so readings from one valley never drive advice in another.
- Compare with the threshold. The rainfall reading and the alert threshold sit side by side. The reviewer checks the reading against the agronomy evidence for the same operation before deciding.
- Approve, reject, complete. An approved observation is the advisory. A rejected one stays on record with its decision date. Completed marks an observation whose operation has closed.
What to agree during setup
Agree the list of stations and how they are named, so the same station is never spelled two ways. Agree the alert threshold for each kind of operation, and who may change it. Decide how quickly submitted observations must be reviewed on a spray day, and who covers when the reviewer is in the field. If readings come from a station network or weather service, agree which reading counts: the daily total or a reading at a fixed hour in the organization’s time zone.
Check the handoff on an actual case
A vineyard spray is authorized for May 15. On May 14 the farm coordinator records the valley station’s reading: 0.6 inches of rain, against a threshold of 0.25 inches for that product. She submits the observation. The Domain Reviewer sees it on Observations Awaiting Review, checks the station and the soil moisture evidence line for the block, and approves it. The approved advisory tells the grower to hold the spray.
The planner moves the spray to May 17, which raises the operation’s revision. A new observation for May 16 shows 0.05 inches, well under the threshold. The reviewer approves that one too, and the coordinator goes ahead. If the coordinator had typed the wrong station, the reviewer would have rejected the observation and asked for a corrected one.
What your team sees
- Weather Observation Log — Every observation by state, with station, date, rainfall and threshold.
- Draft Observations — The coordinator’s readings not yet submitted for review.
- Observations Awaiting Review — Submitted readings waiting for the reviewer’s decision.
Follow the work through
- Weather observation to reviewed advisory: Submit, review and publish each advisory.
Connect your weather source before the first season.
What it keeps track of
Data model- Weather observations
- Station weather readings and advisory revisions supporting a reviewed advisory.
- Field operations
- Planned and executed field work such as spray schedules and pest interventions.
- Agronomy evidence
- Measured evidence lines captured against a field operation, with source and unit.
- Organizations
- Operating organizations that own farms, stations and field operations.
Who uses it
Permissions- Farm Coordinator
- Records and submits observations.
- Domain Reviewer
- Approves or rejects them.
- Operations Planner
- Reads approved advisories when rescheduling work.
- Viewer
- Reads the log.
- Admin
- Corrects records and access.
Set up Weather Station / Advisory your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.