The whole list, plainly, so you can search it for the thing you need, tell us
what is missing from it, or measure it against whatever you use today.
This is a list of what has been built, not of what is planned. Everything on
it works today, in a browser, free, with no account. It covers the network model this site is
about and the rest of the hydraulic calculators it lives beside, because they are one program and
you get all of it either way. The list is honest rather than complete: a line is
on it because somebody sat down and wrote a sentence for it, and plenty of smaller work never got
one. If you only want to know whether the thing is any good, do not read a list —
diving in saves time.
Manning pipe flow solves in both directions — the flow from a depth, and the depth from a flow.
Every pipe and channel page checks the velocity it just computed and says when it is too fast or too slow.
Orifice flow, and the time a tank takes to drain through one.
Micro-hydropower, from gross head and penstock losses to the power a small site can actually deliver.
Canal seepage and conveyance efficiency, including whether lining the canal pays for itself.
Rock chute sizing by the Robinson method.
Sketches drawn to scale from your own numbers, so you can see the section you just described.
A tip on every input saying what the number is, in the language of the page.
One button returns a page to a worked example that passes, so nothing is ever a blank form.
Name a calculation and copy a link to it; the link carries your inputs, and nothing is shared unless you share it.
Changing an input unit asks first, and says plainly that it reinterprets the numbers you typed rather than converting them.
Install it from the browser you already have, and every calculator keeps working with no network at all.
Drawing a water network 8
A drawing toolbar — junction, reservoir, tank, pipe, pump, valve and text — placed by clicking the map.
Many named projects, saved in your own browser, each open in its own tab.
The property box is a window you can drag out of your way, not a panel that owns an edge of the screen.
ID prefixes you choose, with Apply to all for when you change your mind.
Find elements by any property, jump straight to one by ID, and set a property across everything the search found.
The File menu remembers your recent projects, and the map remembers where you were looking.
One toggle clears the readouts off the map when you want the drawing and nothing else.
A Help menu specific to this calculator.
Solving it 4
A looped network solved by the global gradient method, in the page, with no install and no upload.
Or solved by the EPANET 2.3 engine itself, compiled into the page and named by version where you can see it.
Standard gravity throughout, and where the two engines disagree the page tells you by how much.
Answers follow your edits as you make them, and if a big network makes that slow, it is a project setting you can turn off.
Time 5
Extended-period simulation: tanks fill and drain, demands follow their patterns, and a bar along the bottom plays the run or steps to any moment in it.
Patterns on a reservoir head and on a pump's speed, beside the demand patterns.
A Libraries box holding the patterns and curves a run needs.
A Run button (optional, since answers can follow your edits instead) shows real progress, a completion report, and the engine's own report of the run.
Colour limits hold still across a run, so a colour means the same thing at every step.
Files and EPANET 5
Opens EPANET .inp files, takes the part it supports, and reports every difference instead of dropping it quietly.
An import note is filed on the element it concerns, and you read it in that element's own property box.
Writes .inp files back out. Every value you did not edit comes back exactly as it went in, character for character.
Projects are .lwn files — JSON inside, on your own disk, readable without us.
An examples library that opens Net1, Net2, Net3, Elm Street Center and a Net3 placed on the world, in one click.
The map and the world 4
A geographic project is drawn in latitude and longitude over a street map or satellite imagery, with the same drawing tools.
An existing x/y network can be placed on the world — moved, scaled and rotated onto its real ground.
Type a place name and the map goes there, if you turn that on.
Ground elevations read from terrain data and typed into the document, never replacing a number without first showing you the one it would replace.
Labels and lettering 7
Labels place themselves. Where there is no room, a label sheds values in the order you chose instead of disappearing whole.
Any label can be dragged where you want it, and it keeps a leader back to what it names.
Pipe labels lie along their pipe, the way a map draws a street name.
Prefixes, suffixes and a separator you choose, with a link's values on one line.
A Text object takes several lines, bold, and a rotation that can match a pipe.
Lettering is haloed, so it stays readable over the drawing underneath it.
Text, symbols and pipes are three independent screen sizes, so a drawing reads the same at every zoom.
Reading the results 3
A table for each kind of part in the bottom pane — junctions, reservoirs, tanks, pipes, pumps and valves.
Colour the map by any value, from one control: three to seven classes, eight ways of choosing where the breaks fall, and 41 colour ramps.
Profiles. Click along the map to choose the path, and see ground, hydraulic grade and the pressure between them.
Scenarios 1
Change a few properties without disturbing the network they belong to, switch between those scenarios, and see at a glance which elements carry an override.
Language, licence, and privacy 4
Twenty-seven languages, across the whole suite and not only its menus.
Free software under the GNU GPL, source in the open.
It installs on a desktop or a phone as an app of its own, icon and all.
No account, no visitor identifier, and nothing counted about you unless you say yes.
And the edges, in the same breath
A list like this reads as though somebody has surveyed the whole territory. Nobody has. We
know what we built and we know some of what we lack; we do not know the size of the gap between
this and the software an experienced modeller is used to, and saying otherwise would be the
first thing on this page to stop being true.
What we do know we are missing: a run over time goes through the EPANET engine, and the
built-in solver has no time dimension at all. Rule-based controls are not built. Water quality
modelling is not built.
And although you of course prefer working on your PC, it works also on a phone in tall mode.
For your privacy: nothing here reaches anyone else unless you turn on a feature
that needs it, and each one asks separately. Today there are four: street map tiles
from OpenStreetMap; satellite tiles from Mapbox; place-name search, which sends what you typed to OpenStreetMap's
geocoder; and the ground-elevation lookup, which sends the coordinates of your nodes to Mapbox.
Those last two each have a consent question of their own. Nothing you draw is uploaded unless
you turn on one of those, and there is no account to make.