# RustGIS: Map and Analyze Geospatial Data in Pure Rust

This repository profile is provided by osrepos.com, an open source repository discovery platform.

Source: osrepos.com
Repository profile: https://osrepos.com/repo/opengeos-rustgis
Generated for open source discovery and AI-assisted research.

RustGIS is a pure-Rust GIS for mapping, analyzing, and sharing geospatial data on Windows, macOS, Linux, the web, Android, and iOS. It combines a desktop-style interface with scriptable commands, geoprocessing, and local-first data handling.

GitHub: https://github.com/opengeos/RustGIS
OSRepos URL: https://osrepos.com/repo/opengeos-rustgis

## Summary

RustGIS is a pure-Rust GIS for mapping, analyzing, and sharing geospatial data on Windows, macOS, Linux, the web, Android, and iOS. It combines a desktop-style interface with scriptable commands, geoprocessing, and local-first data handling.

## Topics

- rust
- desktop-app
- cross-platform
- geographic-information-systems
- geospatial-analysis
- remote-sensing

## Repository Information

Last analyzed by OSRepos: Tue Nov 17 2026 10:16:29 GMT+0000 (Western European Standard Time)
Detail views: 20
GitHub clicks: 8

## Safety Notice

OSRepos shares public repositories for knowledge and discovery only. Review source code, dependencies, licenses, and security implications before running or installing anything.

## Content

## Overview

RustGIS is a GIS built in pure Rust for mapping, analyzing, and sharing geospatial data. It targets Windows, macOS, and Linux desktops, WebAssembly in the browser, and Android and iOS devices, addressing the need for one GIS workflow that can run across desktop, web, and field settings.

Its command-based design connects the ribbon interface to scripting, the CLI, Python, and an AI assistant. Data stays on the user's machine unless they explicitly use network services or send data to a selected AI model. The interface is built with egui, and the project separates its data, mapping, analysis, rendering, and application layers into Rust crates.

## Key Features

- Read and export a broad range of vector and raster formats, including GeoJSON, GeoPackage, GeoParquet, Shapefile, GeoTIFF, and Zarr.
- Style, label, edit, and inspect spatial layers, with attribute tables and project-wide undo.
- Run geoprocessing, raster, terrain, hydrology, and LiDAR workflows, including tools from GeoLibre and Whitebox.
- Build repeatable workflows with ModelBuilder, command-line commands, scripts, and the Python package.
- Work with web map services, basemaps, STAC catalogs, and other listed open-data sources.
- Extend the application with sandboxed WebAssembly plugins, and connect AI assistants through supported providers or its MCP server.
- Create layouts and reports, export maps, and package projects or mobile maps for sharing and offline use.

## Use Cases

- GIS analysts can edit and style spatial datasets, run analyses, and prepare printable map layouts in one application.
- Remote-sensing and terrain users can explore raster data and use the listed raster, LiDAR, and hydrology tools.
- Researchers can script repeatable analyses through the CLI or Python and use RustGIS in Jupyter notebooks.
- Field teams can use the Android or iOS app and prepare mobile map packages or offline areas.
- Developers can add GIS commands or tools through plugins, or connect external AI clients using the MCP server.

## Our Take

RustGIS is an unusually broad, actively changing GIS project with a command-oriented design, but its very recent launch means teams should validate their specific workflows before relying on it in production.

**Good fit if:**
- You want a cross-platform GIS with desktop, browser, and mobile options and a local-first approach.
- You need workflows that can move between the interface, CLI, Python, or ModelBuilder.
- You want to evaluate a fast-moving GIS project with a broad contributor base and frequent releases.

**Look elsewhere if:**
- Your organization requires a mature GIS with a long-established operating history before adoption.
- Your workflow depends on capabilities or formats not confirmed in the README, especially in the web app, which has fewer features than desktop.
- You need to avoid Apache-2.0 licensing or do not want to review its license terms for your distribution model.

## Project Health

| Signal | Value |
|---|---|
| Status | **New**: less than six months old and changing fast |
| Last commit | 2026-11-17 (today) |
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 7 (latest v0.7.0, 2026-11-16) |
| Contributors | 66 (top contributor: 32% of commits) |
| Issues closed, last 90 days | 25+ (typically closed in 0 days) |
| Pull requests merged, last 90 days | 92 (typically merged in 0 days) |
| Project age | 37 days |

Checked on 2026-11-17 with the GitHub API.

## Project Facts

- Language: Rust
- License: Apache-2.0
- Stars: 2.9k
- Forks: 425
- Topics: geospatial, gis, remote-sensing, rust, rust-lang
- Website: https://rustgis.app
- Archived: no

## What You Need

Detected in the repository:

- Rust 1.90 or newer (from Cargo.toml)
- A Dockerfile, so it can run in a container
- A test suite and automated checks on GitHub Actions

## Getting Started

With Rust 1.90 or later, run the desktop app and its sample project:

```sh
cargo run --release -p rustgis
```

For prebuilt desktop downloads, the browser app, installation notes, and additional commands, see the [README](https://github.com/opengeos/RustGIS#readme).

## License in Plain Words

**Apache-2.0** (permissive).

- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors

A summary, not legal advice: the LICENSE file is what applies.

## Considerations

RustGIS is new and changing quickly. Recent activity includes frequent commits and releases, and contributors are not concentrated around a single person, but that short history still leaves less time for workflows and compatibility to prove themselves in long-term use. The README also identifies desktop-only capabilities, so check the feature table against any browser-based deployment requirements. Some integrations depend on installed tools such as GDAL or DuckDB, and using basemaps, plugins, web data, or an AI provider involves network access. AI requests can send the questions and data read to answer them to the selected provider. The project is licensed under Apache-2.0; review its terms when redistributing or incorporating it into a product.