Accounting a Model from HEC-RAS to Hydrofabric

Goals:

• To walk through the HEC-RAS data from raw model to RRASSLER artifact
• How that data model compares to the Hydrofabric data model

Outcomes and Takeaways:

• A data driven accounting of a significant portion of the RRASSLER to Hydrofabric3D Workflow
• Oriented spatially to data representation
• A “unit test” for RRASSLER artifact ingestion

This presentation

Slide layout: default     Items linked/bordered in green are cited in the tooltip on hover.

: narrative-oriented     Items linked/bordered in blue are hyperlinked to relevant resources.

Alternative Title: A baptism of HEC-RAS data formats I’m not sure which panel of this triptych is the best rendition of my current situation, but this image was too evocative of my general feelings on this topic to not include. To quote one of my giants: “These hands have been burnt by HEC-RAS project layouts before” - Seth Lawler

We make a lot of implicit assumptions about the geometric representation of the landscape, lets look at some of them as we verify the behavior of the RRASSLER code base.

Background image from: OWP template

Orienting to One Dimension

HEC-RAS conventions

Cross sections should be laid out perpendicular to where water will flow in the channel and overbank areas. Therefore, most cross section lines should be created from a minimum of four points (the end points and points at the edge of the main channel). Cross sections will also be visualized when looking in the downstream direction; therefore, they should be created from left to right when looking downstream (RAS Mapper will automatically flip the line to have the correct orientation).

Left to right, looking downstream. Start high and walks down

Orienting to One Dimension

A blend of HEC-RAS and Hydrofabric conventions

Space is arbitrary!

Orienting to One Dimension

Aside: routelink’s definition

The routelink dimensional diagram

Orienting to One Dimension

planform length =/= cross section spacing

Not space

NOAA-OWP.GITHUB.IO/RRASSLER

RRASSLER addresses this! Let’s walk through it.

Follow along!

NOAA-OWP.GITHUB.IO/RRASSLER

1) Make sure RRASSLER is installed

# remotes::install_github("NOAA-OWP/RRASSLER")  # If it asks for package updates: press 1
# library(data.table)
library(RRASSLER)
RRASSLER::marco()                           # A "hello world" test

[1] TRUE

2) Download and examine the sample data

fs::dir_tree(path = file.path(fs::path_package("", package = "RRASSLER"),"extdata","sample_ras","FEMA-R6-BLE-sample-dataset",fsep = .Platform$file.sep), recurse = TRUE)

/usr/local/lib/R/site-library/RRASSLER/extdata/sample_ras/FEMA-R6-BLE-sample-dataset
└── 12090301
    └── 12090301_models
        └── Model
            └── Alum Creek-Colorado River
                ├── ALUM 006
                │   ├── ALUM 006.O01
                │   ├── ALUM 006.f01
                │   ├── ALUM 006.g01
                │   ├── ALUM 006.g01.hdf
                │   ├── ALUM 006.p01
                │   ├── ALUM 006.p01.comp_msgs.txt
                │   ├── ALUM 006.p01.computeMsgs.txt
                │   ├── ALUM 006.p01.hdf
                │   ├── ALUM 006.prj
                │   ├── ALUM 006.r01
                │   ├── ALUM 006.xml
                │   ├── Backup.g01
                │   ├── Multiple
                │   │   └── PostProcessing.hdf
                │   └── _XsOutData
                │       └── XsOutData.txt
                ├── ALUM 107
                │   ├── ALUM 107.O01
                │   ├── ALUM 107.f01
                │   ├── ALUM 107.g01
                │   ├── ALUM 107.g01.hdf
                │   ├── ALUM 107.p01
                │   ├── ALUM 107.p01.comp_msgs.txt
                │   ├── ALUM 107.p01.computeMsgs.txt
                │   ├── ALUM 107.p01.hdf
                │   ├── ALUM 107.prj
                │   ├── ALUM 107.r01
                │   ├── ALUM 107.xml
                │   └── _XsOutData
                │       └── XsOutData.txt
                └── ALUM 114
                    ├── ALUM 114.O01
                    ├── ALUM 114.f01
                    ├── ALUM 114.g01
                    ├── ALUM 114.g01.hdf
                    ├── ALUM 114.p01
                    ├── ALUM 114.p01.comp_msgs.txt
                    ├── ALUM 114.p01.computeMsgs.txt
                    ├── ALUM 114.p01.hdf
                    ├── ALUM 114.prj
                    ├── ALUM 114.r01
                    ├── ALUM 114.rasmap
                    ├── ALUM 114.rasmap.backup
                    ├── ALUM 114.xml
                    └── _XsOutData
                        └── XsOutData.txt

Repo sample data

GFE install helper The sample data can also be grabbed here.

Refresher: The HEC-RAS model format

The Theoretical Standard

Files to Track

File grep Pattern (# denotes single numeric wildcard)	HEC-RAS Model Use
.g##	Geometry definitions
.prj	Projection (can be non-standard proj4 string defined file)
.prj	Project (same extension, defines how RAS models are wired)
.p##	Plan file, used to drive the model
.f##	Steady Flow file. Profile information, flow data and boundary conditions
.h##	Hydraulic Design data file
.v##	Velocity file
.o##	Output file
.r##	Run file for steady flow
.u##	unsteady Flow file. Profile information, flow data and boundary conditions
.x##	Run file for unsteady flow
.dss	Data files
.rasmap	Output plan

These files, followed by a .hdf, are transformations of their counterparts needed for newer versions of HEC-RAS and are automatically created as needed.

Sidecar files are fun.

Refresher: The HEC-RAS model format

Model Standards

Files to Track

File grep Pattern (# denotes single numeric wildcard)	HEC-RAS Model Use
.g##	Geometry definitions
.prj	Projection (can be non-standard proj4 string defined file)
.prj	Project (same extension, defines how RAS models are wired)
.p##	Plan file, used to drive the model
.f##	Steady Flow file. Profile information, flow data and boundary conditions
.h##	Hydraulic Design data file
.v##	Velocity file
.o##	Output file
.r##	Run file for steady flow
.u##	unsteady Flow file. Profile information, flow data and boundary conditions
.x##	Run file for unsteady flow
.dss	Data files
.rasmap	Output plan

These files, followed by a .hdf, are transformations of their counterparts needed for newer versions of HEC-RAS and are automatically created as needed.

Sidecar files are fun.

Refresher: The HEC-RAS model format

A “real-world” example

Files to Track

File grep Pattern (# denotes single numeric wildcard)	HEC-RAS Model Use
.g##	Geometry definitions
.prj	Projection (can be non-standard proj4 string defined file)
.prj	Project (same extension, defines how RAS models are wired)
.p##	Plan file, used to drive the model
.f##	Steady Flow file. Profile information, flow data and boundary conditions
.h##	Hydraulic Design data file
.v##	Velocity file
.o##	Output file
.r##	Run file for steady flow
.u##	unsteady Flow file. Profile information, flow data and boundary conditions
.x##	Run file for unsteady flow
.dss	Data files
.rasmap	Output plan

These files, followed by a .hdf, are transformations of their counterparts needed for newer versions of HEC-RAS and are automatically created as needed.

Data from the wild can be a bit unruly.

What RRASSLER is running

Aside: *_ingest_record as a “Core function?”

Aside: Implications of “geometric orientation”

Aside: “geometric orientation?”

Data “checkpoints”

Model testing: ALUM 114.prj

Major touchpoints along the RRASSLER workflow

Data “checkpoints”

RRASSLER reading

Model testing: ALUM 114.prj

.g## file

Data!

Data “checkpoints”

RRASSLER reading

Model testing: ALUM 114.prj

.g##.hdf file

Data!

Data “checkpoints”

RRASSLER copy files

Files extract consistently

.g## file

.g##.hdf file

Works (this time…)

Some points to note:

• Non-trivial: Of the 57 models OWP received, only 7 had HDF files.
• I am not competent but I am unable to run MCAT-RAS, see RRASSLER need.

Now that we’ve demonstrated that there’s parity between the different ways RRASSLER creates geospatial artifacts, let’s follow those transformations through to the hydrofabric3D repo

Data “checkpoints”

Copy data

Model testing: ALUM 114.prj

Great, I can copy files. That was in question…

Data “checkpoints”

RRASSLER Saving

Model testing: ALUM 114.prj

Great, I can save files. That was also in question…

Data “checkpoints”

Hydrofabric Lines

RAS vs Automated Transects

Hydrofab needs to flip, but match very well with previous toolings

What’s next?

Outcomes and Takeaways:

• A data driven accounting of a significant portion of the RRASSLER to Hydrofabric3D Workflow.
• Oriented spatially to data representation.
• A “unit test” for RRASSLER artifact ingestion.

Next Steps:

• Publish RRASSLER.
• Explore better paramiterization pathways for applications like T-Route.

This presentation

See more at the Official RRASSLER documentation.