Designing a repeatable temperature survey in intertidal tide pools

A temperature reading needs a habitat and a clock

A tide-pool reading is not simply “the coast’s water temperature.” A pool is partly isolated between floods, and its conditions can change as it warms, cools, mixes with incoming seawater or loses water through evaporation. Shore height affects how long a pool may remain isolated, while the time of low tide determines whether exposure overlaps with morning, afternoon or darkness. Measurements made at different points in that cycle can describe different parts of the pool’s daily range. A field study that monitored pools at several tidal elevations found that temperature extremes depended on both pool height and tidal timing; the daily maximum did not occur at the same clock time under every tide pattern. [1]

The first design choice is therefore the question. “How hot does this one pool become during daytime low tides?” calls for repeated observations through the warming period. “Do pools at different shore heights have different temperature ranges?” requires several pools in each defined height band and comparable monitoring windows. Neither question is answered well by a handful of readings taken whenever access happens to be convenient.

Define pools before comparing them

Give each pool a stable identifier and record a location another observer can find. Note its position on the shore, a consistent elevation reference if available, and basic dimensions or a simple sketch. Record the conditions that help explain contrasts: water depth at the sensor, whether the pool is shaded or sunlit, its exposure to waves, and whether fresh water enters it. These details are not decorative metadata. They help separate a difference associated with shore position from one associated with pool shape, shade or water volume.

Choose replicate pools rather than treating multiple readings from one pool as independent examples of a whole shore. A sensor recording every 20 minutes for two weeks gives a detailed time series for that pool; it does not turn that one pool into many independent pools. For a comparison, select several pools within each group and preserve the pool identity in the data. If access or equipment limits the sample, describe it as a case study rather than a representative survey.

Place the sensor to answer the intended question

Secure a waterproof logger so that it stays in the intended water layer and does not rest against a sun-heated rock unless substrate temperature is the question. Keep the position, depth and mounting approach consistent across pools. Before deployment, check the sensor against a known reference or compare instruments together under stable conditions; record the instrument, stated accuracy, interval, clock setting and any calibration or correction. A missing reading or a clock that drifts can matter when a short heat peak is the signal of interest.

One sensor can be adequate when the pool is well mixed at the scale of interest, but that should be a tested assumption. In a tide-pool study of sculpin thermal history, investigators first checked spatial temperature variation within pools; their preliminary observations found less than 1°C of variation, which supported their choice of one logger per pool for that particular question and equipment. They then recorded at 20-minute intervals for 16–18 days in most pools. That is a useful design example, not a universal guarantee that every pool has no meaningful warm or cool pockets. [2]

Match readings to tidal state and sampling interval

For continuous loggers in the intertidal zone, record local time and connect the series to a tide prediction or water-level record for the site. The National Park Service rocky-intertidal protocol uses tide information to distinguish readings likely taken while submerged from readings taken while exposed, because a sensor alternates between water and air as the tide rises and falls. Pool monitoring asks a related but different question: the water may remain in the pool at low tide, yet still experience a long interval without exchange. Keep those categories separate instead of labeling every low-tide reading as air temperature or every logged value as seawater. [3]

Choose a sampling interval based on the event you hope to resolve. Hourly sampling can summarize a broad seasonal pattern, while shorter intervals are more likely to capture a brief afternoon maximum or the rapid change as a pool is flooded. More frequent measurements create larger files and can shorten battery life, so the interval is a tradeoff between temporal detail and practical deployment duration. State the interval and the reason for it.

Summarize the record without overstating it

Keep the raw series, flag gaps and sensor failures, and calculate summaries only for a stated window. Useful summaries might include the observed minimum and maximum, daily range, or the highest value during a defined low-tide period. For a simple hypothetical example, suppose one logger records 12°C before sunrise and 20°C in mid-afternoon during a daytime low tide. The observed range is 8°C for that pool and day. It is not an 8°C range for the entire shore, nor proof that sunlight alone caused the increase: pool depth, cloud cover, water exchange and instrument position also matter.

Compare like with like: same season, comparable tide phase, consistent depth and matching interval. If two pools differ, report both the measured contrast and plausible reasons that remain unresolved. Avoid converting a local maximum directly into a biological threshold or a climate trend. The 1986 pool study and later tide-pool deployments show why timing and habitat context matter, but their places, species, equipment and sampling designs do not supply a universal cutoff. A careful survey is valuable precisely because it states where and when its evidence applies.

Sources & further reading

Have a correction or a source to suggest? Send a note →