The street on the map has the wrong name. The path that exists is missing; the cafe that closed is still listed. You could learn to edit OpenStreetMap and fix it yourself, and this site would love that, but the system has a lighter front door built for exactly this moment: Notes. A note is a marker pinned to the map with a short message saying what is wrong there. Anyone can add one, with no account at all. Local mappers watch for notes in their area, investigate, fix the data, and close the note with a comment. The OSM wiki's Notes page and the OpenStreetMap blog post that launched the feature describe the system this guide teaches: how to report well, what happens next, and what notes are not for.
Home / GIS and Open Map Data for Beginners
OpenStreetMap Report Errors: Notes, the Fixer's Front Door

Photo: Pavel Danilyuk / Pexels
Report It So It Gets Fixed: The Notes Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 7 complete
0% done
Add a Note: Thirty Seconds, No Account
On openstreetmap.org, the Add a note button sits in the right-hand toolbar of the map (the speech-bubble icon); right-clicking the map offers the same action. Click it, and a marker appears, draggable to the exact spot; position it on the feature itself, not in the general neighborhood, because the marker's position is half the message. Type what is wrong, plainly and specifically (the craft of that sentence is the next section), and submit. No account is required to report. An account becomes valuable if you want to follow the conversation: signed-in reporters receive email notifications when someone comments on or resolves their note, and resolving notes is reserved to signed-in users. Anonymous notes are welcome and common, but they are fire-and-forget; if the fix needs a follow-up question answered, an anonymous reporter will never hear it asked. The account is free and takes a minute, and for any report more complicated than a typo it is worth having before you submit.
What a Good Note Says
Notes succeed or stall on their text, and the difference is a formula: what is there, what the map says, and how you know. "The path shown here was closed by a fence in June; the gate is at the marker, signed no entry, seen on foot" gives a mapper everything: the claim, the location, the evidence, the date. Compare the notes that sit open for a year: "map is wrong here," "this is not right," a marker dropped at a town's centroid complaining about a street name with no street named. The mapper who finds your note was not standing where you stood; your sentence is their only visit to the scene. Name the feature, name the change (opened, closed, renamed, moved, demolished), date it if you can, and say how you know (signage, local knowledge, a survey, a dated photograph described). Brevity is fine; vagueness is not. Write the note you would want to receive, and the median time between report and fix collapses, because most of that time was never repair time at all. It was detective time, and a good note spends it in advance.

The Lifecycle: Comment, Fix, Resolve
A note lives in public, on the map's notes layer (toggle it from the layers panel, the stacked icon on the right), as a marker: open notes in one color, recently resolved ones shown fading for a while after closure. Any signed-in user can comment on a note: asking for clarification, adding a second observation, recording "checked on today's survey, the fence is real." The fix itself is an ordinary edit to the data, made in any editor, usually by a local mapper, sometimes by the reporter who has since learned to edit (notes are the community's favorite recruitment device, and more than a few editors arrived through a note they filed). When the data matches reality again, the fixer resolves the note with a closing comment saying what was done. Resolved notes remain readable; the conversation is part of the map's public record, like the changeset discussions in our history guide. A note you filed with an account notifies you at each step, which closes the loop that anonymous reporting leaves open.
Notes Inside the Editors and Apps
You do not have to visit the website to meet notes. The iD editor can display notes as a data layer while you edit, and lets you create and resolve them in place, so a fixing session can sweep an area's notes as it goes. JOSM has full note support: download notes for an area, comment, resolve, upload. The mobile editor Vespucci does the same in the field, which is where notes and their fixes increasingly meet: a mapper surveying a neighborhood sees the open notes around them as they walk. Beyond the editors, the Notes API exposes notes programmatically, and an RSS feed can watch an area for new ones, which is how organized local groups keep their patch covered. The pattern to notice is that notes are not a website feature with integrations; they are a data type in the OpenStreetMap API itself, as first-class as a changeset, and every serious tool speaks them.
The Standing Rules: What Notes Are Not For
The wiki is explicit about the boundaries, and respecting them is part of reporting well. Notes are for data problems at a place: a wrong name, a missing path, a changed one-way, a demolished building. They are not a discussion forum: questions about tagging policy, arguments about a mapper's other edits, and general chat belong on the forum, the mailing lists, or changeset discussions. They are not personal bookmarks: "my hotel" and "park here" markers pollute the layer for everyone; your own map for your own pins is what uMap exists for. And they are never automated: bulk-generated notes dumped by scripts are treated as abuse, because each note asks for a human's attention, and spending that attention by the thousand without a human behind the report breaks the social contract the system runs on. One note, one place, one human observation: that is the unit the whole design assumes.
If You Can Fix It Yourself
The last thing to say about the front door is that it leads somewhere. A large share of note reports describe fixes that take ninety seconds in the iD editor: a name, a closure, an added path. If you find yourself filing a third note, consider making the edit instead; our editor guide walks the first session, and the history guide explains how your change will be recorded and reviewed. The community does not grade the door you arrived by. But it does notice that the people who write the best notes, specific, dated, evidenced, are already thinking like mappers, and the distance from a good note to a good edit is the shortest distance in the whole OpenStreetMap project. File the note either way. Just know the door behind it is open too.
Notes as Data: Feeds, Watchers, and Clean-Up Drives
Because notes are an API data type, they accumulate into something an organized community can work like a queue. The RSS feed for an area turns new notes into a stream a local group can watch the way a newsroom watches a wire; the first responder comments, the nearest surveyor detours past the spot that week, and the note closes with the fix attached. Groups run note clean-up drives the way they run mapping parties: pick a city, sort its open notes by age, and work the list, because the oldest notes are a fossil record of everything the area's mappers never got to, and many resolve in minutes once a human finally reads them (the cafe reopened, the roadworks finished, the one-way was made permanent and the data already agrees). QA tooling across the ecosystem surfaces notes alongside other error reports, so a note filed in a quiet area is not shouting into a void; it is entering every checklist that scans that ground. The lesson for the reporter is encouraging and slightly stern: your note will very likely be read, by someone, eventually, which is another reason to write it as if the reader were standing where you stood, because functionally, through your sentence, they will be.
What a Mapper Sees: The Other Side of Your Note
It helps to meet the note from the fixer's chair once. The mapper opens their editor over their home ground with the notes layer on, and your marker is one of a scatter. They click it and read, and in three seconds they know which of three fates it has: fixable from their chair (a name they know, a closure already in the news), needing a visit (which they may make, notes in hand, on the next survey), or unanswerable as written, in which case the professional move is a comment asking the one question whose answer unlocks it, not silent abandonment. Everything in this article's craft section is aimed at that three-second judgment: position on the feature, the change named, the evidence dated. A note that passes the judgment joins the fix queue of a person who was already going to spend their evening improving the map; a note that fails it waits for a more patient stranger. There is no bureaucracy between your observation and the world's map. There is only a sentence, and the person who reads it. Write the sentence like it matters, because in this system it is the entire mechanism.
Notes and the Law of the Map: A Brief Caution
One boundary deserves plain words before you report from the field. A note is a public statement attached to a place, and it should contain observations, not accusations: "the gate here is locked and signed private" is data; naming a person you believe did something wrong is a dispute, and disputes belong in the community's discussion channels, not pinned to their street. Likewise, report what a place is, not who lives there: notes are read by everyone, forever, and a note that documents a business's closure is cartography while a note that documents a resident's habits is surveillance wearing a hi-vis vest. The system's generosity, anyone may report, no account, no gatekeeper, runs on reporters exercising exactly this judgment. The wiki's rules about discussion and automation cover the formal edges; this caution covers the human one, and it is the difference between a note that improves the map and one that merely uses it.
Related Guides
If this page answered part of the question, these GIS guides cover the rest of the same ground:
- OpenStreetMap Editor: The iD Tour for New Mappers: The ninety-second fix, for reporters ready to make it themselves.
- OpenStreetMap History: Versions, Changesets, and Recovery: The audit trail every fix enters, notes included.
- OpenStreetMap uMap: Layers, Imports, and a Backup: The right home for the personal pins notes are not for.
- OpenStreetMap Opening Hours: The opening_hours Grammar, Decoded: The most common data error worth a note, and how the correct value is written.
Frequently Asked Questions
How do I report an error on OpenStreetMap without editing it?
Add a Note. On openstreetmap.org, click the Add a note button in the right-hand toolbar (or right-click the map), position the marker exactly on the problem, and write what is wrong and how you know. No account is needed to report.
Do I need an OpenStreetMap account to add a note?
No. Anyone can add a note anonymously. An account is needed to resolve notes, and it is worth having as a reporter because you receive email notifications when your note is commented on or resolved, which anonymous reporters never see.
What should I write in a note?
What is there, what the map says instead, and how you know: name the feature, state the change (renamed, closed, moved, demolished), date it if you can, and cite your evidence such as signage or a visit. Vague notes like "map is wrong" are the ones that sit open for a year.
What happens after I add a note?
The note appears on the map's notes layer for local mappers to find. They can comment to ask or add information, fix the underlying data in an editor, and resolve the note with a closing comment. Notes are also visible inside the iD and JOSM editors and in Vespucci, and through the Notes API.
What are OpenStreetMap notes not for?
Not for discussion or questions about tagging, which belong on the forum or in changeset discussions; not for personal bookmarks, which belong in a tool like uMap; and never for automated bulk reports, which are treated as abuse because every note asks for a human's attention.
Photo credits: Pavel Danilyuk (Pexels); Maël BALLAND (Pexels). Photos are served from this site; follow the credit to the library page for the original.