From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Mapbox
Afrikaans Alemannisch aragonés asturianu azərbaycanca Bahasa Indonesia Bahasa Melayu Bân-lâm-gú Basa Jawa Baso Minangkabau bosanski brezhoneg català čeština dansk Deutsch eesti English español Esperanto estremeñu euskara français Frysk Gaeilge Gàidhlig galego Hausa hrvatski Igbo interlingua Interlingue isiXhosa isiZulu íslenska italiano Kiswahili Kreyòl ayisyen kréyòl gwadloupéyen Kurdî latviešu Lëtzebuergesch lietuvių magyar Malagasy Malti Nederlands Nedersaksies norsk bokmål norsk nynorsk occitan Oromoo oʻzbekcha/ўзбекча Plattdüütsch polski português português do Brasil română shqip slovenčina slovenščina Soomaaliga suomi svenska Tiếng Việt Türkçe Vahcuengh vèneto Wolof Yorùbá Zazaki српски / srpski беларуская български қазақша македонски монгол русский тоҷикӣ українська Ελληνικά Հայերեն ქართული नेपाली मराठी हिन्दी অসমীয়া বাংলা ਪੰਜਾਬੀ ગુજરાતી ଓଡ଼ିଆ தமிழ் తెలుగు ಕನ್ನಡ മലയാളം සිංහල ไทย မြန်မာဘာသာ ລາວ ភាសាខ្មែរ ⵜⴰⵎⴰⵣⵉⵖⵜ አማርኛ 한국어 日本語 中文(简体)‎ 吴语 粵語 中文(繁體)‎ ייִדיש עברית اردو العربية پښتو سنڌي فارسی ދިވެހިބަސް

Mapbox ( offers commercial mapping services. Many of them use OpenStreetMap data and involve large open-source efforts. Mapbox is a main contributor to the Mapnik renderer project, it helped create the new web editor iD and it created Tilemill, the software used to design the OpenStreetMap map style. Mapbox employs a data team actively improving the map.

Tools and products

  • Mapbox GL – libraries for embedding customizable vector slippy maps into Web, mobile, desktop, and command-line applications
  • Mapbox Streets - an OpenStreetMap based minutely updated scalable map service
  • Mapbox Studio - A desktop map design and rendering studio
  • TileMill - a desktop map design and rendering studio (phasing out in favor of Mapbox Studio)
  • CartoCSS - CSS-inspired language for styling maps, used both in TileMill and Mapbox Studio
  • MBTiles - an efficient tile storage schema for mobile apps
  • Mapbox Vector Tile Specification - a specification for a lightweight scalable vector tile format
  • To-Fix - a miro tasking manager (GitHub)

OSM Tools

  • OSM QA Tiles Daily OpenStreetMap planet dump as vector tiles. Available as country and historical extracts
  • OSM changeset map Visualize a changeset on an interactive GL map like achavi
  • OSM Comments Find unreplied changeset comments and notes of a user
  • OSMCHA A custom instance of OSM Changeset Analyzer to find and query changesets by certain properties
  • OSM Diary A live feed of the latest diary posts from the data team at Mapbox
  • OSM navigation map A map to explore Mapillary images to add navigation data to OSM like turn restrictions and oneways

Data Tools

  • turfjs Modular geospatial analytical engine using JavaScript
  • minjur Convert .osm data to .geojson
  • tippecanoe Convert .geojson data to .mbtiles vector tiles
  • tile-reduce Run analysis on vector tiles at scale using JavaScript
  • osmlint Validate OSM data using tile-reduce
  • osm-compare Compare two versions of an OSM feature

Other Resources

Mapping Guides


They also provide various tilesets that can be used by customers:

  • Mapbox Streets - a general-purpose tileset
  • Mapbox Outdoors - an outdoors focused tileset with trails and high resolution terrain data
  • OSM Bright - a starter style for creating your own OpenStreetMap design

External Links

Mapbox Data Team

The Mapbox Data Team continuously improves OpenStreetMap by fixing errors and adding data using open data sources. All active mapping tasks are ticketed and documented in our mapping repository.

Team members

Here are the OpenStreetMap user accounts of the Mapbox data team. For any questions, please get in touch with the team member listed or with Arun Ganesh. These are only the user names of people systematically updating OpenStreetMap as part of their job at Mapbox. There are many other Mapbox team members mapping on OpenStreetMap as a hobby - they are not listed here.

Data Team Guidelines

In addition to the rules that apply to everyone in the community, here are the guidelines the Mapbox team reiterates and adds for themselves:

  1. We listen to community. We are looking for your feedback on how to make a better map. Get any time in touch with any of the our data team members. For general feedback message Arun Ganesh.
  2. Quality is paramount. We hold ourselves to the highest mapping standards as documented on the OpenStreetMap Wiki or as established as common practice in the community.
  3. Local knowledge first. Where in any doubt, the locally surveyed information prevails over remote updates.
  4. We disclose all ongoing mapping efforts on the Mapbox mapping repository.
  5. All full time data team members will be listed here on this OpenStreetMap Wiki page and identified on their user profiles.
  6. Where possible we use public tools for coordinating work, allowing anyone in the community to participate.

Related posts


Please send any general feedback on Mapbox's work on OpenStreetMap to Arun Ganesh.