Import:Iran Speed Bumps
This initiative aims to comprehensively map speed bumps across Iran in OpenStreetMap. Before this effort, only a small number of speed bumps had been recorded across Iran.
TAPSI, a leading ride-hailing service in Iran, conducted an extensive data collection campaign as part of their commitment to improving transportation infrastructure. The resulting dataset of speed bump locations is now being shared with OpenStreetMap under the Open Database License (ODbL 1.0).
This contribution will significantly enhance the accuracy of road feature data in Iran, supporting better navigation and improved road safety.
1. Introduction and Overview
1.1 Goals
- To systematically map all traffic calming speed bumps nationwide in Iran.
- To provide openly licensed, high-quality data for the benefit of the global OpenStreetMap community and local users.
- To enhance navigation services for TAPSI drivers and general users, improving ride comfort, safety, and operational efficiency.
- To contribute valuable infrastructure data for urban planning, emergency services, and academic research within Iran.
1.2 Project Lead & Contact
- Project Lead: TAPSI
- Contact Email: [email protected]
2. Data Sources and Licensing
2.1 Primary Data Source
All speed bump data for this project has been collected directly by TAPSI through their internal operational processes and drivers across Iran.
2.2 Data License
The collected speed bump data from TAPSI is formally released under the Open Data Commons Open Database License (ODbL) 1.0.
This licensing decision ensures full compatibility with OpenStreetMap's primary license, allowing for the seamless integration of this valuable dataset into the global OSM database. It guarantees that the data can be freely used, shared, and adapted by the entire OpenStreetMap community, provided the terms of the ODbL are followed (attribution and share-alike).
3. Data Collection and QA
The data for this project was collected through a combination of crowdsourcing, field surveys, and internal validation by the TAPSI team.
TAPSI drivers can report unmapped speed bumps directly through the app during their trips. Over time, this has resulted in a large collection of crowdsourced bump reports across the country.
To validate and improve the quality of this data, TAPSI initiated a focused field mapping effort. Team members physically surveyed roads — especially those with high driver activity — to manually locate and verify speed bumps. These verified bumps were used as ground truth labels.
Using this verified dataset, we trained our system to filter and clean the larger crowdsourced dataset. We then pushed the candidate speed bump data back into the TAPSI driver app, asking drivers to confirm bump presence each time they passed a suspected location.
Only those locations that received consistent confirmations from multiple drivers were retained. Bumps with low or no confirmation were discarded.
The final dataset being contributed to OpenStreetMap is the result of this multi-step validation process.
4. Tagging Schema
This project follows standard OpenStreetMap tagging practices for traffic calming features. All speed bumps are mapped as nodes placed directly on the highway ways they impact.
- The tag used is:
traffic_calming=bump - Each bump is added in a separate changeset, with the following comment format:
#Tapsi Automated Import: Adding speed bump at {lat},{lon} on way {way_id}
5. Import/Upload Strategy
The import process will be carefully managed to ensure data quality and allow for community review.
5.1 Tools for Upload
- Custom Python scripts will be used for initial data cleaning and conversion to OSM XML format.
5.2 Staging and Review Process
- Pilot Import: A small, representative pilot import for a specific, limited geographic area will be conducted initially. This will allow the community to review the data, tagging, and import process in a controlled environment.
- Community Feedback: Feedback gathered during the pilot phase will be thoroughly addressed before proceeding with larger imports.
- Phased Rollout: Following successful pilot review, the nationwide import will proceed in manageable batches, likely broken down by province or major metropolitan area. This phased approach facilitates ongoing review, quality control, and potential rollbacks if issues arise.
- Monitoring: Changesets will be actively monitored using tools like OSMCha to address any immediate concerns or errors.
6. Rollback Plan
In the unlikely event of errors or significant community concerns requiring data removal, a clear rollback strategy is in place.
- All imported changesets will be easily identifiable via the unique
#TAPSI Automated Importchangeset comment. - Any problematic changesets can be reverted using JOSM's revert function or command-line tools like
osm-revertif necessary. - The project team is committed to fixing any identified issues and re-uploading corrected data promptly.
7. Community Involvement and Discussion
Open communication and community feedback are vital to the success of this project.
The project team actively encourages review and constructive feedback from all mappers and data users before, during, and after the import process. You can contact us at:
A discussion is also ongoing on the Imports mailing list.