Specifications

Two questions decide whether a modelling tool is usable. Can I build this package through the interface, and will the model I already have survive being opened and written back? The tables below answer both, per engine, including where the answer is no.

GMDSI Milford, New HampshirePROPS
GWlink PROPS stage on the GMDSI Milford model: river package cells highlighted in blue over the satellite terrain of the Milford valley, package list on the left.
The RIV package on the valley it models, terrain on, EPSG 3437. Every package in these tables is authored or inspected here.

How to read this

Build
Where the package is authored from scratch. Most are built in the properties panel; the grid comes from the meshing tools, and time series are authored as curves and attached to any target.
Existing model
What happens to a package GWlink did not create. Native means it is imported as a real link, editable afterwards. Preserved means the original file is carried through and written back unchanged, without being interpreted. Rejected means the import stops and names the offending feature.
Nothing is lossy
A package that imported and ran but quietly dropped information would be the worst of the three, because you would never find out. GWlink treats that state as a defect rather than a limitation: no package sits in it, in any engine. An import either carries your data or tells you why it cannot.

MODFLOW 6

PackageBuildExisting model
CHDInterfaceNative
DISUGrid toolsNative
DRNInterfaceNative
EVTInterfaceNative
GHBInterfaceNative
GNCPreserved
HFBInterfaceNative
ICInterfaceNative
IMSInterfaceNative
MAWInterfaceNative
NPFInterfaceNative
OBSInterfaceNative
OCInterfaceNative
RCHInterfaceNative
RIVInterfaceNative
SFRInterfaceNative
STOInterfaceNative
TS6CurvesNative
WELInterfaceNative

19 packages read and written, 18 of them built through the interface.

MODFLOW-USG

PackageBuildExisting model
BASInterfaceNative
BCFNative
CHDInterfaceNative
CLNInterfaceNative
DISGrid toolsNative
DISU_MANUALRejected
DRNInterfaceNative
EVTInterfaceNative
GHBInterfaceNative
GNCPreserved
HFBInterfaceNative
LPFInterfaceNative
OCInterfaceNative
RCHInterfaceNative
RIVInterfaceNative
SFRNative
SMSInterfaceNative
TIBInterfaceNative
WELInterfaceNative

18 packages read and written, 15 of them built through the interface.

Still to come

Packages GWlink does not read today. They are listed because a specification that hides its gaps is not a specification.

MODFLOW 6
BUY · CSUB · LAK · MVR · TVD · TVK · TVS · UZF
MODFLOW-USG
SUB · SWR
MODFLOW-2005
Not wired yet. The engine slot exists and the package shapes are mapped, but nothing is claimed until a model of yours opens, runs and writes back.

How this page is kept honest

Every row is generated from the same registry the product builds against, so the page cannot drift from the software the way a hand-written feature list does. The round trip is exercised against published models from the MODFLOW 6 example suite, FloPy and the GMDSI tutorials, each one opened, written back and run.

30 canonical models in the suite, 30 of them expected to converge.

If the package you need is on the second list, it is worth saying so when you write.

Request access

GWlink is in private beta, by invitation.

Specifications — GWlink