Wednesday, November 6, 2013

Filtering Station Elevation Data in HEC-RAS

Written by Daniela Todesco | WEST Consultants
Copyright © RASModel.com. 2013.  All rights reserved.

I am working on a dam breach project where I’m trying to simplify a complicated model with dozens of tributaries and storage areas. In the process, I’m converting a few tributaries into storage areas (which are surrounded by other storage areas). For example, I want to convert the reach below (from 5.43 to 0.55) to a storage area. We happen to have the topographic data used to generate the original model (although we don’t have the original geodatabase), so we’re good to go. clip_image002 In order to do that, we need to delineate the storage area polygon, define new storage area connections, and generate lateral structures. The new “reach” (now a storage area) will look like the one below. clip_image003 Now we need station-elevation data for storage area connections and lateral structures. Easy, right? Well, not so fast. HEC-GeoRAS seems to have some issues exporting data when you take an existing project and try to modify shapefiles and extract data for only a portion of the entire model. It is especially difficult if you’re not the one who built the model in the first place. The shortcut is to think outside GeoRAS and obtain simple 3D station-elevation points directly from a TIN or grid for the storage area or structures you need. The bad part about that is that extracting tools in ArcGIS doesn’t really have an option to limit the number of points that are generated, and you end up with thousands of points that you can’t really use in HEC-RAS (the limit for cross section points, storage area connection weir/embankment points, and lateral structure weir points is 500). For example, in the connection called 83Coal in the figure above, I end up with over 2300 points. I’m stuck. Or so I thought… It turns out that RAS automatically “expands” its Station Elevation table to store however many points you need. In my case, 2339… image HEC-RAS will still give you an error if you try to run the model with this data (the limit of 500 points still stands for computations!), but a simple click of the “Filter” button you see in the figure above solves the problem. Voila! Hope you liked this new (for me) discovery.