Version History
Current release · v1.16.37
Every version of ouRGeo since the first one, newest first — the same release
notes the app shows from the version-history button in Settings. Installer availability is
tracked separately: a release with notes here may not yet have a packaged download.
v1.16.37
Nothing Lost Between Saves
October 2026
Current release
A saved project keeps its whole working state on this computer between saves, reopens exactly where you left it, and recovers what it can after a crash.
- Open documents with their unsaved edits, cursors and scroll positions, the R environment, the map, plots, the console and chats are kept on this computer as you work. Close ouRGeo or switch projects without being asked, and the project reopens exactly as it was — at the next launch too. The project menu says Unsaved changes, kept on this computer while there are any.
- R objects are snapshotted in the background once R has been idle for 30 seconds (adjustable from 10 seconds to 30 minutes in Settings → Projects). On Linux and macOS a forked copy of R writes the snapshot, so your commands are never held up. After a crash, the next launch lists what was recovered and when the R snapshot was taken; anything that cannot survive a restart, such as a database connection, is named with the reason.
- Closing a document with unsaved edits asks Save / Discard / Cancel, whether it is closed from its tab, Ctrl+W, Close Others, Close All or the assistant. Revert to Saved… in the project menu is the one action that throws working changes away, and it lists them first.
- If someone saves over the project file on a shared drive, choose their version, yours, or Resolve conflicts… — a three-way comparison that combines one-sided changes for you and lets you choose per document section, R object, layer, plot, chat or project file. Nothing is written until Finish and save.
- Scratch keeps its untitled notes between launches and offers Save as project… before it drops anything else. A project opens in one window at a time.
- Settings → Projects chooses what closing a project does, whether a project save also writes your open scripts, and lists stored drafts for clean-up; the health check reports them too. Settings → Prompts lists every question you have told ouRGeo not to ask again, with a switch to bring each one back.
v1.16.36
Project Files from R
October 2026
Release notes
Read and write files in the project library from any R function, and send exports straight into it.
- Keep your usual readers and writers and change only the path: read.csv(ourgeo_project_file("data/sites.csv")), write.csv(df, ourgeo_project_path("tables/summary.csv")) or ggsave(ourgeo_project_path("figures/map.png"), p). They work in the console, document chunks, toolbox tools and Knit.
- A written file joins Project Files when the command or chunk finishes, and the console says so. Writing the same name again replaces it and keeps its folder and description. ourgeo_project_save(), ourgeo_project_files() and ourgeo_project_commit() cover the rest, and a location argument writes into a linked folder.
- Plot export, map image export, map Export Code, checked vector export and the Environment panel offer Project Files as a destination and echo the same R. Replacing a file asks first, with a Don’t ask again that Settings → Project Files can turn back on.
v1.16.35
Field Themes, Docking and Guided Updates
October 2026
Release notes
Photographic Field themes and background galleries, panes that dock anywhere, update checks against the official installers, and finer control over the models the assistant uses.
- The Field collection brings the website’s 13 palettes into the app — eight dark and five light — each with six nature photographs and matching code and Markdown colours. Settings → Appearance groups themes as Illustrated, Legacy, Field collection and Custom, and Theme Studio follows the same groups.
- Background images… opens a gallery for the current theme; every painted theme gains five more paintings and a looping GIF. Select one image, or several for a slideshow with your own interval, and link folders of your own pictures. Background visibility sets how strongly the artwork shows, per theme, and reduced motion keeps it still.
- Drag a pane over another to dock it: choose a vertical split, a horizontal split or a tab group, then click where it belongs. Splits nest, groups are remembered across restarts and in saved arrangements, and Escape cancels without moving anything.
- Installed builds check ourgeo.dev for a newer installer shortly after startup and stay quiet when you are current or offline. An available update links to the official download, offers to save your project and shows the steps for your installer; ouRGeo never installs anything itself. Settings → Updates checks on demand or turns the startup check off.
- Settings → AI Assistant → File analysis models picks separate models for project documents and images. They share the chat’s connections and sign-ins, and can optionally write AI descriptions when files are imported.
- A Thinking selector appears for models with supported reasoning controls — OpenAI, ChatGPT plan, Anthropic, Claude subscription, Gemini and Ollama — and is remembered per model. Provider default leaves the choice to the service.
- Launchers, taskbars, pop-out windows and the macOS Dock show the ouRGeo logo.
v1.16.24
Project Files
October 2026
Release notes
Keep reports, standards and supporting documents inside a project, or link folders that stay on disk, and let the assistant cite them.
- A Project Files pane beside the R console and Terminal. Add files or drop them in: In project files travel inside the .ourgeoproj with their exact bytes. Give each one a display name, a logical folder, a description and a role — Reference, Standard or Example.
- Linked folders keep large or working files where they are. Link an existing folder or create one, then rescan, relabel, relink on another computer or forget the link; files on disk are never deleted. A shared project carries folder labels and relative paths, never your absolute folder paths.
- Markdown, text, PDF, Word, Excel, CSV/TSV and images are indexed locally with no model call. Previews are read-only; Export original and Replace file bring back edits made in another application.
- Attach a file, a PDF page, a document section, a sheet range or a line range to a chat message. The assistant searches and reads only what it needs, and answers cite the file and its page, section or cells — click a citation to open it. Clear Available to the assistant to keep a file out of its reach.
v1.16.22
Conversation Memory and Plugin Context
October 2026
Release notes
Manage conversation memories like the other two scopes, keep large sessions responsive, and let plugins supply context the assistant can use.
- Conversation memories can be added, corrected, moved to the project or to About you, and forgotten from the Memory Library, and saved projects keep them with their chat.
- Long tab strips and console histories render only what is on screen, so large sessions stay responsive. Copy all console output in the console header still copies the whole history.
- Plugins can contribute skills and Markdown context sources behind a separate context-source permission. Their sources appear in Browse current context sources, where you can exclude them, and an update that asks for new permissions switches the plugin off until you review it.
- Experimental, Linux x86_64 only: optional local memory engines under AI Assistant → Advanced. Each needs explicit acknowledgement, nothing is imported automatically, and the built-in Memory Library needs none of them.
- Assistant connections to model servers on this computer stay on the loopback interface, with no five-minute reply deadline and no background DNS or IPv6 probes.
v1.16.15
Context, Memory and Checked Export
October 2026
Release notes
An assistant that retrieves only the context a request needs and remembers what you ask it to, a reorganised Settings dialog, and vector export that verifies what it wrote.
- Settings is grouped into Application, Maps & data, Assistant and Extensions. The AI Assistant page is split into Memory Library, Provider & model, Learning & context, Privacy & sources, Budgets, Storage & recovery and Advanced.
- The assistant searches skills, actions, layer schemas, console runs and documents when a request needs them instead of sending everything every time. Expand the context summary under any reply to see what was selected, where it went and its estimated size; Context effort sets how deep retrieval goes.
- The Memory Library keeps About you, Project and Conversation memories apart. Say “Remember that I prefer metric units”, or use Add a memory — both save locally without running a model — then edit or forget it, or review the chat copies to remove. Learned memories are only suggested until you accept them, and project memories are saved with the project.
- Privacy & sources excludes any source, or individual workspace columns, from the assistant and pauses assistant actions that could bypass the exclusion. Budgets sets optional estimated daily and monthly chat limits, and Storage & recovery backs up local memory.
- Export layer… in the Data Viewer writes GeoPackage or RFC 7946 GeoJSON through the same data checks, stages the file, reads it back in full to verify every row, field and coordinate, and only then publishes it. A named layer can be added to or replaced in an existing GeoPackage without touching its other layers.
- The health check gains an S2 geometry-engine test with repairs for each operating system, and clean-up of duplicate package copies across R libraries; the Packages panel loads the copy you choose. An open health check survives sleep and wake.
- Projects keep a portable identity. Opening a duplicate asks whether it is the same project or an independent copy with its own memory.
- Fixed: Buffer and other checked tools could fail with “Check failed: Network Error” because an empty R response was malformed on a reused connection. All 94 toolbox tools are now run by an automated check.
v1.16.4
Check Before You Run
October 2026
Release notes
Data checks inspect a layer before an operation touches it, and the toolbox stops a buffer, join or summary that would quietly produce the wrong answer.
- Data checks → Check data in the Data Viewer profiles a whole layer or table without changing it: geometry validity, empty and non-finite values, field types, repeated values, CRS and coordinate units. Findings name the affected rows and can select them.
- Buffer, area, length, overlay, dissolve, spatial filter and join, transform, the attribute joins and group summary now check their inputs when you press Run. A clean operation simply runs, a consequential choice gets a review, and a blocked one has no “continue anyway”.
- Distances say what they mean. Geographic layers buffer in S2 spherical metres, projected layers convert units explicitly, and international and US survey feet are separate choices. A new Assign CRS tool declares what existing coordinates already are, distinct from Transform CRS; neither ever guesses a CRS or UTM zone.
- Joins preview their relationship, duplicate and blank keys, unmatched rows on each side and the predicted row count. Keys match exactly — no trimming, case folding or lost leading zeros — and a one-to-many expansion has to be approved.
- Summaries ask what to do with missing values — block, propagate, or omit with explicit counts — and an all-missing group is NA, never zero.
- The console records the R that actually ran, including the check and your choices. Checks run locally, with no account or network connection.
v1.16.3
Guided Installation Health Check
October 2026
Release notes
Get started with a guided check of R, its packages, system resources and the AI assistant, with approval before repairs or credit use.
- A dismissible invitation appears on first launch. Start the check when ready, or run it again from Settings → Health check; a saved summary records results and remaining steps.
- Check for R and approve its installation when needed. Repair missing, outdated or incompatible R packages, including the core dependencies that can prevent Rscript from connecting after an R upgrade.
- Save the project before a repair stops the R session, then reconnect after installation. Check backend readiness, writable folders, free storage, system memory, GPU memory and document-export tools.
- Configure a local AI server and choose Qwen models suited to the available memory and storage. Downloads need approval, and testing a cloud or subscription model asks before using credits or plan allowance.
- Fixed: R Markdown Visual mode shows images and code output again.
v1.16.2
Complete ChatGPT Replies
September 2026
Release notes
Keep the full ChatGPT subscription answer and its tool calls, and report a reply that ends without a final answer.
- Completed stream items now supply answer text and tool calls even when the final response summary does not repeat them. Missing text suffixes are recovered once, without duplicating the streamed answer.
- Commentary and final-answer phases survive conversation history and replay, so a preamble is not mistaken for the completed answer on a later turn.
- Reasoning-only, commentary-only and interrupted replies show a recovery message instead of silently stopping. Partial text stays visible and in chat history; request IDs help diagnose failures when the provider supplies one.
v1.16.1
Use Your ChatGPT Plan
September 2026
Release notes
Connect an eligible ChatGPT account and use its plan allowance and subscription credits to power the assistant.
- OpenAI subscription (ChatGPT) is a provider in Settings → AI Assistant. Continue with ChatGPT opens browser authorisation; choose an account or workspace and a model from its eligible catalogue.
- Manage usage and credits opens ChatGPT Settings → Usage. Subscription inference uses the Responses API and the existing tool permissions; API billing remains a separately selected provider.
- Credentials stay in the main process and are saved only when a secure operating-system keyring is available. Accounts, sign-out and rotating token refreshes are managed by the app; projects never contain tokens.
- OpenAI account and workspace eligibility and preview limitations apply. Voice transcription still uses its own configured service.
v1.16.0
Managed Plugin Services
September 2026
Release notes
Let an installed plugin run a managed native background service, with startup and shutdown owned by ouRGeo.
- Plugins can declare a JavaScript background service and its files, with an explicit service permission for native system access. The host provides a private loopback connection, so users do not need a companion terminal or pairing key.
- Starts are deduplicated, and disabling a plugin, losing its renderer or quitting stops the service. Persistent plugin data lives outside the replaceable plugin folder; store packages preserve declared service assets.
- Plugin panels mount as React components with an error boundary per panel, preventing a failed panel from taking down the workspace.
v1.15.6
Curves, Chats and a Plugin Store
September 2026
Previous installer
Type the curve a deed is written in, keep your conversations with the project, and install plugins other people wrote — each one run by a moderator before it appeared.
- Curved courses in Distance & Bearing. Press U and type the call the way the deed or plat writes it — "along a curve to the right, radius 250.00 feet, central angle 45°30′" — and the arc lands where the numbers say it does. Tangent and non-tangent curves, clothoid spirals, the spiral–curve–spiral a highway plan quotes as one unit, and a free curve between two headings.
- Any two elements define a curve, so type the two your plat happens to quote — radius, arc length, chord, tangent, external, mid-ordinate, central angle or degree of curve. ouRGeo works out the rest and prints all of them back, which is how you check a curve against the document it came from. Where two perfectly ordinary curves would fit the numbers you gave, it says so and names both rather than quietly picking one.
- What is written to your layer is a real curve — CIRCULARSTRING and COMPOUNDCURVE, not a densified polyline — so the radius survives a reprojection and a GeoPackage round trip. Closure now measures the arc a curve actually follows rather than its chord, so a figure with curves in it is judged by the right length.
- Arcs are circles on the ground now. Three-point arcs used to be fitted in raw longitude and latitude, where a circle on the map is an ellipse on the Earth: a 250 m radius arc through 90° landed 25 m out at latitude 45 and nearly 47 m at latitude 60. Geometry you have already saved is untouched — it simply draws correctly from now on.
- A plugin store. Browse it in Settings → Plugins → Plugin Store…, or at ourgeo.dev/plugins.html — data connectors, geoprocessing tools, panels and workflows written by other ouRGeo users. Every one has been installed and run by a moderator before it appeared.
- Installing happens inside ouRGeo and needs your free ourgeo.dev account, the same one the forum uses, because plugin downloads are not public. What you install still arrives switched off: turning it on stays your decision, exactly as it is for a plugin you were sent as a file.
- Publish your own. Publish… on any plugin you wrote builds it, uploads it and puts it in the queue; a moderator installs it, runs it, and either publishes it or sends it back with a note you can read. What people download is a built, minified bundle — your source is never published, and ouRGeo will not export or read back a plugin installed from the store.
- Show off what you built: attach several screenshots at once, watch each one resize and upload, and see which of them are on your store page and which are still waiting for you to submit. Pick the one that becomes the catalogue picture, reorder them, or remove one — and removing it takes it off the page rather than just out of the list.
- Updates are offered in Settings → Plugins and never applied for you, with the author’s note about what changed. If a version is withdrawn after you installed it, ouRGeo switches that plugin off and tells you why in the console.
- Ratings and reviews, from people who have actually installed the plugin.
- The assistant can search the store and install from it, and will look there before offering to write you a plugin from scratch — an installed plugin is code somebody has already read and other people are already running.
- A plugin archive can no longer smuggle in code nobody read. ouRGeo used to pack its own compiled cache into an exported .ourgeoplugin and load it back without recompiling, which meant a hand-made archive could ship one thing to read and another to run. Both ends now leave it out, and imported archives are checked and bounded.
- The AI panel keeps as many conversations as you like instead of one. Start a new chat whenever you want and the last is still there — switch back from the header and carry on where you left off. Save the session as a project and its chats are kept with it, ready next time you open it, and they travel inside the .ourgeoproj so a project you send someone carries the conversations that shaped it.
- Chats in the scratch workspace last until you quit, like everything else in scratch — if a conversation turns out to be worth keeping, save the session as a project and it comes along.
- Each chat remembers the model it was held with, and switching back restores it — so a conversation written by a large cloud model is never quietly continued by a small local one. Chats name themselves from your first question, and you can rename or delete any of them.
- Use your Claude Pro or Max subscription as an AI provider. ouRGeo runs the Claude Code command-line tool you already installed and signed in to — no API key to paste, and ouRGeo never sees a credential of yours. Usage counts against your Claude plan.
- The context meter tells the truth. It used to report the total of every request a single answer made — several times the real figure on a long Autopilot turn — and only once the answer had finished. It now follows the live conversation as it grows.
- Much less of your Claude subscription spent per question: the session context ouRGeo sends now extends the cached conversation instead of invalidating it, and says only what has changed since the last turn. On a measured six-turn chat that was 21% fewer tokens overall and a third of the per-turn growth; on a two-turn chat, the difference between $0.0014 and $0.0235 for the same question.
- Local models get the time they need. ouRGeo no longer imposes a hidden five-minute deadline on a reply — a large prompt on a busy GPU used to fail with the words "fetch failed" and nothing else. Failures now name the server and what to do about it.
- Nothing you were reading disappears any more. A dropped connection used to replace a half-written answer with an empty one; pressing Stop used to delete it outright. Both keep what was said.
- Send does something the moment you press it, so a slow session can no longer turn one click into two messages.
- The open-data connectors answer again. NYC, Chicago and every other Socrata portal had been silently returning nothing — they were asking for a catalogue Socrata retired — and Canada’s portal blamed your internet connection for problems that were never yours. Every connector now also carries a Help button that opens the API’s own documentation, which is where the questions a connector cannot answer are answered.
- The USGS water connectors generate R that runs, and let you narrow the data: choose the gauge rather than taking a whole state, and the measurement — discharge, gage height, temperature, conductance, pH — rather than always discharge. Water quality and groundwater had been asking for NWIS services USGS has retired, and now use the endpoints that carry the data.
- Copy buttons throughout the app work again — they had been silently doing nothing since 1.12 while still showing a tick, along with the terminal’s copy and paste.
- Hover any tab to read its full name, the file it came from, and whether it has unsaved changes.
v1.14
Type It, Don’t Eyeball It
September 2026
Development milestone
Distance & Bearing — place the next point by typing how far and which way, on the grid your survey was measured on.
- A Distance & Bearing tool beside Draw, for every kind of layer — lines, polygons and points. Press B, say where you are measuring from, then type each leg: 150 ↹ N45°30′E ⏎, and the vertex lands exactly there.
- Bearings in the notation your notes are already written in: azimuths, degrees-minutes-seconds, quadrant bearings like N45°30′E, deflections (L/R) and angles right. Distances in metres, feet, US survey feet, chains, miles — or type 150ft and the unit comes with it.
- Distances are geodesic on the WGS 84 ellipsoid, computed with Vincenty’s method rather than on a sphere, so a leg is the length you typed anywhere on Earth.
- A bearing off a plat means something different on a projected map, and ouRGeo now says which it is using. On a projected layer it measures on that layer’s own grid — in the layer’s own unit — so grid north and the scale factor are accounted for instead of quietly rotating your traverse by the convergence.
- On a point layer you place a reference point first — a temporary mark to measure from, not a row in your data — and every leg after it fills the row you are on and moves to the next, so the data viewer’s row indicator walks the table exactly as it does when you click. Run out of rows and it asks whether to add another, as always.
- The reference point snaps if snapping is on, carries forward from the last point you placed, and can be moved anywhere at any time by clicking the map.
- It shows its working: where the leg lands as you type, the numbers written on the leg itself on the map, a list of everything entered in the words you entered it in, and — once a figure could close — how far it is from closing and the 1:N a surveyor judges it by.
- Finishing a traverse echoes a runnable ourgeo_traverse() call naming the origin, the legs and the CRS — because the geometry ouRGeo writes records the coordinates, not the distances and bearings they came from.
- The AI assistant can lay one out for you from a list of legs, staged for review like any drawn geometry.
- Fixed: coordinates in the R server’s replies were rounded to four decimal places — eleven metres of longitude — which no feature had needed to more than four until this one did.
v1.13
Run Anything
September 2026
Development milestone
A real terminal inside ouRGeo — your own shell, beside the R console, for the half of the work that was never going to be R.
- A Terminal tab beside the R console, always there. It is your own shell — bash, zsh, fish, PowerShell, whatever you use — with a real pseudo-terminal behind it, so top, vim, git and colour all work exactly as they do in a terminal window.
- Nothing starts until you click the tab. Open as many shells as you like from the + button, rename them, and pick a different shell from the arrow beside it; the tab shows a dot when a command finishes in one you are not watching.
- It opens in R’s working directory, and the path in the header is a control: click it to change directory, copy it, open it in your file manager, or reconcile the two — send R to the shell’s directory, or type cd to R’s.
- Colours follow your code theme and the surface follows your app theme, the same way the editor does, so ls looks like it belongs in the window it is in.
- Search with Ctrl+Shift+F, copy and paste with Ctrl+Shift+C/V, and resize the text with Ctrl+= and Ctrl+- — everything else goes to the shell, including Ctrl+C, Ctrl+R and Ctrl+D.
- Settings → Terminal gives it its own pane beside the console instead of a tab, so both are visible at once — and after that you can drag it anywhere and ouRGeo leaves it there.
- Reload the window and your shells are still running, with their scrollback. Close ouRGeo and they are gone: terminal output is never written to disk, not into a project bundle and not into the session file.
- The AI assistant can use it, behind a Terminal switch in the panel footer that ships OFF and works only with Autopilot on. Every command it runs is typed into a tab you are watching and written to your R console.
- It is not a sandbox and is not offered as one — R’s own system() reaches the same machine. What the switch means is that you decided, once and deliberately, that running commands on your computer is part of what the assistant does. Ask it to do things in R wherever R can do them.
- A second code editor: Settings → Workspace adds one, and documents drag between the two by their tabs or move with a right-click. Removing an editor never closes a document — they move to the one that remains.
- Panel drag grips now ship off. They appeared on every panel header on hover, which is a gesture that mostly fires by accident when you did not go looking for it; Settings → Workspace turns them on and can rearrange everything without them.
- Every on/off setting is now a switch rather than a checkbox, and the whole row is the control — a settings row takes effect the moment it moves, and there was never an OK button to press.
v1.12
Say It Out Loud
September 2026
Development milestone
Dictate to the AI assistant — on your own machine by default, with nothing uploaded and no account needed.
- A microphone beside Send in the AI panel. Click it, talk, and the transcript lands in the message box at the cursor — so you can start typing a sentence and finish it out loud.
- It shows you it is listening: a ring around the microphone that moves with your voice, a timer, and a live level meter in Settings so you can check the right device is picked up before you rely on it.
- Transcription runs ON YOUR MACHINE by default. Whisper is downloaded once (43–242 MB, your choice of model) and then works offline for ever — no account, no key, and nothing you say leaves the computer.
- Prefer something else? Point it at a server you run (whisper.cpp, Speaches, LocalAI), or at OpenAI, Groq, Deepgram, ElevenLabs Scribe or AssemblyAI. Deepgram shows words as you speak them.
- Every recording sent off your machine is recorded in the R console, with how long it was and where it went. The on-device engine never appears there, because there is nothing to report.
- Pick your microphone from the button itself (right-click) or in Settings → Voice input, along with the language, how long a pause should end a recording, and whether to send the message automatically.
- Auto-send is off by default: the assistant can run R, and a misheard instruction is worth reading before it goes.
- ouRGeo now asks your operating system for the microphone and nothing else — the app previously had no permission policy at all, and could have been granted location or notifications without anything appearing on screen.
v1.11
Make It Do More
September 2026
Development milestone
Plugins, and a workspace that goes where you put it — ouRGeo can now gain capabilities it did not ship with, without being rebuilt.
- Plugins (Settings → Plugins): data connectors, geoprocessing tools, actions, toolbar buttons, panels and documentation, added while the app is running. Most are pure JSON and run no code at all.
- Ask the AI assistant for one in prose — "add a connector for this API" — and it probes the API, writes the spec, tests it against the real server, and asks you to turn it on.
- A plugin that ships code is compiled on the spot, runs with ouRGeo’s own privileges, and arrives switched OFF. Enabling one is a decision you make, the way you decide to run install.packages().
- Plugins export and import as portable .ourgeoplugin files. One that fails to load is reported and skipped, never fatal — and one that takes the app down disables itself on the next launch rather than leaving you locked out.
- A workspace you arrange: four zones — left, centre, right and bottom — and any panel can go in any of them, split or tabbed, at whatever size you like. Drag a panel by the grip in its corner.
- Panels sharing a zone share it evenly — two take half each, three a third each — until you drag a divider between them. Double-click a divider to even them out again, and every zone starts each session evenly shared.
- Your arrangement is remembered between sessions, and you can save several as named presets and switch between them.
- Toolbar buttons can be reordered and hidden, and the assistant can rearrange all of it on request — with layout:reset always the way back.
- Fixed: opening a project restored its R objects but showed an empty Environment panel — everything the bundle loaded was being treated as though it were ouRGeo’s own rather than yours.
- Fixed: the helper functions ouRGeo defines for generated code no longer end up in your project bundles, in your Environment panel, or deleted the moment you open a project.
- Fixed: when the assistant moved the map for you — zooming from landmark to landmark on a tour — the view never changed. Every map:setView now moves the map you are looking at, and the export extent follows it.
- Console recording gained a destination: the assistant can now record into a new document, or into a saved file that offers to write itself back when you stop.
- The Environment panel: right-clicking an environment offers Export, Make Copy, Rename and Delete, and Save is now called Export — it writes an .RData file to your computer.
- Environments you can work IN: right-click one and choose “Work in this environment”, and everything you run — console, toolbox, assistant — evaluates inside it. R looks names up outwards and never into an environment, so this is what lets you type x * a instead of env2$x; .GlobalEnv stays visible through it, and the prompt shows where you are. Switching echoes the R for it — evalq({ ... }, env2) — so the same move works in a script.
- Creating an environment now says how to reach what you put in it, in the console, at the moment you make it.
- Objects gained Copy To beside Move To — same name, another environment, the original left where it is.
- An environment is listed beside .GlobalEnv by default; Show in its right-click menu lists it inside .GlobalEnv instead, where R actually keeps it.
- Move To now offers the environments you can actually see: .GlobalEnv and your own while the eye is hiding what is not yours, every environment in the session when it is not.
- Fixed: “Make Copy” on an environment made a second name for the same environment rather than a copy — editing either one changed both.
- Fixed: R’s refusals reach you. Naming an environment after a data frame, moving an object into a package environment, copying onto a name already taken — each one used to do nothing and say nothing.
- Fixed: exporting an environment no longer writes ouRGeo’s own internal functions into your .RData file, and the console shows the exact save() that was run.
- Settings → Workspace: save the panel arrangement by name and switch between arrangements, export and import them as .ourgeolayout.json files, turn the drag grips off if you would rather they weren’t there, and restore the shipped default in one click.
- Fixed: the grip in a panel’s corner did nothing when you dragged it — dropping a panel into another zone now works, and an empty zone offers itself as a target so a panel can always be moved back.
- Move a dataset between panels from wherever you are: Add to Map in the data viewer’s header sends a table to the spatial editor, and right-clicking a layer in Contents opens its attribute table.
- Sending an object that is already on the map now asks first — and offers to show you the layer you already have instead of adding a second copy of it.
v1.10
Make It Yours
August 2026
Development milestone
The Theme Studio — build your own themes on all three axes, with your own artwork, and share them as files.
- Theme Studio (Settings → Appearance): create app themes, code themes and markdown themes of your own, always by copying one that already works.
- Every colour is editable and labelled with what it actually paints — ten interface colours and six editor-surface colours for an app theme — with live contrast warnings and a preview that updates as you type without touching the running app.
- Bring your own artwork: a backdrop image behind the code editor with its own opacity and grey-scale, and a card image for the theme picker. Both are embedded in the theme, so it travels with its pictures.
- An app theme also chooses the code and markdown palettes it starts with, and the basemap the Spatial Editor opens with under it.
- Themes export and import as portable .ourgeotheme.json files — and a file meant for one axis can never land in another’s list.
- The AI assistant can build a theme to your description, check its own contrast, and switch you to it.
- Fixed a settings-file race that could corrupt theme.json and quietly reset the app to the Dark theme on the next launch.
v1.9
Markdown & R Markdown
August 2026
Development milestone
.md, .Rmd and .qmd become first-class documents — written, run, knitted and published without leaving ouRGeo.
- Markdown and R Markdown documents in the code editor, with a formatting ribbon, a slash-command menu, and full R autocomplete inside chunks.
- Runnable chunks with inline output: run a chunk and its plots and printed results appear beneath it, right in the document.
- A Visual mode that edits the rendered document directly and round-trips back to source without reformatting what you wrote.
- “Chunk: current map” generates real tmap or ggplot2 code from the layers, symbology and view currently on the map — the same code the Export dialogs produce.
- Knit to HTML, PDF or Word in a clean R session, with each format pre-disabled and explained when its dependencies (pandoc, LaTeX) are missing.
- Publish an R Markdown document straight to the community forum as a new discussion, figures and all.
- Separate code-editor and markdown editor themes: 26 syntax palettes and 16 prose palettes, chosen independently of the app theme.
v1.8.0
Raster & Imagery Connectors
July 2026
First public release
The Data Connector gains a dedicated Raster / Image Layers category — industry-standard imagery services import straight to the map.
- New Raster / Image Layers category in the Web APIs tab, gathering every raster-serving connector in one place with verified built-in servers for each.
- Esri Image Services connector (USGS 3DEP elevation, USDA NAIP aerial imagery) — the ImageServer workflow, now a first-class connector.
- OGC WCS connector: real raster data values (EMODnet bathymetry, DLR SRTM elevation) via scaled GetCoverage requests that auto-split around server read limits.
- OGC WMS connector: rendered map imagery (NASA GIBS satellite layers with time selection, terrestris OSM/SRTM) chunked and mosaicked into georeferenced rasters.
- ERDDAP Grids connector: gridded scientific data (NOAA sea-surface temperature and friends) — one variable, one time slice, real values.
- Raster imports can now land directly on the map: an "Add to map when done" option registers, styles, and zooms to the layer automatically.
v1.7
The Raster Release
July 2026
Development milestone
Rasters become a first-class data type — rendered, styled, analyzed, imported, and stored like everything else.
- Rasters on the map: SpatRasters render as crisp, server-tiled layers in the Spatial Editor, with a band viewer and full symbology (RGB/pseudocolor/categorical, stretch controls, color ramps, histograms).
- A complete raster toolbox — 30+ tools covering processing (reproject, clip, resample, focal, terrain, hillshade, raster calculator), band math (NDVI and friends), and raster↔vector work like zonal statistics and extract-to-points.
- GeoTIFF and Cloud-Optimized GeoTIFF import: local files, COGs streamed by URL, and STAC raster assets from satellite catalogs.
- Tiled raster storage in .Rgeo databases (format v3): rasters save as compressed block pyramids and connect back instantly as lazy, file-backed objects.
- Map export parity — ggplot2 and tmap exports reproduce on-map raster symbology exactly (band, stretch, ramp).
v1.6
Projects & Polish
July 2026
Development milestone
A real project workflow plus a top-to-bottom refresh of the Settings and theming experience.
- Project workflow: save and load portable .ourgeoproj bundles that snapshot the R environment and full UI state, with a scratch workspace that always launches clean.
- Redesigned Settings: collapsible, icon-led sections and an in-app version history.
- Scenic theme picker — each theme is shown as its own themed illustration, with subtle grey-scaled artwork painted behind the code editor.
- Retired the standalone Map Preview panel; all map-making now lives in the Spatial Editor.
- Package name autocompletion inside library()/require(), with the Packages pane auto-refreshing on install.
- Stability: fixed a black-screen restore after sleep and tightened memory cleanup on exit.
v1.5
Development milestone
The largest release — a ground-up architecture overhaul plus databases and much richer map export.
- Database support: connect to .Rgeo (DuckDB) databases, manage datasets, and edit database-backed spatial objects directly.
- First-class curved geometry via sfarc, plus auto-detected calculation CRS and configurable default CRS for new geometry.
- Expanded Data Connector with a Web APIs framework (Esri, OGC, WFS, STAC, SDMX, OData, CKAN, Socrata, ERDDAP, and more).
- Map export to both tmap and ggplot2 with legends, north arrows, scale bars, and graticules.
- Local model harness support (llama.cpp and others) for the AI assistant.
- Under the hood: modular R server, AI calls proxied through the main process, and a Vitest test suite — plus many data-editor and console improvements.
v1.4
Data & Intelligence
April 2026
Development milestone
Connected ouRGeo to the outside world and added guided, code-free workflows.
- Data Connector for importing from popular open-data portals.
- Kaggle integration for pulling datasets straight into R.
- AI Assistant panel for in-app coding help.
- Toolbox: a GUI over a large set of classic R spatial and tabular operations, with the ability to pipe tools together.
- Plotting preview pane, a ggplot GUI editor, and an in-app Help panel.
v1.3
Development milestone
Turned the workspace into a polished spatial app with real map editing.
- Settings with switchable themes applied across the editor, data viewer, and map.
- Create-dataset dialog for vectors, matrices, data.frames, tibbles, and data.tables.
- Geometry drawing with snapping, a symbology editor, and multiple concurrent spatial editor sessions with user-defined extents.
- Map zoom and fit-to-extent controls, plus selection syncing between the data viewer and the map.
- Switchable R installation path, console recording, and zoomable UI text and icons.
v1.2
Development milestone
Grew from an editor into a full R workspace with packages, environment, and data.
- Package Manager to install and load packages, with actions echoed to the console.
- Environment pane to browse R objects, expandable by data type.
- First Spatial Editor pane for adding sf objects to a map.
- Inline data editing with smooth spreadsheet-style editing and column creation.
v1.1
Development milestone
A clean restart — the distilled core that everything else is built on.
- A Monaco code editor wired to a live, embedded R console.
- File management: open, edit, create, and save .R files.
- Editor tabs that persist across sessions.