Weather Station or Basic Monitoring? What to Watch and Why
A weather station is only worth its cost if the data changes a decision. Rain, level and flow sensors compared by the action each one enables.
Monitoring is not one decision but three: what to measure, who reads it and what action follows. A rain sensor, a water-level probe and a flow meter answer different questions, and a weather station combines them into a picture that only makes sense if somebody is going to look at it. The right level of monitoring is the cheapest one that still changes what the operator does.
01 – Why each channel needs it, and where it is used
| Channel | Role in this decision | Why they need it |
|---|---|---|
| Distribution and wholesale | Offer a monitoring ladder rather than one gadget | Buyers ask for a weather station because it sounds complete, then never use the data. Selling the level that matches the site keeps the account |
| Contractors and integrators | Decide what the site can actually operate | Monitoring that nobody reads becomes a warranty argument after the first dry week; matching it to staffing is the contractor’s job |
| Direct B2B users – farms, nurseries, municipal green, estates | Choose what to watch and who acts | The value is in the response, not the dashboard: a probe that triggers a call is worth more than a chart nobody opens |
| Specifiers and influencers – designers, water engineers | Write the monitoring scope | Sensors determine the control logic, and the control logic determines the specification of everything upstream |
Where it is used follows the question being asked. Rain-only monitoring suits sites where the schedule is fixed and the only variable is weather. Level monitoring suits tanks that must not run dry and wells that recover slowly. Flow monitoring suits systems that must prove delivery or detect leaks. A weather station suits sites with an operator who will use the data to adjust schedules and justify decisions.
02 – How to make a preliminary selection
Start with the action, not the sensor. Write down what the operator would do differently if they knew the number: skip a cycle, stop a pump, open a valve, call a technician. If no action follows, the sensor is decoration and the money is better spent on filtration.
Then check who reads it. A site visited weekly cannot act on a reading that changes hourly; it needs a threshold that raises an alarm, not a graph. A site with a resident grounds team can use a daily summary, because someone will look at it with coffee.
Then confirm the installation conditions: power, signal, mounting, and the environment. A weather station needs a clear exposure; a level probe needs a stable stilling well; a flow meter needs the right straight run and a compatible pipe material. Those are installation decisions that decide whether the reading is usable at all.
Finally, match the data to the control. A sensor that is not connected to the controller changes nothing automatically; a sensor that is connected changes the programme. The specification should say which it is, because the two cost different amounts and deliver different results.
03 – Comparing the realistic options
The table places the levels of monitoring against the action each one enables, which is the comparison a buyer should make.
| Level | What it tells you | Action it enables |
|---|---|---|
| Rain sensor | Whether rain has fallen | Skip a scheduled cycle |
| Water level | Whether the source or tank is adequate | Stop the pump, protect the supply |
| Flow | What the system delivers | Detect leaks, verify zones, record delivery |
| Weather station | Rain, temperature, wind, radiation | Adjust schedules and justify decisions |
Two published reference points help size the data side: pressure-compensating dripline is specified at 120 mesh by Rain Bird and Netafim, which means filtration performance is measurable through flow and pressure rather than through opinion; and ISO 4064 covers water meters for cold potable water, which is the reference class when a meter is used for billing or official records.
04 – What goes wrong, and what still needs confirming
The common failure is a station that nobody reads. The second is a probe installed where it cannot sense – a level probe in a turbulent sump, a rain sensor under a tree, a flow meter with too short a straight run. The third is data with no threshold, so an anomaly is recorded and never acted on.
Items to confirm in writing: what is measured and to what accuracy; how the reading is transmitted or displayed; what the alarm threshold is and who receives it; the installation requirements (straight run, exposure, power); the data ownership and export format; and the commercial terms – MOQ, spares, price and lead time.
05 – What we can supply and what to send
Delta AgriFlow supplies the monitoring layer alongside the irrigation hardware: rain and weather monitoring stations, rain, water-level and flow monitors, electromagnetic flow meters, and the controllers that can act on the signal.
Send six items: what you want to know; who will read it and how often; what action should follow; power and signal available on site; the pipe or tank where it will be installed; and the quantity for a first order. With those, the monitoring level becomes a matching exercise.
One economic argument for monitoring is worth making explicitly: a flow meter converts a water bill into a per-zone number. On a municipal or estate site that number is what separates a leak from a demand increase, and the difference is usually found in weeks rather than seasons. The meter pays for itself the first time it prevents a hidden burst from running for a month.
A second is that monitoring changes the maintenance conversation. With a flow record, a declining zone can be investigated before the plants show stress; without it, the first evidence is a dry bed and a suspicion. The cost of the meter is a fraction of the cost of the water lost while nobody was measuring.
Where a station is chosen, the data has to be owned by the site rather than by a subscription. Export format and local storage matter more than the dashboard, because the record is what gets used in the next budget cycle and in any dispute with a supplier or a water authority.
Finally, decide the review rhythm before buying. A monthly review with one clear question – did any zone drift – captures most of the value. A station whose data is never reviewed is an expensive sensor, and the installation would have been better served by a single flow meter and a notebook.
A final check before ordering a station: ask what the site will do in the first week of data. If the answer is a specific action – a schedule change, a threshold, a call – the station is justified. If the answer is that it will be interesting, the money belongs in a flow meter and a spare element, because both of them change something immediately.
Where several sites are managed by one team, the value of monitoring compounds: a single dashboard with comparable zones lets the team spot the site that is drifting. That is an operational argument rather than a technical one, and it is usually the argument that gets a monitoring budget approved.
06 – Questions, sources and next steps
Is a weather station necessary? Only where somebody will use the data to change schedules or justify decisions. A single rain sensor or a flow meter often delivers more value for less money.
Can a controller act on the sensor? Only if the sensor is wired or connected to it. Monitoring that is not connected informs a person, not the system.
How accurate does the meter need to be? As accurate as the use requires: indicative readings for maintenance, classed meters for billing or official records.
A useful question before buying any station: which of its readings would change a decision this month? If the answer is none, the station can wait; if the answer is the level or the flow, buy that sensor alone and add the rest later.
A last practical point: put the monitoring point where a person can reach it without a ladder. The best sensor in the world is not checked if checking it is awkward.
Information boundary
This article describes how the decision is structured. It is not a performance specification and does not state capacity, flow, pressure or service-life values for a specific product. Those values are confirmed per project after a written quotation; manufacturer figures cited are the published values for those products, not project commitments.
Reviewed: 2026-10-26. Next review after supplier specifications are confirmed in writing.
Sources and further reading
- Rain Bird XFA 13 mm dripline datasheet – 120 mesh filtration requirement, 50-350 kPa compensating range
- Netafim Techflow bid performance specification – 120 mesh or finer filtration, disc grades 40-200 mesh
- ISO 9912-1:2004 – Filters for micro-irrigation: classification
- ISO 18471:2015 – Verification of filtration grade
- FAO – Irrigation manual, Chapter 6: drip irrigation
Choosing a monitoring level? Tell us what you want to know and who will act on it through our quotation request.
