Case Study · Coupled Surface Water-Groundwater

Barron Lake — A Fully-Coupled Lake-Aquifer Model

Building a coupled SW-GW simulation of Barron Lake (Niles, Michigan) with 3D T-PROGS geology, watershed-scale overland flow, shapefile-driven transient boundary conditions, and pumping augmentation.

Site: Barron Lake, Niles, Michigan · Period: 135-day transient starting 6/25/2013 · Observations: Lake levels 2006–2013 + 11 private monitoring wells
Lake-Aquifer Coupling T-PROGS 3D Geology Watershed Solver Shapefile BCs Transient Simulation ≈ 2.5 hours
Case summary

This case study showcases a fully-coupled surface water-groundwater model of Barron Lake in Niles, Michigan. The lake is represented as a two-way head-dependent feature whose stage is computed as part of the coupled process — groundwater-lake exchange, runoff input from the watershed, and pumping augmentation all contribute to the lake water balance simultaneously.

The model integrates features that no single quick tutorial covers end-to-end: a T-PROGS 3D geologic model from Michigan Wellogic borehole data drives the aquifer conductivity field; the Watershed / Overland Flow Solver runs alongside the groundwater solver; shapefile-imported zones provide transient stage boundary conditions from 11 private monitoring wells; and a pumping augmentation well moves water from the deep aquifer into the lake on a transient schedule. All data — domain polygon, lake polygon, bathymetry, geology, pumping and stage time series, boundary-condition shapefiles — come from provided files.

The site and the monitoring story

Barron Lake sits in a glacial terrain near Niles, in southwestern Michigan's Lower Peninsula. The lake has been monitored since 2006, with stage records through 2013. Since 2013, groundwater levels have been recorded at 11 private wells surrounding the lake — enough spatial coverage to infer boundary-condition dynamics but not so many that local flow gradients can be interpolated with high confidence.

The system has three distinctive features that drive the modeling approach:

1. Load domain and set baseline aquifer attributes

The model starts by loading a pre-defined domain polygon via LoadModel using the provided Domain.txt. Domain-wide aquifer attributes are then assigned via DomainAttr:

World-scale MAGNET4WATER interface with DrawDomain menu expanded, showing DM from a txt file option
Figure 1Loading the domain polygon from a provided text file (Domain.txt).
Map display zoomed to Barron Lake area showing red rectangular model domain polygon around the lake
Figure 2Domain polygon loaded and displayed — centered on Barron Lake (visible in blue).

The aquifer parameters to assign at the domain level:

Domain attributes
  • Specific Yield: 0.08
  • Conductivity: deferred to the DM zone (see step 2) — domain value is ignored
  • Specific Storage: 1×10⁻⁶ 1/ft
  • Top Elevation: DEM (default)
  • Bottom Elevation: Data Center — Michigan aquifer thickness layer
  • Surface Drainage Discharge: 1/day (default)
  • Recharge: Data Center — Michigan spatial data layer
Aquifer Attributes menu with Specific Yield 0.08, Specific Storage 1e-6, Top Elevation DEM, Bottom Elevation Data Center, and Recharge Data Center all configured
Figure 3Aquifer Attributes window — all properties configured except Conductivity which will be set at the zone level from T-PROGS output.

2. Import a T-PROGS 3D geology model as the conductivity field

The aquifer conductivity field comes from a pre-computed Transition Probability (TP) geostatistical model built from Michigan Wellogic borehole data. To apply it to the aquifer:

DM zone + borehole simulation

Create a zone with the same geometry as the domain using Conceptual Models Tools → Zones → Zone=DM — a "domain-matching" zone that inherits the domain geometry but can carry zone-specific attributes.

Map display showing Zone=DM menu option creating a zone with identical geometry to the domain polygon
Figure 4Creating a DM Zone with identical shape/size to the domain.

Inside the DM zone's Flow Properties, check Conductivity and select Borehole Simulation as the sub-option. Click the options button to open Borehole Simulation Options. Check Import and browse to BarronLakeTP.tp (the T-PROGS result file). Assign typical x-direction conductivity values for the 4 material types identified by the geology model:

Typical Kxx per material
  • Material 1: 53 ft/day (coarse sand/gravel)
  • Material 2: 5 ft/day (fine sand)
  • Material 3: 0.01 ft/day (silt/clay)
  • Material 4: 0.001 ft/day (very fine clay/till)

Use defaults for Kxx/Kyy, Kxx/Kzz (horizontal isotropy, 10:1 vertical anisotropy).

Flow Properties tab of Zone Attributes with Conductivity checked and Borehole Simulation selected as sub-option, plus the Zone Name and Type settings
Figure 5Zone Flow Properties — Borehole Simulation selected for Conductivity.
Borehole Simulation Options dialog showing BarronLakeTP.tp imported, with Material table for 4 materials having Kxx, Kxx/Kyy, Kxx/Kzz, porosity, Sy, Ss columns
Figure 6Borehole Simulation Options with BarronLakeTP.tp loaded and material-specific K values assigned.
Why this matters: Rather than using a single representative K for the whole aquifer or a simple 2D K raster, T-PROGS produces a fully 3D geologic field that honors observed stratigraphic sequences from borehole data. Each cell in the grid is assigned to one of 4 material types based on the TP simulation, and the K values above apply based on that assignment. This is the most realistic geologic representation IGW-NET supports.

3. Configure overland / watershed modeling

Still inside the DM zone's Flow Properties, click the Overland Flow… button towards the bottom-right. This opens the Surface Water Overland Flow Options menu. Check Overland Flow to direct IGW-NET to simulate land-surface hydrologic processes — runoff, recharge, evapotranspiration, snowpack dynamics.

Overland flow inputs (all from Data Center)
  • Land Use and Cover: raster from Data Center
  • Rainfall: From Rain Gauges → From Data Center
  • Temperature (min and max): from Data Center
  • Soil Type: raster from Data Center; open Lookup Table and change all CtaO values to −1.0 (this tells IGW-NET to pull initial soil moisture from a provided file rather than computing from type)
  • Root Zone Depth: raster from Data Center
  • EVT: Priestley-Taylor Equation with default adjustment factors
  • Snowpack: enabled with default parameters
Surface Water Overland Flow Options menu showing Land Use and Cover tab with Manning coefficient and other surface parameters
Figure 7Surface Water Overland Flow Options — Land Use and Cover with Manning roughness values for different surface types.
Climate tab of Overland Flow Options with Rainfall From Rain Gauges selected, Temperature enabled, and Load Rainfall Data dialog showing From Data Center option
Figure 8Climate tab — rainfall and temperature sourced from the MAGNET4WATER Data Center.
Soil Type tab with Raster from Data Center selected, Lookup Table button highlighted, and full soil parameters listed
Figure 9Soil Type tab — raster from Data Center, with Lookup Table accessible for overrides.

4. Load the lake polygon

Load BarronLake.txt as a zone via the text-file import. Two prompts require attention: tolerance (for polygon smoothing) should be 0 (no smoothing applied); "delete all existing attribute zones" should be Cancel (keep the DM zone intact).

Map showing lake polygon loaded from BarronLake.txt with tolerance=0 prompt dialog and keep-existing-zones confirmation
Figure 10Loading the lake polygon — tolerance 0 (no smoothing) and preserving existing zones.

5. Parameterize the lake — two-way coupling with bathymetry and stage

In the lake zone's Zone Attributes, navigate to the Source and Sinks Head Dependent tab and check Two-way Head Dependent. Configure:

Lake configuration
  • Initial lake level (Stage, Const): 230.0259392 m (from observations at simulation start)
  • Leakance: 0.1 1/day
  • River Bed: -999999 (sentinel indicating a bathymetry file will be used; DEM is the reference)
  • IsBathymetry option: selected; Import WaterDepth.txt
  • Stage: check From coupled SW/GW modeling — this tells IGW-NET that stage is computed as part of the coupled process, not prescribed
Head Dependent Sources and Sinks tab with Two-way Head Dependent checked, lake name, Const stage 230.02, From coupled SW/GW modeling checked, River Bed -999999, IsBathymetry with WaterDepth.txt imported
Figure 11Lake zone as two-way head-dependent — with bathymetry and coupled stage calculation.

Click the From coupled… button to open the Surface Water Source and Sink interface. Configure transient inputs:

Surface Water Source and Sink dialog with SW Prescribed Source/Sink, Runoff Flow Rate, Hydraulic Outlet, Precipitation, Evaporation, Snow Melting, and SW Stage Measurement options
Figure 12Surface Water Source and Sink dialog — all lake water-balance components configured.

6. Activate the Watershed Solver

Open DomainAttr and navigate to Simulation Settings. Click the Watershed Solver button.

Watershed solver settings
  • Number of SW sub-time steps: 1 (one surface-water time step per groundwater time step)
  • Import Initial Soil Storage: check Import; load Cta0000.T first, then Cta0000.V
  • SW Infiltration as GW Recharge: checked (couples SW infiltration directly into GW recharge)
  • Overland flow solver: non-process-based (default)
Simulation Settings tab with Watershed Solver button highlighted, and Watershed Model Solver dialog showing SW sub-time steps, soil storage imports, infiltration-as-recharge, and rainfall duration parameters
Figure 13Watershed Solver configuration — coupling SW infiltration as GW recharge.
Concept reminder: With the Watershed Solver active, Manning's n values stored on polyline vertices are actually used for channel flow computations. Without it, Manning's n is saved to the model file but has no effect. See Manning's n is usually ignored.

7. Add the lake augmentation well

The augmentation well extracts water from the deep aquifer and delivers it to the lake — a common management strategy for small recreational lakes with marginal water balance. Draw a well anywhere using DrawWell, then correct coordinates in the Well Input Options menu:

Well configuration
  • Latitude: 41.8479458145246
  • Longitude: −86.1756223309731
  • Transient pumping rate: check Transient, load Qpumping.csv (the time-varying pumping rate)
Map showing model domain with newly placed augmentation well and Well Input Options menu displaying coordinates and Transient pumping enabled
Figure 14Augmentation well placement with precise coordinates and transient pumping schedule.

8. Transient boundary conditions from a shapefile

Time-varying boundary conditions around the lake perimeter are based on regional flow patterns and water-level records at 11 private wells. They're modeled as transient "rivers" with very high leakance (mimicking prescribed-head BCs) but conceptualized as two-way head-dependent source/sink zones.

Import the shapefile

Conceptual Model Tools → Zones → Zone from a shapefile opens the Shapefile Import Options interface. Upload StagePolygons.shp, .dbf, .prj (all three required). Filter by MUNICIPLTY and select all entries. Click Next.

Shapefile Import Options with three files uploaded, Select Shape Record Options showing MUNICIPLTY filter with multiple zones selected like Stage_Wlekllinski Stage_Nelson Stage_Kutcheck Stage_Kelly VirtuaPts1 VirtuaPts2
Figure 15Shapefile import — 5 stage polygons filtered by MUNICIPLTY attribute.

Under Select Attributes Options:

Select Attributes Options with Used as Zone and Shape-specified chosen MUNICIPLTY, Two-way flux checked, group name River, Constant water depth 1.0, Leakance 5000 1/day
Figure 16Attribute mapping — Shape-specified zone naming and two-way flux with very high leakance.

Add time-varying stage to each zone

For each imported zone:

Transient Data Input dialog showing loaded Stage CSV with time-value pairs starting at 0,228.109272 with multiplier to meter
Figure 17Transient Data Input — loaded stage time series for a boundary-condition zone.

9. Grid, layers, and transient flow settings

Final simulation settings
  • Grid NX = 80 (80 cells in west-east direction)
  • Number of SubLayers = 5 (checked)
  • Modeling Transient Flow: checked
  • Start date: 6/25/2013
  • Time step: 1 day
  • Simulation Length: 135 days
  • Overwrite with Steady State Solution at t=0: checked (IGW-NET first solves steady state, then uses that as initial condition)
  • Recharge threshold: Recharge = 0 when K ≤ 0.005 ft/day
Simulation Settings with Grid NX=80, SubLayers=5, Modeling Transient Flow checked with 6/25/2013 start, 1 day time step, 135 day simulation length, Overwrite Steady State checked
Figure 18Transient flow simulation configuration — 135 days starting from a steady-state initial solution.

10. Run and analyze the coupled simulation

Simulation Tools → SIMULATE. Accept the suggested projection. The status bar reports progress; after the first time step (1 day) is solved, head contours and velocity vectors appear over the domain.

Analysis Tools → Analysis → Display Charts opens the full chart suite. Configurations of note:

Simulation in progress view with map display showing head contours, velocity vectors, and chart panels for SW Lake Level, Max Distance, Cross Section, and Monitoring Well Time Series
Figure 19Mid-simulation view — head contours and velocity vectors developing with charts actively updating.
Cross-Section Diagram showing layered conductivity structure from T-PROGS with red high-K and blue low-K horizons, and lake level chart showing simulated vs observed water levels
Figure 20Cross-section through the lake showing the T-PROGS geologic heterogeneity (red = high K, blue = low K) with velocity vectors around the lake.
Final results view with map, SW Lake Budget Chart showing inflow outflow components, lake level chart comparing simulated blue line to observed red dots, and cross-section
Figure 21Results at ≈ 58 days — lake level chart shows tight match to observed (red dots); lake budget chart quantifies storage, outflow, runoff, precipitation, and evaporation components.
Final simulation result at 135 days with prompt Flow max simulation time reached, lake budget showing all balance components, observed versus simulated lake levels tracking closely throughout the 135 day period
Figure 22Simulation complete at 135 days — observed and simulated lake levels track closely throughout, validating the coupled SW-GW model.
Model validation: The simulated lake level tracks the observed records closely across the full 135-day period. The lake budget chart decomposes the water balance into its constituent flux components — inflow from groundwater, outflow to groundwater, runoff from watershed, precipitation, evaporation, and storage change. This level of decomposition is only possible because the model is fully coupled; a groundwater-only or surface-water-only model would miss the lake-aquifer exchange entirely.

Technical notes and advanced features exercised

This model exercises several advanced platform features that are each touched by individual quick tutorials but rarely combined. The coupling patterns are worth noting:

Source Provenance

Original document
Barron Lake Integrated Model tutorial v1 (PDF)
Site location
Barron Lake, Niles, Michigan — approximately 41.85°N, 86.18°W
Monitoring period
Lake levels: 2006-2013 | Groundwater monitoring: 11 private wells, 2013–
Simulation period
135 days starting 6/25/2013
Geology source
Michigan Wellogic borehole database; T-PROGS geostatistical realization (BarronLakeTP.tp)
Platform
IGW-NET / MAGNET4WATER with Watershed / Overland Flow Solver active
Last reviewed
2026-04-20
Chapters that teach the techniques used here
📘 Users' Reference Manual: Ch. 13 — Nested Modeling (parent + submodel) · Ch. 14 — Surface Water as BC · Ch. 15 — Coupled Lake-Aquifer · Ch. 9 — Transient Simulation · Ch. 18 — Calibration
📖 Science foundation: Pinder §5 Modeling More Details (lakes, streams, nesting)