Build a model from a location
Type a place name and get a runnable network. This is the fastest way to have something to reason about, and the fastest way to mislead yourself, so it is worth understanding what the generator is doing.
Generating
Section titled “Generating”-
Toolbar, Project ▸ Generate model from location.
-
Search for the place. The map moves there.
-
Choose the study area. Drag the rectangle, or switch to polygon and trace the real service area.
-
Choose the system type: sanitary (foul only), storm (surface water only), or combined (both, with overflow structures).
-
Optionally open the dry-weather-flow settings to set water use per person, return fraction, and the served population if you know it.
-
Generate.
What it actually does
Section titled “What it actually does”- Streets come from open source datasets. Manholes are placed at junctions and dead ends, pipes run along the street centre lines.
- Ground levels are sampled from a world terrain dataset.
- Connectivity is solved as a tree draining downhill to one or more outfalls, because a gravity sewer is a tree.
- Catchment areas are allocated to each node by nearest-node (Thiessen) polygons, clipped to your study area, and normalised so the total matters.
- Pipes are sized from the flow each one carries.
How pipes get their size
Section titled “How pipes get their size”Worth reading, because it is what makes the output defensible or not.
For storm and combined systems the design flow is the Rational method, Q = C i A / 360,
where each pipe uses:
- A, the catchment accumulated from everything upstream;
- C, an area-weighted runoff coefficient derived from land use, so a catchment that is mostly forest is not sized as though it were paved;
- i, a rainfall intensity that varies with the time of concentration. A small lateral concentrates in minutes and sees a short intense burst; a trunk draining a whole valley concentrates in over an hour and sees a much gentler average.
For sanitary systems the design flow is peak dry-weather flow: population, per-capita water use, return fraction, and a population-dependent peaking factor (Harmon), with no rainfall at all.
The required diameter comes from Manning, rounded up to the next commercial size, and never narrows going downstream.
Reading why a pipe is that size
Section titled “Reading why a pipe is that size”Open Flex Tables, choose Conduits, and look at the green columns: catchment area, Tc, the intensity actually used, C, design flow, full-bore capacity, full-bore velocity, and Sized by, which is the interesting one:
| Sized by | Meaning |
|---|---|
hydraulic | Genuinely flow-driven. Manning decided this. |
minimum-size | The minimum practical diameter governs, not hydraulics. |
downstream | Held up by continuity, never narrowing downstream. |
capped | You set a maximum diameter and it was reached. |
If most of a small foul network reads minimum-size, that is not a failure. For systems of
that scale the standard genuinely governs and hydraulics barely participates.