01 What ouRGeo is
A desktop spatial IDE that keeps R at the centre — ArcGIS Pro’s interface, RStudio’s transparency.
ouRGeo is a free, AGPL-3 licensed desktop application for spatial analysis. It gives you
a map canvas, a layers panel, a geoprocessing toolbox and a digitizing environment
— the tools you’d expect from a GIS — but it runs every one of them
on R’s spatial stack (sf, terra, ggplot2,
tmap) and shows you the code as it goes.
It runs entirely on your machine. There is no telemetry and no cloud dependency; an internet connection is only needed if you pull data from a web service or use a hosted AI model, plus one quiet check of ourgeo.dev for a newer installer at startup, which you can switch off in Settings → Updates. An ourgeo.dev account is free and entirely optional — it exists for the community forum and for installing plugins from the plugin store, and nothing else asks for one.
02 Install and one-time R setup
Grab an installer from the Download page. Windows and Linux builds are available today; macOS is on the roadmap.
R 4.1 or newer is required and is installed separately from ouRGeo. Follow the
Windows or
Linux instructions to install R,
install ouRGeo and run the required R package commands in PowerShell or your Linux terminal.
Use the same Rscript executable in the terminal and in Settings → R Backend.
The core packages (httpuv, jsonlite, later,
httr2 and rlang) must be installed before ouRGeo can connect
to R. The download page also lists the packages for spatial work — including
s2 and units, which data
checks use for geographic measurements — databases and exact curves.
Already on an older version? Install the new release over it; your projects, settings and R installation are separate from the application. From 1.16.35 on, ouRGeo checks for new installers itself and walks you through the update.
On Debian or Ubuntu, an N: Download is performed unsandboxed as root
notice or a skipped AppArmor profile message does not stop installation. If APT
reports Setting up ourgeo, the package installed successfully.
03 The health check
A guided check of R, its packages, your computer and the AI assistant — and nothing is installed or spent without your approval.
A dismissible invitation appears on first launch; run the check whenever you are ready, and again from Settings → Health check — after updating R, for example. Use Back and Next to move through the steps. It checks:
- R — that it is installed, and offers to install it when it is not.
- R packages — missing, outdated and incompatible packages, packages built for an older R, and duplicate copies of a package across R libraries. Keep the copies you want and approve removing the rest; protected and read-only libraries are left alone.
- The S2 geometry engine — a real spherical distance, three 100-metre buffers, validity and containment on synthetic geometry. A failure shows the native loader error and the repair for your operating system.
- The backend and your computer — backend readiness, writable folders, free storage, system and GPU memory, document-export tools, and stored project drafts.
- The AI assistant — local Qwen models sized for your memory and storage, existing model servers, or a cloud or subscription provider. Downloads need approval, and a response test asks before using credits or plan allowance; it sends no project data.
Repairs that replace loaded packages stop R, so the check offers to save your project first and reconnects afterwards. The final report records what was ready, fixed, skipped and unresolved. An open health check survives sleep and wake.
04 Your first five minutes
ouRGeo always opens into a scratch project — a clean R session that you can experiment in freely and never have to name or save.
- Check R connected. A small status dot sits next to the project name at the top right. If R did not start, run the health check, or open Settings → R Backend and pick an installation.
- Load something. Press Load Data in the toolbar and open a shapefile, GeoPackage, CSV or GeoTIFF — or press Data Connector and pull a layer straight from a public web service.
- Look at the console. The import you just clicked through emitted an R command. That is the whole idea — see below.
- Put it on the map. Open the spatial editor with the globe button, then use Add Features to add your layer to the map.
- Run a tool. Open the Toolbox, pick something like Buffer, and watch the Code Preview build the R as you fill the form.
- Keep the work. Either Save As a
.ourgeoprojproject — from then on nothing is lost between saves — or turn on recording and walk away with a runnable script.
05 The one idea that matters
Every GUI action has a matching R command, and you always get to see it.
When you buffer a layer, run a join, reproject, compute a distance or draw a feature through the interface, ouRGeo does not perform a hidden internal operation. It writes the real R command and runs that in your session, echoing it to the console exactly as if you had typed it.
# What appears in your console after clicking through Toolbox → Buffer parcels_buffered <- sf::st_buffer(parcels, units::set_units(50, m))
Three things follow from that:
- Your click-through is an audit trail. Anyone can read the console and see precisely what was done to the data, in a language they can check.
- You can leave the GUI at any point. The objects the toolbox creates are ordinary R objects in your environment. Type at the console, edit them, model them, hand them to a package the GUI knows nothing about.
- Point-and-click work is reproducible. Not "reproducible in principle" — you can literally copy the commands into a script and re-run them.
06 Recording a session
Seeing the code is useful; keeping it is better. The Record Console button (the circle icon in the toolbar) appends every command your session generates to a file of your choosing.
.R file on disk.
07 Projects and what persists
ouRGeo has two ways of working, and the difference decides what survives a restart.
.ourgeoproj file. Its whole working state
— documents with unsaved edits, the R environment, the map, plots, console
and chats — is kept on this computer as you work and reopens exactly where you
left it, so closing or switching never costs work. R is snapshotted in the
background, so a crash costs only what came after the last snapshot.Saving, closing, crash recovery, three-way conflict resolution on shared drives, and the Project Files library that keeps reports, standards and data with the project are all covered in Projects & Files.
08 Keyboard shortcuts
| Keys | Where | Action |
|---|---|---|
| Ctrl+Enter | Code editor | Run the current line and advance the cursor |
| Shift+Enter | Code editor | Run the selection (or the current line if nothing is selected) |
| Enter | Console | Send the command |
| Shift+Enter | Console | Insert a newline instead of sending |
| Ctrl+Space | Code editor | Trigger autocomplete manually |
| Ctrl+O | Anywhere | Open a file |
| Ctrl+S | Code editor | Save the active tab |
| Ctrl+N | Code editor | New tab |
| Ctrl+W | Code editor | Close the active tab |
| Ctrl+Shift+= / - | Anywhere | Zoom the interface in / out |
| Ctrl+Z / Ctrl+Y | Drawing | Undo / redo — draft edits first, then staged commits |
| Enter | Drawing | Commit the geometry and advance to the next row |
| Esc | Drawing | Finish and close the drawing session |
| Backspace | Drawing | Remove the last vertex |
| N | Drawing | Save the current part, start the next |
| H | Drawing | Start a hole in the polygon |
| B | Drawing | Distance & Bearing — type the next course instead of clicking |
| U | Drawing | Curve — the same strip, starting on a curved course |
| Ctrl+C / R / D | Terminal | Go to the shell unchanged — interrupt, reverse-search, end of input |
| Ctrl+Shift+C / V | Terminal | Copy / paste (everything else is the shell’s) |
| Ctrl+Shift+F | Terminal | Search the scrollback |
| Ctrl+= / - | Terminal | Text size in the focused terminal |
09 Troubleshooting
R will not connect
- Run the health check from Settings → Health check. It finds and repairs most connection problems, with your approval.
- Confirm R 4.1+ is installed and that
Rscriptis on your PATH. - Check the five core packages are present:
httpuv,jsonlite,later,httr2,rlang. Without them the backend cannot start. - If you recently upgraded R, rebuild your packages
(
update.packages(ask = FALSE, checkBuilt = TRUE)). - Point ouRGeo at a specific interpreter with Settings → R Backend → Browse for Rscript….
A tool fails on curved geometry
Some operations are GEOS-only and cannot handle true arcs. Tick Linearize curved geometry before calculation in the tool form — see Linearize and Calculation CRS.
A tool says its check is blocked
Checked tools refuse an operation that would give a wrong answer rather than running it anyway. The panel names the reason and the affected rows: a layer with no CRS (use Assign CRS if you know what it is), keys that break the join relationship you declared, missing values with no policy. Change the data, parameters or method and check again — see Data checks before Run.
Buffer or area results look wrong
Almost always a CRS problem. Checked tools now measure geographic layers in S2 spherical metres and label the method and units they used — expand the check to see them. For exact curved buffers, transform a copy to a projected CRS first. Details in the toolbox docs.
Geographic checks fail or S2 will not load
The health check’s S2 spherical geometry engine result tests it and shows the native error. Select s2 under Review package repairs: Windows and macOS install a compatible CRAN binary; Linux rebuilds from source with bundled Abseil, which needs a C++17 compiler, CMake, pkg-config and OpenSSL headers — the review lists the commands for your distribution.
A project reopened with unsaved changes
That is the draft ouRGeo keeps on this computer between saves. Save writes it into the project file; Revert to Saved… discards it. Old drafts are listed, with their size, in Settings → Projects → Stored unsaved changes.
A raster layer vanished from the map
Raster map layers are tied to the R object backing them. If that object is replaced or removed, the layer is invalidated; ouRGeo re-registers it automatically where it can and drops it where it cannot. Re-add it from Add Features.
The window went black after sleep
Known behaviour of the underlying graphics stack. ouRGeo forces a repaint on resume; if a window stays blank, resizing it triggers a redraw without losing state.
Still stuck
Ask on the community forum. Include your OS, ouRGeo version, R version, and the console output — the console text is the single most useful thing you can paste.
10 Where to next
.Rgeo databases, and the R helper functions behind them.Elsewhere
- Features — the tour of what makes ouRGeo different, if you have not read it.
- Download — installers and system requirements.
- Community forum — questions, bug reports and workflows.