Data and Code for "Coevolving topography, patchy soils, and forest structure"

This dataset contains the data and scripts used in Coevolving topography, patchy soils, and forest structure by Rossi et al. (2026). Files are organized into five main directories:gis_data: In this directory, you will find drone_ortho.tif and a geodatabase called features.gdb. Drone data was acquired on July 21, 2021 using a DJI Phantom 4 Pro. Lidar data was acquired by the National Center for Airborne Laser Mapping (NCALM) and are archived and freely accessible at OpenTopography. While the source DEM and DSM data are not archived in this repository, the gis files provided here will allow you to geolocate examples shown in the main text. See readme.txt files for more details.accuracy_assessment: In this directory, you will find the matlab scripts and data used for accuracy assessment in an 8.1 hectare region along North Beaver Creek, Rampart Range, CO, USA. Documentation is provided within matlab files. Functions from TopoToolbox will be needed.elevation_analysis: In this directory, you will find the matlab scripts and data used to extract stream profiles and quantify changes in bedrock exposure as a function of elevation. Documentation is provided within matlab files. Functions from TopoToolbox will be needed.aspect_analysis: In this directory, you will find the matlab scripts and data used to quantify differences in bedrock exposure, canopy height, and crown density as a function of topographic aspect. Documentation is provided within matlab files. Functions from TopoToolbox will be needed.landlab: In this directory, you will find two folders called model and model_output. The model is built using the Python-based modeling library called Landlab. Specifically, this hillslope evolution model simulates depth-dependent soil creep and humped soil production on a 2D swath hillslope. Model scenarios can take a long time to run so model outputs are provided for all scenarios shown in the main text and supporting materials for this manuscript. See readme.txt files within subdirectories for more details.