docs: highlight the 1,000+ browser-based geoprocessing tools

The toolbox ships 1,009 runnable tools but the docs never said so, and
several pages still described it as sidecar-backed and desktop-only. It
has run in WebAssembly since v1.7 and carries no mobile gate, so the full
set is available on the web and Android builds too.

Author: giswqs

README.md

@@ -16,14 +16,49 @@
 
 A free and open-source, lightweight, cloud-native GIS platform for visualizing, exploring, and analyzing geospatial data. It runs everywhere you do, in the web browser, on the desktop, on mobile, and inside Jupyter notebooks, all while keeping your data local and private.
 
+It also ships **1,000+ geoprocessing tools** that run *entirely in your browser* on WebAssembly — terrain, hydrology, LiDAR, remote sensing, and vector analysis with no server, no install, and no data ever leaving your machine.
+
 GeoLibre is built with **Tauri v2**, **React**, **TypeScript**, **MapLibre GL JS**, **DuckDB-WASM Spatial**, and **deck.gl**. The same workspace runs as a native desktop app, a native Android app, in any modern web browser, and adapts responsively to mobile and small screens.
 
 - **[Launch GeoLibre Web](https://web.geolibre.app/)** — the full app in your browser, nothing to install
 - **[Download the desktop app](https://geolibre.app/downloads/)** — Windows, macOS, and Linux installers
 - **[Get it on Google Play](https://play.google.com/store/apps/details?id=org.geolibre.app)** — the native Android app
+- **[1,000+ geoprocessing tools](https://geolibre.app/user-guide/processing/#geoprocessing-toolbox)** — the full toolbox, in the browser
 - **[Get started](https://geolibre.app/getting-started/)** — install, run from source, and configure
 - **[Features](https://geolibre.app/features/)** — the complete feature list
 
+## Geoprocessing: 1,000+ tools, zero install
+
+[![The GeoLibre Whitebox toolbox running locally with WebAssembly, listing all 1,009 tools with the Regularize Building Footprints tool selected](https://files.opengeos.org/whitebox.webp)](https://files.opengeos.org/whitebox.webp)
+
+**Processing → Whitebox** opens a toolbox of **1,000+ geoprocessing tools** that
+execute in the browser through a WebAssembly runtime with native raster and
+vector I/O. There is no Python sidecar to install and no server to call — the
+tools, your data, and the results all stay on your machine, so the full toolbox
+is available on [GeoLibre Web](https://web.geolibre.app/), on the desktop app,
+and on Android alike.
+
+The tools come from the [Whitebox Next Gen](https://github.com/opengeos/Whitebox-Next-Gen-ArcGIS)
+suite plus GeoLibre's own WASM tools, and are browsable by category straight from
+the Processing menu:
+
+| Category | Tools | Examples |
+| --- | --- | --- |
+| **Vector** | 280 | overlays, buffers, joins, cleaning, topology, generalization |
+| **Raster** | 232 | algebra, filters, reclassification, zonal and focal statistics |
+| **Remote sensing** | 154 | spectral indices, band math, classification, change detection |
+| **Hydrology** | 100 | flow accumulation, watersheds, stream networks, depression filling |
+| **Terrain** | 99 | slope, aspect, hillshade, curvature, ruggedness, viewsheds |
+| **LiDAR** | 65 | point-cloud filtering, ground classification, DEM/DSM generation |
+| **Conversion** | 49 | format translation to cloud-native GeoParquet, PMTiles, and COG |
+| **Network** | 26 | connectivity, cost distance, and routing analysis |
+| **Projection** | 4 | reprojection for raster and vector data |
+
+Any tool is deep-linkable with a `?tool=` URL parameter that preselects it and
+pre-fills its form. See the [Processing Tools guide](https://geolibre.app/user-guide/processing/#geoprocessing-toolbox)
+for details, and [Geoprocessing in the Browser](https://youtu.be/W32bIQO_nG8) for
+a video walkthrough.
+
 ## Demos
 
 **Click any screenshot to open it at full resolution, or any animation to play the full-quality video.**

docs/android.md

@@ -19,15 +19,16 @@ The rest of this page is for developers building the app themselves.
 
 ## What works on Android vs desktop
 
-The Android build ships the full map workspace, Add Data, the Vector tools
-(Turf.js / in-browser GeoPandas via Pyodide), the SQL Workspace (DuckDB-WASM and
-the in-browser PGlite/PostGIS engine), the Python Console (Pyodide), geocoding,
-statistics, the AI assistant, story maps, and plugins.
+The Android build ships the full map workspace, Add Data, the Whitebox
+geoprocessing toolbox (1,000+ tools, run in the browser on WebAssembly), the
+Vector tools (Turf.js / in-browser GeoPandas via Pyodide), the SQL Workspace
+(DuckDB-WASM and the in-browser PGlite/PostGIS engine), the Python Console
+(Pyodide), geocoding, statistics, the AI assistant, story maps, and plugins.
 
 Tools that depend on a **local desktop process** are hidden on mobile, because
 Android has no Python sidecar or local helper binaries:
 
-- Processing → **Whitebox**, **Raster**, **Conversion**, **AI Segmentation**
+- Processing → **Raster**, **Conversion**, **AI Segmentation**
   (all need the Python sidecar)
 - Add Data → **PostgreSQL** (served by the local Martin tile server)
 

docs/architecture.md

@@ -68,7 +68,9 @@ Local MBTiles tiles are read through a custom MapLibre protocol backed by Tauri
 
 ## Python sidecar
 
-The FastAPI app in `backend/geolibre_server` backs the Whitebox toolbox and the format Conversion tools through a managed local processing sidecar. The desktop app starts the sidecar on demand, communicates over `127.0.0.1`, and keeps the heavier Python processing stack outside the browser bundle.
+The FastAPI app in `backend/geolibre_server` backs the format Conversion tools, the raster tools, and the optional server engine for the Whitebox toolbox through a managed local processing sidecar. The desktop app starts the sidecar on demand, communicates over `127.0.0.1`, and keeps the heavier Python processing stack outside the browser bundle.
+
+The Whitebox toolbox does **not** depend on it: its 1,000+ tools run in the browser on the `geolibre-wasm` WebAssembly runtime by default, and the sidecar is an opt-in alternative engine that can read native file paths for batch runs over a directory.
 
 The Vector tools (Processing → Vector) run client-side with Turf.js and need no sidecar. All of the tools can optionally run on the sidecar's `/vector` endpoints, backed by GeoPandas and Shapely, for projection-aware results; the sidecar reports availability through `/vector/status`, and the dialog falls back to the client engine when the optional `vector` extra is not installed.
 

docs/downloads.md

@@ -59,8 +59,9 @@ The portable build relies on the Microsoft Edge WebView2 Runtime, which is
 preinstalled on Windows 11 and current Windows 10. If the app does not start,
 install the
 [Evergreen runtime](https://developer.microsoft.com/microsoft-edge/webview2/).
-The optional Python sidecar tools (Whitebox, raster, conversion) need Python
-available just as in the installed build; everything else runs without it.
+The optional Python sidecar tools (raster, conversion) need Python available
+just as in the installed build; everything else — including the 1,000+ tool
+Whitebox geoprocessing toolbox, which runs on WebAssembly — runs without it.
 
 ## macOS installation
 
@@ -221,9 +222,10 @@ Sideloaded builds do not update themselves, so download a newer APK to upgrade.
     Android will not upgrade one into the other. Uninstall the existing copy
     (`adb uninstall org.geolibre.app`) before switching between them.
 
-Tools that need a local desktop process — the Whitebox, Raster, Conversion, and
-AI Segmentation toolboxes, and the PostgreSQL data source — are hidden on
-Android. See [Android](android.md) for the full list and for build instructions.
+Tools that need a local desktop process — the Raster, Conversion, and AI
+Segmentation toolboxes, and the PostgreSQL data source — are hidden on Android.
+The Whitebox geoprocessing toolbox runs on WebAssembly and stays available. See
+[Android](android.md) for the full list and for build instructions.
 
 ## Build from source
 

docs/features.md

@@ -156,9 +156,11 @@ the [Tutorials](tutorials/index.md); for what is planned next, see the
 - Conversion menu for Vector to GeoParquet, FlatGeobuf, and PMTiles; a generic Vector to Vector converter that translates between any supported vector formats by file extension; CSV to GeoParquet; and Raster to COG
     - In the browser build every conversion runs client-side on DuckDB-WASM, the pure-JS writers, or `geolibre-wasm` (Vector to PMTiles on a background worker)
     - The desktop app prefers the Python sidecar, whose GDAL/rio-cogeo stack reads more input formats and tiles deeper
-- Whitebox toolbox that runs entirely in the browser through a WebAssembly runtime with raster I/O — no Python sidecar required
-    - Surfaces both Whitebox tools and GeoLibre's own WASM raster tools
+- **1,000+ geoprocessing tools** in the Whitebox toolbox, running entirely in the browser through a WebAssembly runtime with raster and vector I/O — no Python sidecar required, so the full set works on the web, desktop, and Android
+    - Surfaces both the Whitebox Next Gen suite and GeoLibre's own WASM tools, filterable by source
+    - Nine categories: vector (~280 tools), raster (~230), remote sensing (~150), hydrology (~100), terrain (~100), LiDAR (~65), conversion (~50), network (~25), and projection
     - Browsable by category directly in the Processing menu, with nested subcategory submenus and an offline-bundled tool catalog
+    - A **Run locally (WASM)** toggle switches any tool between the in-browser runtime and the Python sidecar, which reads native file paths for batch runs over a directory
     - Deep-linkable through a `?tool=` URL parameter that preselects a tool and pre-fills its form, with a Copy link button that builds the shareable link
     - Batch tools run against a selected input directory
 - Vector menu
@@ -247,6 +249,6 @@ See the [Plugin API](plugin-api.md) to build your own.
 - Native Android app built from the same codebase with Tauri v2 mobile, published on [Google Play](https://play.google.com/store/apps/details?id=org.geolibre.app). See [Android](android.md)
     - A GitHub Actions workflow builds both the universal App Bundle that Play ships and signed, per-architecture sideload APKs (~40 MB)
     - A permanent `org.geolibre.app` package id, API level 36, and 16 KB page-size alignment verified in CI
-    - Tools that depend on a local desktop process (Whitebox, Raster, Conversion, AI Segmentation, PostgreSQL/Martin) are hidden on mobile, so nothing is shown that cannot run
+    - Tools that depend on a local desktop process (Raster, Conversion, AI Segmentation, PostgreSQL/Martin) are hidden on mobile, so nothing is shown that cannot run; the WebAssembly geoprocessing toolbox needs no such process and stays available
 - iOS build scaffolding on the same codebase, with Tauri iOS configuration, location permissions, and a CI workflow that signs and exports an `.ipa` when Apple signing secrets are present (bring-up: no iOS build has shipped yet). See [iOS](ios.md)
 - Installable, offline-capable Progressive Web App (PWA) build, plus a **Download Offline Area** tool that pre-caches the current map view's basemap tiles, and service-worker caching of the CDN-loaded Pyodide and PGlite/PostGIS engines so browser SQL and Python keep working offline after first use

docs/index.md

@@ -56,9 +56,9 @@ Add Data covers XYZ, WMS, WFS, WMTS, ArcGIS, and STAC services; GeoParquet, Flat
 </div>
 
 <div class="feature-card" markdown>
-### Conversion and Whitebox
+### 1,000+ geoprocessing tools
 
-Convert vector and raster data to cloud-native GeoParquet, FlatGeobuf, PMTiles, and COG from the Conversion menu, and run batch geoprocessing with the extensive Whitebox toolbox running on the optional Python sidecar.
+Run **1,000+ geoprocessing tools** — vector, raster, remote sensing, hydrology, terrain, LiDAR, conversion, network, and projection — from the Whitebox toolbox, browsable by category in the Processing menu. They execute in the browser on a WebAssembly runtime with raster and vector I/O, so there is no Python sidecar to install and the full set works on the web, desktop, and Android. Convert data to cloud-native GeoParquet, FlatGeobuf, PMTiles, and COG from the Conversion menu.
 </div>
 
 <div class="feature-card" markdown>
@@ -174,7 +174,7 @@ what comes next, see the [Roadmap](roadmap.md).
 
 - **Core workspace** — the map workspace, the `.geolibre.json` project format with Save, Open, and Share, the plugin API, and the plugin marketplace for installing, updating, and removing external plugins.
 - **Data** — browser vector import, DuckDB-WASM Spatial loading, the full Add Data surface (files, web services, cloud formats, 3D layers, and databases), and cloud integrations through the Planetary Computer and Earth Engine panels, the Overture Maps plugin, and the federal Web Services plugins.
-- **Processing** — vector tools (Turf.js with an optional GeoPandas sidecar), raster tools (rasterio sidecar with a client-side fallback), a Spectral Index toolbox, a Raster Georeferencer, a Spatial Statistics toolbox, network analysis (isochrones, service areas, OD cost matrices), the Conversion menu (GeoParquet, FlatGeobuf, PMTiles, COG), the Whitebox toolbox, and AI Segmentation via SamGeo/SAM 3.
+- **Processing** — the Whitebox toolbox of **1,000+ geoprocessing tools** running in the browser on WebAssembly, vector tools (Turf.js with an optional GeoPandas sidecar), raster tools (rasterio sidecar with a client-side fallback), a Spectral Index toolbox, a Raster Georeferencer, a Spatial Statistics toolbox, network analysis (isochrones, service areas, OD cost matrices), the Conversion menu (GeoParquet, FlatGeobuf, PMTiles, COG), and AI Segmentation via SamGeo/SAM 3.
 - **SQL and scripting** — the SQL Workspace for DuckDB Spatial SQL (with PGlite PostGIS and Apache Sedona engines), a docked Notebook panel running Jupyter beside the map (JupyterLite on the web, a JupyterLab server on desktop), a natural-language AI assistant, and an in-app Python Console.
 - **Field and collaboration** — a Field Collection tool for point, line, and polygon observations, real-time multi-user collaboration, and a scroll-driven story map builder.
 - **Map surface** — multi-provider geocoding, the Time Slider plugin, a Controls menu (Measure, Bookmark, Minimap, View State), Layout settings, runtime environment variables, and diagnostics.

docs/ios.md

@@ -34,8 +34,9 @@ Tools that depend on a **local desktop process** are hidden on mobile because
 iOS has no Python sidecar or local helper binaries and its sandbox forbids
 spawning subprocesses:
 
-- Processing → **Whitebox**, **Raster**, **Conversion**, **AI Segmentation**
-  (all need the Python sidecar)
+- Processing → **Raster**, **Conversion**, **AI Segmentation**
+  (all need the Python sidecar). The Whitebox geoprocessing toolbox runs in
+  WebAssembly, needs no sidecar, and stays available.
 - Add Data → **PostgreSQL** (served by the local Martin tile server)
 
 These are gated by a user-agent `isMobile()` check (which already matches

docs/tutorials/index.md

@@ -5,7 +5,7 @@ These tutorials walk through common GeoLibre workflows end to end. Each one is s
 ## Before you start
 
 - You can follow most tutorials in the **live viewer** at [web.geolibre.app](https://web.geolibre.app/), which is the browser build of GeoLibre. No installation required.
-- A few steps need the **desktop app**: opening and saving project files, reading local MBTiles and rasters, and the Python sidecar tools (raster processing, sidecar conversions, and Whitebox). These are called out where they appear. See [Downloads](../downloads.md) to install.
+- A few steps need the **desktop app**: opening and saving project files, reading local MBTiles and rasters, and the Python sidecar tools (raster processing and sidecar conversions). These are called out where they appear. See [Downloads](../downloads.md) to install. The Whitebox geoprocessing toolbox is not among them — its 1,000+ tools run in the browser on WebAssembly.
 - The sample dataset used in several tutorials is a public GeoParquet file of world countries: `https://data.source.coop/giswqs/opengeos/countries.parquet`.
 
 ## The tutorials