Visual MODFLOW Flex 11.0 Product Release

Importing models has been massively overhauled in Visual MODFLOW Flex 11.0. Model import now uses a new, proprietary Python library based on FloPy, significantly improving flexibility and stability when importing external models.

• MODFLOW-6 models can now be imported
• SEAWAT models may now be imported
• Model grids in the DIS and DISV format can now be imported separate from other model elements
• Flow properties (such as hydraulic conductivity and storage) in LPF, NPF, and UPW formats can now be imported independent of the model import step
• Flow property package settings can be brought in during import
• Most common boundary conditions (CHD, RIV, GHB, DRN, RCH, and EVT) can now be imported independently
• Solver settings (IMS, PCG, GMG, SIP, WHS, SAMG) may now be imported
• Output control settings may now be imported

Working with unstructured grids

Unstructured grids can now be imported into Visual MODFLOW Flex and unstructured grids can now be created outside of the conceptual modeling workflow.

• Unstructured MODFLOW-6 models using DISV grids may now be imported
• DISV unstructured grids may now be imported independently
• Unstructured grids (Voronoi, quadtree) may now be created directly in the numerical modeling workflow
• 3D unstructured gridded data (such as heads or concentration results) may now be imported
• 3D unstructured gridded data can be used to set model properties such as initial heads and initial concentrations

TIN surfaces

Triangular irregular network (TIN) surfaces can now be used with your Visual MODFLOW Flex projects. The following functionalities are now supported:

• Import TINs from point shapefiles (.shp) and from Triangle .node or .ele files
• Generate TINs from existing point data objects, using linear or kriging interpolation schemes
• Generate TINs from model layers
• Use TINs to define model horizons
• Use TINs in the expression builder of other data objects
• Use TINs to define boundary condition parameters and model properties in the numerical modeling workflow

Performance, Usability, and other Enhancements

Visual MODFLOW Flex includes the following improvements for working with your models:

Usability:

• Objects in the data tree can now be reordered by dragging-and-dropping
• Runs can be given an alias, renaming them in the interface
• The coordinate reference system (CRS) selector is now searchable

Data operations:

• Attribute data from points and polygons may now be referenced in the expression builder
• Elevation data from points may now be referenced in the expression builder
• Export
  • Recharge and Evapotranspiration boundary conditions as shapefiles
  • Surfaces and TINs as point shapefiles
  • TINs as polygons
  • Water table outputs as shapefile contours or surface

Boundary conditions:

• Inactive transport areas: transport models can include explicit zones for active transport and inactive transport (ICBUND for MT3D-MS, RT3D, and SEAWAT)
• Recharge and EVT can now be assigned to specified layers:
  • Edit/assign layer in recharge/EVT boundary conditions
  • Support for RCHOP = 2, NEVTOP = 2 options at the translation step for applicable flow engines
  • The expression builder supports the layer() function which takes an elevation (from a surface or a constant values) and outputs the associated layer number (useful for e.g., assigning recharge to outcropping layers in unstructured grids)
• Specified Flux BCs can now be translated to the mathematically-equivalent WEL package file when using MODFLOW-6 (which does not include/support the specified flux BC)

Other enhancements

• Upper and lower cutoffs can now be applied when visualizing surface and TIN data objects
• When defining model horizons, surfaces that do not cover the entire model area can now be extrapolated to the model boundary
• In the PEST workflow, flux observations are now available for the MODFLOW-USG engine (consistent with other engines)
• In the conceptual modeling workflow, horizons can now be defined using a constant value, instead of always requiring a surface or TIN
• US regional settings for number and date formats are no longer required to run Visual MODFLOW Flex (however, these settings are still recommended)
• The CRS library has been expanded

For a full version history, see the Visual MODFLOW Flex readme file.