1 of 41

Bathy Tooling

Jim Coll, Arash Modaresi Rad, J. Michael Johnson, Dami Eyelade, Angus Watters, Justin Singh-Mohudpur

2 of 41

If I have seen further than others, it is by standing upon the shoulders of giants.�

- Isaac Newton

3 of 41

If I have seen further than others, it is by standing upon the shoulders of giants.�

- Isaac Newton

4 of 41

Findable Accessible�Interoperable Reusable

&

Analysis-ready�Cloud Optimized

To Google Gemini: �Can you draw me a picture of loosely humanized satellite in the position of a sprinter athlete?

5 of 41

A (FIM-centric) timeline of bathymetry data

  • HEC-RAS 1D

When: 1995

Who: U.S. Army Corp of Engineers

What: A one-dimensional hydraulic solver

6 of 41

  • Discussed and set standards for FEMA flood risk zone definitions, which are widely used in establishing flood insurance requirements and rates

7 of 41

  • Set baseline for Base Level Engineering (BLE) model & mapping output and deliverables production

8 of 41

9 of 41

  • Set baseline for Base Level Engineering (BLE) two-dimensional model & mapping output and deliverables production

10 of 41

11 of 41

12 of 41

National Water Model

Version 1.0: Model Chain

5. Channel &

Reservoir

Routing

Modules

4. NHDPlus Catchment

Aggregation

(2.7M unique

catchments and

river reaches)

2. NoahMP LSM

(1 km grid)

1. NWM Forcing Engine

(1 km grid)

3. Terrain Routing

Module

(250 m grid)

2-way coupling

Forecast

Products

NWM uses NCAR supported community WRF-Hydro system

​

NWM: http://water.noaa.gov/about/nwm

WRF-Hydro: https://www.ral.ucar.edu/projects/wrf_hydro

13 of 41

Where is bathymetry needed?

14 of 41

Legacy cross section formats

.g##  - Geometry definitions

.prj  - Projection (can be non-standard proj4 file)

.prj  - project file (Defines how a model is set up to run)

.p##  – Project file, used to drive the model

.f##  - Steady flow boundary conditions

.u##  - unsteady flow boundary conditions

.q##  - quasi-unsteady flow boundary conditions

.o##  - output file

​

Other notes: 

  • The wildcards (#) are always numeric, and will always be two digits 
  • utf-8 encoding
  • These files, followed by a .hdf, are transformations of their counterparts needed for newer versions of ras and are automatically created by HEC-RAS when needed. 

15 of 41

https://webapps.usgs.gov/infrm/estbfe/

16 of 41

https://webapps.usgs.gov/infrm/estbfe/

1.8 TB Zipped

17 of 41

https://maps.austintexas.gov/FloodPro/

18 of 41

https://maps.austintexas.gov/FloodPro/

19 of 41

 

https://github.com/NOAA-OWP/RRASSLER

20 of 41

 

https://stacspec.org/en

21 of 41

https://radiantearth.github.io/stac-browser/#/external/lynker-spatial.s3.us-west-2.amazonaws.com/bathymetry/RRASSLER_public_catalog/stac/catalog.json?.language=en�&�https://lynker-spatial.s3.us-west-2.amazonaws.com/bathymetry/RRASSLER_public_catalog/model_map.html

22 of 41

​

�        ���

7

�

Baseline of learned At a Station Hydraulic Geometry

��

AHGestimation software and associated published at JOSS

https://github.com/mikejohnson51/AHGestimation/

23 of 41

Machine learning using network attributes to predict channel geometry over CONUS using AHG relations

POLARIS

StreamCat

NWM 2.1

Scaled to

Reference Fabric

24 of 41

  • Providing data (https://www.lynker-spatial.com/data) for width, depth and shape (and all AHG coefficients) ~2.7 million catchmentsThe dataset indexes bathymetry-related data resources into the National Hydrologic Geospatial Reference Fabric, enabling exhaustive watershed-level queries.
  • ML derived channel geometry paper currently under revision submitted to JGR ML

�

https://github.com/NOAA-OWP/channel-shape-ML

https://github.com/NOAA-OWP/hydrofabric

https://www.lynker-spatial.com

�

CONUS scale representations of river geometry 

25 of 41

26 of 41

27 of 41

eHydro database overview

28 of 41

29 of 41

30 of 41

31 of 41

32 of 41

33 of 41

34 of 41

35 of 41

36 of 41

Issue: Grossly inconsistent database structure

37 of 41

38 of 41

Issue: Uncertainty and accuracy of transformations

US Survey Foot�1 ft = (1200/3937) of a meter = 0.3048006096

Foot:�1 ft = 0.3048 meters

Difference of 2 ppm ~0.01 ft/mile

​

Datum uncertain in transformations:�From obs: ~0.2-0.2 m from vdatum

39 of 41

40 of 41

Terrain blender for cross section creation

41 of 41

Thank you!

Parting thoughts:

  • “real” data in FAIR form facilitates integration into CONUS+ scale applications
  • ARCO data formats make database curation and access interfaces redundant
  • Modeling inputs are application specific

Please reach out to collaborate��james.coll@noaa.gov

mike.johnson@noaa.gov

arash.rad@noaa.gov

jsmohudpur@lynker.com

awatters@lynker.com

​