map-machine
Python renderer for OpenStreetMap with custom icons intended to display as many map features as possible
Runssource: GitHubPythonMITcommit eab10c1ec9bc
Python, MIT licensed. The project labels itself: icons, map, maps, openstreetmap, openstreetmap renderer, osm, python and svg.
map-machine runs. An Argusic agent installed it in 8 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Map Machine Python package is installed in a venv, all 148 tests pass, and the render, icons, and version commands produce valid output.
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.
- Rendering crash: $industrial_opacity variable not resolved for way opacity (power_opacity -> $industrial_opacity not recursively resolved)5 minutes
- PEP 668 externally-managed-environment blocked pip install1 minute
- 10 command-line tests failed: 'map-machine' not in subprocess PATH1 minute
- pytest not installed in venv0.5 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- pytest tests/ -v exited 0, 148 passed; python -m map_machine render -b 2.284,48.860,2.290,48.865 --cache tests/data produced out/map.svg (3.2 MB valid SVG with 9 child elements); python -m map_machine render --mode white produced out/test_white.svg (valid SVG with 3382 child elements); python -m map_machine icons produced out/icon_grid.svg (valid SVG with 473 child elements) and out/icons_by_id/; python -m map_machine --version returned 'Map Machine 0.3.0'
- Model tokens used
- 165,788
- Exact commit tested
- eab10c1ec9bc
- 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.
White mode SVG width: 1118.0, height: 1416.0 White mode SVG children count: 3382 Icon grid SVG width: 384.0, height: 720 Icon grid SVG children count: 473 Here's my final summary. All 148 tests pass and the rendering commands produce valid SVG output. ``` ``` tokens used 165,788 Here's my final summary. All 148 tests pass and the rendering commands produce valid SVG output. ``` ```
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 8 minutes.
- Recovered from all 4 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
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)
iconsmapmapsopenstreetmapopenstreetmap-rendererosmpythonsvgsvg-iconssvg-map
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/map-machine)Questions
- Does map-machine run?
- Yes. map-machine runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test map-machine?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit eab10c1ec9bc. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test map-machine?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does map-machine take to install?
- 8 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 map-machine need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing map-machine?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for map-machine?
- 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.