GCS GUI documentation

This webpage includes the documentation for the Geomorphic Covariance Structure (GCS) Analysis Tools Graphic User Interface (GUI).

You can find the repository here.

Included files

• Graphic user interface executable script, gui_tkinter.py

• Python files defining GUI implemented function/methods.

• A copy of pre-requisite executables from RapidLasso’s LAStools.

• A copy of the ‘Breeze’ GUI theme.

Pre-requisite packages

• arcpy with a valid Spatial Analyst license.

Attention

The GUI must be ran using a clone of the default ArcPro Python 3 environment!

• scipy

• pillow - https://python-pillow.org/

• plotly - https://plotly.com/

• seaborn - https://seaborn.pydata.org/

• openpyxl - https://openpyxl.readthedocs.io/

All non- arcpy packages can be installed to the cloned ArcPro Python environment by simply using the ArcPro Python Package Manager or via conda in the command line:

$ conda activate ...\ESRI\conda\envs\arcgispro-py3-clone\python.exe
$ conda install -c conda-forge scipy
$ conda install -c conda-forge pillow
$ conda install -c conda-forge plotly
$ conda install -c conda-forge seaborn
$ conda install -c conda-forge openpyxl

Setting up

Create a folder containing following:

• LAS/LAZ point cloud data files with spatial extents/footprint that capture a river valley’s in-channel topography. Either bathymetric LiDAR or traditional LiDAR collected during dry channel conditions.

• Any shapefile (.shp) from the LiDAR project’s metadata that has a spatial reference frame matching the point cloud data. Can also be manually created based on project metadata files.

• A shapefile (.shp) defining the analysis area of interest (AOI). Projected in a spatial reference frame with desired analysis units (Meters or US Feet)This shapefile’s spatial reference is applied to all output files.

• A folder (within the top level directory) containing only 4-band, 1m- resolution NAIP imagery .jp2 files that cover the AOI.

Bugs and errors

I would appreciate if all bugs and feature requests be made via out GitHub Issues page_. .. _page: https://github.com/xaviernogueira/GCS-Analysis-Tools/issues

If you prefer a more direct approach, do not hesitate to contact me via email at xavier.rojas.nogueira@gmail.com with bug reports, questions, or other feedback.

I will try to respond expeditiously, and update the software when necessary.

Processing steps

• Prepping LiDAR data from processing
  • Inputs
  • Relevant outputs
  • Applied method flow chart
  • Example of a correctly set up input directory
• Generating a ground-surface DEM from LiDAR data
  • Inputs
  • Relevant Outputs
  • Applied method flow chart
• Generating a thalweg centerline + elevation profile
  • Inputs
  • Relevant outputs
  • Applied method flow chart
• Thalweg based DEM detrending
  • Inputs
  • Slope breakpoint selection example
  • Relevant Outputs
  • Applied method flow chart
• Selecting key flow stage heights + refining center-lines
  • Inputs
  • Outputs
  • Key flow stage selection example
  • Generating key flow stage centerlines
  • Applied method flow chart
  • Draft centerline editing examples
• Extracting Geomorphic Covariance Structure (GCS) series
  • Inputs
  • Extracted cross-sectional values
  • Choosing cross-section lengths
  • Using a clip polygon (optional)
  • Applied method flow chart
• GCS stage analysis outputs
  • Methodology + motivation
  • Outputs
• GCS nesting analysis outputs
  • Methodology + motivation
  • Outputs
• Export to River Builder
  • Real world topography to River Builder
  • GUI inputs
  • Outputs
  • Examples

Information

• Background geomorphology
  • Geomorphic Covariance Structures (GCS) video lectures
  • Flow convergence routing (FCR) theory
  • Geomorphic Covariance Structures (GCS) and FCR landforms
  • Example: GCS with landform classification
• Literature
• Glossary
• Acknowledgements

Indices and tables

• Index

• Module Index

• Search Page