NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum

# What are the most common mapping mistakes that other users make?

 64 28 I'm interested in identifying the most common mapping errors you stumble upon from other OSMers (or that you make yourself). If we could list some of the most common mistakes then we could use that information to drive improvements that may help to prevent the same mistakes being made in the future (e.g. by clarifying the wiki documentation, modifying the editor UI, writing scripts to find the mistakes etc). This is obviously a very subjective question, but hopefully some people may find the answers useful. Please try to stick to definite actual errors, rather than simple differences of opinion. This question is marked "community wiki". asked 06 Oct '10, 15:01 GrahamS 3.6k●21●45●54 accept rate: 28%

 -1 Missing bridges above (which I also up-voted), provided the answer to one of my questions: how to mark two intersecting one-way highways that do not permit turning from one to the other. In the acute angle case, than 135 degree and very difficult at 35mph (55km/hr). In the obtuse angle case, it would result in collisions at that speed or higher. The answer: put a node at the intersection. I already had placed no turns permitted restrictions on the approaches to the intersection. answered 16 Mar '17, 01:37 OverThere 25●1 accept rate: 0%
 2 Sharing highway nodes with landuse answered 24 Feb '17, 12:43 Martin Borsje 40●2●3●6 accept rate: 0% That's not a "mistake" since there is no consensus. Although many mapper discourage from joining ways with landuses. (24 Feb '17, 15:21) scai ♦

# Not identifying the different segments of a road properly

Often different segments of a given road are given different names. (Typically, the name of the road changes after a major junction or roundabout.)

But often the mapper does not break the road into segments, or provide the correct names to these segments.

This is a common mistake of a mapper who is tracing an uncharted area just using the Bing satellite image, but without much local knowledge.

NarayanAras
3115818
accept rate: 0%

# To draw a building shape, the mapper traces its terrace, but does not move it to its base

This "parallax error" is an extremely common mistake in drawing shapes for highrises.

The mapper uses the Bing satellite image, and traces out the top of the building.

But he forgets that the satellite image is not exactly "top-down", about 15 degrees angle to the vertical. Thus the base of the building does not lie exactly under its top. In fact, the taller the building, the more this offset!

On the other hand, all map features having low heights are traced without such parallax errors. For example, roads, boundary walls, low-rise buildings.

As a result, many tall buildings appear to be shifted from their actual positions. Some even touch (or "crash into"!) the adjoining areas.

NarayanAras
3115818
accept rate: 0%

# Confusion between "Common Name" and "Operator" of a POI

For example, take a Citibank ATM.

1. Is "Citibank" a 'common name' or 'operator'?
2. Should "ATM" be a part of the Common name?

Another example: A Dominos pizza joint. Legally, "Dominos" is the brand, operated by a local franchisee (a separate business entity). So how to fill these attributes?

As a result, I have seen inconsistent entries in POIs.

Suggested solution: The mapping tools (iD/Potlatch) should have more explicit tooltips.

NarayanAras
3115818
accept rate: 0%

For standalone ATMs (not part of some other feature) "amenity=atm". If the operating bank is indicated, then also tag with, eg, "operator=Citibank". I've never seen a standalone ATM with a name (eg "Jimmy's Cashhole"?), but the world is full of wonders.

It's tempting to name them after the operating bank, so the bank name will render on the map. But of course that's a no-no, "tagging for the renderer."

To indicate the presence of ATMs as part of another feature, tag with "atm=yes". If that feature is a bank, that bank would be presumed to be the operator. If that feature is not a bank, very often the ATM is no-name and doesn't need an operator.

But of course there's always an exception. For instance, in New York the Duane Reade pharmacies usually contain ATMs operated by Chase Bank, and it would be great to be able to tag them as such. We might consider something like "atm:operator=Chase" after the "atm=yes", or just skip the "atm=yes" and create a separate "amenity=atm" node with "operator=Chase".

As far as Domino's pizza goes, "name=Domino's" or "name=Domino's Pizza" (whatever the sign says) and leave the operator off unless you observe specific operator data.

(06 Jan '18, 17:56)
 6 In Africa highway mapping, track only goes to farmland. So ruled in Highway_Tag_Africa. "The road conditions in African countries do not always correspond to their economic and social role. A road typology should be based on the road importance and not on the surface or the visual appearance of a road." This means, it may look like a track but, if it goes from a major road to a hamlet, it's an unclassified highway, except a 4x4 can't drive it because it wiggles too much (then it's a path). Ditto from hamlet to hamlet. People new to Africa mapping always get this wrong. answered 13 Dec '14, 14:51 rwst 160●3●6●9 accept rate: 0% 1 That's not so different from other countries. The highway tag should be used to tag the road classification, not the road's look. (13 Dec '14, 17:13) scai ♦
 0 Sometimes users forget to mark that location which is most important for the people during travel like signs of hospitals, fire brigade and shopping complex. Hope you can understand the fact behind mapping. answered 08 Jul '14, 06:37 denygarcia 35●2 accept rate: 0% SomeoneElse ♦ 36.9k●71●370●866 1 I would not classify this as mistake, people are not obliged to map. Contributing something that you consider not the most important thing is NOT a mistake. (16 Jul '14, 23:41) Mateusz Koni...
 1 Deleting nodes whose tag's don't show up in Potlatch 2. I have seen situation where new users will "clean up" nodes whose tags are "Not recognised". Hopefully this will be going away with the greater prominence of iD. answered 06 Jul '14, 13:58 InsertUser 11.0k●13●69●185 accept rate: 19%

## Using search-and-replace to do small 'mass edits'

New users tend to use the search-and-replace function of editors to do 'corrections' to a massive amount of nodes or ways in their area when they believe they found an 'error' of some kind.

Not mentioning here if the 'error' really is one or not (new users might have trouble understanding all the tagging schemes used in OSM), the mere application of such changes in an automated manner often destroys more valuable data than it fixes. This is also regularly used to fill in perceived "blanks", even if those blanks are left intentionally or are coverde by some kind of default.

Examples are

• attaching addr:postcode or addr:city to all buildings in a region (overwriting manually set fringe cases where postal address doesn't match real location)
• adding oneway=no to all highways which don't have oneway=yes
• standardizing names of shops/food chains, even if there really are some that carry another name on their sign

This is often combined with the "leave no changeset comment" problem already mentioned.

Chaos99
5311711
accept rate: 14%

By Email:

Markdown Basics

• *italic* or _italic_
• **bold** or __bold__
• image?![alt text](/path/img.jpg "title")
• numbered list: 1. Foo 2. Bar
• to add a line break simply add two spaces to where you would like the new line to be.
• basic HTML tags are also supported

Question tags:

×352
×193
×45
×1

question asked: 06 Oct '10, 15:01

question was seen: 70,592 times

last updated: 20 Sep '20, 21:15

### Related questions

NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum