GeoLibre 1.0: Cloud-Native GIS Built on DuckDB-WASM and MapLibre Hits Stable

GeoLibre has shipped its 1.0 release, a lightweight GIS platform that runs the same workspace on desktop (via Tauri) and in the browser, scaling down to mobile screens. The stack leans heavily on the modern web-geospatial toolchain — React, TypeScript, MapLibre GL JS, deck.gl, and DuckDB-WASM with its spatial extension — which lets users run spatial SQL queries directly in the browser against loaded layers, local files, or remote URLs streamed over HTTP range requests. Format support is unusually broad for a 1.0: cloud-native formats like GeoParquet, FlatGeobuf, PMTiles, COG, and Zarr sit alongside classic web services (WMS, WFS, WMTS, ArcGIS, STAC), LiDAR, 3D Tiles, Gaussian splats, and direct DuckDB and PostgreSQL connections.

Processing splits between in-browser and sidecar execution. Vector operations (buffer, dissolve, clip, union, and similar) run client-side with Turf.js, with an optional GeoPandas engine, while raster tools like hillshade and contour generation require a Python sidecar built on rasterio. A Whitebox toolbox handles batch geoprocessing, and a conversion menu turns legacy data into cloud-native formats. The release also includes a plugin API with a marketplace for installing third-party extensions, plus built-ins covering Overture Maps, Earth Engine, Planetary Computer, and a time slider.

The browser demo is notable for its privacy posture: it’s a static GitHub Pages deployment with no analytics or server accounts, processing all data client-side unless the user explicitly loads a remote URL or shares a project. Embed-friendly URL parameters, including a chrome-free map-only mode, target dashboard and documentation use cases. The project self-describes 1.0 as a ‘stable prototype’ — feature-rich but early — positioning it as an open, web-first alternative in a space long dominated by desktop QGIS and proprietary ArcGIS.