Home / GIS and Open Map Data for Beginners

OpenStreetMap History: Versions, Changesets, and How Deleted Features Come Back

A magnifying glass lying on a vintage book opened to a map

Photo: Feyza Daştan / Pexels

OpenStreetMap never throws anything away. Every node, way, and relation carries a version number, and behind that number sits the complete sequence of its earlier selves, each stamped with the changeset that made it and the editor who saved it. That history is not an archive locked in a vault; it is a public page one click from every feature, and it turns the map into something unusual among databases: a system where every fact can be audited back to its author and its moment. This guide teaches you to read that record: the element history page, the changeset page, the history tools in JOSM, the visual viewers, one subtlety about versions that confuses everyone once, and the recovery workflow for features that have been deleted outright.

Interactive tool

Read the Biography: The History Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 7 complete

0% done

The Element History Page: Every Version, in Order

On openstreetmap.org, open any feature and follow its View history link (every element page carries one, at an address of the form openstreetmap.org/node/123456/history, and likewise for ways and relations). The page lists every version of the element from first to last: version number, the date and time, the changeset it belonged to, the editor's username, and the state of the element at that version, its coordinates for a node, its member nodes for a way, its tags throughout. Reading top to bottom, you watch the feature's life: created as a rough point, moved to the surveyed position, tagged, retagged when the shop changed hands, corrected after a survey. Two uses dominate. The first is diagnosis: when a feature looks wrong today, its history shows whether it was always wrong, was vandalized last week, or was right until a well-meaning edit moved it. The second is attribution: history is how the community thanks, questions, and when necessary blocks editors, because nothing on the map is anonymous in the record.

Changesets: The Unit of Editing

Versions do not float free; each belongs to a changeset, the bundle of edits an editor uploaded in one save. The changeset page shows the bundle whole: its bounding box on a map, the list of elements created, modified, and deleted, the editor's comment describing the work, and the discussion thread where other mappers can ask about it, publicly, forever. The comment matters more than newcomers expect. "Survey, added buildings" tells a reviewer exactly what to check; an empty or misleading comment invites suspicion of everything in the bundle. When you investigate a suspicious edit, the changeset is your real subject: one bad version is an accident, a changeset full of them is a pattern, and the discussion thread is where the community's immune system does its work, usually politely, in the open.

Vintage eyeglasses and a magnifying glass resting on an antique map
Vintage eyeglasses and a magnifying glass resting on an antique map

The JOSM History Window: Versions Side by Side

The website's history pages list versions; JOSM, the desktop editor, compares them. Select an element and press Ctrl+H to open its history in JOSM, where versions sit side by side: tags added, removed, and changed are highlighted, and for ways you can see how the geometry itself evolved as nodes were added, dropped, and moved. For nodes, JOSM can show the coordinate drift across versions on a small map, turning "someone moved this" into "someone moved this 40 meters northeast in March." This is the working tool for the two forensic jobs that matter most: reviewing a disputed edit with evidence instead of vibes, and preparing a revert, where a damaging changeset is undone and the prior versions are restored as new versions on top. History in OSM is append-only; even a revert does not erase the bad version, it supersedes it, which is why the record stays trustworthy.

Achavi and OSMCha: Watching Change as Pictures and Feeds

Two community tools make history visual at scale. Achavi renders a changeset as a map of its changes: new features in one color, modified in another, deleted in a third, laid over the area the changeset touched. It answers the reviewer's first question, what did this edit actually do to the map, in one picture. OSMCha works the other end of the telescope: a feed of changesets filtered by area, size, editor, or suspicion flags, built for the mappers who patrol their regions watching for damage. Together with the history pages they form the community's observatory: Achavi for the single edit under your nose, OSMCha for the stream of edits across your city, the element page for the biography of the thing itself.

The Subtlety: Moving a Way's Nodes Does Not Raise the Way's Version

Here is the fact that breaks every beginner's mental model once. A way's geometry is its list of nodes, and when an editor drags one of those nodes to a new position, the node's version rises, because the node changed. The way's version does not, because the way's own data, its node list and its tags, did not change at all; the same nodes, in the same order, with the same tags, merely sit somewhere else now. The way moved on the map while its history page shows nothing. This is not a bug; it follows from the data model our PBF guide describes, where ways reference nodes rather than containing coordinates. But it means a way's history alone cannot prove its geometry never changed: for the full story you must read the histories of its nodes, which is exactly what JOSM's history tools assemble for you. Remember the rule and a whole class of "but nobody edited this road" mysteries dissolves.

Recovering a Deleted Feature: Overpass Attic Data

Deletion in OpenStreetMap means the current version of an element is marked deleted; the record remains, and with it, recovery. The workflow: find the element's ID (from its history page if you have it, or from a changeset that touched it), read its last good version in the history, and then fetch the feature as of a date before the deletion using an Overpass attic query, Overpass's ability to query the database as it stood at a past moment. The attic returns the element's geometry and tags as they were, ready to be restored in an editor as a new version (or a new element referencing the old one's history, handled with the care the community's revert guidelines describe). Two courtesies govern this power: check first whether the deletion was deliberate and correct, because restoring a rightly deleted feature restarts an argument; and say what you are doing in your changeset comment, because the next historian to read this biography will be glad you did. The editor tour in our OpenStreetMap editor guide covers the tools you will restore it with.

Why History Is the Product

It is tempting to treat all this as plumbing. It is closer to the point of the project. A map anyone can edit survives on the ability to check anyone's edits, and that ability is history: public, complete, and permanent. It is why vandalism on OpenStreetMap is usually a nuisance measured in hours rather than a corruption measured in years, why researchers can reconstruct the map as it stood on any date, and why your own edits deserve good changeset comments: you are writing, in public, the biography of the world as the next mapper will read it. Edit like a historian is watching, because one is, and it might be you, in JOSM, at Ctrl+H, wondering what a past editor meant. Leave them the comment you would want to find.

History at Scale: The API and the Full History Dump

Everything above works through web pages and editors, one element or changeset at a time. The same record is available in bulk for people whose questions are bigger. The OpenStreetMap API exposes history programmatically: an element's full history can be fetched directly, which is how research tools and QA pipelines ask "show me every version of everything in this bounding box's past." And the project publishes a full history dump of the planet, every version of every element, the so-called history file, which is the dataset behind serious studies of the map's growth: how cities were mapped, how fast vandalism is reverted, how coverage evolved country by country. Working with it is a specialist's game (the file is enormous and its format assumes you know the data model cold, which our PBF guide can help with), but its existence completes the picture this article has been drawing. History in OpenStreetMap is not a feature of the website. It is a property of the dataset, published like the dataset, at every scale from one node's page to the biography of the whole planet. A mapping project that can be audited at any zoom, temporal as well as spatial, is a different kind of public record than a map that merely shows the present, and it is the deepest reason the community's trust model works.

Reading History Responsibly: The Editor on the Other End

One etiquette completes the technical picture. Every version you will ever read was written by a person, most of them volunteers, all of them entitled to the presumption that an odd edit was an honest attempt before it was anything else. History makes investigation easy, and ease invites a prosecutorial tone the community works to avoid: the standard first move on finding a damaging edit is a friendly changeset comment explaining the problem, because the commonest authors of bad edits are beginners who did not know, and a large share of them become careful mappers after exactly one such message. Save the heavier machinery, the revert discussions, the data working group, for the patterns that survive a polite question: the repeated, the deliberate, the commercial spam. The record gives you the evidence to tell those apart, which is its purpose. Use it to understand first and to accuse rarely, and the history pages become what they were designed to be: not a surveillance system, but a shared memory that lets strangers maintain one map together without ever meeting.

Related Guides

If this page answered part of the question, these GIS guides cover the rest of the same ground:

Frequently Asked Questions

How do I see the history of an OpenStreetMap feature?

Open the feature on openstreetmap.org and follow its View history link. The history page lists every version of the node, way, or relation, with the date, the changeset, the editor, and the element's tags and geometry at each version.

What is a changeset in OpenStreetMap?

A changeset is the bundle of edits uploaded in one save: the elements created, modified, and deleted, shown on a map with the editor's comment and a public discussion thread. Versions of individual elements each belong to exactly one changeset.

Why did a way move on the map when its history shows no new version?

Because moving a way's nodes changes the nodes, not the way. The way's own data, its node list and tags, is unchanged, so its version does not rise. To see the movement, read the histories of the way's nodes; JOSM's history window assembles them for you.

Can a deleted OpenStreetMap feature be recovered?

Yes. Deletion marks the current version as deleted but keeps the record. Read the element's history for its last good state, fetch it as of a date before deletion with an Overpass attic query, and restore it in an editor, after checking the deletion was not deliberate and correct.

What are Achavi and OSMCha used for?

Achavi renders a single changeset as a color-coded map of what was created, modified, and deleted. OSMCha is a review feed of changesets, filterable by area and other criteria, used by mappers who monitor their regions for damaging edits.

Photo credits: Feyza Daştan (Pexels); Feyza Daştan (Pexels). Photos are served from this site; follow the credit to the library page for the original.