No articles match
Accessing 'Rangeland Analysis Platform' (RAP) Products with R8 months ago
Animated Plots | Tabular data
rgeedim Demo9 months ago
Determine Target Region | Access Images by ID | Download SRTM Topographic Diversity product | Create a local Hillshade from DEM | Working with Image Collections | Composite LiDAR DEM | Downloading individual images in a collection
Daymet Example9 months ago
Earth Engine Export Example9 months ago
Earth Engine Vector Asset Example9 months ago
Hillshade Example9 months ago
Landsat Example9 months ago
LiDAR Example9 months ago
Parallel and Distributed Processing with 'rgeomorphon'9 months ago
Working with Tiles | The Parallel Ecosystem | Two Layers of Parallelism | Scaling Up: From a Laptop to a Cluster | Scenario 1: Sequential Processing (No Parallelism) | Scenario 2: Local Multicore Processing | Scenario 3: Distributed Cluster Processing | The geomorphons() Call Stays the Same | Demo with salton | Important Notes | Beyond Parallelism: The Flexibility of LAPPLY.FUN
Installing GDAL on Windows with rgeowheels11 months ago
Overview | Getting Started: Creating a Virtual Environment | Using reticulate to Create a Venv | Detecting Available Python Versions | Installing GDAL via rgeowheels | Basic Installation (Auto-Detect Python Version) | Suppressing the Auto-Detect Message | Explicit Version Specification | Check Available Versions | Complete Workflow Example: CI/CD Integration with Reticulate | Troubleshooting | "Could not find wheels for..." Error | Python Binary Not Found | Setting Custom Python Path | CI/CD Integration Examples | GitHub Actions Workflow | Performance Benefits | Summary
Introduction to gpkg1 years ago
Background | What is a GeoPackage? | Create a Geopackage | Insert Vector Layers | Insert Attribute Table | Read a GeoPackage | Inspect Contents of GeoPackage | Lazy Data Access | Method 1: gpkg_table_pragma() | Method 2: gpkg_vect() and gpkg_query() | Method 3: gpkg_rast() | Method 4: gpkg_table() | Managing Connections
whitebox Demo2 years ago
Introduction | Setup | How whitebox works | Interfacing with R spatial packages | Working with Raster Data | WhiteboxTools R setup | Installing WhiteboxTools | Package Settings with wbt_init() | exe_path argument | wd argument | verbose argument | Long-term Package Option Settings | Running tools | Example: Compare input v.s. output with terra | Run wbt_breach_depressions() (BreachDepressions tool) | Visualize results with terra | Example: Identifying Tributaries | wbt_breach_depressions() -- Breach DEM Depressions | wbt_d8_pointer() -- Calculate Flow Direction | wbt_d8_flow_accumulation() -- Flow Accumulation | Additional Flow Direction and Accumulation Tools | wbt_extract_streams() -- Extract Stream Network | wbt_tributary_identifier() -- Identify Tributaries | Compare results | Appendix: wbt_* utility functions | wbt_help() | wbt_license() | wbt_version() | wbt_list_tools() | wbt_tool_help() | wbt_toolbox() | wbt_tool_parameters() | wbt_view_code()
wbt() method: call 'Whitebox' tools by name4 years ago
wbt() | Getting Started | Result Objects | wbt_result class | wbt_result on error | Vignette Topics | Input and Output with R spatial objects | Compare raster and terra as R raster object frontends | wbt_source(): rasters in memory, and vector data | Running Sequences of Tools | Using pipes | Coordinate Reference Systems (CRS) | Setting the CRS
whitebox Tool Metadata4 years ago
What version of WhiteboxTools are these data sets generated from? | WhiteboxTools Tool Names and R Function Names | WhiteboxTools Tool and Parameter Names | Example: Finding Tools by Parameter Type | Appendix: Tables of Function Names by Toolbox