Philippine Tropical Hydrology and Design Storm Workflow

Learning Objectives

  • Explain why tropical cyclone, monsoon, convective, and orographic rainfall require careful spatial and temporal treatment in Philippine hydrology.
  • Build a defensible design-storm workflow from approved rainfall/IDF information.
  • Delineate watersheds conceptually using DEM terrain processing and verify drainage topology.
  • Connect rainfall losses, runoff transformation, routing, and frequency analysis into one modeling chain.
  • Distinguish event-based rainfall-runoff simulation from statistical flood-frequency estimation.
  • Apply urban-drainage screening while preserving hydrograph, storage, tailwater, and downstream-capacity limitations.
  • Document data source, period of record, return period, climate assumptions, and uncertainty before issuing design values.

Philippine Data Basis

Use project-approved and authority-accepted Philippine rainfall, IDF, river, topographic, and hazard data. This lesson teaches workflow and checks; it does not invent a universal national IDF equation. Local rainfall intensity, return period, climate allowance, and drainage criteria must come from the governing project/agency basis.

Tropical Rainfall Context

Philippine catchments may experience intense convective storms, prolonged monsoon rainfall, tropical-cyclone rainbands, and strong orographic enhancement over mountainous terrain. A single point gauge can therefore be unrepresentative of a basin, especially when elevation and storm track vary across the watershed.

Design Storm Is a Defined Input, Not a Historical Storm Copy

A design storm combines a selected return period, duration, temporal pattern, and spatial representation. The engineer must document the source IDF/DDF relationship, areal-reduction treatment where appropriate, hyetograph pattern, antecedent condition, and any climate or safety adjustment required by the project.

IDF Design Intensity

Generic project-specific IDF form; constants must come from the accepted rainfall study.

i(T,td)=KTx(td+c)ni(T,t_d)=\frac{K T^x}{(t_d+c)^n}

Variables

SymbolDescriptionUnit
iiDesign rainfall intensitymm/hr
TTReturn periodyr
tdt_dStorm durationmin or hr
K,x,c,nK,x,c,nLocation-specific fitted constants-

Do Not Transfer IDF Constants Between Cities

IDF constants are location- and dataset-dependent. Using constants from another station or city without hydrologic justification can dominate the design error.

DEM Watershed Delineation Workflow

Terrain-to-Catchment Workflow

  1. Select a suitable DEM and coordinate reference system. Resolution must match the scale of the drainage problem.
  2. Inspect and condition terrain. Correct sinks or artifacts only with a documented method; do not erase real depressions blindly.
  3. Derive flow direction. Assign the downslope drainage direction for each terrain cell.
  4. Accumulate contributing area. Build flow accumulation to identify drainage paths.
  5. Define the outlet/pour point. Snap the outlet to the correct drainage cell where justified.
  6. Delineate the watershed. Trace all cells draining to the selected outlet.
  7. Extract morphometry. Determine area, flow-path length, elevation range, slopes, and subbasins.
  8. Verify against reality. Compare with contours, mapped streams, roads/culverts, field observations, imagery, and known drainage divides.

A GIS Polygon Is Not Automatically Correct

Road embankments, culverts, storm drains, karst, man-made diversions, DEM artifacts, and urban pipe networks can route water differently from the bare-earth surface. Hydrologic judgment is required after automatic delineation.

Use this review path to decide when terrain conditioning or outlet placement needs revision before accepting a DEM-derived catchment boundary.

DEM-to-Catchment Delineation and Review

Prepare terrain data, locate a defensible pour point, delineate the contributing area, and review topology against real drainage evidence.

Terrain preprocessing commonly derives flow direction and accumulation, defines a stream network using a documented area or cell threshold, and delineates catchments from a selected outlet. DEM conditioning is optional and should be tied to known artifacts, mapped channels, or other defensible evidence; preserve genuine closed depressions. A mismatch with mapped streams, contours, infrastructure, or field observations is a reason to review the terrain, conditioning, stream threshold, or outlet and rerun preprocessing. The resulting polygon is a model that requires hydrologic review, especially where roads, culverts, storm drains, diversions, or karst change surface flow.

DEM-to-Catchment Delineation and ReviewPrepare terrain data, locate a defensible pour point, delineate the contributing area, and review topology against real drainage evidence.. Terrain preprocessing commonly derives flow direction and accumulation, defines a stream network using a documented area or cell threshold, and delineates catchments from a selected outlet. DEM conditioning is optional and should be tied to known artifacts, mapped channels, or other defensible evidence; preserve genuine closed depressions. A mismatch with mapped streams, contours, infrastructure, or field observations is a reason to review the terrain, conditioning, stream threshold, or outlet and rerun preprocessing. The resulting polygon is a model that requires hydrologic review, especially where roads, culverts, storm drains, diversions, or karst change surface flow.. Delineate the contributing catchment → Set analysis outlet and required basin scale; Set analysis outlet and required basin scale → Select DEM, projection, resolution, and extent; Select DEM, projection, resolution, and extent → Coverage, units, and elevation data suitable?; Coverage, units, and elevation data suitable? — Yes → Known artifacts or channels require conditioning?; Coverage, units, and elevation data suitable? — No → Resolve DEM gaps or obtain suitable terrain; Known artifacts or channels require conditioning? — Yes → Condition only with documented terrain evidence; Known artifacts or channels require conditioning? — No → Retain terrain; document conditioning decision; Condition only with documented terrain evidence → Derive flow direction and contributing area; Retain terrain; document conditioning decision → Derive flow direction and contributing area; Derive flow direction and contributing area → Extract drainage paths using a stated threshold; Extract drainage paths using a stated threshold → Place outlet on intended drainage path; Place outlet on intended drainage path → Outlet matches the intended basin outlet?; Outlet matches the intended basin outlet? — Yes → Delineate upstream catchment and subbasins; Outlet matches the intended basin outlet? — No → Review outlet location and mapped stream evidence; Review outlet location and mapped stream evidence — Recheck → Place outlet on intended drainage path; Delineate upstream catchment and subbasins → Boundary matches terrain and drainage evidence?; Boundary matches terrain and drainage evidence? — Yes → Extract area, flow paths, slopes, and subbasins; Boundary matches terrain and drainage evidence? — No → Review DEM artifacts, conditioning, threshold, or outlet; Review DEM artifacts, conditioning, threshold, or outlet — Reprocess → Condition only with documented terrain evidence; Extract area, flow paths, slopes, and subbasins → Record terrain source, processing, threshold, and limits; Record terrain source, processing, threshold, and limits → Use the reviewed catchment model

Delineate the contributing catchment → Set analysis outlet and required basin scale; Set analysis outlet and required basin scale → Select DEM, projection, resolution, and extent; Select DEM, projection, resolution, and extent → Coverage, units, and elevation data suitable?; Coverage, units, and elevation data suitable? — Yes → Known artifacts or channels require conditioning?; Coverage, units, and elevation data suitable? — No → Resolve DEM gaps or obtain suitable terrain; Known artifacts or channels require conditioning? — Yes → Condition only with documented terrain evidence; Known artifacts or channels require conditioning? — No → Retain terrain; document conditioning decision; Condition only with documented terrain evidence → Derive flow direction and contributing area; Retain terrain; document conditioning decision → Derive flow direction and contributing area; Derive flow direction and contributing area → Extract drainage paths using a stated threshold; Extract drainage paths using a stated threshold → Place outlet on intended drainage path; Place outlet on intended drainage path → Outlet matches the intended basin outlet?; Outlet matches the intended basin outlet? — Yes → Delineate upstream catchment and subbasins; Outlet matches the intended basin outlet? — No → Review outlet location and mapped stream evidence; Review outlet location and mapped stream evidence — Recheck → Place outlet on intended drainage path; Delineate upstream catchment and subbasins → Boundary matches terrain and drainage evidence?; Boundary matches terrain and drainage evidence? — Yes → Extract area, flow paths, slopes, and subbasins; Boundary matches terrain and drainage evidence? — No → Review DEM artifacts, conditioning, threshold, or outlet; Review DEM artifacts, conditioning, threshold, or outlet — Reprocess → Condition only with documented terrain evidence; Extract area, flow paths, slopes, and subbasins → Record terrain source, processing, threshold, and limits; Record terrain source, processing, threshold, and limits → Use the reviewed catchment model

  • Delineate the contributing catchment: terminator
  • Set analysis outlet and required basin scale: input output
  • Select DEM, projection, resolution, and extent: process
  • Coverage, units, and elevation data suitable?: decision
  • Resolve DEM gaps or obtain suitable terrain: terminator
  • Known artifacts or channels require conditioning?: decision
  • Condition only with documented terrain evidence: process
  • Retain terrain; document conditioning decision: process
  • Derive flow direction and contributing area: process
  • Extract drainage paths using a stated threshold: process
  • Place outlet on intended drainage path: process
  • Outlet matches the intended basin outlet?: decision
  • Review outlet location and mapped stream evidence: process
  • Delineate upstream catchment and subbasins: process
  • Boundary matches terrain and drainage evidence?: decision
  • Review DEM artifacts, conditioning, threshold, or outlet: process
  • Extract area, flow paths, slopes, and subbasins: process
  • Record terrain source, processing, threshold, and limits: document
  • Use the reviewed catchment model: terminator

Rainfall-Runoff Model Chain

Four Linked Questions

A rainfall-runoff model must answer four different questions:

  1. How much rain becomes excess rainfall? — infiltration/loss model such as Horton, Green-Ampt, or Curve Number.
  2. How quickly does excess rainfall reach the outlet? — transform method such as a unit hydrograph or kinematic approach.
  3. How is flow modified by storage and channels? — reservoir/channel routing.
  4. What boundary conditions control discharge? — downstream stage, tide, backwater, pumps, gates, or receiving-system capacity.

SCS Curve Number Runoff Depth

Event runoff-depth relation after the initial-abstraction condition is satisfied.

Q=(P−Ia)2P−Ia+SQ=\frac{(P-I_a)^2}{P-I_a+S}

Variables

SymbolDescriptionUnit
QQDirect runoff depthmm
PPStorm rainfall depthmm
IaI_aInitial abstractionmm
SSPotential maximum retentionmm

Calibration and Validation

A model should not be considered reliable merely because it runs. Calibrate against observed rainfall-flow events where possible, then validate against independent events. Compare peak flow, runoff volume, timing, hydrograph shape, and spatially observed flood behavior rather than matching only one metric.

Flood Frequency and Event Modeling Are Complementary

Statistical Frequency Analysis

Frequency analysis estimates the magnitude associated with an annual exceedance probability from a flood series. It is useful when a suitable streamflow record exists and the statistical assumptions are defensible.

Design-Storm Modeling

Design-storm modeling converts a specified rainfall event through a catchment model. It is useful for drainage networks, ungauged/changed catchments, scenario analysis, and spatial intervention design.

Do Not Assume Equal Return Periods Automatically

A 100-year rainfall event does not necessarily produce a 100-year flood because soil moisture, storm pattern, spatial coverage, basin storage, tide, and model nonlinearity affect runoff. The rainfall and flood frequency concepts must be connected carefully.

Urban Drainage Workflow

Urban Drainage Design Sequence

  1. Delineate each inlet/subcatchment and verify overland/pipe flow paths.
  2. Determine time of concentration or travel time using a method appropriate to the actual surface/network.
  3. Obtain design rainfall intensity for the selected return period and duration.
  4. Estimate runoff using a method valid for the catchment scale and purpose.
  5. Size inlets, gutters, pipes, channels, and storage using hydraulic calculations.
  6. Route larger events and check surcharge, surface exceedance paths, and downstream tailwater.
  7. Check the receiving system so the project does not merely transfer flooding downstream.
  8. Evaluate detention, infiltration, green infrastructure, and safe overland flow paths where appropriate.

Rational Method Peak Flow

Peak-flow screening for small catchments under its applicability assumptions.

Qp=CiAQ_p=C i A

Variables

SymbolDescriptionUnit
QpQ_pPeak discharge with units consistent with the adopted coefficient convention-
CCRunoff coefficient-
iiRainfall intensity for duration approximately equal to time of concentration-
AADrainage area-

Peak Flow Is Not a Hydrograph

The Rational Method does not provide runoff volume or the time-varying inflow needed for storage routing. Detention, floodplain, and major-system design often require a full hydrograph.

Climate and Nonstationarity

Document the Assumption

Historical frequency analysis commonly assumes stationarity. Where the project or authority requires climate-adjusted design, document the approved scenario, horizon, adjustment method, uncertainty, and how the change propagates through rainfall, runoff, storage, and freeboard checks. Do not apply an undocumented percentage increase simply because it appears conservative.

Philippine Design-Storm Modeling Workflow

Trace a design from verified catchment definition and station-appropriate rainfall through losses, transform, routing, hydraulic checks, calibration or uncertainty review, and documented acceptance.

Philippine Design-Storm Modeling WorkflowTrace a design from verified catchment definition and station-appropriate rainfall through losses, transform, routing, hydraulic checks, calibration or uncertainty review, and documented acceptance.. Define drainage or flood-design objective → Set return period, duration basis, authority criteria and receiving boundary; Set return period, duration basis, authority criteria and receiving boundary → Gather station IDF/rainfall, DEM, soils, land use, network and observed events; Gather station IDF/rainfall, DEM, soils, land use, network and observed events → Use the reviewed catchment boundary and basin attributes; Use the reviewed catchment boundary and basin attributes → Construct location-appropriate design rainfall; Construct location-appropriate design rainfall → Select loss, transform, storage/channel routing and boundary models; Select loss, transform, storage/channel routing and boundary models → Suitable observed events available?; Suitable observed events available? — Yes → Calibrate and validate against independent events; Suitable observed events available? — No → Document transferred parameters and uncertainty; Calibrate and validate against independent events → Run design-storm hydrograph and hydraulic system checks; Document transferred parameters and uncertainty → Run design-storm hydrograph and hydraulic system checks; Run design-storm hydrograph and hydraulic system checks → Unsafe hydraulic result?; Unsafe hydraulic result? — Yes → Revise conveyance, storage, infiltration or safe overflow path; Revise conveyance, storage, infiltration or safe overflow path — Recheck → Select loss, transform, storage/channel routing and boundary models; Unsafe hydraulic result? — No → Climate basis set?; Climate basis set? — No → Apply required climate basis to design inputs; Apply required climate basis to design inputs — Recompute → Construct location-appropriate design rainfall; Climate basis set? — Yes → Record assumptions, sensitivity, boundaries and accepted design basis; Record assumptions, sensitivity, boundaries and accepted design basis → Issue design-storm model basis

Define drainage or flood-design objective → Set return period, duration basis, authority criteria and receiving boundary; Set return period, duration basis, authority criteria and receiving boundary → Gather station IDF/rainfall, DEM, soils, land use, network and observed events; Gather station IDF/rainfall, DEM, soils, land use, network and observed events → Use the reviewed catchment boundary and basin attributes; Use the reviewed catchment boundary and basin attributes → Construct location-appropriate design rainfall; Construct location-appropriate design rainfall → Select loss, transform, storage/channel routing and boundary models; Select loss, transform, storage/channel routing and boundary models → Suitable observed events available?; Suitable observed events available? — Yes → Calibrate and validate against independent events; Suitable observed events available? — No → Document transferred parameters and uncertainty; Calibrate and validate against independent events → Run design-storm hydrograph and hydraulic system checks; Document transferred parameters and uncertainty → Run design-storm hydrograph and hydraulic system checks; Run design-storm hydrograph and hydraulic system checks → Unsafe hydraulic result?; Unsafe hydraulic result? — Yes → Revise conveyance, storage, infiltration or safe overflow path; Revise conveyance, storage, infiltration or safe overflow path — Recheck → Select loss, transform, storage/channel routing and boundary models; Unsafe hydraulic result? — No → Climate basis set?; Climate basis set? — No → Apply required climate basis to design inputs; Apply required climate basis to design inputs — Recompute → Construct location-appropriate design rainfall; Climate basis set? — Yes → Record assumptions, sensitivity, boundaries and accepted design basis; Record assumptions, sensitivity, boundaries and accepted design basis → Issue design-storm model basis

  • Define drainage or flood-design objective: terminator
  • Set return period, duration basis, authority criteria and receiving boundary: input output
  • Gather station IDF/rainfall, DEM, soils, land use, network and observed events: data
  • Use the reviewed catchment boundary and basin attributes: process. Complete DEM conditioning, outlet review, delineation, and terrain verification before continuing.
  • Construct location-appropriate design rainfall: process
  • Select loss, transform, storage/channel routing and boundary models: process
  • Suitable observed events available?: decision
  • Calibrate and validate against independent events: process
  • Document transferred parameters and uncertainty: process
  • Run design-storm hydrograph and hydraulic system checks: process
  • Unsafe hydraulic result?: decision. Check surcharge, surface exceedance paths, and whether the project transfers flooding to the receiving system.
  • Revise conveyance, storage, infiltration or safe overflow path: process
  • Climate basis set?: decision. Confirm whether the authority requires a climate or nonstationarity treatment; document the approved scenario, horizon, method and uncertainty.
  • Apply required climate basis to design inputs: process
  • Record assumptions, sensitivity, boundaries and accepted design basis: document
  • Issue design-storm model basis: terminator
Key Takeaways
  • Philippine design hydrology must account for tropical rainfall variability, terrain, urban drainage modification, and downstream boundary conditions.
  • IDF values must come from an accepted local dataset; constants are not portable between locations without justification.
  • DEM delineation is a starting model that must be checked against actual drainage infrastructure and field evidence.
  • Rainfall losses, runoff transform, routing, and boundary conditions form one connected model chain.
  • Statistical flood frequency and design-storm modeling answer different questions and should not be conflated.
  • Urban drainage requires both minor-system capacity and safe major-system/exceedance routing.
  • Every design value should retain its data source, return period, units, record basis, and uncertainty assumptions.

References