OSM2World
converter that creates three-dimensional models of the world from OpenStreetMap data
Runssource: GitHubhomepageJavaMITcommit 8ec26a9ea426
Java, MIT licensed. The project labels itself: 3d, 3d tiles, gltf, openstreetmap, pbr and wavefront obj.
OSM2World runs. An Argusic agent installed it in 17 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OSM2World 0.5.0-SNAPSHOT builds, passes all 808 tests, and successfully converts real OSM data into a 2.3 MB valid binary glTF 3D model file.
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 100 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.
- jogamp.org (source for JOGL 2.4.0) unreachable - connection timed out5 minutes
- No Java or Maven installed in container3 minutes
- Install time
- 17 minutes
- Cold machine to finish
- 20 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- mvn test exited 0 with ~808 total tests, 0 failures; 'java -jar --version' printed '0.5.0-SNAPSHOT'; 'convert -i test.osm -o out.glb' produced a 2.3 MB file with valid glTF magic bytes (67 6c 54 46) and version 2
- Model tokens used
- 119,999
- Exact commit tested
- 8ec26a9ea426
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 32394ms: [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS All tests pass. Let me summarize the findings. exec /bin/sh -lc 'export JAVA_HOME=/tmp/jdk-17.0.20.1+1 && export PATH=$JAVA_HOME/bin:/tmp/apache-maven-… succeeded in 37298ms: [INFO] BUILD SUCCESS All verified. Here's the summary: tokens used 119,999 All verified. Here's the summary:
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.
- Recovered from all 2 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.
What did not, or is not known
- Took 17 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 7 3d projects Argusic has installed and timed, OSM2World was the 5th fastest to reach a running state, and 6 of 7 reached one at all.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/osm2world)Questions
- Does OSM2World run?
- Yes. OSM2World runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test OSM2World?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8ec26a9ea426. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test OSM2World?
- The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OSM2World take to install?
- 17 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 OSM2World need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OSM2World?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does OSM2World compare with the alternatives?
- Of the 7 3d projects Argusic has installed and timed, OSM2World was the 5th fastest to reach a running state, and 6 of 7 reached one at all.
- Where is the evidence for OSM2World?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.