Measuring Trees with Mobile Apps: DBH, Height and Photos

Updated 2026-11-02 · 4 min read · By the akar.earth specialist team

Tree measurement app guide: how phones capture DBH, height, species and geotagged photos, how accurate they are, and what verifiers need to trust the data.

Mobile apps let field teams and farmers record tree diameter, height, species, location and photos directly into a database, which cuts transcription errors and gives verifiers an audit trail. They are reliable when the measurement method is controlled (for example a tape or calibrated photo method), every record carries photo and location evidence, and a sample is independently checked.

What a good app captures

Data should sync to a central system with versioning, so edits never overwrite raw values. See building a dMRV data pipeline.

Measurement methods compared

• Diameter tape. The reference method. Measure at 1.3 m, above buttresses, perpendicular to the stem. The app records the value and a photo of the tape.
• Photo with reference object. A card or marker of known size is placed on the stem; image analysis estimates diameter. Fast and auditable, but sensitive to angle, distance and irregular stems.
• Phone lidar or depth sensors. Available on some handsets. Promising for diameter and height; accuracy depends on range and canopy clutter.
• Height by phone. Clinometer-style apps use tilt angles and distance. Workable for small trees, error grows for tall trees in closed canopy where the top is hard to see. A laser hypsometer remains better for forest plots.

Whatever the method, test it on your species and size range against tape and hypsometer values, and report bias and spread.

Step-by-step deployment

1. Write the protocol. Point of measurement, minimum diameter, how to handle multi-stem, leaning, buttressed and forked trees, and photo angles.
2. Configure the app with the species list, validation rules (e.g. DBH ranges by age) and required fields.
3. Train measurers in the field, in Bahasa Indonesia or local languages, with practice and a test.
4. Tag trees with durable numbered tags so remeasurements match.
5. Collect, sync and review daily: automatic checks flag missing photos, outliers and duplicates.
6. Independent check. Remeasure a random sample with a separate team. Compare and retrain where errors exceed tolerance.
7. Convert to carbon with justified allometric equations.

Smallholder and community measurement

In agroforestry and smallholder ARR, farmers can measure their own trees. This scales coverage and builds ownership, and fits standards that value participation, such as Plan Vivo, and Indonesia’s emphasis on community roles under Permenhut 6/2026. It requires simple protocols, offline-capable apps, fair compensation for time and strong QA/QC. See aggregating smallholders and farmer registration and consent.

Choosing an app or platform

When comparing apps, check: offline operation; custom forms and species lists; enforced photo and GNSS capture; validation rules; exports to open formats; data ownership terms; access control for personal data; and whether the vendor can show independent accuracy tests for any photo-based diameter method. Ask for the data model before signing; switching later is costly.

Common mistakes

• Letting measurers type values without photo evidence.
• Changing the point of measurement between rounds, creating fake growth.
• No unique tree IDs, so trees cannot be tracked.
• Phone GNSS points accepted without checking accuracy; under canopy, errors of tens of metres occur.
• Correcting data in spreadsheets outside the system, breaking the audit trail.
• Assuming app accuracy from a vendor brochure without local testing.

What good evidence looks like

A VVB will sample records and trace them to trees in the field. Provide: the measurement protocol; app configuration and version; training records; raw data with timestamps, locations and photos; QA/QC check results with tolerances; and the scripts converting measurements to biomass. Being able to show a tree’s photo history across years is strong evidence of survival and growth.

Indonesia specifics

Connectivity is patchy in rural Kalimantan, Papua and eastern Indonesia, so apps must work offline and sync later. Many farmers use low-cost Android phones, so the app must run on modest hardware. Species local names vary by region; keep a mapped species list. Field timing should avoid harvest peaks for coffee, cocoa or rubber when farmers are busy.

Our akar dMRV product supports tree-level field capture with photos and location. For the wider system, see the dMRV hub.