Root-zone measurement
Multiple representative locations and depths help reveal depletion and wetting, but installation, calibration, soil contact, temperature, salinity, and spatial variability remain important.
MEASURE THE ROOT ZONE, ACCOUNT FOR THE WATER
Irrigation
Decision Support
Irrigation decision support connects measurements and estimates to a field-specific plan. It should explain its water balance, sensor assumptions, crop context, system constraints, confidence, human responsibility, and outcome checks.
5CHAPTERS4VISUAL BLOCKS15GRAPH LINKS3SOURCES
DECIDE / SELECTED CONCEPTIrrigation Decision SupportStart with the role, then move through the editorial sequence.
HOW TO READ THIS PAGE
Visual explanationA diagram or operating scene makes the relationship visible.
Structured modelA flow, comparison, capability set, or boundary map organizes the idea.
Guided explanationOriginal prose connects the concept to its operating context.
01 / Overview
A dashboard does not irrigate.
A qualified decision loop does.
University of Minnesota Extension describes direct soil-water monitoring and weather-based root-zone water balance as two core scheduling approaches, and recommends using field sensing together with daily accounting.
USDA ARS describes advanced tools that combine soil, plant, environmental, weather-station, sensor-network, software, and variable-rate irrigation capabilities. These tools still require field-specific interpretation and continued validation.
02 / Decision loop
Observe, reconcile, schedule,
apply, measure again.
01OBSERVE / 01Estimate root-zone stateSensor depths, soil texture, rooting depth, crop stage, rain, irrigation, and field inspection
02BALANCE / 02Reconcile water inputs and useInitial condition, evapotranspiration, precipitation, applied water, runoff, drainage, and uncertainty
03SCHEDULE / 03Fit the field and systemAllowable depletion, forecast, water allocation, pump capacity, application depth, travel time, and zones
04VERIFY / 04Check the applied outcomeMeasured application, soil response, runoff, pressure, uniformity, crop response, faults, and updated balance
03 / Evidence stack
No single sensor owns
the irrigation decision.
Atmospheric demand
Reference weather and evapotranspiration estimates describe atmospheric demand that must be translated using crop, stage, canopy, and local field context.
Plant condition
Canopy temperature, growth stage, rooting depth, visual inspection, and stress observations can challenge or support the soil-water account.
Delivery reality
Flow, pressure, pump capacity, travel speed, distribution uniformity, runoff, leaks, plugged emitters, and measured application determine what reached the field.
04 / Scheduling methods
Methods complement each other
when their assumptions are visible.
MethodPrimary signalKey limitation
Soil-moisture monitoringMeasured water content or water potential at selected places and depthsRepresentativeness, installation, calibration, root-zone interpretation, and sensor condition
Weather-based water balanceEstimated crop water use minus measured or estimated water inputsInitial condition, crop coefficients, local weather, runoff, drainage, and application accuracy
Plant feedbackCrop response such as canopy temperature or other stress indicatorsStress may have multiple causes and can appear after avoidable loss
Hybrid decision supportReconciled soil, weather, crop, forecast, and system evidenceMore inputs create more failure modes unless provenance, quality, and fallback are explicit
05 / Boundaries
Automated scheduling is not
unbounded water control.
A recommendation needs a water budget and machine reality.Available water, legal allocation, energy, pump and system capacity, application uniformity, forecast, runoff risk, drainage, and labor can constrain the schedule.
Sensor failure needs a safe fallback.Missing, stuck, drifting, unrepresentative, disconnected, or implausible inputs should trigger qualification, cross-checking, and a defined human decision path.
Software does not remove field responsibility.The operator remains responsible for inspection, local recommendations, crop and soil context, equipment condition, water rules, and the consequences of application.
06 / Connections
See the system around this concept.
Follow incoming and outgoing relationship records to understand what supplies, informs, enables, coordinates with, or extends this technology in the published knowledge graph.
Relationship radar / published edges15 records / 15 neighboring systems
Incoming12records point toward this concept
decide roleIrrigation Decision SupportSelected technology
Outgoing03records point from this concept
15connections visible
observe / Environmental sensingAgricultural Weather Stations ↗supplies local weather observations to
Qualified local weather observations can supply atmospheric-demand and precipitation inputs to a field-specific irrigation scheduling workflow.
observe / Field sensingSoil Moisture Sensing ↗provides root-zone evidence to
Representative, depth-aware soil-moisture observations can inform the estimated root-zone state used in irrigation scheduling.
decide / Farm softwareFMIS ↗can organize the field records around
Farm management software can organize field identity, crop context, observations, irrigation plans, applied records, and outcomes around a decision-support workflow.
act / Water and nutrient applicationPrecision Fertigation ↗can coordinate water timing and demand context with
Irrigation decision support can contribute crop-water timing and demand context, while fertigation adds nutrient preparation, hydraulic delivery, root-zone verification, and greenhouse-specific safeguards.
observe / Crop water intelligenceCrop Evapotranspiration Estimation ↗can supply bounded crop-demand evidence to
A qualified crop ET estimate can inform root-zone accounting, but initial soil water, rainfall, measured irrigation, runoff, drainage, rooting, crop condition, system capacity, local guidance and field verification remain separate.
observe / Irrigation sensingIrrigation Flow Measurement ↗can provide measured delivery evidence to
Verified flow rate and totalized volume can strengthen irrigation accounting, while meter installation, telemetry, destination, distribution, runoff, drainage, soil storage and crop response remain part of interpretation.
observe / Crop water intelligencePlant Water Status Sensing ↗can add crop-response evidence to
Qualified plant water-status observations can add crop response to an irrigation review, while diagnosis, soil profile, weather, delivery, system capacity, salinity, disease, nutrition, economic objective and human authority remain explicit.
act / Irrigation controlVariable Rate Irrigation ↗can provide a reviewed irrigation plan to
Decision support can organize a reviewed timing and spatial plan, but VRI execution still requires exact compatibility, field geometry, position, machine state, hydraulic capacity, physical verification, alarms, fallback and operator authority.
act / Water managementDrip Irrigation Systems ↗provides a delivery system to check within
A drip-irrigation system provides the physical delivery layer that an irrigation decision must qualify through source, filtration, pressure, distribution, root-zone evidence, crop context, and field-specific operating constraints.
decide / Water quality and irrigationIrrigation Salinity and Sodicity Evidence Integration ↗adds water, soil, drainage and accumulation context to
Irrigation decisions may need qualified salt- and sodium-related evidence while no indicator independently determines an irrigation action.
connect / Water quality and irrigationAgricultural Recycled Water Governance ↗constrains source, field, method and exposure context for
An irrigation plan using recycled water remains bounded by authorization, distribution, monitoring, cross-connection and exposure controls.
decide / Water managementFarm Water Accounting ↗provides measured delivery context to
Water-accounting records can inform irrigation review by keeping source, flow measurement, time, area, delivery event, uncertainty, and reconciliation visible.
connect / Environmental sensingAgricultural Weather Data Integration ↗can deliver qualified weather context to
A weather-data handoff can supply time-, location-, unit-, and quality-aware observations to irrigation review without turning those observations into an automatic instruction.
act / Irrigation controlAutomated Irrigation Control ↗can provide reviewed intent to
A reviewed irrigation decision can provide bounded timing or target intent to automation while sensing, interlocks, delivery evidence, operator authority, and safe fallback remain separate.
observe / Environmental sensingAgricultural Microclimate Sensor Networks ↗adds local atmospheric and surface contrasts to
Microclimate observations can qualify irrigation context without independently determining crop water demand or an irrigation amount.
5CONNECTED ROUTES1–7STEP POSITIONS36ROUTE SOURCE LINKS
Operating practice
From soil and weather evidence to an irrigation decision
Follow the water-management evidence stack from spatial soil context and local weather through root-zone sensing, a qualified scheduling decision, and field verification.
CURRENT POSITION04
04 / DECIDE
Open the complete route ↗Reconcile the scheduling evidence
Combine soil, crop, weather, water-balance, forecast, and delivery-system constraints into a bounded decision.
07 / Evidence
Primary sources.
This briefing uses University of Minnesota Extension guidance on soil-moisture and evapotranspiration-based scheduling plus USDA ARS research context on advanced tools. It provides no universal threshold, crop coefficient, water amount, or automated control instruction.
01
Evapotranspiration-based irrigation scheduling or water-balance methodUniversity of Minnesota Extension · Accessed 2026-07-20
02
Soil moisture sensors for irrigation schedulingUniversity of Minnesota Extension · Accessed 2026-07-15
03
Advanced tools for irrigation schedulingUSDA Agricultural Research Service · Accessed 2026-07-20