Features
What is in the tool
Runoff before and after, for six design storms, with the practices that fix it and a report that shows its sources.
-
Every storm in one run
Water quality, 1, 2, 10, 25 and 100-year. Existing, proposed and with practices, pass or fail.
Details
Depths are read from NOAA Atlas 14 at the site; the water quality depth is 1.0 in and you can change it. You can turn a storm off, or raise the Atlas depths by a climate factor. Every storm runs after the first compute, in one press. The General check is one plain test: the peak with practices is at or below the existing peak. It is not a local rule. A chart shows the flow over time for each storm, before and after.
-
Suggest a fix
CurveNumber reruns every storm at larger practice sizes and keeps the smallest that passes the most.
Details
It picks the practice that overflows in the most failing storms, unless you name one, and tries 1.25, 1.5, 2 and 3 times its size. Where no size passes more storms, it says plainly that resizing this practice alone will not pass. Nothing on the site changes: to keep a size, change the practice and run again. The assistant writes the sentence about it; the sizes and the figures are CurveNumber's.
-
Drainage areas, suggested from the ground
Several practices on a site, each with its own drainage area. One press suggests them from USGS elevation.
Details
Each part of the site goes to the first practice its water reaches, so suggested areas never overlap; the rest is bypass. Use these keeps them; you can untick one, or draw your own. On flat or paved ground, where pipes decide where water goes, it says so and asks you to draw. You can also trace what drains to a point, including ground uphill of the site that runs onto it. Proposed land use is drawn on the map, and practices already built go in today's ground.
-
Quiet warnings
One line when something needs you, with the why behind a "?".
Details
Ground uphill, as large as the site, that drains onto it; an area beyond the TR-55 limits, ground too flat to trace; a practice that overflows, drainage areas that are out of date or leave ground uncounted, a large jump in paved area with little of it treated, and a time of concentration over 10 hours. Each one says what to do.
Thirteen more checks run over the site record every time the workspace is opened: an implausible input combination, a composite curve number that disagrees with the measured impervious share, a design storm that does not match the one the manual names, a dataset that has gone stale, an area above the method's limit or below the threshold at which deriving means anything. One of them blocks the action outright. No warning calls a model, sends anything or costs anything.
-
Help with the words, never the numbers
Explain a result, suggest a fix, draft text for the report, and tidy what you type.
Details
Every number comes from CurveNumber, not from the AI, and a check blocks any number the run or your record does not hold. Drafted report text is yours to edit and sign, and it is checked again before you publish. Writing help in text boxes can be off, can suggest, or can fix automatically, in your account settings. What each feature sends, and to whom, is on the privacy page.
-
A report a reviewer can check
Every storm, its depth and its source. Every figure says where it came from.
Everything in the tool, by step
A site moves through the steps the tool shows: Site, Today, Proposed, Results, and Report and share.
Where it works: sites in the contiguous United States (the lower 48 states). Alaska, Hawaii, Puerto Rico and the territories are not covered, because the public data sets it reads do not cover them.
All of it, in detail
Site is the boundary and the public data read for it, Today is the ground as it is with any practice already built, and Proposed is what you plan to build, drawn as land use, with its practices. The aerial photograph and calibration are each a side analysis that returns to a step. What sits under each is below.
An override is not a text box
The interface states what the choice is worth before it is made, asks for a reason in proportion to that figure, and names the account the sentence will be filed against. An engineer who has to write "because the software said B" tends to go and look instead, which is the entire intent.
The soil survey rates no hydrologic group for a large share of urban land, which is the ordinary case on the sites this product is for. That is not a blank to fill with B. It is a question, and it goes to the person who can answer it.
In detail
How it handles what it does not know
When a number is not computed, and what it asks for instead
Not computed, with the reason
Where a material share of a site is unresolved, no site result is produced
CurveNumber separates the states that have different remedies and keeps them separate all the way to the screen. A service being down and a site being outside the survey are not the same problem and are never the same message.
The threshold is a tenth of the site. It is recorded as a judgment rather than a finding, and it is one of the defaults you can see and argue with.
Every check and default, counted
CurveNumber states in writing when a number cannot be computed and what it needs, instead of guessing, in ninety-seven named checks, each with what would resolve it.
Method limits, not waivable.
Range checks: proceed with a reason that names the threshold you are arguing with.
Needs input: supply it, or proceed with an attestation that states what it rests on.
Each default says what it is worth in your answer: Hydrologic condition = Fair is worth 5 to 12 CN units. Twenty-four practices, seventeen modeled; the other seven are marked not computed, in writing.
Ninety-seven checks in one published list: see what is not computed and why, and every kind of check, the default values, or the list as data for software.
Default values, and what each is worth
The list of default values
An assumption that states its own price
One hundred twenty-six values in CurveNumber are defaults rather than anything read off your site. Every one of them is written down in one list, classified by what would have to happen for it to change, and carries two fields that turn a lookup into guidance: what it is worth in the answer, in computed figures rather than adjectives, and what evidence would displace it.
Fifty-four of them say no external source exists on their face, because nobody publishes the figure at all. Seven more say the source exists and was not checked, which is a different admission with a different remedy, and the two are never merged.
That is also how the interface can be quiet. A user shown thirty defaults confirms none of them, so CurveNumber ranks its own assumptions by what they are worth on this site and surfaces the two or three that move the answer.
Reference views: the defaults and the curve number tables
Open to anyone
Reference views: the default values and the curve number tables
The tool has five reference views; two are shown here. They read the same data a run reads, so there is no separate marketing copy of them to fall out of date.
no source chip rather than implying one.
Public data, named and dated
Where the inputs come from
Public data, named, dated and cached
You supply the boundary and the design storm. Everything below is retrieved, and each retrieval is recorded with its URL, its status, the timestamp and a hash of the response body, so a figure in a report traces to a specific server response on a specific day.
The boundary is drawn on the map, or edited vertex by vertex, or cut with a hole where a building is excluded. The enclosed area is computed on the ellipsoid and shown while you draw, because an acreage that appears only after you save is an acreage nobody checks.
These are unfunded public services, so every response is cached, and a second look at the same site does not ask them again.
Aerial imagery, a guess you accept or reject
Read this before you use it
Aerial imagery is a guess you have to accept
The tool will fetch a public-domain NAIP photograph of your boundary and sort its pixels into impervious, vegetation, bare soil, water and shadow. That is not a measurement of your site and it is not treated as one. It arrives pending: you can see it, it is labeled a guess, nothing in the product reads it, and it becomes a figure in your record only when you accept it. Accepting is recorded with your name, the time, the revision you acted on and the reason you gave, and the report prints it as an override with the provider and the flight date beside it. Rejecting costs you one click and no reason, and the rejection stays on the record, because a guess you looked at and rejected is evidence about the site.
The source register, open to anyone
The register the product runs on
Check the sources before you trust the output
Every regulatory document this product holds is tracked in the open: what has been found, what has been downloaded and parsed, and what a person has reviewed. The register is published, needs no account, and is as specific about the gaps as it is about the coverage.
The reference library the assistant quotes from holds 124 documents and about 20,800 pages, and growing: federal and state manuals, published agency studies and CurveNumber's own published examples.
Every public dataset CurveNumber reads, who publishes it, the edition in use and when it is read is on the data sources page, the page every report points to.
What it is for, and what it is not
CurveNumber computes runoff volume and peak discharge for a site's existing and proposed conditions by the NRCS methods (TR-55 and NEH-630), checks stormwater practices against them, and writes a report a plan reviewer can follow. It is a runoff and peak calculator with practice checks. It is not a full stormwater design package, and it does not replace one where a project needs:
- a site outside the contiguous United States;
- detention design from scratch: CurveNumber routes the practices you size; it does not size a pond for you or route a network of connected basins.
Peaks use the NRCS standard unit hydrograph, or the NRCS Delmarva unit hydrograph (peak rate factor 284) on the Delmarva coastal plain and where a local rule asks for it; every peak names the one it used. Design rainfall comes from NOAA Atlas 14, and in Washington and Oregon from NOAA Atlas 2 (1973), for 24 hour storms of 2 to 100 years; type other durations and return periods from the published source.
Two free sites, then USD 100 per site
Every new account gets two free site codes. After that, USD 100 opens a 30-day working window on a site, and USD 20 adds each extra 30 days.