Organised Editing/Activities/Snapp
Snapp — organised mapping in Iran
Organiser: Snapp, Map Data team (Iran) · Area: Iran · Status: ongoing since 2018 ·
Contact: map-admin@snapp.cab
Snapp is an Iranian ride-hailing and services platform. Its Map Data team maps in Iran to support ride-hailing, food delivery and marketplace services. This is the English counterpart of Fa:Snapp, published to meet the Organised Editing Guidelines.
Part of this activity is automated. How those edits are decided, tagged and reverted is documented separately at Automated edits/Snapp.
Goals
Keep Iran's road network and POIs accurate enough to route on: street names and spelling, road direction and access, road existence, and business locations. Corrections originate from map problem reports submitted by passengers and drivers, and from discrepancies observed against driver trajectories.
Accounts
| Account | Use |
|---|---|
| snapp-map-editor | Every API / scripted upload from the feedback pipeline. See Automated edits/Snapp. |
| Cartographer accounts | Manual JOSM editing by members of the team. Individual mappers are not listed here by name; anything scripted goes through the account above, never through a personal account. |
Changeset hashtags
#snapp_api— uploads from the automated pipeline#Snapp— general organised editing by the team#Snapp_missing_roads— adding roads missing from OSM#Snapp_users_feedback— edits derived from user reports, done manually
Tools
- JOSM, with our presets and plugins, for manual mapping.
snapp_osm_api, our internal upload service, which writes accepted changes to the OSM API v0.6. Its decision logic, tagging and opt-out policy are documented at Automated edits/Snapp.
Data sources
- Map problem reports submitted by passengers and drivers in Snapp's apps.
- Anonymised, aggregated GPS traces recorded from driver devices during trips, used to corroborate road direction and road existence. The traces themselves are never uploaded, and no passenger location data is collected or used.
No data is taken from other map providers.
Training
Everyone the team asks to edit OSM is briefed on OSM tagging conventions, the Iranian community's conventions, and this activity's rules before they edit. Pipeline rule changes that affect what reaches OSM are reviewed by the team before deployment.
Validation
Uploads are sampled and reviewed after the fact by our cartographers. Reports from the community — by email or as changeset comments — are triaged within two working days.
Feedback and opt-out
Mail map-admin@snapp.cab or comment on any changeset. We will stop editing in a
named area, stop touching named objects or tags, and revert any changeset on request.