Project Mapbox Trees

No repository file or test is identified. Review the linked OpenStreetMap tagging guidance, the OSM Data Team Members wiki, and the iD Editor workflow; a concrete documentation change or requested outcome would be needed to define when this issue is done.

Introduction

The Mapbox Trees project focuses on mapping trees, including individual tree nodes and tree rows, to enhance the density of natural features, improve environmental data accuracy, and achieve the highest quality and attractive visual presentation of green spaces in OpenStreetMap.

Types of Activity

Our team will focus on adding and refining green coverage data, specifically:

• Tree points: natural=tree
• Tree rows or lines: natural=tree_row

We pay strict attention to local mapping conventions and aerial alignment. In cases where tree boundaries or individual plants are unclear from available imagery, we refrain from guessing and leave the area unmapped or leave a note for local contributors.

Geographical Scope & Timeframe

• Geographical Scope: The project will take place in the USA, starting with California and potentially expanding to other regions over time.
• Project Status & Phases:
  • Phase 1 (Validation & Pilot Setup): Completed an initial workflow alignment and source accuracy test (~1,500 tree features mapped in California under #mapbox_editing).
  • Phase 2 (Structured Mapping): Full rollout starting in October 2026 under the dedicated #mapbox_trees hashtag without a fixed end date.
• Timeframe: This project is ongoing and will be active starting from October 2026 without a fixed end date.

How to Find Edits

All edits made by our team within this project will use the dedicated hashtag:
#mapbox_trees

Editing Team

All members of the team have completed a thorough onboarding process prior to editing on OpenStreetMap and are fully familiar with OSM mapping principles, community guidelines, and organised editing guidelines.

• List of participating mappers: A full and updated list of team accounts is maintained here: OSM Data Team Members
• Tools & Training: The team primarily uses the iD Editor. New editors are guided to standard OSM training materials, including the OSM Wiki and iD editor panel, as well as internal training sessions.

Mapping Documentation & Guidelines

When mapping trees and green areas, the team follows standard OpenStreetMap documentation:

• Tag:natural=tree
• Tag:natural=tree_row
• Key:leaf_type
• Key:leaf_cycle

Sources

For mapping green features, we rely on standard and compliant sources:

1. Aerial or Satellite Imagery: High-resolution orthophotos available in OSM editors such as Bing, Mapbox, Esri, and local municipal imagery where available, with careful consideration of capture dates and seasonal alignment.
2. Street-Level Imagery: Open street-level photography such as Mapillary and Bing Streetside to verify individual tree positions and types.

Quality Assurance & Clean-up

To ensure high data quality and prevent errors such as overlapping geometries, floating nodes, or misalignment with imagery and roads:

• Edits undergo internal validation prior to and after uploading.
• Team members review history and local mapping patterns before making changes.
• Feedback from local OSM communities is monitored continuously.

Results

Progress reports and metric updates will be provided periodically, at least quarterly, in our public repository ticket.

Metrics tracked:

• Number of changesets
• Added tree nodes
• Added tree rows

Contact

We strongly welcome feedback from local mappers, as local ground truth always prevails. If you have questions about a specific changeset, suggestions for process improvement, or local insights:

Role / Scope	Contact
Project Coordinator	Zhanna (zhanna.baravenskaya@mapbox.com)
General Escalations & Feedback	osm-edit-escalations@mapbox.com

You can also find any relevant changeset using the #mapbox_trees tag and leave a comment directly.