SWAT+ water quality modeling software for U.S. watersheds

Water-quality modeling here means SWAT+ in its constituent-transport role: simulating how land use, soils, climate, and management drive in-stream nitrogen, phosphorus, sediment, and the water balance that carries them — continuously, over years to decades. SWATGenX clips and wires the national data (NHDPlus HR hydrography, gSSURGO soils, NLCD land cover, PRISM/NSRDB climate) into a QSWAT+ / SWAT+ Editor project so you start from a working constituent model instead of a blank GIS canv canvas. Beyond the standard constituents, PFAS fate and transport is supported through the open coupled SWAT+/MODFLOW 6 engine — Freundlich sorption in soils, advective–dispersive aquifer transport, and groundwater-to-stream discharge — demonstrated at AFFF-impacted sites with a manuscript under peer review (see the SWAT+MODFLOW-6 page and the watershed-to-site PFAS demonstration under Research).

Order at a USGS gage, a catalog HUC12 outlet, a whole HUC8 where enabled, or a 30 m HUC14 single-catchment site model (drill into a HUC12 and pick catchments). Each build returns SQLite + SWAT+ text inputs with the routing, HRUs, soils, and management hooks already in place — the same lineage you can compare against rows in the public example-models catalog before spending calibration budget.

Water-quality engineers, TMDL and nutrient-criteria analysts, agricultural BMP and conservation planners, and graduate researchers comparing SWAT+ against other constituent and loading models.

SWATGenX does not deliver a calibrated, sign-off-ready load estimate, and it is not a receiving-water hydraulics or in-lake eutrophication model. It removes the national data-assembly step; calibration to observed loads, scenario design, and regulatory documentation remain your work PFAS is likewise not part of the hosted auto-calibration: PFAS simulation runs through the coupled SWAT+/MODFLOW 6 engine as a downstream, study-specific workflow (the engine simulates sorption and transport; it does not model precursor transformation, atmospheric deposition, or bioaccumulation).

Where SWAT+ fits among water-quality tools

SWAT and SWAT+ are among the most widely applied watershed water-quality models in the literature — EPA describes SWAT as simulating the water-quantity and water-quality effects of land management and climate, and SWAT+ extends that with a restructured, relational design. Their strength is non-point-source loading: nutrients and sediment generated across the landscape and routed through the channel network continuously.

That is a different job from receiving-water and design tools. Event-based hydraulics (HEC-HMS/RAS), pipe-level urban stormwater quality (EPA SWMM), and in-waterbody eutrophication models answer questions SWAT+ does not. Use SWAT+ (via SWATGenX) for watershed-scale source loading and management scenarios on national NHDPlus HR hydrography; pair it with the right receiving-water model when your question is in-channel or in-lake.

A PFAS plume in 3D — live

This is actual coupled SWAT+/MODFLOW 6 output, interactive: the simulated PFOS plume at Wurtsmith AFB. Orbit the aquifer, scrub five decades of plume evolution, drop the threshold to the regulatory limit, and hover any well, source, or plume cell for its numbers.

Data backbone (citations & resolutions):

• 25,000+ USGS stations — live context via USGS Water Services (instantaneous values often ~15-minute; see USGS for provisional data caveats)
• NHDPlus HR — built from 1:24,000 NHD, 10 m 3DEP, and WBD; USGS cites on the order of ~27 million flowlines vs ~3 million in NHDPlus V2 (USGS NHDPlus HR)
• PRISM gridded climate (~4 km cells; PRISM defines a “day” as 24h ending 12:00 GMT); NLCD land cover 30 m; gSSURGO soils (gridded SSURGO per NRCS); NSRDB solar/meteorology nominally ~4 km (≈0.038°), 30-minute series — SWATGenX may resample/regrid for operations; see methodology for lineage

Full methodology & provenance table →

After you download a water-quality setup

You run SWAT+ locally or on HPC, then calibrate constituents against observed loads (often a two-stage flow-then-quality calibration) in SWAT+ Editor or your calibration toolchain. SWATGenX removes the national input assembly; it does not replace calibration, scenario design, or peer review for a defensible load estimate.

What a water-quality workflow looks like here

• Constituents in the SWAT+ frame: in-stream and in-HRU nitrogen, phosphorus, and sediment driven by the continuous water balance — not a single design-storm load
• Management & BMP scenarios: land-use, fertilizer/manure, tillage, and conservation-practice changes evaluated over multi-year series in SWAT+ Editor after download
• National lineage baked in: gSSURGO soils, NLCD land cover, and PRISM/NSRDB climate clipped to your basin so source-area loading reflects real inputs, not placeholders
• Audit before you commit: example models list HRU counts, delineation source (NHDPlus HR vs TauDEM fallback), and downloads so you can vet a setup before calibration
• Screen observed conditions first: the Watershed Explorer overlays ~163,000 EPA/USGS stream nutrient & sediment monitoring stations (plus a multi-source PFAS inventory) so you can see measured nitrogen, phosphorus, and sediment in your basin before spending calibration budget — observed context for screening, not part of the downloaded package

SWATGenX delivers automated SWAT+ setups for nutrient, sediment, and land-management analysis — for your review, calibration, and validation. A downloaded package is not a calibrated, regulatory-ready water-quality model (e.g. a TMDL submittal) until you complete calibration against observed loads and document it for your study objective.

Explore related