OpenStreetMap logo OpenStreetMap

We know OpenStreetMap is one of the most powerful and collaborative geospatial databases in the world. It relies on contributions from everyday users, developers, humanitarian workers, and mapping enthusiasts to keep data accurate and up to date.
But like any open data project, OSM faces issues. And understanding the types of issues we encounter is essential to maintaining map quality. One simple and effective way to think about OSM data problems is, to divide them into two broad categories:

1. Existing Issues: Errors in the Map

These are problems that exist within the current OSM data. The features are already mapped, but something about them is incorrect, inconsistent, or outdated.

Common examples:
  • Incorrect tags: A residential road tagged as a motorway.
  • Geometry errors: Buildings that are misaligned, roads that don’t connect properly, or rivers overlapping with buildings.
  • Outdated features: A shop that closed years ago but still shows up on the map.
  • Inconsistencies: Using different tags for the same type of feature in nearby areas (amenity=school vs. building=school).
2. Non-Existing Issues: Missing from the Map

These are features or data that should be on the map but are completely absent. The problem here is not about fixing what’s wrong, it’s about recognizing what’s not there at all.

Common examples:
  • Unmapped buildings visible in satellite imagery.
  • New roads or paths that haven’t been digitized.
  • Missing POIs like schools, hospitals, or shops.
  • Lack of metadata such as opening hours, accessibility info, or addresses.

Why This Distinction Matters

Thinking in terms of “existing” vs. “non-existing” issues helps:

  • Prioritize tasks: Fixing vs. adding require different skills and time.
  • Guide new mappers: Beginners can focus on adding missing data, while experienced users fix complex issues.
  • Organize mapping campaigns: Humanitarian or local efforts can be tailored to the type of issue in a region.
  • Improve data validation: Tools like OSMCha, or Osmose focus on identifying existing issues, while others like MapSwipe or HOT Tasking Manager target missing data.

Please comment your thoughts and write another diary by linking this problem sets with your solutions.

Discussion

Comment from kumakyoo on 13 May 2025 at 15:36

I think, there is a third category: Issues where our mapping scheme does not work well. The mapping scheme with all it’s tags has evolved over time, but it is far from perfect. For example the question of what a highway=path should be pops up over and over again and the answers aren’t satisfying. This should be changed, but of course it’s a lot of work to do so, especially, because every “solution” will have a lot of opposition from other mappers.

Comment from Harry Wood on 15 May 2025 at 16:06

It’s a useful broad category for thinking about Notes or Completeness tools.

Log in to leave a comment