TomTom is a Dutch multinational developer and creator of location technology and consumer electronics. TomTom has been making data improvements to OpenStreetMap through organised editing since 2021.
When we create new organised editing projects or share leads or sources, we consider several factors:
- Is there a similar project or activity already in existence that might duplicate or conflict with what we are considering?
- Are there appropriate sources, such as clear imagery, available for the relevant region?
- Is the project a reasonable size with tasks grouped logically?
- Do the tasks align with local capturing rules?
To create the tasks for our editing projects, we analyze the OSM data to pinpoint possible gaps, inconsistences, or other potential issues. We use sampling to manually validate a selection of tasks within a new project to help maintain accuracy and quality.
Our organised editors are careful to ensure that their edits are accurate and compliant with all relevant OSM guidelines.
- Sources such as recent aerial or street level imagery or other community recommended local sources are checked to ensure accuracy of edits, and only edits that are clearly supported by these sources are uploaded to OSM.
- For some OSM map edits TomTom editors will use proprietary sources for support. These will typically be in situations where there is not sufficient evidence using the available sources in OSM editors themselves. The proprietary sources will be ground-level imagery and GPS traces, both collected by TomTom's mobile mapping vans. On occasion, we will also use sources collected from a field survey by one of TomTom's sourcing specialists who have visited the location and collected data to support the required map updates.
- The OSM wiki is checked to ensure an edit follows both general guidelines and local conventions.
- Each changeset references the sources used and is accompanied by a comment that explains the edit made in clear, simple language.
- When members of the community comment on our changesets, someone on our team (usually the original editor) responds within two business days.
Below is an overview of all editing projects. Click the links to see the project details.
Algeria, Angola, Argentina, Aruba, Australia, Austria, Bahamas, Barbados, Belarus, Belgium, Belize, Benin, Bermuda, Bolivia, Bosnia and Herzegovina, Botswana, Brazil, British Virgin Islands, Brunei, Bulgaria, Burkina Faso, Burundi, Cambodia, Cameroon, Canada, Cape Verde, Cayman Islands, Central African Republic, Chad, Chile, Colombia, Comoros, Costa Rica, Côte d'Ivoire, Croatia, Curaçao, Cyprus, Czech Republic, Denmark, Democratic Republic of the Congo, Djibouti, Dominica, Dominican Republic, East Timor, Ecuador, El Salvador, Equatorial Guinea, Eritrea, Estonia, Eswatini, Ethiopia, Fiji, Finland, France, Gabon, Gambia, Georgia, Germany, Greece, Greenland, Ghana, Grenada, Guadeloupe, Guatemala, Guinea, Guinea-Bissau, Guyana, Honduras, Hungary, India, Indonesia, Ireland, Israel, Italy, Jamaica, Kazakhstan, Kenya, Kiribati, Kosovo, Kuwait, Laos, Latvia, Lesotho, Liberia, Liechtenstein, Lithuania, Luxembourg, Madagascar, Malawi, Malaysia, Malta, Martinique, Mauritania, Mauritius, Mexico, Moldova, Mongolia, Montenegro, Montserrat, Morocco, Mozambique, Namibia, Nepal, Netherlands, New Zealand, Nicaragua, Niger, Nigeria, Norway, North Macedonia, Oman, Palau, Panama, Paraguay, Peru, Philippines, Poland, Portugal , Qatar, Republic of the Congo, Réunion,Romania , Rwanda, Saint Barthélemy, Saint Kitts and Nevis, Saint Lucia, Saint Martin, Saint Vincent and the Grenadines, São Tomé and Príncipe, Saudi Arabia, Senegal, Serbia, Seychelles, Sierra Leone, Singapore , Sint Maarten, Slovakia, Slovenia , Solomon Islands, South Africa, South Korea, Spain, Sri Lanka, Suriname, Sweden, Switzerland, Taiwan, Tajikistan, Tanzania, Thailand, Togo, Tonga, Trinidad and Tobago, Tunisia, Türkiye, Uganda, United Arab Emirates, United Kingdom, United States, Uruguay, Uzbekistan, Venezuela, Vietnam, Zambia, Zimbabwe.
Edits based on map feedback
- This section has been migrated to a new activity page:Organised Editing/Activities/TomTom Map Feedback
Tools and Data Sources
JOSM editor. Standard tools and sources within the editor and public information.
There are other TomTom team members mapping on OpenStreetMap as a hobby. They are not listed here. In addition, some of the mappers listed here do not edit exclusively for TomTom; some of their edits will be in pursuit of their own mapping interests.
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.
We contact the community about all organised editing projects using their preferred communication channels, to the extent that we can identify those based on community input and publicly available information such as the OSM community index and the country pages on the OSM wiki. Examples include OSM Community Forums, Discord, Telegram, Slack, or Facebook.
We started making data improvements to OSM through organised editing in 2021. We plan to continue making these improvements on an ongoing basis for the foreseeable future.
Measuring our Success and Performance
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.
Please reach out to firstname.lastname@example.org with any questions.