Use the ANSI/ASABE S626 Landscape Irrigation System Uniformity and Application Rate Testing standard to conduct and document a system audit's distribution uniformity (DU) measurement.
domain: ASABE (asabe.org) · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the current status of ANSI/ASABE S626 (SEP2016, reaffirmed R2020) as the applicable edition before citing it in an audit report.
Scope the test to continuous turf/ground-cover areas where irrigation coverage is unimpeded, since S626 is written for that landscape type rather than obstructed or mixed-planting beds.
Follow the standard's catch-can (or equivalent) field procedure to measure application rate and distribution uniformity for each zone being audited.
Calculate the uniformity metrics the standard specifies and record them alongside zone-level precipitation rate data for the audit report.
Use the DU results to inform irrigation scheduling recommendations (e.g., feeding into a water budget or CLIA-style audit deliverable) rather than treating the raw DU number alone as the final work product.
Known gotchas
S626 is a reaffirmed 2016 standard (R2020) — it was not substantively revised in 2020, just reapproved, so don't describe it to a client as a '2020 standard' implying new content.
The standard applies specifically to continuous turf/ground-cover coverage; applying its uniformity methodology unmodified to drip/microirrigation zones or heavily obstructed beds is a scope mismatch.
A DU test result alone doesn't certify a system as 'compliant' with any specific ordinance — some jurisdictions or rebate programs may specify their own minimum DU threshold on top of the S626 test method.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?