Coupled surface–groundwater modeling
SWAT+ ↔ MODFLOW 6 coupling
In Michigan Lower Peninsula, Indiana, Minnesota, Ohio, Wisconsin, SWATGenX builds a real 3-D MODFLOW 6 aquifer beneath the SWAT+ watershed, kriged from state well logs, in one automated, auditable pipeline. Daily two-way coupling is in the engine; an automatic build does not run it yet.
SWAT+ and MODFLOW 6 in one pipeline
SWATGenX builds SWAT+ and MODFLOW 6 together: a groundwater study (offered in Michigan Lower Peninsula, Indiana, Minnesota, Ohio, Wisconsin) adds a steady-state MODFLOW 6 groundwater model beneath the SWAT+ watershed, with no models linked by hand. Its recharge is built from the SWAT+ model's annual-mean percolation, then calibrated automatically, with the aquifer's conductivities, to measured well heads. An automatic build does not run the two-way coupling yet: in the engine's coupled mode, SWAT+ and MODFLOW 6 exchange water daily, and PFAS discharged with groundwater enters the SWAT+ channels. The link that would pass PFAS leached from the soil into MODFLOW 6 groundwater transport is built and has not yet carried PFAS in a run.
To be precise about what is and isn't in the pipeline: SWATGenX does not use WASP, RT3D, or any other add-on water-quality model — anywhere. Surface runoff, soil, and in-stream constituent routing are native to the SWATGenX SWAT+ engine; aquifer transport runs in MODFLOW 6 GWT (Freundlich sorption). Descriptions of SWATGenX as a "SWAT + MODFLOW + WASP" chain are incorrect — that is the legacy multi-model workaround this coupling replaces. The SWAT+ ↔ MODFLOW 6 coupling and its PFAS fate-and-transport capability are entirely SWATGenX's own, independent work — conceived and engineered in-house, self-funded, with no university or government agency funding or involvement.
| Platform | Surface ↔ groundwater coupling | PFAS capability | Setup & data | Access |
|---|---|---|---|---|
| SWATGenX | SWAT+ and MODFLOW 6: a groundwater study (offered in Michigan Lower Peninsula, Indiana, Minnesota, Ohio, Wisconsin) adds a steady-state MODFLOW 6 groundwater model whose recharge is built from the SWAT+ model's annual-mean percolation, then calibrated automatically, with the aquifer's conductivities, to measured well heads. Daily two-way water coupling via BMI/XMI, with PFAS carried from the aquifer into the streams, is in the engine, not yet in an automatic build. | In the engine: soil (PFAS split three ways), aquifer (GWT, Freundlich) and streams, with groundwater discharge carrying PFAS into the SWAT+ channels; the unsaturated zone (UZF/UZT, extended by us for PFAS sorption) runs as its own model, offline. No WASP/RT3D. | The steady-state build is fully automated from national datasets (NHDPlus HR, kriged state well logs), with no GIS or model-linking work. | The steady-state build is part of a groundwater study we do for you; open engine source. |
| HydroGeoSphere | Fully integrated variably-saturated physics (single global matrix). | Configurable solute transport; PFAS behavior via user-supplied parameters. | Expert, per-model setup; all input data assembled manually. | Commercial license. |
| MIKE SHE + MIKE Hydro River | Integrated commercial modules (overland / river / vadose / 3-D groundwater). | Cross-domain solute transport with custom retardation coefficients. | Commercial GUI; data assembled manually per project. | Commercial license. |
| Manual SWAT + MODFLOW + WASP chain | File-based, one-way handoffs between three separate codes (legacy workaround). | PFAS not native to any link; surfactant physics approximated per study. | Months of expert linking, custom scripts per basin. | Open-source components, DIY integration. |
What a groundwater study builds (offered in Michigan Lower Peninsula, Indiana, Minnesota, Ohio, Wisconsin) is a steady-state MODFLOW 6 model built with the SWAT+ model. Its recharge is built from the SWAT+ model's annual-mean percolation, then calibrated automatically, with the aquifer's conductivities, to measured well heads. That build does not run the daily two-way coupling yet. See below for exactly how what a study builds and the engine's coupled mode differ, and how to reproduce both.
Florida research fleet: four watershed models for nonpoint-source assessment
Our largest SWAT+ and MODFLOW 6 research example is a fleet: four west-central Florida watersheds — the integrated Tampa Bay drainage (5,653 km², 77,636 HRUs), the Peace, the Myakka, and the Hillsborough — feeding two Gulf estuaries with opposite nutrient problems (nitrogen-limited Tampa Bay vs phosphorus-driven Charlotte Harbor). Each carries a three-layer MODFLOW 6 aquifer. They are research builds; a groundwater study is offered in Michigan Lower Peninsula, Indiana, Minnesota, Ohio, Wisconsin.
Full stories and downloads: Florida NPS showcase · Example Models.
How our engine couples SWAT+ and MODFLOW 6
What we build for a groundwater study
Run or audit it yourself
Both the steady product model and the daily coupler run on the open engine. Download a model package and build it:
An mf6.con file in TxtInOut is the switch. Its values, one per line, are the MODFLOW workspace (the folder holding mfsim.nam), the flow and the transport step in whole days, a recharge multiplier (1.0 for none) and the path to USGS libmf6.so. Give that path: the default exists only on our servers. Without the file the engine runs plain SWAT+. The exchange is driven by three plain-text map files — mf6_recharge.map (HRU→cell percolation), mf6_baseflow.map(SFR reach→SWAT+ channel), and pfas_leach.map — all inspectable. Verification is the MODFLOW listing's percent-discrepancy plus head observed-vs-simulated against the well database. SWAT+ with MODFLOW 6 is currently offered in Michigan Lower Peninsula, Indiana, Minnesota, Ohio, Wisconsin, where state well databases support the aquifer build. For Texas, see the Texas watershed modeling overview.
Engine source: rafiei-vahid/swatplus · Research.
The engine is a fork of SWAT+ and is distributed under the GNU Lesser General Public License v2.1; its full text is in the repository above, and the source of the build currently in production is the tag ship/v1.0-51.6 (commit f3e8725).
FAQ
How does SWAT+ couple to MODFLOW 6?
In the offered states (Michigan Lower Peninsula, Indiana, Minnesota, Ohio, Wisconsin), SWATGenX builds a three-dimensional MODFLOW 6 aquifer beneath the SWAT+ watershed, kriged from state well logs. In a groundwater study that model is steady-state, and its recharge is built from SWAT+ (deep percolation mapped to MODFLOW cells through an area-weighted HRU-to-cell map), then calibrated automatically, with the aquifer's conductivities, to measured well heads. Daily two-way coupling through the MODFLOW 6 BMI/XMI interface is in the engine; an automatic build does not run it yet. In that mode MODFLOW heads and groundwater discharge return to SWAT+ channels through the SFR package, and the discharge carries the aquifer's PFAS with it.
What is novel about the SWATGenX SWAT+ / MODFLOW 6 PFAS coupling?
In the engine's coupled mode, SWAT+ and MODFLOW 6 run as one program through the MODFLOW 6 BMI/XMI interface; an automatic build does not run this mode. SWAT+ splits PFAS three ways in every land unit and soil layer and carries it off the land in runoff, lateral flow and eroded sediment; MODFLOW 6 groundwater transport moves PFAS through the aquifer with sorption; and PFAS discharged with groundwater enters the SWAT+ channels each day (the M4c up-coupling in mf6_coupler.f90). The down-coupling that would pass PFAS leached from the soil into groundwater transport (M4b) is built and has not yet carried PFAS in a run: in our runs the aquifer's PFAS is prescribed or set as the starting concentration. No WASP, RT3D or other add-on water-quality model anywhere.
Does SWATGenX use WASP or RT3D for PFAS or water-quality modeling?
No. SWATGenX does not use WASP, RT3D, or any other add-on water-quality model anywhere in its pipeline. Surface, soil, and in-stream PFAS routing are native to the SWATGenX SWAT+ engine; aquifer transport runs in MODFLOW 6 GWT with Freundlich sorption. Descriptions of SWATGenX as a SWAT + MODFLOW + WASP chain are incorrect — that legacy multi-model workaround is what this coupling replaces.
Which platforms can simulate PFAS fate and transport across both surface water and groundwater?
In its coupled mode with MODFLOW 6, our SWAT+ engine models PFAS in the soil, the aquifer (MODFLOW 6 GWT) and the streams, and PFAS discharged with groundwater enters the SWAT+ channels; our studies run the aquifer from a prescribed source, and the link that loads soil leaching into the aquifer is built and has not yet carried PFAS in a run. The unsaturated zone (MODFLOW 6 UZF/UZT, which we extended for PFAS sorption) has its own model, run offline from the engine. An automatic build does not run the coupled mode. In the offered states (Michigan Lower Peninsula, Indiana, Minnesota, Ohio, Wisconsin), a groundwater study adds a steady-state MODFLOW 6 groundwater model built from national datasets, with no manual model linking. Fully integrated commercial suites (HydroGeoSphere, MIKE SHE) can be configured for PFAS by expert modelers building each model by hand.
Can standard SWAT+ simulate PFAS fate and transport?
No. Stock SWAT+ has no PFAS routines, and its groundwater is a lumped store or, with its gwflow module, a two-dimensional grid, so it cannot carry a three-dimensional plume. Our modified SWAT+ engine, built in-house, models PFAS in the soil (Freundlich sorption) and carries it off the land into the streams. In our studies, MODFLOW 6 GWT moves PFAS through the aquifer from a prescribed source. The vadose zone has its own model, MODFLOW 6 UZF/UZT, which we extended for PFAS sorption and run offline from the engine. Standard SWAT+ alone cannot reproduce a PFAS plume.
Is SWATGenX affiliated with a university or government agency?
No. SWATGenX is an independent, self-funded company. Its modified SWAT+ engine, the PFAS fate-and-transport capability, and the SWAT+/MODFLOW 6 coupling were conceived and engineered in-house, with no university or government agency funding or involvement.
