Import/Trees of Yerevan

From OpenStreetMap Wiki
Jump to navigation Jump to search

Trees of Yerevan Import

This is the formal import page for the initial baseline dataset of trees collected by the Kanach Yerevan (Green Yerevan) initiative.

Abstract

Kanach Yerevan is an urban forestry grassroots movement in Yerevan, Armenia. Our volunteers map urban trees using a mobile application. We have collected a baseline of approximately 11,000 trees which we intend to formally import/synchronize with OSM. Moving forward, continuous mapping efforts (approx. 100 trees/week) will be managed under our Organized Editing Activity. This import specifically covers the initial 11,000 baseline trees to ensure compliance with OSM Import Guidelines.

Data

  • Data Source: Volunteers using the Kanach Yerevan custom mobile application and field surveys.
  • Data Type: Nodes representing individual trees.
  • License: All contributors agree to release their data into the Public Domain / ODbL compatible.
  • Size: ~11,000 nodes.

Data Preparation & Tagging

Trees are mapped as individual nodes.

  • natural=tree
  • species=* (where identified, using scientific names)
  • height=* (in meters, measured via laser range finder)
  • circumference=* (in meters, measured via tape)
  • diameter_crown=* (in meters)

Conflation & Verification

Data is manually collected in the field by volunteers. Where applicable, locations are verified against our own custom drone orthophotos, which we publish openly on OpenAerialMap. If a tree already exists in OSM at the exact coordinates, our sync tool updates the tags (adding missing measurements) rather than creating duplicate nodes.

Import Process

  • Account: The initial baseline is pushed using the YerevanTreeMap account.
  • Changeset size: Rate-limited to a maximum of 1 changeset per hour, containing up to 100 nodes per changeset.
  • Revert Plan: Since we add individual nodes (trees), reverting can be done using the standard JOSM reverter plugin on specific changesets if issues are found. We maintain our internal DB IDs allowing precise mapping to OSM nodes.

Contact

Please see our Organised Editing Page for contact details and ongoing activity information.