SOIL. WATER. CLIMATE. BETTER DECISIONS.
Agricultural Monitoring Intelligence for Growing Systems
RAUZ combines soil, irrigation, weather, microclimate and remote-sensing data to verify conditions, diagnose change and support clearer agricultural monitoring decisions across farms, orchards, vineyards and greenhouses.
Monitoring Domain
Monitor the growing environment as a system—not as a single soil-moisture number.
Agricultural monitoring becomes more useful when soil, water, weather, microclimate and remote-sensing observations are reviewed together. RAUZ works above the measurement layer: existing sensors and field systems can remain in place while the data is checked, aligned, compared and interpreted against the actual growing environment.
Root-zone conditions
Review soil moisture, soil temperature, water potential and other relevant soil observations by depth, location and management zone rather than relying on one point reading.
Irrigation response
Compare irrigation events with soil response, rainfall, drainage behaviour and available flow or pressure information to see whether the observed response is credible.
Weather & microclimate
Bring air temperature, humidity, rainfall, wind, solar radiation and leaf-wetness observations into the same review where they help explain field conditions.
Field-scale context
Use suitable satellite or other spatial data to add wider context where point sensors alone cannot represent variation across a farm, orchard, vineyard or irrigation scheme.
Key Questions
Start with the decision that the monitoring needs to support.
A useful monitoring plan is built around questions, not around a catalogue of sensors. The exact answer remains crop-, soil-, climate- and site-specific, but the questions below are common starting points.
Is water reaching the intended root zone?
Compare irrigation timing, rainfall and soil response at suitable depths and locations. A wet surface does not necessarily describe deeper root-zone conditions.
Is a dry or wet reading representative?
Check placement, depth, soil variability, calibration, nearby sensors and recent management events before treating one reading as a field-wide condition.
What changed before the trend changed?
Review irrigation, rainfall, temperature, maintenance, sensor replacement, cultivation and other recorded events against the time series.
Is the pattern local or spatially wider?
Compare field points, zones and suitable remote-sensing products where scale and resolution are appropriate to the question.
Is the anomaly physical or a data problem?
Look for missing records, timestamp shifts, sudden steps, flat-lines, implausible values, communication gaps and disagreement with independent observations.
What should be checked next?
Turn the review into a short list of defensible next actions: verify the sensor, inspect the field, obtain another observation, adjust monitoring frequency or seek crop-specific advice.
Site Context
Instrument selection follows soil, water, climate and management context.
Agricultural monitoring is highly site-specific. Before recommending a sensor type, depth, spacing or reporting frequency, the monitoring question should be connected to the field profile, water system, crop or production system, operating constraints and the decision-maker who will use the information.
- Soil profile: texture, layering, rooting depth, variability and zones that may respond differently.
- Subsoil & geology: relevant where drainage, shallow rock, groundwater, salinity, slope behaviour or earthworks influence the growing environment.
- Water source & irrigation: rainfed, drip, sprinkler, surface irrigation, storage, pumping, drainage or other project-specific arrangements.
- Topography: elevation, aspect, low points, runoff pathways and exposure that can create different moisture or microclimate zones.
- Climate & microclimate: rainfall, heat, humidity, radiation, wind, frost exposure and seasonal operating windows.
- Production system: field crops, orchards, vineyards, plantations, nurseries, greenhouses or botanical production have different spatial and operational needs.
- Data infrastructure: power, communications, logger access, manual readings, APIs, spreadsheets and maintenance capability.
- Decision requirement: irrigation review, anomaly investigation, environmental baseline, water-use assessment, research, reporting or another defined purpose.
What to Monitor
Use a measurement set that can explain the physical process—not just record numbers.
USDA NRCS’s SCAN programme is a useful public example of multi-variable agricultural observation: typical stations monitor soil moisture at several depths together with soil temperature, air temperature, relative humidity, solar radiation, wind, precipitation and barometric pressure. A private project may need fewer or different variables, but the same principle applies.
| Parameter | Why it may matter | Possible measurement approach | Interpretation caution |
|---|---|---|---|
| Soil water content | Tracks changes in volumetric water status and response to rainfall or irrigation. | In-situ volumetric water-content sensors, TDR/FDR/capacitance-type systems, manual verification where appropriate. | Sensor response depends on soil, installation, depth, calibration and spatial variability. |
| Soil water potential | Helps describe how strongly water is held and complements water-content observations. | Tensiometers or other matric-potential sensors selected for the expected range. | Useful range and maintenance requirements vary by sensor type and field condition. |
| Soil temperature | Adds context to root-zone and seasonal conditions and can help explain sensor or biological response. | Temperature probes installed at relevant depths. | Depth and local exposure should be recorded; surface and deeper conditions can differ materially. |
| Air temperature & relative humidity | Provides basic microclimate context for heat, humidity and atmospheric demand. | Shielded temperature/RH sensors at a representative location. | Siting and radiation shielding matter; greenhouse and outdoor layouts require different treatment. |
| Rainfall | Helps distinguish natural wetting from irrigation and supports water-balance interpretation. | Rain gauge or verified local meteorological data. | Spatial variability, wind effects, siting and missing periods can affect interpretation. |
| Solar radiation | Supports microclimate and evapotranspiration-related context. | Pyranometer or suitable radiation sensor. | Keep the measurement objective and sensor class proportionate to the project. |
| Wind | Can affect evapotranspiration, spray operations, exposed-field conditions and sensor siting. | Anemometer and wind-direction sensor where relevant. | Obstructions and mounting height strongly influence local measurements. |
| Leaf wetness | Can provide a proxy observation for periods of surface wetness where relevant to the monitoring objective. | Leaf-wetness sensor located to represent the intended canopy or exposure condition. | Interpretation is crop- and disease-model-specific; it is not a disease diagnosis on its own. |
| Irrigation flow / pressure | Provides independent evidence that water was delivered and can help explain uneven soil response. | Flow meters, pressure sensors, controller logs or pump records. | Delivered volume does not prove uniform infiltration across the field. |
| Water level / groundwater | May matter where shallow groundwater, drainage or waterlogging influences the site. | Water-level sensors, piezometric observations or existing monitoring records. | Only include where the hydrogeological mechanism is relevant to the agricultural question. |
| Electrical conductivity | May support review of salinity-related conditions in soil or irrigation water. | Soil or water EC instruments suited to the required application. | EC is context-dependent and should not be interpreted as a complete soil-fertility assessment. |
Instrumentation
Choose instruments by measurement question, operating range and field reality.
The options below are discussion categories, not a universal bill of quantities. Final selection should consider required accuracy, sensor range, soil type, installation method, depth, spatial variability, power, communications, maintenance, calibration, data ownership and the consequences of missing data.
Soil moisture, water potential and soil temperature
Weather and microclimate station
Irrigation and water-delivery observations
Data loggers, gateways and telemetry
Remote sensing and spatial data
RAUZ Data Intelligence
Connect the evidence, test its credibility, then interpret the change.
RAUZ applies the same evidence discipline used across its environmental and engineering monitoring work: preserve the source, check data quality, compare independent observations, understand the physical context and keep the interpretation traceable. Automated screening can accelerate review; technical conclusions remain engineer- or specialist-reviewed within the agreed scope.
Bring related data into one review layer
Field sensors, irrigation records, weather observations, spreadsheets, APIs, remote sensing and operational notes can be aligned without forcing one proprietary hardware stack.
Run data QA/QC before interpretation
Check missing records, duplicates, units, timestamps, flat-lines, sudden steps, drift, communication gaps, baseline changes and other inconsistencies that may mislead a decision.
Review trend, rate and relationships
Compare time series, zones, depths, rainfall or irrigation events and relevant spatial evidence to determine whether an apparent change is persistent and coherent.
Put the pattern back into site context
Relate observations to soil profile, water system, weather, management events, crop or production setting and the limitations of each measurement source.
Produce a traceable review
Separate observed facts from interpretation, state uncertainty, document excluded or suspect records and show the evidence supporting each conclusion.
Define the next useful question
Recommend verification, inspection, additional measurement, monitoring-frequency changes or specialist agronomic review where the evidence does not yet support a firm conclusion.
Remote Sensing
Use satellite observations as another layer of evidence—not as a substitute for field context.
Agricultural monitoring spans scales. A sensor may represent centimetres to metres around an installation point, while satellite products can represent field, regional or much broader areas. RAUZ can combine them where the spatial resolution, revisit interval and physical variable are appropriate to the question.
Broad soil-moisture context
NASA’s SMAP mission maps surface soil moisture and has been used operationally in USDA global crop monitoring. It is valuable for broad context, but its footprint and sensing depth differ from an in-situ root-zone sensor.
Vegetation-state observation
ESA states that Sentinel-2’s spectral bands can support crop discrimination and plant indices such as leaf area, chlorophyll and leaf-water information. These observations can add spatial context to field measurements.
Water-productivity information
FAO WaPOR provides open, remotely sensed information for agricultural water and land productivity at multiple scales, with particularly detailed applications in Africa and the Near East.
Agrometeorological and crop-monitoring context
The European Commission’s JRC MARS programme combines meteorological information, maps, statistics, positional information and remote sensing for agricultural monitoring and crop-condition assessment.
Regional Context
One monitoring architecture; different environmental and operating conditions.
RAUZ’s priority markets span the South Caucasus, European Union, United Kingdom, Middle East and Africa. Agricultural monitoring should not be copied from one region to another. Local soil, water, climate, cropping system, communications, maintenance capacity and regulatory context must be established before the monitoring design is fixed.
South Caucasus
European Union
United Kingdom
Middle East
Africa
Official Reference Systems
Four public monitoring programmes show why agricultural evidence works best when sources are combined.
These are not RAUZ projects. They are official public examples used to illustrate monitoring architecture, scale and data-integration principles that can inform project discussions.
Multi-depth soil + weather monitoring
SCAN stations focus on agricultural areas and typically combine soil moisture at several depths with soil temperature, air temperature, humidity, radiation, wind, precipitation and pressure. Design lesson: one soil sensor rarely describes the whole growing environment.
Satellite soil moisture used in crop monitoring
NASA reports that SMAP soil-moisture information has been incorporated into USDA global cropland monitoring and forecasting workflows. Design lesson: satellite observations can add broad context, but they should be interpreted at their actual spatial scale.
Meteorology + remote sensing + modelling
The JRC MARS programme uses meteorological information, maps, statistics, positional data and remotely sensed observations for agricultural monitoring. Design lesson: stronger interpretation comes from combining evidence types rather than treating each dataset as an isolated dashboard.
Water productivity from remote sensing
FAO WaPOR provides open water- and land-productivity information at different spatial levels, including detailed applications across Africa and the Near East. Design lesson: remote sensing is especially useful when a project needs spatial context beyond individual field instruments.
Project Workflow
Begin with the question and existing evidence before adding more hardware.
A project can start from an existing sensor network, a spreadsheet, irrigation records, a weather station, satellite data or a site that has not yet been instrumented. The monitoring architecture should expand only where additional evidence is justified.
Define
Location, production system, monitoring objective, decision, timing and constraints.
Inventory
Existing sensors, data files, platforms, weather sources, irrigation records and remote-sensing options.
Design
Measurement variables, depths, zones, frequencies, telemetry, QA/QC and responsibilities.
Review
Data integration, validation, trend analysis, cross-source comparison and anomaly investigation.
Report
Clear findings, uncertainty, limitations, priorities and the next technical or operational questions.
Why RAUZ
An independent intelligence layer between agricultural measurements and operational decisions.
RAUZ is structured to work with existing field systems rather than forcing a farm, research team or operator into one sensor brand. The same platform logic used across RAUZ environmental and engineering monitoring is applied to agriculture: connect evidence, check quality, interpret change and communicate what the observations can actually support.
Vendor-neutral
Use suitable existing sensors, loggers, spreadsheets, APIs and remote-sensing products where the data can be accessed and traced.
Cross-source review
Compare soil, irrigation, meteorological, operational and spatial observations instead of interpreting each dataset in isolation.
Data QA/QC first
Investigate whether a trend is credible before turning it into a management narrative or automated alert.
Remote-first delivery
Data review, analytics, reporting and technical coordination can be delivered internationally while field tasks remain local where appropriate.
Traceable interpretation
Keep source data, transformations, exclusions, assumptions and limitations visible so that conclusions can be reviewed later.
Engineering + environmental discipline
Bring soil, water, weather, remote sensing and monitoring-system behaviour into a structured evidence review without pretending that monitoring replaces agronomy.
Official Sources
Public references used for this technical discussion.
The sources below are official public references used to frame monitoring variables, remote-sensing capability and agricultural-water context. They do not define a project-specific RAUZ specification.
- World Meteorological Organization — Agricultural Meteorology
Official application-area description and observation variables relevant to agricultural meteorology. - USDA Natural Resources Conservation Service — Soil Climate Analysis Network (SCAN)
Official example of multi-depth soil moisture/temperature monitoring combined with weather observations. - NASA — Soil Moisture Active Passive (SMAP)
Satellite mission for mapping soil moisture and freeze/thaw state. - NASA Goddard — NASA–USDA Global Soil Moisture Data
Official soil-moisture datasets integrating satellite observations into agricultural monitoring products. - European Space Agency — Sentinel-2 Plant Health
Official description of Sentinel-2 spectral information used for vegetation and crop monitoring. - European Commission Joint Research Centre — Monitoring Agricultural Resources (MARS)
Operational use of meteorological, geospatial and remote-sensing information for agricultural monitoring. - FAO — Agricultural Water Management
Official context on water use, irrigation and agricultural water management. - FAO — WaPOR Remote Sensing for Water Productivity
Open remotely sensed water-productivity information for agricultural monitoring. - FAO — AQUASTAT
Global information system for water resources and agricultural water management.
FAQs
Common questions before an agricultural monitoring discussion.
Does RAUZ require a new proprietary sensor network?
Can RAUZ monitor only soil moisture?
Can satellite data replace field sensors?
Can RAUZ support vineyards, orchards and greenhouses as well as field crops?
Does RAUZ provide agronomic prescriptions?
What information is useful for a first technical discussion?
Discuss Your Project
Tell us what you need the growing-environment data to explain.
A first discussion does not need a finished instrument list. Share the site, production system, soil and water context, existing measurements, the technical problem and the decision you need to support. RAUZ can then help identify whether the useful next step is monitoring design, data integration, QA/QC, anomaly diagnostics, remote-sensing comparison or recurring reporting.
RAUZ is the environmental intelligence and monitoring platform of Rauz Caucasus LLC, Tbilisi, Georgia, structured for international and remote-first technical delivery.