Reviewing OSM Changes Before Integration: Introducing LeBonTag

Room: Talks I / Opening - Amphi Caquot (Coriolis)

Saturday, 17:20
Duration: 20 minutes (plus Q&A)

Language: en

Back to schedule
  • Bruno Béguin
  • Mathieu Ambrosy

LeBonTag is an open-source web application that allows organizations to review OpenStreetMap changes before integrating them into their own datasets.

Originally initiated by Montpellier Méditerranée Métropole to support its internal data workflows, LeBonTag enables a human-in-the-loop process to monitor, inspect, and validate OSM edits before integration.

OpenStreetMap is increasingly used as a data source in operational contexts. However, directly integrating upstream changes into downstream databases can lead to inconsistencies or unwanted modifications.

LeBonTag is an open-source tool designed to introduce a validation step between OpenStreetMap and external systems. It was initially developed in collaboration with Montpellier Méditerranée Métropole, which needed a way to safely integrate OSM data into its internal workflows.

Instead of automatically importing changes, users can review and decide which edits should be accepted.

In this talk, we will present:

  • The problem of uncontrolled OSM data integration
  • How LeBonTag allows users to visualize and review OSM changes
  • The validation workflow: inspecting objects, accepting or rejecting edits
  • An overview of additional modules, such as a data quality module used to check tags, geometry, or consistency on OSM objects
  • Feedback and lessons learned from real-world usage

LeBonTag is designed as a modular platform, where different tools can support various needs around OSM data. Other modules, such as statistics or analysis tools, can be developed within the same framework. Other local french administrations have participated to the improvement of the software (Brest, FireDpt Hérault, Paris, Clermont).

This session focuses on a practical approach to working with OpenStreetMap: combining automation and human validation to ensure data quality and consistency before integration.

Key takeaways

  • Why reviewing OSM changes before integration can be important
  • How to implement a human-in-the-loop validation workflow
  • How modular tools can support different OSM data use cases
  • Practical insights from building and using a real-world tool