Designing Urban Stormwater Systems for Aerosol‑Driven Rainfall Variability

Urban and industrial aerosols can shift cloud microphysics so that light-to-moderate warm‑rain is suppressed or delayed while convective extremes remain possible; this creates greater uncertainty in runoff timing and volumes. Planners should treat aerosol effects as an additional source of hydrometeorological variability and adjust design, operation, and emergency plans accordingly.

1. Adopt a risk‑based sizing approach

Use scenario ensembles rather than a single design storm: combine historical rainfall statistics with plausible shifts in light‑rain frequency and changes in storm intensity timing. For capacity and detention sizing, prioritize performance under a small set of defensible scenarios (e.g., baseline, +20% extreme-intensity, and -30% light‑rain frequency) and design to maintain target service levels (e.g., no flooding for 2‑yr event; managed overflow for 10‑yr event).

2. Emphasize adaptive, staged solutions

Prefer modular or upgradable systems (e.g., staged detention basins, modular underground tanks, or upsizable outfalls) so infrastructure can be adjusted as local precipitation signals change. Build monitoring triggers (see section 5) that prompt incremental upgrades rather than overbuilding up front.

3. Size green infrastructure for dual uncertainty

Design GI (rain gardens, bioswales, permeable pavements, green roofs) to both capture episodic intense bursts and store smaller cumulative rainfall when drizzle returns. Use deeper media, bypass overflow paths, and multiply distributed GI elements across catchments to smooth variability. For retention-based GI, target a range (e.g., 10–30 mm per event) rather than a single depth so some benefit remains if light‑rain frequency falls.

4. Revisit conveyance and CSO management

Because delayed drizzle can reduce baseflow but not eliminate convective extremes, evaluate combined sewer overflow systems for both reduced baseline flushing and episodic peak loads. Increase temporary storage, add real‑time control gates where feasible, and model both reduced low‑intensity runoff and concentrated peak flows in hydraulic simulations.

5. Implement enhanced monitoring and decision triggers

Install local rainfall and aerosol monitoring (fog/PM sensors, collocated rain gauges) and integrate with operational models. Define trigger thresholds (e.g., sustained reductions in light‑rain days over 3–5 years or systematic increases in short‑duration extreme intensities) that activate predefined responses: increase pump runtime, deploy temporary storage, or schedule infrastructure upgrades.

6. Update stormwater design standards and safety factors

Where codes allow, apply an additional uncertainty factor to peak runoff and retention targets (e.g., +10–25% capacity margin) when local aerosol trends are uncertain. Document assumptions so future planners can revise margins as observations accumulate.

7. Use nature‑based co‑benefits and equity considerations

Prioritize GI in underserved neighborhoods to reduce flood risk and deliver heat‑island and air‑quality co‑benefits. Co‑locate storage with community amenities (parks, schoolyards) to increase public value while providing flexible detention during extreme events.

8. Incorporate aerosols into modelling workflows

When collaborating with meteorologists, ask for sensitivity runs that alter warm‑rain autoconversion rates or CCN load analogues to reflect higher aerosol concentrations; translate those outputs into catchment runoff scenarios. If such meteorological runs are unavailable, emulate effects by adjusting rainfall frequency‑intensity distributions used in runoff models (e.g., fewer low‑intensity events, modestly higher short‑duration peaks).

9. Plan emergency operations around timing uncertainty

Because aerosol effects can delay precipitation onset but not eliminate extremes, update emergency staging (pump deployment, temporary barriers) to respond to observational triggers rather than fixed schedules; run exercises assuming delayed but intense storms.

10. Document, monitor, and revise

Record design choices, assumed aerosol‑rainfall scenarios, monitoring data, and upgrades. Reassess every 3–5 years or after anomalous seasons to refine scenarios and de‑risk future investments.

Applying these steps lets cities manage stormwater under the added uncertainty from aerosol–cloud interactions while avoiding wholesale overbuilding and preserving flexibility as scientific understanding improves.

Sources

a Latviešu valoda