5 Concepts for Mastering Surface-water Modeling

Learning Aquaveo’s Surface-water Modeling System (SMS) can feel like climbing a steep hill. If you are learning Aquaveo’s Surface-water Modeling System (SMS), you are not alone. A surprisingly small set of concepts causes the vast majority of beginner errors. This short guide pinpoints the five key concepts for setting up an SMS project.

1. Feature Objects vs Computational Mesh in SMS

One of the biggest beginner mistakes in SMS modeling is assuming that anything drawn on the map is automatically used in the simulation. In SMS, feature objects (arcs, polygons, points) are instructions; the mesh is what the solver actually uses.  

If your features don’t transfer to the mesh, they don’t exist in the model. If a coverage has not been added to or linked to a simulation, it will not be used by the solver (numeric model).

Common issues:

• Boundaries not applied to mesh nodes

• Materials not assigned to elements

• Features ignored during simulation run

• Coverages not linked to simulation

Tip: Always confirm that features are transferred to mesh nodes and elements. If a boundary arc or material polygon isn’t applied to the mesh, the solver will ignore it. 

2. Snapping and Attribute Transfer Problems

Snapping controls how attributes move from your feature objects to the mesh. Snapping typically happens during the model export. Mis-snapped features lead to missing boundary conditions or roughness zones.

Common issues:

• Boundary arcs slightly off position

• Missing roughness zones

• Results that look “wrong” but don’t crash

Tip: Take the time to zoom in, check your connections, and diagnose transfer errors before running the simulation. Use the display options to see how features will snap to the mesh or grip during export. 

3. Projection and Unit Errors in SMS

If your map data, such as DEMs, is measured in meters, but your model settings are in feet, your simulation may run, but produce completely incorrect results.  

Common issues:

• Mixing meters and feet

• Using geographic vs projected coordinates

• Distorted meshes and elevations

Tip: Check projection metadata first. Reproject datasets and confirm units before creating coverages or meshes to prevent distorted grids and incorrect water velocities. 

4. Mesh Design Strategy for Better Results

Grids that are too chunky, unnecessarily dense, or poorly aligned with how the water actually flows lead to slow or unstable models.

Common issues:

• Mesh too coarse → poor results

• Mesh too dense → slow simulations

• Poor alignment with flow direction

Tip: Focus refinement where it matters most: near structures, along channels, at boundaries, and in areas with rapid terrain change. 

5. Boundary Conditions and Solver Behavior

Different SMS solvers (like SRH-2D or ADCIRC) interpret boundary conditions differently.  Assigning inflow vs. stage boundaries without understanding solver assumptions causes mass imbalance and instability leading to unstable or unrealistic models.

Common issues:

• Mass imbalance

• Incorrect water levels

• Simulation instability

Tip: Learn the basic assumptions of your chosen solver. Understand what boundary conditions actually mean to the solver. Match time steps and boundary types to the solver’s stability requirements.

Conclusion

Ready to make the most of SMS? Download SMS today and apply these 5 concepts to make modeling your projects smoother.