You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've read from the docs this great OpenTopo/RiverREM CLI tool is built upon the methodology described by Dan Coe in Creating REMs post on the IDW method.
Would it make sense in addition to exposing it as a python script, to make a QGIS plugin (or Processing Toolbox algorithm) out of RiverREM that wraps the python script? Seems low-hanging fruit, and could simplify producing such REMs for any QGIS community user not familiar with the command line, based on the current implementation.
Most settings could probably be left default, and others could be controllable like
selecting input DEM
river centerline source: default to OSM longest river, could be user input vector layer first feature
sampling distance could be customized
exporting idw-interpolated water-surface elevation layer or not etc
Good suggestion, thanks. Not sure we have the bandwidth at the moment to tackle it, but we've talked about building more QGIS plugins to connect to OT services, so we'll add this one to the list.
Thanks for getting back and adding to the list of OpenTopography QGIS plugins, although there's no bandwidth for now!
This would be like closing the loop, circling back to the origins of RiverREM/Dan Coe workflow directly through QGIS!
For information, I built a GUI frontend to OpenTopography/RiverREM running the python processing backend, and the project later evolved into a pure-frontend REM compute engine. Thanks a lot for the great inspiration! This REM-UI does:
client-side fetching osm river (longest named, all named, all rivers) via overpass or qlever faster engine, even vector tiles
using Mapterhorn DEM data-source from @wipfli (or custom COG)
sampling elevation at discrete points along river for client-side idw
or running client-side WSE water Surface Elevation altitude-polyline interpolation EDT/JFA rather than sample-based
then detrending the REM = DEM - WSE
applied as a maplibre custom protocol, per tile, encoded as Terrarium RGB
styled via colorramp, symbology edition, contours, basemaps, slider bounds user-controlled, saved to backend gallery
served as COG via geomatico protocol if built by RiverREM on the backend, or tiled if produced on the client frontend that can be exported to COG. Can also export the raw data REM/DEM or the composited styled screenshot.
Activity
cjcrosby commentedon Jun 9, 2026
Good suggestion, thanks. Not sure we have the bandwidth at the moment to tackle it, but we've talked about building more QGIS plugins to connect to OT services, so we'll add this one to the list.
jo-chemla commentedon Jun 10, 2026
Thanks for getting back and adding to the list of OpenTopography QGIS plugins, although there's no bandwidth for now!
This would be like closing the loop, circling back to the origins of RiverREM/Dan Coe workflow directly through QGIS!
jo-chemla commentedon Jun 23, 2026
For information, I built a GUI frontend to OpenTopography/RiverREM running the python processing backend, and the project later evolved into a pure-frontend REM compute engine. Thanks a lot for the great inspiration! This REM-UI does:
https://rem.prod.heritagewatch.ai/ (repo)