2D Troubleshooting – Fragmented Inundation

Written by Chris Goodell | February 18, 2015


(Initial post 19 Feb., 2015.  Updated 20 Feb., 2015).  I continue to be more and more impressed with how user-friendly and robust the new 2D feature is in HEC-RAS.  However, there are some issues to be aware of, particularly in how results are mapped.  I want to take the next two blog posts to highlight two of the more important mapping problems to be aware of.  Today’s post covers what I call “Fragmented Inundation”, or fragmented mapping.  If you’ve run some 2D data sets already, you are likely to have seen this, especially if your 2D area starts off dry, you have steep terrain, and/or your cell size is too large.  Fragmentation usually shows up just as a part of a 2D area becomes wet (i.e. very shallow depths), and tends to go away as depths increase.  Very rarely do you see fragmentation in the maximum water surface plot.  Here’s an example of fragmented inundation:
image
Notice the isolated “ponds” of water in some cells, disconnected from the water in its neighboring cells.

First off, fragmented inundation is mostly a graphical phenomenon.  By that, I mean computationally a hydraulic gradient is realized between neighboring cell centers.  Fragmentation appears simply because currently the computations in HEC-RAS result in a single water surface elevation per cell.  During computations, a hydraulic gradient over the cell is computed in 2 dimensions using the fully dynamic or diffusive wave form of the conservation of momentum equation (your choice) coupled with the conservation of mass equation.  One thing to keep in mind is that currently the cell face hydraulic parameters between the two cell centers is based on the higher of the two neighboring water surface elevations.  An average between the two cell center elevations would make more sense hydraulically, but computationally this can cause problems, particularly if there is an inflection (i.e. high ground) over the length between the centers, in which case it could result in a water surface elevation lower than then lowest ground point in the cell face.  This produces a small amount of error, particularly in steeper terrain, but is not the reason for fragmented inundation, as it is plotted in RAS Mapper.
image
When plotting results in RAS Mapper, HEC-RAS will use a single water surface elevation computed per cell and plot that.  Normally, with sufficient water depths, this would go unnoticed.  However, when water first enters a portion of a 2D area, depths are very low, and fragmentation may show up initially, especially if the terrain is steep and the cell size is relatively large.
Take the following example of a 2D mesh in profile view, where cells are too large on a steep slope.
image
Here we have two neighboring cells, with water flowing from left to right over steep terrain.  The computed water surface elevation is a graphical representation of how the conservation of momentum and continuity equations are solved.  In reality, the cell face hydraulics will be based on the water surface elevation from the upper cell center and the depth difference between the mapped water surface elevation and the computed water surface elevation at a cell face can be considered a schematization error.  However, computationally, a water surface gradient is realized between the cell centers, but when plotted, a single average water surface elevation is used for the entirety of each cell.  If the depth is too low, you’ll have dry portions in between wet portions, resulting in fragmented inundation.
Now take the same terrain, but with smaller cells:
image
With the smaller cell size, each entire cell will be completely wetted for the same computed hydraulic gradient, resulting in a smoother, more realistic-looking inundation map.
Decreasing cell size will help to reduce or eliminate fragmented inundation and the schematization error associated with how cell face hydraulics are computed, but so will strategic alignment of the cells in the direction of flow.  However, before going to the trouble to reduce cell size everywhere this happens in your 2D area, ask yourself if it’s really important to fix this.  Remember, computationally a hydraulic gradient is still realized over the length between cell centers, even when you see fragmented inundation.  The visualized fragmentation is an artifact of how the HEC-RAS computational scheme arrives at a single water surface elevation for a given cell, and plots that water surface elevation.  If you are most interested in the maximum inundation, then eliminating fragmentation at the beginning of the flood event may not be necessary.  I have been told that future versions of HEC-RAS will be able to plot sloping water surfaces over individual cells, but for now we’ll have to understand fragmented inundation and what it means in our results.
When checking your inundation maps, if you see fragmented inundation, make sure that is indeed what is going on by checking the underlying terrain.  Another, more serious mapping error called “leaking” can look similar to fragmented inundation.  Leaking is a result of high ground terrain not being captured in the cell faces, thus allowing water to seemingly flow through barriers.  This must be addressed in your model for an accurate solution.  I will discuss leaking in the next post (coming soon!).
In the meantime, keep checking back here for the official release of HEC-RAS Version 5.0.  Latest word is that it will be offered to the public by the end of this month (February 2015) or early next month.

(Thanks to Vern Bonner for providing expert critique to the initial post!)

Comments

  1. Anonymous

    on February 20, 2015

    Chris – Are you sure the problem is only graphical? I have not seen the Hydraulic Reference Manual chapter on 2D, but I understood from Gary that the Cell volume and the Face hydraulics are computed from the upper cell center elevation. If that is true, then the hydraulics are based on the histogram, stair-step, water surface as you show as Mapped WSEL, above. Generally, it would not be worth while to model steep streams in 2D, and if you do, you should use very small Cells to minimize the errors. Vern

  2. Chris Goodell

    on February 20, 2015

    Hi Vern-

    I think by saying it's purely a graphical issue may have been an over-simplification on my part. You are correct that the face hydraulics are based on the upper (higher water surface) cell's elevation. So in a sense, that can be a small amount of error introduced-small especially in typical overbank terrain (i.e. not too steep). However, the point I was trying to make was that the momentum equation and continuity equation are solved over the length between cell centers, so in that regard, a hydraulic gradient is realized between the two cell centers, even though the hydraulic parameters are based on the higher of the two neighboring cell's water surface elevations. Nevertheless, your point is a good one, in that smaller cells should be used when modeling steep streams/terrain in 2D. Thanks for pointing that out. I will edit this post to be more clear about this issue.

  3. somnath kanase

    on April 22, 2015

    Hello Sir,
    I am trying to see the extent of water at different discharge values in HEC RAS 4.1, but I am getting the same extent for different discharge values. Please help me resolving this problem.

  4. Chris Goodell

    on April 22, 2015

    Are the stages the same also?

  5. ana adeva bustos

    on June 6, 2017

    Hello Chris,

    Does this applies also when we have a river with islands and the water seems to remain in small depressions inside the island? Or is there any other reason? Thanks a lot!

  6. Chris Goodell

    on June 6, 2017

    That is a different thing altogether. If you have depressions in your terrain, and water can get there, it will stay there.

  7. ana adeva bustos

    on June 6, 2017

    Thanks Chris,

    is this due to a missing component for the subsurface flow drainage? where could i find a bit more information regarding this? Until now we are just ignoring this "problem" but for further work, like publishing etc., it will be nice to have a reference to justify that we ignore this water. Also is there any way to avoid this?

    thanks again!! 🙂

  8. Chris Goodell

    on June 6, 2017

    RAS currently has no "infiltration" option for 2D areas. Therefore, when water gets into a low depression, where there is no terrain outlet, it will remain there. You can avoid it by manually filling in the terrain, or just ignore it. You can also remove the "ponds of water" from your map manually in GIS.

  9. ana adeva bustos

    on June 6, 2017

    OK thanks a lot Chris!!

  10. Angana Borah

    on June 10, 2018

    can we get the measurement of inundation area from a 1d-2d coupled hec ras directly? or is there any other way? Thanks in advance.

  11. Emmanuel Jjunju

    on August 27, 2018

    Hello, we have a 2d model which is behaving rather weirdly. In rasmapper, we have a profile line and when we turn on the maximum WSEL, we get a rather high WSEL of 133.6 (at the centre, its a little lower at the ends) near a connection between an upstream 2d and a 1d reach. However a time series simulation shows that the water level never goes above 132.6. In fact the profiles for all the timesteps are nice and flat and generally lower than the maximum profile. We have the same interval for mapping and hydro-graph ( 1 minute). Is the maximum profile not based on these intervals? is it based on the computation interval (in our case 5 sec). Or is this a fragmented Inundation issue?

  12. Unknown

    on February 7, 2019

    1d/2d project. 1d can overflow directly to 2d area?

  13. Chris Goodell

    on February 7, 2019

    a 1D reach can flow directly into a 2D area, or vice versa with a direct connection. A 1D reach can also flow laterally into a 2D area via a lateral structure.

  14. Daniel

    on March 4, 2019

    Has this issue been resolved in newer versions of HEC-RAS?

  15. Chris Goodell

    on March 5, 2019

    Not entirely. But they have added sloping rendering which does help a lot.

  16. Ken Oko

    on July 2, 2021

    Does the latest version RAS. 6.0 address this issue?

  17. Chris Goodell

    on July 2, 2021

    Not specifically, although HEC is always improving the rendering techniques to help to mask the fragmentation. Ultimately it is up to you to understand how the computations work and how to best set up your model and view results to display your results most appropriately.

  18. Anonymous

    on February 16, 2023

    Hi Chris,

    I am modelling a flood with HEC-RAS 6.0 in 2D. When I inspect the raster of the maximum flood depth over the simulation, I find some flooded areas that are disconnected from the main floodplain flooded by the river. In many cases, these disconnected flooded areas are small ponds or small ditches which normally have water, but I did not include them explicitly in the model (only captured as depressions by a 1-meter DEM). Do HEC-RAS 6.0 simulate groundwater flow by default, so indeed we can see ‘disconnected’ flooded areas from the main floodplain (and them being simulated correctly)? Thanks in advance.

  19. Chris Goodell

    on February 23, 2023

    Groundwater is not simulated in RAS by default. Those ponds of water came from overland. Usually this happens when your initial elevation in your 2D area is higher than the terrain where those ponds are. It could also be when the water gets high enough during the simulation, water flows over to the ponds, then when the flood recedes, they are left disconnected.

  20. Alex K.

    on May 4, 2023

    I have created a routine in QGIS to automatic post -process results outlines in order to remove fragmented (not connected) areas of flood outline of HECRAS results. I find it helpfull when you need to show eliminated flood extents (by excluding areas with e.g. depth<0.3m) which have thousands of fragmented (islands) polygons.
    https://we.tl/t-jOt0ApAYrx

  21. Alex K.

    on May 4, 2023

    Wrong link above. Correct:

    Correct below:
    https://we.tl/t-GL4n1mYH4F

Add Your Comment

Leave a Reply

fifteen − 3 =


Related Posts

SEE ALL BLOG POSTS