I generated contours from a GeoTIFF DEM with WhiteboxTools' ContoursFromRaster. When I sample the DEM at the contour vertices, the values don't match the elevation the contour claims, and the lines don't line up with the ones from gdal_contour. Is WhiteboxTools putting the contours somewhere different, and which one is right?

A GeoAgent for Geospatial Data Analysis and Visualization - opengeos/GeoAgent

Download WhiteboxTools v2.3 for your Windows, Linux &/or MacOS operating system. WhiteboxTools is an advanced geospatial data analysis engine.

For years, QGIS users have relied on external toolsets from processing providers such as SAGA, GRASS, WhiteboxTools and PCRaster for hydrological analysis. These tools are powerful, but they also intr...

One of the most exciting phases in the EAGLE Earth Observation MSc is the moment when our students open the door to the broad ecosystem of spatial scientific software. Over the course of the semester, they dive into a range of tools—QGIS, GRASS GIS, Blender, WhiteboxTools, SAGA, Orfeo Toolbox and more—each with its own philosophy, […]

YouTube video by Hans van der Kwast

For years, QGIS users have relied on external toolsets from processing providers such as SAGA, GRASS, WhiteboxTools and PCRaster for hydrological analysis. These tools are powerful, but they also introduce challenges: installation issues, inconsistencies across operating systems and versions, and workflows that break when dependencies change....

For years, QGIS users have relied on external toolsets from processing providers such as SAGA, GRASS, WhiteboxTools and PCRaster for hydrological analysis. These tools are powerful, but they also intr...

Welcome to the Whitebox Geospatial. The home of the open-source, fast, innovative, and company geospatial software, WhiteboxTools.

Trying to create a hydro-corrected DEM using WhiteboxTools (breach-then-fill: BreachDepressionsLeastCost + FillDepressions). In some places, due to DEM error, there's a dam-like blockage in the DEM across the stream. The fill corrects this by raising the entire stream length upstream of the block, flooding the channel with an artificial flat. Increasing the breach search distance doesn't help. Anyone know how to fix this? 30 m ALOS DSM, UTM 45N.

When delineating a watershed using QGIS 3.44.11 (Solothurn) on Windows 11 with a WhiteboxTools-based flow, I created the fill dem and then the stream_order file. However, the stream_order file came completely blank and contains no identifiable data, even though the file repository shows 2000 KB of information. When I add it to layers in QGIS and place it at the top, with all other layers turned off, it remains blank and shows nothing. I've already tried everything possible in "Symbology" and zoomed to the layer, but the problem persists. Can anyone tell me how to create a visible stream_order file using WhiteboxTools, or how can I delineate my watershed using standard QGIS tools?

ArcGIS Python Toolbox for WhiteboxTools. Contribute to opengeos/WhiteboxTools-ArcGIS development by creating an account on GitHub.

I am experimenting with the WhiteboxTools via the WBT library in R. This is to design a scriptable and open-source workflow to extract stream networks from a digital elevation model (DEM). From Archydro, I am used to getting a vectorized river network with topologic information. Specifically, each link in the river network would have a to_node and from_node id, i.e., information about where the link originates and ends (as a unique identifier, not coordinates). This information can then be used for all sorts of connectivity analyses. Does anyone know if WhiteBox has similar functionality? I can assign individual IDs to stream links (whitebox::wbt_stream_link_identifier) and extract those IDs into a vector river network (whitebox::wbt_raster_streams_to_vector), but that does not give me information about upstream and downstream nodes.

I have acquired the DEM raster for a watershed area. I want to first calculate the flow accumulation using D8(Deterministic 8-Node) algorithm. Earlier in our lab people have used GRASS in Python to calculate flow accumulation. Now when I am doing it and looking up for how people are doing it now, new libraries and functions are being used. For example, pysheds, RichDEM, WhiteboxTools, and also it could be done through using GRASS library. One could also write the code for D8 on their own. What I want to know, which of the libraries and frameworks should I go with? I also want to do later many downstream tasks and calculate other primary and secondary features.

I am experimenting with the WhiteboxTools via the WBT library in R. This is to design a scriptable and open-source workflow to extract stream networks from a digital elevation model (DEM). From Archydro, I am used to getting a vectorized river network with topologic information. Specifically, each link in the river network would have a to_node and from_node id, i.e., information about where the link originates and ends (as a unique identifier, not coordinates). This information can then be used for all sorts of connectivity analyses. Does anyone know if WhiteBox has similar functionality? I can assign individual IDs to stream links (whitebox::wbt_stream_link_identifier) and extract those IDs into a vector river network (whitebox::wbt_raster_streams_to_vector), but that does not give me information about upstream and downstream nodes.

I am conducting a hydrologic analysis of DEMs. Suppose that I have the following basins in an area as shown below:. I need to get the cascading order of each of the basins. In other words, I need to know the next downstream basin for each one of those basins. Is there a function that can do this in QGIS, Whiteboxtools, or R. I am aware of the trace downstream function but it gives the flow line to the outlet, not the next downstream basin.