Organised Editing/Activities/TomTom Map Feedback

From OpenStreetMap Wiki
Jump to navigation Jump to search


TomTom started making data improvements to OSM through organised editing in 2021. Starting in 2023 TomTom will validate map feedback from end users for potential updates to OSM.

TomTom receives both business to business (B2B) and business to consumer (B2C) users map feedback. When we say map feedback we mean incidental reports of map errors submitted by a person. It originates as direct reports from users via a variety of apps, APIs, or tools. All of the reports flow into the same production projects on the TomTom side.

We then analyze the reports against existing available sources to validate the suggested addition or change to the map.  If we can confirm the report we update the TomTom map content directly and in many countries for specific features we will analyze the validity of the report for OSM map improvement as well.

However, if we cannot find an ODbL compliant source to validate the OSM improvement then we may do one of the following:

1) Share it as a note to the community on the map directly;

2) Reach out to community members in the area to ask for their feedback or suggestions on means to validate;

3) Perform field collection ourselves, or request community support, to confirm the change in the real world. TomTom field collection could then include edits completed during a survey, capturing & uploading GPS traces, or collecting ground truth images to upload into Mapillary.

Here is a list of the types of edits to be made, provided they do not conflict with others’ edits and a local source is available:

  • Highways
    • Adding or correcting highways
    • Adding or correcting link roads
    • Adding or adjusting bridges, tunnels, layers, or relations
    • Adding or updating lanes and related properties
    • Adding or updating traffic signs
    • Adding or updating access barriers
    • Adding or updating turn restrictions
  • Addresses
    • Adding or correcting addresses
    • Updating the position of address nodes, usually when an object has multiple addresses
    • Adding or correcting names of ways
  • POIs (Points of Interest)
    • Adding POIs
    • Correcting POI locations
    • Adding or correcting POI information
    • Resolving POI-land use discrepancies
    • Handling POI closures
  • Land use
    • Adding land use
    • Modifying existing land use extent
  • Buildings
    • Adding buildings
    • Updating building type
    • Adjusting building shape
  • Water
    • Adding or realigning rivers, streams, and lakes
  • Railways
    • Adding railway tracks
    • Realigning railway tracks
    • Adding or adjusting railway infrastructure tags such as bridges, tunnels, level crossings
  • Ferry lines
    • Adding ferry lines
    • Realigning ferry lines
    • Adding ferry terminals

Imports and mechanical edits are out-of-scope for this activity. Should we encounter systemic issues during the course of editing, we will reach out to the community for guidance.


Please reach out to with any questions.

Community consultation

We contact the community about all organised editing projects using the local mailing lists. In cases where there there is no active local mailing list, we communicate using the preferred communication channel for that community. Examples include OSM Community Forums, Discord, Telegram, Slack, or Facebook.


Current practice is to use the #tomtom hashtag on edits. Edits based on user feedback additionally have the hashtag #tt_mapfeedback.

#tt is a hashtag that has been used for TomTom’s edits in the past.


These are incidental edits spread across the globe starting in February 2023. During the course of 2023 we expect to extend to additional countries.

We plan to continue edits based on map feedback an ongoing basis into the foreseeable future.

Edits based on map feedback will be made in the following countries:

  • Algeria (start date: May 1, 2023)
  • Angola (start date: March 16, 2023)
  • Argentina (start date: April 11, 2023)
  • Australia (start date: February 27, 2023)
  • Austria (start date: April 27, 2023)
  • Bahrain (start date: May 1, 2023)
  • Belgium (start date: March 13, 2023)
  • Bosnia-Herzegovina (start date: July 17, 2023)
  • Brazil (start date: February 27, 2023)
  • Bulgaria(start date: July 17, 2023)
  • Canada (start date: June 5, 2023) (from the list above, addresses in Ottawa will be avoided)
  • Chile (start date: June 5, 2023)
  • Colombia (start date: July 17, 2023)
  • Czechia (start date: May 22, 2023)
  • Denmark (start date: June 5, 2023)
  • Egypt (start date: March 16, 2023)
  • Eritrea (start date: March 30, 2023)
  • Estonia (start date: July 17, 2023)
  • Ethiopia (start date: March 16, 2023)
  • France (start date: June 5, 2023)
  • Finland (start date: July 17, 2023)
  • Germany (start date: April 27, 2023)
  • Ghana (start date: February 27, 2023)
  • Greece (start date: May 25, 2023)
  • Guernsey (start date: July 17, 2023)
  • Hungary (start date: April 26, 2023)
  • India (start date: May 13, 2023)
  • Indonesia (start date: May 5, 2023)
  • Ireland (start date: July 3, 2023)
  • Isle of Man (start date: July 17, 2023)
  • Israel (start date: June 9, 2023)
  • Italy (start date: May 10, 2023)
  • Jersey (start date: July 17, 2023)
  • Kazakhstan (start date: July 20, 2023)
  • Kosovo (start date: August 1, 2023)
  • Latvia (start date: August 18, 2023) (from the list above, addresses will not be edited in Latvia)
  • Liechtenstein (start date: April 27, 2023)
  • Lithuania (start date: August 18, 2023)
  • Luxembourg (start date: May 22, 2023)
  • Malaysia (start date: July 20, 2023)
  • Mexico (start date: June 5, 2023)
  • Montenegro (start date: August 1, 2023)
  • Morocco (start date: May 22, 2023)
  • Netherlands (start date: February 14, 2023) (from the list above, addresses and buildings will not be edited in the Netherlands)
  • New Zealand (start date: September 04, 2023)
  • North Macedonia (start date: August 1, 2023)
  • Norway (start date: February 28, 2023)
  • Peru (start date: September 4, 2023)
  • Philippines (start date: September 4, 2023)
  • Poland (start date: April 26, 2023)
  • Portugal (start date: June 5, 2023)
  • Romania (start date: June 5, 2023)
  • Saudi Arabia (start date: May 1, 2023)
  • Serbia (start date: September 04, 2023)
  • Singapore (start date: June 6, 2023)
  • Slovakia (start date: September 7, 2023)
  • Slovenia (start date: September 7, 2023)
  • South Africa (start date: March 16, 2023)
  • Sweden (start date: April 18, 2023)
  • Switzerland (start date: April 27, 2023)
  • Taiwan (start date: September 13, 2023)
  • Tanzania (start date: February 28, 2023)
  • Thailand (start date: February 27, 2023)
  • Turkey (start date: April 18, 2023)
  • United Arab Emirates (start date: May 1, 2023)
  • United Kingdom (start date: March 13, 2023)
  • United States (start date: February 27, 2023)
  • Uruguay (start date: September 4, 2023)
  • Vietnam (start date: August 3, 2023)

Tools and data sources

JOSM editor. Standard tools and sources within the editor and public information.


All team members can be found here:Organised Editing/Activities/TomTom

Measuring our success

We perform quality checks to ensure that the changesets made by our editors are accurate, add value to the map, and meet community guidelines. For each quality check, a live editor double checks the following elements of the changeset under review:

  • Did the editor follow the instructions in the challenge and task description?
  • Does the completed changeset fit the scope of the project/challenge/task?
  • Did the editor use the correct task status?
  • Did the editor correctly use the appropriate hashtags?
  • Is the edited map data accurate, according to the applicable source material?
  • Does the changeset follow any and all country-specific capturing methods available on the OSM wiki pages?
  • Was there any community feedback, and, if so, was it implemented correctly?
  • Are the changeset comments clear and accurate?

These quality checks are performed in the following cases:

  • 100% of changesets made by new editors are checked until at least 95% of that editor’s changesets pass the quality checks without any issues.
  • 100% of changesets that are part of a new project are checked until at least 95% of that project’s changesets pass the quality checks without any issues.


New editors are directed to existing OSM training materials, such as the OSM Wiki and the Help panel of the iD editor. Our team also holds regular editing parties where less experienced editors can receive help and guidance from their more experienced peers.

Post-event clean-up

As referenced above, under Measuring Our Success and Performance, we regularly perform quality checks on our changesets. Whenever a quality check uncovers an issue with a changeset, that changeset is returned to the original editor to be reworked. Once the editor resubmits the changeset, a new quality check occurs. This process repeats until the changeset passes the quality check without issues. To ensure that no issues are missed, each changeset that successfully passes its quality check is then passed on to a second reviewer for an additional check.


Results will be shared through the preferred communication channel for the community.