ApiaryActiveLive
Try: pause · settings · learn · wipe
← Community / Reading Room
AD
nature · 25 min read

A Dry Rain Gauge and a Dripping Redwood Can Both Be Right

By Austin Little

By Austin Little

AI disclosure: Drafted with AI assistance for Apiary. The trail and gauge examples are hypothetical. The research studies cited below are real; their sites and methods limit what the results establish.

Two people can come back from the same coastal headland with contradictory weather stories. One stood in an open clearing long enough to decide that it hadn’t rained. The other waited beside a redwood and heard drops hard enough to rattle a leaf. Neither person has to be wrong. A forest canopy can intercept fine droplets moving through it, then send larger drops down after the water has accumulated on vegetation. A familiar sound at the trail level need not mean that measurable rain was falling in the open at the same moment. National Park Service: Redwood National and State Parks, about the trees

The easy story is that a redwood makes its own rain. The useful story starts a few steps earlier: where did the water come from, what did it touch, what did we actually measure, and what happened after the drop left the branch? Those questions separate a wet hat from useful evidence. They also explain why scientists can agree that fog contributes water to redwood forests while studying quite different pieces of the process.

Fog droplets don’t need to fall like rain to meet a tree

Fog and rain both involve water droplets, but the kind of encounter matters. In a fog layer near the ground, air can carry tiny droplets along with it. A leaf or twig gets in the way. On a foggy coast, a canopy presents a large surface that can intercept part of that moving water. Individual droplets can merge on the surface, and accumulated water can stay there for a time, move along the plant or come down in drops. The sound you hear is the last part of that sequence, not a direct recording of how the water arrived. Limm and colleagues: foliar water uptake in redwood forest plants

Think of a canopy partly as a collection surface and partly as a complicated roof. A simple roof can deliver water to a few drip lines. In a crown there are many surfaces, many possible paths, and gaps where water can pass without touching a branch. Some places below it can be wetter than others within a short walk. There may be a striking wet stripe under the end of one branch with a relatively dry patch nearby. You don’t need a precise explanation for each stripe to notice that it is spatially patchy.

The comparison to a roof has limits. Leaves are living tissue and branches do not have a simple predictable slope. A living canopy can interact with water before it is released, and the rest can move in ways a single catch would miss. Also, not every wetness event starts with droplets striking it. Dew can form when a surface cools enough for water vapor to condense on it. A canopy might also still be shedding water from earlier rain. A large drop under one branch is evidence of water falling there, not a determined meteorological origin.

That is why a photograph of beads on a twig tells you less than a good sequence of photographs and notes. A camera might record the wet surface perfectly and give you no way to tell when it got wet. If the photographer also knows when the ground was dry, where the mist was and whether water was falling away from the crown, the scene becomes easier to interpret. Evidence of conditions during the whole interval can matter more than the resolution of the final image.

Separate the entry points before comparing the amounts

Forest hydrology has names for several routes that are easy to confuse. Throughfall is water that reaches the ground through the canopy, whether it passes through gaps or drops from vegetation. Stemflow travels down stems or trunks. The water that stands on leaves or evaporates from a wet surface does not appear as a drop in a container under the crown; neither does water that runs down the exterior of the trunk if the collector is farther out. A total near the ground has a boundary the observer chose, whether or not the label explains it.

A rainfall study at the Caspar Creek Experimental Watersheds in northwest California compared open precipitation, throughfall and stemflow in a redwood and Douglas-fir forest. Repeated measurements helped researchers ask about interception and timing rather than treating the forest floor as one uniform gauge. The study is about rainfall. It helps explain the measurement types, but it isn’t a source for assuming that a fog event has the same proportions of throughfall and stemflow. Caspar Creek rainfall interception study

In a different part of coastal California, an investigation in a Sonoma County coast redwood forest looked at fog and rain as separate inputs and measured what the water carried as well as where it went. The research report is useful because there is more than one way a water supply matters to an ecosystem. It could make a leaf wet. It could add water reaching the soil. It could carry dissolved material whose concentrations change as the water passes through the canopy or moves in the soil. Those are separate observations, not three independent additions to a volume total. US Forest Service research record: fog and soil weathering as sources of nutrients

If you are explaining results to someone who lives under a tree, it helps to describe where the collection happened before saying which place was “wetter.” Wet under a branch can mean one high reading in one collector. Wet at the soil level can mean a probe recorded moisture at a particular depth. Wet in the canopy can mean leaves stayed wet for hours. A distance of a few meters or a different instrument can change the question. More decimal places don’t settle that difference.

A rainfall event can look like the reverse case

Suppose light rain continues long enough to leave water across an open parking lot. Under a certain crown the ground remains comparatively dry, at least at first. That does not disprove fog drip. The situation is different: rain that could otherwise reach the ground is being intercepted, and the canopy can hold or redirect some of it. In another event, a tree collects moving fog droplets that are not easily detected as open rainfall. The same plant can participate in both effects under different conditions.

The timing can make the difference look bigger than it is. When an event begins, water may go toward wetting surfaces rather than falling through. When the sky clears, already wet foliage can continue to drip. If you compare the open and sheltered spots only after the last shower, one may appear wetter for reasons that started much earlier. A fixed beginning and ending window gives the comparison a meaning. A second note after the event helps distinguish water still arriving from water stored and then released.

Here is an invented example. On Monday a visitor sees a soaked path below a tree and dry gravel in a clearing. In the note app they write “canopy creates rain.” On Tuesday another observer finds dry gravel under a tree during a drizzle, with water on an adjacent wide path, and writes “canopies block rain.” The two statements sound like a disagreement only because both summaries strip out initial conditions. Monday’s record would be improved by documenting that the canopy was dripping while the open spot had no observed rainfall, and writing down whether there was fog or recent rain. Tuesday’s would be improved by specifying how long drizzle lasted and where the open and sheltered observations were made. Either data row may still leave the cause uncertain, but it won’t claim more agreement or disagreement than the notebook actually contains.

A tree can benefit before much water reaches the ground

It is tempting to track fog only by the amount of water that makes it out the bottom of a canopy. Plant researchers have found another piece: direct water uptake through leaf surfaces in some redwood forest plants. Leaf wetness can also reduce loss of water under some conditions. Direct uptake and reduced loss both affect water status, but they are not the same process. A little moisture retained on foliage may matter even when you cannot see a drip reach the path. Limm and colleagues: experiments on foliar uptake and leaf wetting

That changes the ordinary picture of a tree getting a drink. If we follow one route, intercepted water falls down, wets the forest floor and may reach roots. If we follow another, at least some of the water crosses into leaves directly. Researchers need ways to distinguish these possibilities; they cannot simply look at a plant that appears less dry. Controlled comparisons and the composition of water can supply that evidence. The fact that tissue water can contain a fog contribution does not by itself assign every molecule to one route.

The distinction is important when a summary gives a numerical estimate of the role of fog. That might mean a share of physically collected water, a share of water in some plant material at a given site, or a statistical comparison of fog occurrence through time. All could legitimately be described as information about fog, but their quantities cannot be substituted for one another. Dawson: ecosystem inputs and use of fog water by plants · Johnstone and Dawson: regional summer fog analysis

The other limit is that forests and plant species aren’t identical. A result for foliage from one species does not prove every understory plant responds the same way. Some habitats may depend on leaf wetting while others get more water that reaches the soil. A useful headline says which outcome was measured or avoids borrowing a numeric result beyond its study. “Forest plants can make use of coastal fog” is broader and safer than “this trail’s trees get a fixed fraction of all their water from fog.”

Listen and watch without running a bogus survey

A visitor doesn’t need equipment to notice the effect of a canopy. On a wet visit, compare what you can see and hear in an open area and below foliage, from places you may stand safely. Note the time, the broad weather and whether drops seem to fall from above a particular branch. Do not enter closed areas, leave objects in a park or climb for a better photograph. Check the park’s visitor guidance before the outing and keep the visit ordinary rather than turning it into a field trial.

A clean note might look like this: “At 9:15, mist visible above the clearing; no falling drops observed there during two minutes; audible drops near the trail edge under trees; earlier weather unknown.” A photo of the open space and a photo of the sheltered space can illustrate where the observations were made. The phrase “earlier weather unknown” will annoy anyone who wants the scene to settle everything. It is a useful reminder that a final snapshot cannot rule out water deposited before you arrived.

If you are taking observations on private property with permission and are comparing two identical collectors, put your definition in the notebook. Decide which places you are comparing and start and read both at the same times. Record whether they were near splashing surfaces, overhangs or a sprinkler. If one collected no measurable water, keep “not measurable at this resolution” distinct from “zero water was present.” These observations can compare what fell into each opening over an interval. They do not measure all water in fog blowing horizontally, all moisture collected by the tree or all water absorbed by the soil.

Collector placement is part of what the result means. A container at a drip point is a good way to observe that drip point. It is a bad stand-in for the entire forest floor if chosen because you already knew it would catch a lot. If the question changes, the design should change too. A project about extremes might deliberately visit known wet spots. A project about average conditions would need a sampling design that does not pick those spots simply because they were easy to hear. The same observation can be good evidence for one question and poor evidence for another.

The fog that moves through and the fog you can see

A ridge, a stand of trees and a roadway can offer different views of the same layer. One observer may say the coastline was foggy because a bank of fog was visible offshore. Another may say there was no fog at the site because the bank never reached the trees while they were watching. Decide whether the note refers to visible fog somewhere in the scene or actual immersion of the canopy. For a question about droplets coming in contact with leaves, the second description is closer to the mechanism. The first can still give good weather context.

Distance matters in another way when you look up an official rain measurement. A station report can be valuable confirmation about a particular instrument at a particular location. The ruling-out power of that report decreases when its site and exposure are quite different from the grove. Use the station as a reference rather than replacing your site note with its number. If the rain station is dry and you documented a wet canopy, you have two useful records. Identifying what happened in between them is an inference that improves when additional records agree.

Keep the original observation as the first line of the story

Climate records of coastal fog, rain gauges, wetness sensors, collectors below trees and leaf experiments all provide useful windows. They do not look through the same wall. For example, a paper analyzing regional fog frequency has a different footprint from a photo sequence in one grove. The regional series can show relationships in the study area without providing a log of the actual drops that hit your sleeve. A close-up helps a person understand the delivery point without measuring a climate trend. The strongest explanation can use both kinds of information without asking either to stand in for the other. Johnstone and Dawson: climatic context of summer fog

Imagine coming back from the trail with a short video. You see beads at a leaf tip, hear a faint tap and pan to the open stretch where nothing obvious is falling. It is a good piece of reporting if the caption says what the frame gives the viewer: visible canopy droplets, intermittent sound and no obvious rain in the second view. Then the story can introduce fog interception as a plausible mechanism, compare it with other explanations and link to the forest research. The note and the explanation support each other better when they are not presented as the same thing.

The next person who visits may find no fog, a soaking shower, or light mist on leaves without any heavy drip. They have not failed to confirm the forest’s existence. They have a different event, and a better starting point for describing it. That is why the seemingly conflicting reports make such a good introduction to the topic. A dry gauge is a result about a known opening and interval. A drip is a result about a point beneath a canopy. Put their settings back into the sentence and they can both be right.

Start a three-clock record instead of a weather diary

A forest-water story can run on three clocks. The first is the timing of incoming conditions, such as the appearance or breakup of cloud at the observer's vantage point. The second is the timing of release from a wet canopy. Dips, leaves, and branch junctions need not empty as soon as there is a clearing in the sky. The third is the timing of the evidence being consulted: when a weather station began a reporting interval, when a video clip was made, or which period a research study represented. A timeline that keeps only a single event time may line up things that were never synchronized.

Use an ordinary visitor note as a starting unit. Record when and where the scene was readable, what was directly visible in the open area, and what could be heard or seen under overhead cover. If the sound continued when the lookout showed a clear opening, that is a useful ordering, not a cause by itself. A clearing in one direction while low cloud still interrupts the ridge in the other is not the same as an established end to fog at the forest patch. Much of this information can be written without identifying droplets as any particular source. “At noon, from the designated viewpoint, leaves above the platform looked wet and regular drops made a tapping sound” can be an excellent initial sentence.

Establish an interval for uncertainty. If you arrived at 11:25 to find a canopy dripping and did not have a direct view of conditions before arrival, report that the first recorded scene already had dripping. Do not date the onset to the minute at which you entered the path. If clouds were readable on arrival and no longer obvious on the way back, you can bracket that visual change with times. If those pictures were made looking in opposite directions, there is a further change in geometry to record. A notebook that makes these distinctions allows a genuinely informative sequence even when your visit begins or ends in the middle of events you might like to explain.

In a fictional lookout example, a visitor notes dripping at 09:10 under a dense crown, a dry-looking walking surface away from the crown at 09:15, and a temporarily bright sky at 09:25. At 10:00 the drip is no longer audible from the same spot, but traffic became louder while the visitor was away. The last row should read “not heard under these changed listening conditions,” not “canopy empty.” Comparing the visible leaf tips where possible might strengthen the result. So would a fully analogous period at a later date. The value is in knowing when the quiet record is a measurement and when it is simply a missing view.

Draw the routes water could take before assigning a source

Make a simple site sketch containing four locations: exposed sky, outer crown, trunk or large branches, and ground beneath the crown. From a safe path, a visitor can label which parts were actually visible and which were in an opaque area. Draw possible routes in a different style from observed ones. A route from a wet tip to a visible drop is an observation if you saw the separation and fall. A route from small atmospheric droplets to the surface of that exact leaf is a plausible process supported in general by research, not something most visitors have watched unfold. The tree can remain a compelling piece of the story even when a line in the sketch needs a dashed rather than a solid arrow.

The National Park Service's redwood interpretation is a way into this aerial collection idea. It gives a regional, ecological explanation and the idea of water gathering on canopy features. It is not a calibration for a particular day under a particular tree. A diagram based on that explanation can make the underlying process intelligible next to a source photo; if you caption every arrow in the diagram as what happened in the photo, the diagram's role has changed unnoticed. Keep explanation and evidence in separate visual layers.

Likewise, water on a trunk may not follow the particular route that is obvious in a cropped image. A long shiny streak can be a surface receiving water from above, a spot where drops repeatedly hit, or something lit differently from the adjacent bark. Do not assume the atmospheric source from the wet pattern. If a short video from the open path shows visibly moving water over a known bark surface, that supports a statement about the local route in view. It still does not establish the history of every drop up the tree. No collection or marking of the bark is needed to keep these observations small and honest.

Think from the opposite direction too. A drop hitting a gravel path can bounce into fine spray, leaving the path visibly wet away from the vertical point it struck. A breeze may also drift falling drops away from the area directly below their release. The neat outline a canopy draws overhead does not give a visitor an exact map of every point where water landed. Conversely, wet soil may be easier to detect than wet gravel under particular lighting even when the place itself is different. If you map damp-looking patches, name the surface and the fact that appearance was the method; do not generalize a subtle dark line into a measured delivery boundary.

Treat a distant gauge as a neighbor, not an eyewitness

A public station record can be an excellent companion to a forest visit. First ask what it reports, where the instrument is, what period the summary covers and how those data were recorded. Exposure to wind and the position of an instrument relative to terrain and vegetation matter to interpretation. An exposed gauge designed for rainfall answers a different question from the observation of water dropping along a forest path. Even two instruments of the same general kind at different locations need not record the same weather. The station contributes context, not a ready-made attribution for moisture you saw at another location.

A common mismatch puts a short field record next to a daily station table. The “day” may be defined by the provider in its own way and may not begin when your notebook day begins. Returning to the fictional lookout, imagine the field notebook says “dripping near morning arrival.” The station table is labeled with a calendar date and reports no measurable rain. If you have not checked the table's sampling and reporting period, you do not yet know even the exact temporal comparison. If you have checked it, the correct narrow synthesis still has two sites and measures: “The station recorded no measurable rainfall during its stated period; dripping was visible at the lookout in the observed morning interval.” Whether both indicate an event of a particular origin at the tree is a second question.

Missing and zero records deserve the same care. If a provider has an instrument outage, an omitted reading or a source whose export encodes missing entries as blanks, don't treat the missing record as “no rain.” If the data indicate a trace or a report below a usable threshold, keep the provider's terms and consult its documentation rather than converting it to a crisp binary. A record that reads zero at a precise reporting scale can be completely trustworthy within that scale and still have little power to explain a nearby tree's dripping. Scientific credibility involves recognizing what valid measurements cannot do, not treating incompatible observations as a contest somebody has to lose.

If the visual conditions are especially variable, store the date and provenance of the copy you consulted. A later quality-control revision or a corrected station map should not force you to reconstruct which file informed the original report. Keeping the file name or an accession and an exact date range is enough for most public-history or school applications. Preserve units as given and resist stitching multiple stations' measurements into one local time series without labeling why. A regional weather story can use several contextual records; a location-specific inference does not become stronger merely because it has more numbers in its footnotes.

A comparison exercise with competing causal stories

Set out three fictional cards for three classroom teams. Team one sees low cloud in the opening, notices shining branch tips, and records dripping. Team two visits after known rain elsewhere nearby, sees clear sky and persistent drops. Team three sees cloud hugging an adjacent ridge but notes no visible drips from the chosen safety rail. Ask all three to write exactly one observation and one plausible route that remains unverified. The first case is consistent with canopy interaction with fog, without excluding earlier rain or proving a water flux. The second is consistent with release of stored water, without establishing its atmospheric source at the site. The third is a non-detection of recognizable dripping from one view while cloud was visible elsewhere. It is not proof that no canopy intercepted any water.

Now add a hypothetical new piece of evidence for each team. Team one gets two additional scenes from before and after the interval, but both come from different ridges. Team two learns that the station's gauge and the scene are on opposite sides of a headland. Team three adds a short clip from the same vantage point in which a few drops are visible only when backlit. Ask what conclusions really improve. The wider scenes add landscape context but don't automatically ensure local ordering. The station location weakens any undocumented equivalence between measured and observed weather. The clip resolves a very local detection issue and changes one observation; it does not imply that the earlier overall site was wet or dry. A good review celebrates these appropriately small changes instead of demanding a conclusion that settles every causal pathway.

Another way to teach the distinction is to require one counterexample to any catchy line. “The rain gauge was dry, so the tree must have made rain from fog” could be challenged by water previously caught in the canopy or a station that didn't cover the location. “The sun came out, so the dripping stopped” could be challenged by storage and timing. “This fog did not make the trail wet” might mistake a dry-looking surface for absent water. Counterexamples need not be presented as equally likely alternatives in a real event. They expose hidden premises in the proposed wording. The exercise also shows why often the strongest replacement is not “impossible to know” but a narrower affirmative description of what happened in the available view.

One useful deliverable is a two-row evidence table. The observed row holds time, position, and visible or audible material. The interpretation row holds the explanatory source, what method supports it, and the part of the local scene it cannot settle. The two rows can be shared with different audiences without sacrificing accuracy. For example, a parent preparing a story for a child can narrate how a crown can intercept droplets, while still marking the observer's photo as “dripping at this moment, source unknown.” Children can understand that a good explanation is a tool for asking better questions, not a responsibility to name each drop.

Be precise about which biological result a paper measured

The leaf-water study by Limm and colleagues helps explain why “the leaf was wet” and “the plant took up water through its foliage” are different observations. The difference matters in a public write-up. A researcher can deliberately compare plant responses under documented conditions. A scene of visibly wet surfaces does not tell you the tissue's water status, the quantity involved, or the corresponding route of water to the ground. When summarizing the paper, label measured responses under its design as such and separate the mechanism from what a park visitor saw through the rail.

Apply the same distinction to ecosystem context. Some studies link fog and site chemistry, with the Forest Service archive record on fog and soil weathering providing one deliberately scoped example. Soil and plant observations collected over a documented project are not predictions for every roadside stand. If you want to tell readers about different lines of evidence, compare the measured outcomes before comparing their magnitude. Water collected at a surface, changes in plant water relations, and materials associated with water inputs are not different versions of one simple “percent fog” statistic. Each comparison needs an explicit denominator and the conditions for interpretation.

If someone asks whether a photographed tree is thriving because of one wet morning, the honest response starts with the outcome they want to know. Short-term leaf appearance, season-long growth, condition following disturbance, and long-term recruitment need very different observations. A visitor can tell a vivid story about drip without scoring a health outcome. At a broader scale, regional fog records and site measurements can help readers understand why patterns demand attention without using an individual photograph as independent confirmation of a trend. Tie causal claims to their evidence source, then return to the local record with verbs of seeing and hearing.

End with a portable scene note and one next question

The final handoff can fit on a single slide or notebook page. Use a context image from a lawful established view, the most readable detailed view if you have one, and a compact timeline with observation and external-context rows. Preserve the exact length of any clip and note when it shows only an interval, not the start or end of the process. Cite authoritative explanations separately from weather receipts and label any simple site sketch as a diagram. A reader should be able to repeat the act of looking without repeating a misleading measurement or entering an unsafe area.

Ask a colleague to reconstruct the story while the narrative caption is hidden. Can they identify which water movement was visible? Can they tell where the instrument was relative to the stand? Does “fog present” name the location the observer could see, rather than a claim about the whole valley? If not, rewrite the short record before adding a strong explanatory sentence. This is the quickest route to a useful shared observation because you can defend its integrity without producing a professional survey or bringing anyone back to the forest to verify a transient event.

A repeat project can choose one unanswered question each time. Find whether the usual public view distinguishes releases from one branch tip and drops blowing across the scene. Try to record whether a nearby opening and a shaded viewpoint remain comparable over a short walk. Learn what time scale is represented by an accessible daily weather summary. These are practical tasks that improve understanding without experimenting on trees, measuring from protected soil, or adding any unapproved equipment. A tightly stated next question preserves an inviting view of the forest's complexity. The dripping tree remains as real as the careful words needed to tell its story.

Name which missing piece would change the headline

If a better source arrives later, identify the claim that it would actually strengthen. A confirmed observation of prior rainfall at the immediate site changes your interpretation of which sources fit a visible release, but it doesn't show which route an individual drop followed through branches. A measured observation of water reaching plant tissues can strengthen a mechanism explanation under its own conditions while leaving the amount of liquid pooled on the path unknown. Attach each update to the question it changes. That small editorial habit keeps a local story from claiming two discoveries for every new observation.

An overview title can stay engaging without becoming a scientific result. “Why the redwood dripped while a nearby street looked dry” names a comparison and invites explanation. “This tree made its own rain” converts an impression into a distinct, much larger physical claim. Keep the first version unless you can support the literal mechanism, including the dryness of the exposed comparison surface and local evidence about what reached the tree. A dated correction entry can revisit that wording if new evidence appears. Whether that happens or not, the original scene retains its value: it was observed under a specified view, for a specified interval, with limits a later reader can understand.

Sources and field references

Frequently asked
What is A Dry Rain Gauge and a Dripping Redwood Can Both Be Right about?
By Austin Little
What should you know about fog droplets don’t need to fall like rain to meet a tree?
Fog and rain both involve water droplets, but the kind of encounter matters. In a fog layer near the ground, air can carry tiny droplets along with it. A leaf or twig gets in the way. On a foggy coast, a canopy presents a large surface that can intercept part of that moving water. Individual droplets can merge on the…
What should you know about separate the entry points before comparing the amounts?
Forest hydrology has names for several routes that are easy to confuse. Throughfall is water that reaches the ground through the canopy, whether it passes through gaps or drops from vegetation. Stemflow travels down stems or trunks. The water that stands on leaves or evaporates from a wet surface does not appear as a…
What should you know about a rainfall event can look like the reverse case?
Suppose light rain continues long enough to leave water across an open parking lot. Under a certain crown the ground remains comparatively dry, at least at first. That does not disprove fog drip. The situation is different: rain that could otherwise reach the ground is being intercepted, and the canopy can hold or…
What should you know about a tree can benefit before much water reaches the ground?
It is tempting to track fog only by the amount of water that makes it out the bottom of a canopy. Plant researchers have found another piece: direct water uptake through leaf surfaces in some redwood forest plants. Leaf wetness can also reduce loss of water under some conditions. Direct uptake and reduced loss both…
References & sources
  1. Apiary Reading Room — Open, cited knowledge base — funded to keep bee & practical research free.
From the Apiary Reading Room. Opinion & editorial — not financial advice. We don't overclaim.
More from the Reading Room