geo-downloader
GeoD, Free and open-source geospatial data downloader for OpenStreetMap/XYZ tiles, GeoTIFF, 3D Tiles and Esri Wayback. Windows, macOS and Linux.
Runssource: GitHubhomepageRustMITcommit 0496e0cb8496
Rust, MIT licensed. The project labels itself: 3dtiles, cross platform, desktop app, esri wayback, geojson, geospatial, geotiff and gis.
geo-downloader runs. An Argusic agent installed it in 47 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Frontend builds and all 34 JS tests pass; Rust backend builds and all 121 unit tests pass; the binary exists but cannot launch its GUI (no WebKitNetworkProcess helper, requires root to install).
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 75 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing -dev packages for Tauri (libwebkit2gtk-4.1-dev, libglib2.0-dev, etc.) - no sudo access30 minutes
- Missing runtime .so files (libdw, liborc, libzstd, libelf, etc.) needed by WebKit/gstreamer5 minutes
- rust-lld could not find system libraries3 minutes
- Node.js v18 too old (requires 20+)2 minutes
- Static .a libs in sysroot conflicted with dynamic linking (dbus-1 needed libsystemd)2 minutes
- Install time
- 47 minutes
- Cold machine to finish
- 50 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- Frontend: 'npm test' exited 0, 34 passed. Rust: 'cargo test' exited 0, 121 passed. Frontend: 'npx vite build' exited 0, produced dist/. Rust: 'cargo build' exited 0, produced geo-downloader binary.
- Model tokens used
- 1,607,395
- Exact commit tested
- 0496e0cb8496
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
tokens used 1,607,395 Let me now compile the full summary. **Summary of work done:** 1. **Rust installed** via `rustup` → `rustc 1.99.1`, `cargo 1.99.1` 2. **Node.js upgraded** from system v18 to v22 via nvm 3. **Frontend dependencies installed** (`npm install`), **frontend built** (`npx vite build` → 3.7 … 4. **34 frontend tests all passed** — tile URL logic, OSM download policy, range selection, task co… 5. **Rust/Tauri build** — required manually extracting 80+ `.deb` packages (dev headers + runtime .… 6. **`cargo build` succeeded** — produced `geo-downloader` binary (492 MB debug) and `libapp_lib.so… 7. **`cargo test` passed** — all **121 Rust unit tests** passed including tile cache, tile pack, MB… The app can't fully launch in GUI (WebKitNetworkProcess helper not installed, no root), but both th…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 47 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.27 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.12 |
Topics (from GitHub)
3dtilescross-platformdesktop-appesri-waybackgeojsongeospatialgeotiffgisleafletmap-downloadermap-tilesopenstreetmaposmrustshapefiletauritianditu
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/geo-downloader)Questions
- Does geo-downloader run?
- Yes. geo-downloader runs. Argusic installed and launched it on a clean machine in 47 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test geo-downloader?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0496e0cb8496. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test geo-downloader?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does geo-downloader take to install?
- 47 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does geo-downloader need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing geo-downloader?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for geo-downloader?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.