Skip to content

Feature request, publish a QGIS plugin #14

Open

Description

@jo-chemla

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

Activity

  1. cjcrosby commented on Jun 9, 2026

    @cjcrosby

    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.

  2. jo-chemla commented on Jun 10, 2026

    @jo-chemla
    Author

    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!

  3. jo-chemla commented on Jun 23, 2026

    @jo-chemla
    Author

    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.

    https://rem.prod.heritagewatch.ai/ (repo)

    Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions