Remote Moisture Monitoring: Where to Place Soil Sensors in a Drip-Irrigated Field

Remote moisture monitoring starts with a placement map. In a drip-irrigated field, put soil moisture sensors where the crop actually takes up irrigation water, then record which soil, root depth and valve zone each station represents. A strong radio signal cannot compensate for a probe beside a leaking emitter or outside the wetted root zone.
Soil moisture monitoring equipment being installed in a Wisconsin research field. Photo: Tyson Ochsner / USDA Agricultural Research Service, public domain.
The practical deliverable is a short station register that connects every graph to a field location and a management decision. Build that register before enabling moisture-based irrigation rules. The example below is an original planning exercise, with assumed dimensions and station numbers, rather than a measured farm trial or a universal installation specification.
1. Define the irrigation decision before choosing a sensor location
Start with the smallest area you can actually irrigate independently. Draw its valve boundary and mark changes in crop, planting date, soil texture, slope and dripline layout. A monitoring zone describes an area with similar water behavior; a valve zone describes the area controlled by one valve. They can overlap without being identical.
For example, one valve might serve both a sandy strip and a deeper loam. Monitoring both areas can reveal different drying patterns, but the sensors do not create independent water control. Record that constraint explicitly. A decision to extend the whole valve runtime may help one area while applying unnecessary water to the other.
Virginia Cooperative Extension's sensor placement guidance recommends representative management zones and warns that uneven irrigation application can distort decisions. Use that principle to separate routine decision stations from deliberately unusual diagnostic locations.
2. Locate the wetted root zone before fixing an emitter offset
A drip emitter wets a local volume of soil. Its relationship to the crop row matters more than the distance from the gateway. Inspect an ordinary irrigation event at a proposed station: identify the emitter, the row and the wet soil around active roots. Record the runtime and when the inspection occurred, because an offset measured immediately after startup describes a different observation from one made later.
UF/IFAS guidance for citrus and other fruit trees emphasizes placing sensors inside the irrigation wetting pattern. Its crop-specific distances should not become a fixed offset for every vegetable bed or orchard. Confirm the actual pattern in the intended soil and planting arrangement.
Use a neighboring inspection location rather than excavating the final sensing volume repeatedly. Mark the proposed horizontal offset on a sketch, including which side of the dripline it occupies. If two trial positions behave differently, document the difference before deciding which one represents the crop. Keep a dry-edge position only when its diagnostic purpose is clear.
3. Choose depths from the observed root profile
A sensor depth needs a reason: observing water in the active upper roots, following the lower root zone, or checking movement below it. Determine the relevant rooting depth from the crop, growth stage and a field profile. Bed surfaces, compacted layers and shallow soil can make an assumed rooting depth unsuitable.
University of Minnesota Extension describes paired sensors around one-third and two-thirds of rooting depth. Treat this as a starting arrangement to verify locally. In an assumed 45 cm effective root zone, those fractions give 15 cm and 30 cm, approximately 6 and 12 inches.
Those two depths do not monitor below a 45 cm root zone. A separate deeper diagnostic point would have a different role. Label that distinction in the dashboard. Also state whether the recorded depth refers to the center of a sensing volume, the probe tip or another installation reference; a long probe can span more than one depth.
4. Worked placement plan: three zones in a 12 ha field
Assume a 12 ha field, about 29.7 acres, has three independently controlled valve zones. Zone A covers 5 ha of sandy loam, B covers 4 ha of loam and C covers 3 ha with a shallower effective root profile. The following proposal uses two representative stations in each zone so the manager can compare locations. It is a project example, not a sensors-per-hectare recommendation.
| Zone and area | Representative station IDs | Assumed depths at each station | Placement question to verify |
|---|---|---|---|
| A: 5 ha | A1 and A2 | 15 and 30 cm | Do both locations represent the ordinary sandy-loam bed and wetting pattern? |
| B: 4 ha | B1 and B2 | 15 and 30 cm | Are both away from atypical ponding while covering the intended loam area? |
| C: 3 ha | C1 and C2 | 10 and 20 cm | Does the assumed 30 cm effective root depth match the actual shallow profile? |
The base plan contains 3 zones × 2 stations × 2 depths = 12 measurement points. If the investigation also needs one point near a suspected dry edge and one below a root zone, the total becomes 14 points. They might be delivered by separate sensors or by compatible multidepth probes. Twelve measurement points do not necessarily mean twelve radio nodes.
Give the additional points diagnostic names, such as A-edge and B-below. Do not blend their readings into an unlabeled field average. If a budget reduction removes A2, record that Zone A now has no second representative location for comparison. This describes the information lost more usefully than simply stating that the system has fewer sensors.
5. Install a station that can be found and interpreted again
For every station, record its coordinates, row number, emitter reference, horizontal offset, sensing depths, device serial number and installation date. Photograph the location and a depth reference before finishing the installation. The next technician should be able to identify A1 without guessing which flag or cable belongs to it.
NC State Extension's vegetable plasticulture guidance distinguishes upper and deeper root-zone observations and shows why the crop-row and drip-tube arrangement affects placement. Preserve those relationships in the station record rather than writing only “sensor in tomato field.”
Follow the selected device's installation procedure for soil contact, orientation and cable handling. Check the completed record against the physical installation before backfilling. Protect the site from routine cultivation and harvest traffic, while keeping access practical. Put the antenna or logger where its approved cable arrangement allows reliable communication without moving the soil measurement into an unrepresentative spot.
6. Commission the placement through a documented irrigation event
The following acceptance workflow tests whether a station is interpretable. It does not set a crop's irrigation threshold or certify sensor accuracy. Run it while a person can still inspect the field, and retain the observations alongside the graph.
- Confirm identity. Match each dashboard channel to its station ID, depth and physical device. Check that no two channels have been given the same location label.
- Confirm units and time. Record whether the channel reports volumetric water content or soil water tension. Verify the time zone and the distinction between measurement time and upload time.
- Record the starting condition. Note recent rain, the previous irrigation, crop stage and visible soil conditions at each representative station.
- Observe the irrigation. Log the valve start and stop, measured flow if available, and any pressure or emitter-delivery checks made near the stations.
- Compare the response. Review upper and lower depth traces, then compare the two representative locations within each zone. Allow for the observation timing and the device's response behavior.
- Investigate a mismatch. Check installation, soil conditions, local emitter delivery and data freshness before treating an unusual graph as a need for more water.
- Accept or revise the map. Sign off the location and channel labels only after the graph can be explained. Record any move as a new installation event, preserving the previous history.
7. Use disagreements as questions for a field check
A pattern can have several causes. The table is a diagnostic prompt list, not a set of automatic watering commands. Compare readings only after confirming their units, timing and location roles.
| Observed pattern | Question to investigate | Useful next check |
|---|---|---|
| One station changes; its paired location does not | Did both places receive comparable irrigation? | Check emitter delivery, valve assignment and fresh timestamps at both sites. |
| The upper point changes; the lower point stays steady | Has water reached the monitored lower depth at this observation time? | Inspect the wetting profile and review later readings before extending runtime. |
| The below-root diagnostic point repeatedly changes during irrigation | Is water moving beyond the intended root zone, or is another water source involved? | Compare event timing with rain, local drainage and a field profile. |
| A dry-edge diagnostic point remains dry | Is it doing the job for which it was installed? | Compare its mapped position with the measured wetting boundary. |
| Every trace becomes perfectly flat at the same time | Are new measurements still arriving? | Check the latest measurement timestamp and logger status before changing irrigation. |
If local delivery is questionable, use the separate drip irrigation maintenance and monitoring checklist to investigate the water system. A moisture trace is a reason to inspect a suspect area; it does not independently identify a blocked emitter or prove that a filter needs cleaning.
8. Keep placement history when the crop or layout changes
Review the map after moving drip tape, changing bed geometry, replanting, or discovering a different root profile. Keep the previous station record and mark when the new arrangement began. Joining pre-move and post-move readings without annotation can make a change in location look like a change in crop water use.
When preparing a new bed layout, carry the emitter spacing and line position from the drip tape specification record into the monitoring sketch. For a vegetable drip irrigation layout, show the relationship between each row and tape. For an orchard dripper system, show the tree, emitter positions and the root area being observed. These links provide layout context, not a claim that every system includes compatible sensors.
9. Questions about remote soil moisture sensor placement
How many soil moisture sensors does a field need?
Count the management zones, the comparisons required within them and the depths needed for each decision. Then distinguish measurement points from physical probes and radio nodes. The 14-point example above is a transparent project assumption; field area alone does not prove that it is sufficient for another farm.
Can the strongest wireless signal determine the sensor location?
Use communication quality as an installation check after choosing a representative soil location. Explore permitted logger, antenna or gateway positions if the first radio arrangement fails. Document any compromise, because moving the probe to the field edge may change what its readings represent.
Can one soil moisture percentage control every zone?
A shared number needs a demonstrated agronomic basis. Soil, crop stage, sensing method and calibration affect interpretation. Begin with individually labeled trends and a crop-specific scheduling method; approve automatic rules only after the relevant station's placement, data quality and management role have been checked.
10. What a completed placement file contains
A usable file contains the valve and soil-zone map, station IDs, offsets and depths, channel units, installation photographs, event observations and unresolved limitations. It also names the person who will check a stale or contradictory reading. With that record, remote moisture monitoring becomes a traceable field decision process instead of a collection of graphs whose locations have been forgotten.



