HEC-RAS 6.7 Beta 4

Reported problems with previous versions can be seen by choosing the Versions drop down in the upper right corner of this page.

HEC-RAS 6.7 Beta 4

LW HW/LW TW Position Column Value Always Saves as LeftOverbank in RAS Mapper.

Stop Editing (resulting in a file Save operation) in RAS Mapper will cause all lateral structures to change their LW HW Position and their LW TW Position value to LeftOverbank.  Saving in the geometry schematic does not cause this issue. Workaround: Beta 4a fixes this issue, download HEC-RAS 6.7 Beta 4a here.

RESOLVED

Floodway Encroachments - Large Terrain.Encr Changes

The wave fill method for creating the Encroached Terrain (Terrain.Encr) would create large changes ("blocky" Terrain) in Terrain elevations.  Often this is due to a higher water surface upstream (acceptable) propagating to downstream areas. However, sometimes the poor terrain resulted from an unsuccessful wave fill attempt to create continuous watershed drainage (intended for rain on mesh models).

RESOLVED

Reference Points - Observed Stages Not Plotting

Observed Stage data for Reference Points are not plotting. High Water Mark Data (single value) do plot.  Workaround: Use Reference Lines.

RESOLVED

Pipe Network Limit on number of Junction nodes that have 3 or more connections

There is a limit of 900 Junctionnodes that have 3 or more conduit connections of. If this limit is exceeded, a fortran error will prevent the compute from completing. There are no workarounds aside from thinning out the pipe network to less than 900 of these locations.

RESOLVED

Geometry pre-process error message "Cannot recompute 2D Property Tables - No Terrain is associated with this geometry".

When terrain files are not within the project folder (or project subfolder), users who run the geometry pre-processor will see this error message.  Workaround: There are two workarounds.  The first work-around is leave RAS Mapper open when doing a simulation. The geometry pre-processor will be able to find the terrain regardless of where it is relative to the project.  The second work around is move the terrain files so that they are in or within the project folder.

IN PROGRESS

Export Layer → As Line Contours Not Producing Line Contours

For some terrains and tif files, doing Export Layer → As Line Contours is not producing any vector lines.   The vector contour algorithm can only handle so many lines at once, if there are too many lines it will fail.  Workaround: Use a bigger cell size or a larger contour interval when making vector contours.

FUTURE VERSION

1D elements are not computing infiltration losses when finite volume solution is used

1D elements are not computing infiltration losses when the finite volume method is selected. This will result in the total precipitation entering the 1D system, not excess precipitation. 

FUTURE VERSION


Unable to Import WPC - QPF data in GRIB2 format

The National Weather Service's Weather Prediction Center provides 2 national gridded precipitation products in GRIB2 format: Quantitative Precipitation Estimates (QPE) and Quantitative Precipitation Forecasts (QPF). Currently, RAS is unable to import the QPF dataset due to its compression type. WorkaroundUse HEC-MetVue or HEC-Vortex to convert the QPF data to DSS before use in RAS. 

FUTURE VERSION

Unable to Create Terrains from GeoTIFFs Exported from CAD Application

HEC-RAS geospatial libraries cannot determine the projection data stored in GeoTIFFs exported from a common CAD application. This results in a failure when importing the geotiff to a RAS terrain. 
WorkaroundReproject the terrain to a desired projection in a GIS application before importing. Alternatively, import the terrain in RAS before defining a projection in Mapper, then set the appropriate projection (spatialreference.org) following import. 

FUTURE VERSION

GDAL Conflict when Opening RAS Mapper

"Error initializing the GDAL path variables. Please check HEC-RAS installation" error message is displayed when attempting to open RAS Mapper.


1 RESOLVED - issue is fixed and will be available in the next release.
2 IN PROGRESS - issue is currently being worked on.
3 IMPROVED - the next version includes an incremental improvement but not a total fix.
4 FUTURE VERSION - this requires a structural change or major development. The team will add it to a future version if funding permits.