Good practice
OpenStreetMap is a free project done by volunteers. Anyone can contribute, and nobody is forced to follow rigid rules, but shared practices keep the map data accurate and easier to maintain. Exceptions apply, and guidelines can occasionally conflict. For a brief summary of the shared community values behind these practices, see How We Map.
Do correct errors
When OpenStreetMap is missing data or when things change in the real world, be bold and edit the map to reflect the current situation.
Your additions can be refined or reverted when needed, so do not hesitate to edit. However, be respectful of the work done by other mappers and consider consulting them when existing data uses unfamiliar methods or tags, as there is often more than one valid way to map a situation. Also be careful when deleting data, because finding and restoring removed objects is harder than adjusting additions.
If you are a beginner, unsure, or mapping in an unfamiliar area, feel free to ask local mappers to review your edits. For practice or test edits, use the editing sandbox instead of the live database.
Don't copy from other maps
- Main article: Don't copy from other maps
Contributions to OpenStreetMap must not infringe anyone else's copyright or database rights and are submitted under the Contributor Terms. Never copy from commercial maps (such as Google Maps or Apple Maps), commercial street-view services, or proprietary directories. Even publicly visible or "open" external datasets are not automatically compatible with OSM unless explicitly cleared (see Copyright, Legal FAQ, and Licence Compatibility).
Map verifiable features
- Main article: Verifiability
OSM data should, as far as is reasonably possible, be verifiable. This applies to geometry, tags, and other details, meaning another mapper should be able to visit the same place and confirm what you entered. It excludes hypothetical, speculative, or opinion-based data such as personal ratings.
Map what's on the ground
Sometimes sources conflict on details such as a place name. An old map may spell it one way, another dataset a second way, and a street sign a third. People using our maps need names to match local signs on the ground, so local signage generally takes priority. The main exception is an obvious typo on a sign such as John F. Kennwdy Square in places where people would clearly look for the standard spelling. See Ground truth, Verifiability, and Scope (including established exceptions such as unmarked administrative borders or underground infrastructure mapped from surface markers and permitted records).
Don't map historic events and historic features
- Main article: History
Do not map objects that no longer exist or the sites of historic events, as they cannot be verified on the ground today. If physical ruins remain and are verifiable, map the ruins (for example using historic=ruins). Objects that no longer exist and historic events belong in OpenHistoricalMap. Features that were recently demolished but still appear in older imagery may temporarily carry a Lifecycle prefix such as demolished:*=* until imagery updates so that other mappers don't add them back by mistake.
Don't map temporary events and temporary features
Our map data is often downloaded and used offline on devices for weeks or months. For mapped features to stay useful, they should normally be expected to remain in place for at least several weeks. Regular recurring events (such as a weekly market) can be mapped with time tags like opening_hours=*. Active building work can be mapped using construction=* once work visibly starts, while unbuilt plans should stay off the map (with proposed=* used sparingly for officially approved major infrastructure).
Don't map private information
Don't map private personal information such as residents' names, personal contacts, or home interiors. Ordinary visible structures like houses, rooftop solar panels, backyard swimming pools, and residential driveways are not considered private information and are fine to map, as long as you use appropriate access tags like access=private whenever applicable.
Don't tag for the renderer
- Main article: Tagging for the renderer

Map things as they are on the ground. Do not enter wrong tags or distort geometry just to make a map renderer or data consumer draw things differently. Renderers improve continuously, so instead of bending the data, try another map style or report rendering issues or requests upstream, for example on OpenStreetMap Carto's GitHub for issues with openstreetmap.org's "Standard" layer.
Don't tag for the router
- Main article: Tagging for the router
Do not use inaccurate tags or alter geometry to force a specific route calculation. Follow standard mapping practices instead, try another routing engine, or report routing bugs to the routing project.
Don't map local legislation if not bound to specific objects
OpenStreetMap is a geographic database, not a legal code. Only tag rules that apply to a specific feature or vary from place to place (such as maxspeed=*, oneway=*, or access=* on a road). Do not tag general laws that apply uniformly across a whole country or region, such as the legal driving age or blood alcohol limits.
Tagging the default speed limit under maxspeed=* on an unsigned road is still useful because speed limits vary by road, and adding it shows the street was checked rather than left unmapped.
Don't use name tag to describe things

- Main article: Names
The name=* tag is only for a feature's proper, specific name (something locals call it or a name on a sign or plaque, such as Main Street or Central Park), never a description of what kind of thing it is. For example, do not tag an unnamed statue as name=Marble statue or an unnamed forest track as name=track or name=Waldweg. Use tags such as highway=track or material=marble to describe the feature instead.
Write good changeset comments
- Main article: Good changeset comments
A good changeset comment concisely explains what you changed and why. It helps fellow mappers understand your edits and intentions. Listing your sources lets others know that your information is accurate and up-to-date. Answer changeset questions politely, avoid edit wars, and escalate unresolved disputes to the Data Working Group.
Keep the history
- Main article: Keep the history
When things change in the real world, be bold and update the map directly, but try to preserve element editing history by modifying existing objects rather than deleting and redrawing them from scratch.
However, do not reuse one OSM element to carry the history of a completely different replacement object. See Don't mix the history for details. Before making significant changes to major features, check their history first.
One feature, one OSM element
- Main article: One feature, one OSM element
An OSM element should represent one real-world feature once and only once. Do not place a duplicate node inside an identically tagged area just to make an editor icon appear.
If you trace the area of a feature that previously existed as a node, delete the old node or reuse it in the outline as explained in Keep the history, moving its tags onto the area. See One feature, one OSM element for known exceptions.
Editing Standards
- Main article: Editing Standards and Conventions
Align aerial imagery before tracing
- Main article: Using aerial imagery
Aerial imagery always has some offset relative to real positions on the ground. Often the offset is small, but it can easily be well over 10 meters and shift across short distances. Always check and adjust imagery alignment before moving existing OSM data or tracing new features.
To check alignment:
- Use existing GPS traces or high-precision survey data
- Compare imagery against trusted existing OSM features
iD, JOSM (plus Imagery Offset Database), and Vespucci all include imagery alignment tools.
Do not trace from outdated imagery
- Main article: Armchair mapping
Available aerial imagery may be years out of date. Before changing or deleting existing OSM data based on aerial photos, check the element's history, changeset comments, and imagery capture dates so older photos do not overwrite newer ground surveys. When mapping remotely, take extra care to cross-check newer sources.
Average out GPS-traces
- Main article: Accuracy of GNSS data
A single GPS trace can drift by several meters depending on signal conditions. Averaging multiple traces over the same road reduces individual errors substantially. It helps to upload your GPS traces even on already-mapped roads so others can use them to average positions and align imagery.
Keep straight ways straight
When a road or wall is genuinely straight on the ground, draw it with as few intermediate nodes as needed (just two endpoints where there are no intersections). Individual GPS tracks often wobble even on straight streets (Accuracy of GNSS data).
JOSM, iD, and other editors have tools to straighten ways and square corners cleanly. Still, whenever multiple GPS traces or aligned aerial imagery show a real bend, follow the real shape on the ground.
As an exception, on straight features longer than roughly 500 meters (such as state borders following lines of latitude or longitude), add intermediate nodes so their geometry stays accurate across different map projections.
Map curves with an appropriate number of nodes
Use a reasonable number of nodes on curves and other non-linear features. There is no rigid node count, so use judgment and place enough nodes to follow the curve smoothly without sharp angles between consecutive segments. Tight bends need closely spaced nodes, while gentle curves need fewer.
Mark estimations with fixme
Occasionally it is useful to map an approximate position or uncertain tag rather than leaving a gap completely unmapped. Mark rough estimates with fixme=* (and add note=* if helpful context explains what still needs checking) so someone knows to revisit it later.
Don't over-use semi-colon separated values
Semi-colon value separator characters allow a key to hold multiple values. While this works well in minor attributes or list-like tags such as opening_hours=*, avoid multi-value strings in major top-level tags like highway=*. Over-using semi-colons complicates tagging and weakens support across data consumers. Also avoid using relations as categories.
Document your custom tags
- Main article: Proposal process
- Main article: Creating a page describing key or value
When you use tags not listed on Map features, help other mappers understand them by documenting them cleanly. Avoid placing unproven custom tags directly onto Map features or creating Key: or Tag: pages prematurely, as those pages document established tags with significant real-world usage. Instead, create a proposal page, document the tag on a user subpage, or discuss it on an existing talk page (see also Any tags you like).
Don't remove tags that you don't understand
You will sometimes encounter elements carrying unfamiliar tags. Do not delete them just because you do not recognize them. They may serve a specialized tool or mapping effort. Research them on the wiki or ask the original author first (see Chesterton's fence on Wikipedia).
Don't remove objects that you don't need or like
Be bold when adding missing data, and careful when deleting someone else's work. Details such as underground pipes or manhole covers may not show up on your preferred map style, but they might serve a purpose to someone else. Do not delete valid real-world features merely because you do not need them, dislike them, or an automated validator questions them.
Consult the community before big changes
While normal day-to-day mapping needs no permission, large changes can easily break existing data or clash with local conventions. Always discuss data imports, automated edits or mass tag changes, and organised mapping campaigns with local mappers via Contact channels beforehand, and follow the linked guidelines.
See also
- Scope (what belongs and what does not belong in OpenStreetMap)
- Editing Standards and Conventions (detailed technical conventions for editing geometry and tags)
- Quality assurance (tools for spotting and checking mapping issues)
- Organised editing best practices
- Tagging samples (highway tagging examples with photos)
- Category:Tagging guidelines by country (country-specific guidelines and local conventions)
- Any tags you like
- Just map
- Limitations on mapping private information
- Good practice in OpenHistoricalMap