learnosm-tw
  • Introduction
  • index
  • contribute
  • status
  • beginner
    • introduction
    • start osm
    • start id
    • start josm
    • more about josm
    • gps
    • papers
    • editing with josm
    • remote mapping
    • moving forward
  • editing
    • josm tools
    • josm plugins
    • josm more tools
    • josm presets
    • creating custom presets
    • josm relations
    • editing techniques
    • aerial imagery
    • correcting imagery offset
    • josm conflict resolution
    • id editor
    • josm adding orbview imagery
  • surveying
    • gps etrex20
  • coordination
    • remote
    • review
    • tasking manager
    • glossary
    • MMaps field
    • quality assurance
    • editing the wiki
  • osm data
    • data overview
    • file formats
    • getting data
    • geofabrik and hotexport
    • osm in qgis
    • setting up postgresql
    • osm2pgsql
    • osmosis
    • overpass api
    • converting to shapefile
  • map design
    • mapbox
    • tilemill
    • wms
    • github
  • sys admin
    • sds
    • postgis
  • mobile mapping
    • osmand
    • oruxmaps
    • osmtracker
    • gpsessentials
Powered by GitBook
On this page
  • Connecting Objects
  • Some Objects Should Not Connect
  • But, Some Objects Should Connect!
  • Overlapping Objects
  • Summary

Was this helpful?

  1. editing

editing techniques

Previousjosm relationsNextaerial imagery

Last updated 4 years ago

Was this helpful?

There are a number of common mistakes that mappers make when they start using OpenStreetMap. In this chapter we'll identify a few of the most frequent errors and offer some tips for mapping better.

Connecting Objects

Some Objects Should Not Connect

When you are creating polygons and lines that are not supposed to be connected, make sure that they are not merged together by sharing a node. For example, highway nodes should not be snapped to buildings, because no one likes a road that leads directly into a wall! If you want to disconnect two or more objects that share the same node, select the node and go to Tools->UnGlue Ways or press \<\>.

But, Some Objects Should Connect!

Roads that intersect should always share a node. If they do not share a common node, then the computer has no way of knowing that the roads actually connect to each other.

The only time that you would NOT have intersecting roads share a node is if one of the roads goes over the other road, and they do not, in fact, connect.

Overlapping Objects

A common error is to have overlapping polygons when the objects they represent do not overlap in real life. A building cannot overlap another building. This mistake is commonly made with buildings and landuse polygons. For example, a polygon drawn to represent a park outside a building should not overlap with the building. Instead it should be drawn next to the building.

There are some exceptions to this rule, such as schools. Within a school yard you might identify individual buildings using polygons, yet you also might want to create a polygon around the entire school yard. In this case it is fine for the polygons to overlap, but the rule to follow here is to make sure that the buildings are completely inside the landuse polygon.

Summary

We all make mistakes, but the more you map the less you will make less mistakes! Just remember that even if you upload data that contains mistakes, you can always fix your mistakes and upload the changes again. This is what is great about OSM: you can always make it better!