What Is OpenStreetMap? The Free Map of the World, Explained

OpenStreetMap is the Wikipedia of maps. It is a free, open, crowd-sourced map of the entire world, built by a community of millions of volunteers and used as the data backbone for thousands of products you already use, from weather apps to hiking apps to ride-share platforms.

This guide explains what OpenStreetMap actually is, how it works as a data set, how it differs from Google Maps, and what role it plays inside a modern production mapping stack like MapAtlas.

The Project, in One Paragraph

OpenStreetMap (OSM) was founded in 2004 in the United Kingdom by Steve Coast, after he grew frustrated with the lack of freely available digital map data. The idea was to build a map of the world the way Wikipedia was building an encyclopedia: anyone can sign up, anyone can add or edit a feature, and the resulting data is published under an open license. Today the project has more than 10 million registered users and a stable base of about 250,000 active mappers per year. The full planet file is about 88 GB as compressed PBF and grows every minute.

What OSM Looks Like as Data

OSM is not a folder of map tiles. It is a structured database of three primitive types:

• Nodes: single points with a latitude and longitude. Used for things that are essentially a point (a bench, a tree, a parking meter), and as the building blocks of more complex shapes.
• Ways: ordered sequences of nodes. Used for linear features (a road segment, a river) and closed shapes (a building footprint, a park boundary).
• Relations: groupings of nodes and ways. Used for things like bus routes (a sequence of road segments), administrative boundaries (a polygon made up of many ways), and multipolygon features.

Every node, way, and relation has a set of key-value tags. A road might have highway=residential, name=Rue de Rivoli, maxspeed=30. A coffee shop might have amenity=cafe, name=Cafe Central, opening_hours=Mo-Fr 07:00-19:00, wheelchair=yes. The tagging vocabulary is community-defined, evolving, and documented on the OSM wiki.

This combination of open primitives and tagged metadata is what makes OSM so reusable. You can extract every cycle path in Berlin, every defibrillator in the Netherlands, or every wine region in France with one structured query.

How the Map Gets Made

OSM is edited continuously by volunteers using web editors (iD), desktop editors (JOSM), and mobile editors (Vespucci, StreetComplete). Edits flow into a central database within minutes. Source material includes:

• Aerial imagery licensed for OSM use (Bing, Esri, and national orthophotos)
• GPS traces uploaded by community members
• Government open data (cadastre, road inventories, address files)
• Local knowledge, especially for opening hours, names, accessibility, and small features
• Mass imports of structured data sets (carefully reviewed, since bad imports damage data quality)

Quality control is community-driven: experienced mappers review changes, automated tools flag suspicious edits, and per-region communities maintain local conventions. The result is a map that is unusually detailed in places where the community is active (Western Europe, urban North America, Japan) and patchier in less-mapped regions, where commercial alternatives sometimes have an edge.

This is also why categories a commercial vendor would never carry end up on the open map. Traffic enforcement cameras are tagged with highway=speed_camera and enforcement relations, and an Overpass count on 27 August 2026 returned 76,800 worldwide.

OSM and the Wider Open Map Data Landscape

OSM is the best-known source of open map data: geographic data published under a license that lets anyone use, modify, and redistribute it. "Open" describes the license, not the price. Plenty of free map data only lets you look, while open data lets you build and pass it on.

Since 2022 there is a second large open dataset. The Overture Maps Foundation, backed by Amazon, Meta, Microsoft, and TomTom and hosted by the Linux Foundation, publishes versioned releases organised into themes such as transportation, buildings, places, addresses, and divisions. Overture ingests OSM, adds data contributed by its members and features derived by machine learning (building footprints detected from imagery, for example), and runs everything through conflation and quality checks.

The licensing differs in a way that matters. OSM uses the ODbL, a share-alike license: if you publicly distribute a database derived from OSM, that database must also be offered under ODbL, with attribution. Most Overture layers use permissive licenses such as CDLA-Permissive, which drop the share-alike obligation, although layers that carry OSM data keep OSM's terms. Before you ship, check the license on each specific layer you use.

Overture's most debated contribution is GERS, the Global Entity Reference System, which gives each road, building, or place a stable ID that persists across releases, so you can join your own records to the map without re-matching by name and coordinates each time. In February 2026 the Open Geospatial Consortium requested public comment on adopting GERS as an OGC Community Standard. Supporters see a long-missing universal join key; critics in the OSM community worry about an identifier scheme governed by a group of large companies becoming the default for data that volunteers maintain.

OSM vs Google Maps

The most common question developers ask is whether to build on OSM or on Google Maps. The honest answer depends on what you are building.

OSM strengths: open data you can host, redistribute, and analyse; richer point-of-interest tagging in many regions; transparent provenance; full European data sovereignty; predictable pricing through OSM-based providers; the ability to render custom map styles for your brand.

Google Maps strengths: Street View imagery; very strong business listing data in some regions; consumer brand recognition.

For developer-grade products that need EU hosting, GDPR-clean data flows, custom styling, and predictable pricing, an OSM-based stack is usually the better choice. For consumer products that lean heavily on Google's business reviews or Street View imagery, Google has unique value.

How Production APIs Build on OSM

You almost never call the OSM database directly in production. Instead, you use a hosted API that builds on OSM data and adds the layers OSM does not provide on its own:

• Tile rendering: rendering the full planet into fast map tiles for every zoom level requires a serious tile pipeline. Hosted providers do this for you.
• Geocoding: turning addresses into coordinates needs an indexed search engine on top of OSM, plus heuristics for ranking and disambiguation.
• Routing and isochrones: OSM has the road graph, but computing actual driving directions and travel-time polygons needs a routing engine (OSRM, Valhalla, GraphHopper) running on dedicated infrastructure.
• Map matching, distance matrices, optimisation: same story.
• SLAs, EU hosting, GDPR compliance: hosted providers package the data with the contract terms enterprise teams need.

MapAtlas is the European mapping platform built on OSM-grade data with EU-only hosting, GDPR-clean infrastructure, and developer-grade APIs for geocoding, routing, isochrones, distance matrices, and dynamic styled maps.

When You Need Direct OSM Data

Sometimes you do want the raw data. Common cases:

• Bulk analysis: counting all electric vehicle charging stations in Germany, mapping every defibrillator in Spain.
• Custom GIS workflows: importing into PostGIS for spatial joins.
• Internal map products: rendering your own tiles with full control over the style.
• Data enrichment: adding OSM tags to your own location records.

For these, the Geofabrik extracts or Overpass API are the standard entry points. Both are free, both run on volunteer infrastructure, and both come with attribution and license terms you should respect in any redistributed product.

Why MapAtlas

MapAtlas builds developer-grade APIs on top of OSM-derived data with EU-only hosting and GDPR-clean infrastructure. The Geocoding API, Search API, Directions API, and Isochrone API all return clean, well-tagged location records that work cleanly in production code and in the structured data you ship to AI assistants. For a hands-on intro, try the Coordinates Lookup tool or read What Is a Geocode for the deeper context.