OpenStreetMap Is Turning 20

Original Article ↗ Hacker News Discussion ↗

Overall sentiment & use cases

  • Many commenters express long‑term affection for OSM and nostalgia for early contributions.
  • OSM is praised as essential for hiking, cycling, and mountain use, especially offline.
  • It’s valued for privacy: unlike big commercial maps, it’s seen as less surveillance‑oriented.
  • People highlight niche uses: public toilets, parking, accessibility, drinking fountains, bike repair stations, etc.

Data quality vs commercial maps

  • Consensus: OSM is often better than Google Maps for trails, bike paths, and some local details.
  • For businesses and POIs, Google is typically more up to date; many shops and restaurants in OSM are outdated or missing.
  • Some users still rely on paper or “official” maps because OSM sometimes contains invented or imagery‑only paths.
  • Tags like check_date exist for verification, but are said to be rarely used.

Tools, apps, and contribution workflows

  • Recommended editing tools:
    • Casual / gamified: StreetComplete (Android), EveryDoor (POIs), Go Map!! (iOS) with “quests”.
    • General editors: in‑browser iD on openstreetmap.org; JOSM for advanced work.
  • Navigation / viewing:
    • OsmAnd and Organic Maps are the main offline routing apps; trade‑off is simplicity (Organic Maps) vs power (OsmAnd).
    • Other frontends: mapy.cz, GraphHopper Maps, cartes.app, TomTom (partly OSM‑backed).
  • Image and street‑level data: Mapillary, Kartaview, Wikimedia Commons, and Panoramax are used to support mapping.

UX, discoverability, and web frontends

  • The official openstreetmap.org site is described as functional but weak as a consumer map: basic search, cluttered default style, editing‑oriented.
  • Several people want a Google‑Maps‑like, web‑based OSM frontend with:
    • Smart local search (e.g., “ATM”, “bakery”).
    • Clear POI display with opening hours.
    • Public transport integration and navigation.
  • Some find current styles visually noisy (too many symbols, building outlines, bus stops at low zoom).

Data freshness, local mapping, and business info

  • Thread strongly emphasizes the need for “good local mappers” who monitor shop openings/closures, road changes, and details like opening hours.
  • Tools like StreetComplete and EveryDoor are seen as good “gateway drugs” into deeper mapping.
  • Business data is hard to keep current: owners rarely know or care about OSM, focusing instead on their website, social platforms, or Google Maps.
  • Some report OSM beating Google on specific details (e.g., updated opening hours, disaster‑related closures), but others describe failed or reverted edits and find OSM harder than Google to update.

Licensing, data sources, and ethics

  • OSM’s attribution/ODbL requirements are seen by some as limiting data ingestion from open government sources and discouraging adoption; others note attribution is standard in mapping.
  • Combining OSM with other attribution‑required datasets is described as complex; workarounds depend on specific agreements.
  • Commenters warn against scraping OSM and recommend using published data dumps or Overpass API instead.
  • There is criticism of companies that solicit free public contributions into closed, proprietary databases; some argue such data should be required to remain public.