Agriculture & Controlled Environments

Multi-Span Greenhouse Humidity Control: Diagnose Across Connected Spans

Map humidity across greenhouse spans, diagnose condensation and local air delivery, then prepare dehumidifier inputs for actual operating conditions.

Written byYakeclimate Engineering TeamEngineering Team
Conceptual illustration of a multi-span greenhouse with crop rows, roof vents, circulation fans and a generic equipment area; not an actual Yakeclimate installation.

Humidity control in a multi-span greenhouse begins with a spatial question: where is moisture accumulating, when does it happen, and what air or water path connects that location to the rest of the house? A control sensor in one aisle cannot prove that a perimeter bay, a central span, the leeward crop canopy and the air below a roof gutter share the same condition. Map those places and trend them at the same time. Then decide whether the problem is a water source, a cold surface, poor air delivery or an unmet whole-house removal duty.

This guide is for operators and project engineers investigating a connected-span house or preparing a dehumidification equipment inquiry. The crop specialist sets the crop limits. The greenhouse climate designer owns vents, screens, heating and whole-house air paths. An equipment manufacturer can review the performance and interfaces of its proposed unit against the conditions supplied. None of those roles can be replaced by a single relative-humidity reading or a nominal liters-per-day label.

Why connected spans need their own humidity map

Connected roofs create a broad volume with repeated ridges and gutters. Edge spans face the perimeter; interior spans have different roof and air routes; windward and leeward openings can operate under different pressures. Crop height, row density, thermal screens and circulation equipment can further change what a control sensor represents. A field study in an eight-span house observed spatial temperature and RH differences among positions and crop-height conditions, and separately compared ventilation arrangements. Those observations are a reason to map the actual house, not a numerical correction to apply elsewhere.

A local RH difference is also not automatically a difference in water-vapor content. Cooler air can have a higher RH even when it holds the same amount of vapor. For condensation, compare the temperature of the relevant leaf, gutter, cover or frame with the dew point of nearby air at the time of the event. When the investigation needs an absolute-moisture comparison, calculate it from synchronized temperature, RH and the appropriate pressure rather than comparing RH readings alone. The greenhouse humidity-control guide explains the wider water-balance and control-route decision.

Draw the house before placing temporary measurements

Start with a plan that names each span and compartment. Mark roof and side vents, gutters and drains, screens and their edges, heating, circulation fans, supply and return paths, irrigation zones, doors and the location of the control sensor. Add crop type and canopy height by zone. Note whether the greenhouse is operating as an open, closed or mixed-air arrangement during the event; do not infer that from a control label alone.

Use the plan to assign each measurement a question. A diagnostic grid can be small at first and expanded where observations disagree. The table is a starting set of roles, not a universal sensor count or spacing rule.

Location to compareWhat it can revealRecord alongside it
Windward or perimeter crop spanA boundary or vent influence on crop-level airOutdoor state, wind, vent position and nearby heating
Interior crop spanThe condition away from the perimeter and any weak delivery pathCanopy height, screen state and circulation status
Leeward or reported wet spanWhether the reported problem is local and persistentMatching crop-level temperature/RH and visible wetting
Above and below a relevant screen; near a roof or gutter surfaceWhether vapor is redistributed, discharged or condensed at a cold surfaceScreen movement, roof vent, surface temperature and drip path
Equipment inlet, outlet and a remote crop pointWhether unit operation and delivered air correspond to the crop responseActual run feedback, entering/leaving air and condensate or exhaust

Where crop heights differ, measure at the height that represents each crop decision. Add a second height when a canopy-to-roof or upper-to-lower contrast is part of the symptom. Protect instruments from direct sun, spray and a nearby heater or discharge. Keep instrument identity, location and calibration status with the record. The sensor-placement guide covers permanent control-point choice and temporary reference checks; it should inform the final grid.

Trend the event, not just the daily average

Align clocks before comparing data. Record the interval before, during and after the reported problem. Include outdoor temperature and moisture state, wind direction, irrigation and drainage events, roof and side vent positions, screen movement, heating, circulation and equipment run feedback. A command to open a vent or enable a dehumidifier is not proof of measured airflow or water removal.

Use paired observations: the same moment and comparable height in a wet span and a reference span; the same screen state when comparing below-screen air; the same weather and crop period when judging a control change. A whole-house average may conceal a short wetting event or a persistent local zone. Conversely, a one-minute peak at one point cannot establish a sustained whole-house load. The uneven crop humidity zones guide explains how to read those time and location differences without turning research observations into site targets.

For suspected roof condensation, record where water first appears and where it lands. Water on leaves can arrive from cover drips, irrigation, a leak or direct condensation. Inspect the gutter and drain route and compare the wet surface temperature with nearby-air dew point during the event. A dry surface after sunrise cannot resolve what happened before dawn. Cover drips that wet plants require attention even if a nearby aisle sensor looked acceptable.

Separate four common diagnoses

Work from the observed symptom to a testable hypothesis. Do not increase machine capacity until a local water or air-delivery fault has been checked.

Pattern in the synchronized recordNext evidence to seekDecision it does not yet justify
One span remains wetter while neighboring crop points recoverCompare supply, return and circulation paths, canopy obstruction, screen edges and actual vent behaviorA larger whole-house unit based on that RH gap alone
Roof or gutter drips after cooling or screen closureMeasure the local surface and nearby-air dew point; inspect drainage, leakage and drip pathCounting uncontrolled cover condensation as useful moisture removal
Wetting begins after irrigation or at a drainInspect application, leaks, standing water and discharge, then repeat the event recordTreating liquid-water repair as an equipment-sizing input
Several spans accumulate moisture during the same constrained periodEstimate water added and removed on one boundary and time basis; verify vent and existing-equipment operationSelecting a unit from floor area or a catalog rating alone
Controller reports acceptable RH but a crop span stays wetValidate sensor placement and compare synchronized crop, surface and controller conditionsChanging the controller offset merely to make displays agree

The table does not diagnose crop disease or set an acceptable RH. It makes the next measurement explicit. The crop specialist should interpret plant symptoms, and the greenhouse operator should inspect liquid-water faults before climate equipment is blamed.

Choose a control route that has a real water exit

Ventilation can export water vapor when the entering air and operating conditions make exchange useful. Compare indoor and outdoor absolute-moisture state, not outdoor RH alone. Verify which roof or side openings actually provide a route across the affected spans. Wind direction and screen position can change that route. Venting may also change crop temperature, heat demand and carbon-dioxide strategy. The greenhouse ventilation guide covers the general air-path check.

Heating can raise air and surface temperatures, lower RH at a given vapor content and protect a cold surface. It does not remove water by itself. Circulation can bring conditioned air to a stagnant crop zone and reduce local differences, but it is not outside-air exchange or water removal. Neither should be credited as a dehumidifier without a documented exit path.

Mechanical dehumidification can address a defined remaining water-removal duty during a period when ventilation is constrained or insufficient. The proposal must state actual entering-air temperature and humidity, expected hourly removal, runtime limits, heat added or rejected, the documented moisture-discharge path, electrical requirements and how dry air reaches the wet spans. If a unit sits beside one aisle but cannot serve the remote canopy, its catalog capacity is not proof of whole-house control. A thermal screen can split the air volume, so a proposed supply path must be checked with the screen in the state used during the difficult period. The thermal-screen humidity guide develops that boundary in detail.

These routes may operate together under the greenhouse designer's sequence. A study of a modeled three-span house examines nighttime cover condensation and roof ventilation, but its geometry and climate are not a universal control program. Trial one approved operating change at a time within crop and safety limits, and keep the before-and-after crop-zone and water-removal record.

What to send before an equipment proposal

Provide the greenhouse plan with span labels, crops and heights, roof/gutter and screen arrangement, air and water paths, and available unit, duct, drain and service space. Include synchronized risk-period trends from the reference and affected spans, outdoor air and wind conditions, vent and screen states, irrigation, heating, circulation and existing equipment request and run status. State who owns the crop target and allowed excursions.

For the proposed equipment, ask for capacity at the relevant inlet states and time basis, not only at a rating point. Ask how supply and return air will reach each affected span; how heat and removed moisture will leave under the proposed process; what power and protection are required; how alarms and control interlocks will be handled; and where serviceable components can be reached. If water load, airflow or entering-air conditions are unknown, mark the proposal provisional. The separate greenhouse project-design data guide provides the broader sizing-data checklist.

An acceptance plan should identify the actual operating mode and observation window. Trend equipment inlet and outlet state, verified running and evidence of moisture removal under the proposed process, plus representative crop points in the affected and reference spans. Check that the observed crop conditions meet the crop team's agreed criteria and that the moisture-discharge route, heat path, alarms and service access work as specified. A unit operating or a controller RH number alone does not demonstrate that a remote span received the intended condition.

FAQ

Frequently asked questions

Is one humidity sensor enough for a multi-span greenhouse?

One sensor can control a defined point, but it cannot by itself establish the condition across every span or canopy height. Use temporary comparison points where different vents, screens, crops or symptoms may create a separate decision. Validate the permanent control point against the observed risk period.

Why is the leeward span wetter when the controller looks normal?

Possible explanations include a cooler local surface, a different wind and vent path, dense crop resistance or weak supply-air delivery. Compare simultaneous local temperature and moisture, vent and fan state, crop height and surface evidence before assigning a cause. The controller point may simply represent another part of the house.

Does a roof gutter drip mean that dehumidifier capacity is too small?

No. First identify whether the water came from cover condensation, a leak or another liquid source. If condensation is suspected, compare the gutter or cover temperature with nearby-air dew point at the event and inspect the drainage route. A whole-house removal shortfall is a separate finding that needs a water-balance and equipment-operation record.

Can circulation fans replace dehumidification across several spans?

Fans move air inside the house and may help a dry-air supply reach the crop. They do not export water vapor unless another defined route removes it. Verify the crop response and the actual removal route rather than counting fan operation as moisture removed.

Should we open every roof vent to lower humidity?

There is no universal vent sequence. Compare indoor and outdoor moisture state, wind, crop temperature, carbon-dioxide and heating constraints, and the actual path through the affected spans. A vent command is not measured exchange. The greenhouse climate designer should approve and test the sequence.

How many dehumidifiers does a multi-span house need?

Span count and floor area are not enough to answer. The decision needs period-specific water load, actual inlet conditions, unit performance, supply/return distribution, heat and drain interfaces, and the crop-zone result required in each affected span. Request a project-specific equipment review after those inputs are available.

Turn the map into a reviewable equipment discussion

A useful handoff names the wet span, the event window, the water source or unresolved hypothesis, the available control routes and the evidence still missing. Yakeclimate designs and manufactures industrial dehumidification equipment for complex climate applications, with a focus on agriculture and energy projects. For a project-specific equipment discussion, share the annotated span plan and synchronized operating record. The greenhouse designer and crop team remain responsible for the complete climate strategy and crop criteria.

About the author

Yakeclimate Engineering Team

Engineering Team

Yakeclimate technical articles are prepared by the engineering team using inputs from product development, application review, manufacturing, testing, and project support.

View author profile

Continue reading

More on agriculture & controlled environments

Project evidence

Related case studies

Project support

Ready to turn the operating conditions into a project brief?

Use the project-input checklist to help our team review the environment, moisture load, interfaces, installation limits, and validation needs from one consistent brief.
Send project requirements