Wandering Around: a browser game that turns OSM into a walkable world
Posted by MikeHur on 3 November 2026 in English. Last updated on 5 November 2026.I’ve been building Wandering Around, a free browser game in which you can walk around any town or city on Earth. The whole world comes from OpenStreetMap, so I’d like to share how it uses OSM data and ask this community for feedback.
Play it here: https://wanderingaround.games (works on phone and desktop, no account needed) Screenshots and a short video: https://mikehur.itch.io/wandering-around
How the map is built
- Streets, buildings, water, parks and bridges come from OpenFreeMap vector tiles (zoom 14, OpenMapTiles schema). The game fetches the tiles around the player, decodes them in the browser, stitches buildings that are split across tile edges and turns everything back into OSM-style features with tags. The game logic works on those tags, so it is the same code whether the data comes from tiles or (as a fallback) from Overpass.
- 2D and 3D: the same data drives a 2D map and a 3D eye-level view. Building heights come from OSM where they are tagged.
- Transit: train routes and stations, city buses, ferries and signposts come from Overpass queries, so you can travel between real stops and stations.
- Country map: towns, airports and ferry ports within 100 km come from pre-built tiles made from Overture, OurAirports and Natural Earth.
What the game adds itself
Vector tiles leave out some details, such as single trees, benches, crossings, traffic lights and roof shapes. The game fills those in itself so streets don’t look empty. These are decoration, not data: they are never written back anywhere.
Wikidata postcards
Every feature with a wikidata tag (and, in the Netherlands, ref:rce for national monuments) becomes a landmark. When you visit one you get a postcard with:
- a photo from Wikimedia Commons (P18), with the photographer and licence shown,
- year built (P571), height (P2048) and floors (P1101),
- a summary from Wikipedia in your language.
In the 3D view the game uses the Wikidata height for the building and takes the facade colour from the photo. So a good wikidata tag on a building directly improves what players see.
What I’d love feedback on
- Does your own area look right? Missing buildings, odd water or bridges, or stops in strange places usually point to a tagging pattern I don’t handle yet.
- How do performance and rendering hold up in very dense city centres, compared with rural areas?
- Any ideas for using more OSM data in a game in a way that is fun and encourages people to improve the map.
Thanks to everyone who maps. Without your work this game would be an empty grey square.
Map data © OpenStreetMap contributors · tiles by OpenFreeMap · Wikidata · Wikipedia · Wikimedia Commons
Discussion
Comment from frederik_nlp on 5 November 2026 at 15:09
The “Wikipedia summary in your language” is the feature that made me stop and read the whole entry. It’s the same entity - a building, a bridge, a park - accessible from any language, and this is the first place I’ve seen that done in a way that feels natural rather than bolted on. The 3D facade colour from the photo is a nice touch too; a good
wikidatatag does double duty.I’ll try it in Aarhus this week and report back on how the Danish summaries come through - danwiki is small but it covers the major landmarks, so it should be a decent test case for the less-resourced end of the spectrum.
For the “encourage people to improve the map” question: the postcard mechanic is already doing that quietly. When someone sees their local church rendered with a photo and a summary, and then notices the summary is missing or the photo is bad, the fix is three clicks away in the editor. That’s the loop you want.
Comment from MikeHur on 5 November 2026 at 15:33
Thanks, glad that part landed! One honest correction though: “your language” currently means the app’s interface language, which is Dutch or English. So in Aarhus you’ll get the English Wikipedia summary, not the Danish one, even when danwiki has an article.
That said, your test is still useful: I’d love to hear how many Aarhus landmarks have a decent enwiki summary at all, and how many only exist on danwiki. That would tell me whether it’s worth adding a fallback: take the summary from the device’s language when a sitelink exists, and fall back to English otherwise. The wikidata sitelinks make that fairly cheap to do.
Comment from rphyrin on 6 November 2026 at 15:51
Add quests and storylines, particularly around specific points of interest (POIs) such as schools, stores, clinics, etcs. Introduce NPCs who serve more meaningful purposes than just being bots: characters players can interact with, talk to, receive quests from, and buy items from.
Also, consider opening the platform to user-generated storylines, similar to NationStates.net’s issue submission system.
A long time ago, I also developed a similar game. The main objective was to find a destination as efficiently as possible, using the fewest possible paths, with one restriction: players could only travel along public roads. While travelling towards their destination, players could encounter hidden quests placed around specific POIs whenever they passed through those locations.