Automatic Rainfall Monitoring Station: Data for Drainage Assessment

An automatic rainfall monitoring station records precipitation at its location. For a drainage assessment, that record can help explain how a real storm loaded a system, but it is not automatically the design storm or a complete measure of catchment rainfall. Specify the observation interval, data quality and intended engineering use before choosing the gauge and logger.

Separate an observed storm from a design rainfall

An observed storm is a measured sequence at a particular place and time. Design rainfall is selected through an accepted engineering method for a stated duration and probability. A newly installed station does not establish a long-term frequency relationship merely because it provides a detailed record of one heavy event.

The NOAA precipitation-frequency FAQ explains comparing observed precipitation with corresponding frequency estimates and discusses the limits of using point estimates over watersheds. For projects elsewhere, use the applicable local rainfall guidance and design requirements. A U.S. frequency resource should not be presented as a universal design standard.

Specify which drainage question the station must answer

Keep rainfall depth, intensity and duration explicit

Rainfall depth is an amount in millimetres. Average intensity divides that amount by a stated duration, commonly expressed in mm/h. A gauge specification in mm/min describes a different unit, not a cumulative storage limit. Never label an intensity range as the maximum amount the station can record over an entire storm.

For illustration, 12 mm recorded over 15 minutes is an average intensity of 48 mm/h for that interval. It is not evidence that 48 mm fell during an hour, nor that the peak one-minute intensity was 48 mm/h. Preserve the original intervals so an engineer can derive the required duration without inventing detail absent from the record.

Choose a gauge whose limits match the expected event

The NiuBoL NBL-W-RS tipping-bucket rain gauge is one option for liquid-rainfall acquisition. The recorder must convert the selected output into correctly timed amounts. Output versions, acquisition inputs and power requirements should be matched in the quotation.

Retain enough time detail for the drainage response

A daily total can support daily water accounting but can hide a short intense burst. Select the logging method with the drainage analyst. Where tip timestamps are required, confirm that the logger actually records events at suitable precision rather than only storing a periodic cumulative counter.

With 0.2 mm increments, one tip assigned to a one-minute interval corresponds to 12 mm/h for that minute. This illustrates quantization of short-interval totals, not a constant measured rain rate during every second. Inter-tip calculations and fixed-interval averages have different behavior in light rain; identify which output the software provides.

Clock-hour totals may also split an intense period across two records. Preserve suitable underlying data when moving-window amounts are required. Changing a report heading from hourly rainfall to maximum 60-minute rainfall cannot recover information discarded by the acquisition schedule.

Compare rainfall and drainage response on a common clock

For an event investigation, align rain observations with water-level or pump records using their field observation times. Network upload delays must not shift the apparent storm sequence. Record level references and pump states independently; rainfall does not measure the pipe's available capacity or prove that a pump actually ran.

A single gauge may miss a localized burst affecting another part of a catchment. Review its position, nearby observations and available spatial rainfall information before diagnosing a drainage asset from a weak apparent response. Do not impose a universal station spacing without considering the terrain, storm variability and required analysis.

Protect the event record during inspection and testing

Mark calibration water and service-generated tips so they are not included as natural rainfall. Record the start and finish of cleaning, counter resets and any period when the collector was removed. Do not erase a whole day merely because part of it contains a test; preserve the valid portions with an identifiable qualification.

Before a critical observation season, check levelling, collector cleanliness, bucket operation and the complete counting path. Use the appropriate controlled delivery method for a gauge check. Pouring a known volume too quickly can create a different test condition from the specified intensity and does not establish performance across the measurement range.

Define the acquisition and export before ordering

For an RS485 Modbus RTU option, obtain the actual counter or rate registers, units, reset behavior and serial settings. For a switching-output gauge, check the logger's contact input and counting behavior. Wireless transmission belongs to the logger or gateway configuration; it is not implied by the rain gauge's electrical output.

Ask for an export example containing the required intervals, observation times, site identity and quality annotations. Confirm how missing periods and recovered records appear. A continuous line on a chart is not proof that rainfall was observed throughout a power interruption.

Rainfall Data for Drainage FAQ

Q1. Can one year's observations define a rare design storm?

Not on their own. Use the applicable accepted frequency information and engineering method. Local observations can support event investigation and longer-term analysis without replacing that design basis.

Q2. Does 0-4 mm/min mean the gauge stops after 4 mm of rain?

No. It is the specified intensity range. Cumulative amount is derived from repeated observations or counts, subject to the logger's counter and storage limits.

Q3. Can a 24-hour total identify a short drainage peak?

Not reliably. The same total can have different distributions. Retain the intervals needed to compare rainfall with the asset's response.

Q4. Should an outage be filled with zero rainfall?

No. Unobserved rainfall is different from a valid dry interval. Identify the gap and use any reconstruction only through an explicitly documented analytical method.

Q5. What should an engineer send with an enquiry?

Provide the catchment and gauge locations, expected rainfall conditions, required time resolution, existing inputs and export format. State whether the record is for operations, an event investigation or a design study.

Summary

An automatic rainfall monitoring station is useful for drainage assessment when depth, duration, timing and data quality remain clear. Select the NiuBoL gauge and acquisition configuration for the required record, then interpret it with spatial rainfall, asset observations and the applicable design method. A detailed local storm record is valuable without being labelled a complete drainage design.

NBL-W-RS-Rain-sensors-instruction-manual-V4.0.pdf

NBL-W-DRS-Double-Tipping-Bucket-Rain-Sensor-Instruction-Manual.pdf

NBL-W-ARS-Tipping-bucket-rain-gauge-instruction-manual.pdf