One Field Dataset for Carbon and EUDR

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

How to design one field dataset that serves both carbon credit MRV and EUDR due diligence for coffee, cocoa, rubber, palm oil and wood supply chains.

Yes, one field dataset can serve both carbon crediting and EUDR due diligence, if you design it for both from the start. The shared core is farmer identity, plot polygons, consent and land-use history verified against satellite imagery; carbon adds tree measurements, and EUDR adds legality evidence and links from plots to shipments.

The overlap is largest in smallholder agroforestry. Coffee, cocoa and rubber, all EUDR commodities, are often grown in the same Indonesian landscapes where tree-planting carbon projects operate. The EUDR applies from 30 December 2026 according to the Commission (check its page for later changes). Building one dataset now avoids paying twice to visit the same farms.

What each use needs

Step-by-step: design the shared dataset

1. Agree one farmer ID. Every farmer and every plot gets a stable identifier used by the cooperative, the exporter and the carbon project. Duplicate IDs are the most common source of data failure.
2. Register and record consent. Capture consent for data use and for carbon participation separately. See farmer registration and consent.
3. Map polygons, not points. Walk the boundary with a GNSS device or a phone with good accuracy settings, or digitise on high-resolution imagery and confirm in the field. RTK GNSS gives survey-grade accuracy for reference plots.
4. Check land history once, against both dates. Use satellite time series to classify each polygon on 31 December 2020 and across the carbon eligibility window.
5. Add tree measurements where carbon applies. Record species, diameter and height on sample plots or per tree, using mobile measurement with photo evidence.
6. Attach legality documents. Land certificates, permits and village letters, linked to the plot ID.
7. Store with an audit trail. Every edit should be logged with who, when and why. Validators and EU authorities both want evidence that data was not changed after the fact.
8. Set refresh cycles. EUDR needs current data for each shipment period; carbon needs scheduled remeasurement.

Data quality rules that serve both

• Positional accuracy: state the accuracy of each polygon and how it was captured.
• Topology checks: no overlapping plots, no slivers, no self-intersections.
• Version control: keep old polygons when boundaries change.
• Ground truth: check a sample of plots against satellite classification. See ground truth vs satellite.

Indonesia specifics

Smallholder tenure is often informal. Many farms rely on village letters (SKT or similar) rather than certificates, and some sit inside the state forest area, where social forestry permits define rights. Record what exists, flag gaps honestly, and plan for legality checks under Indonesian law. Agroforestry plots can also meet the EUDR forest definition, so classification needs care (see EUDR and agroforestry).

Where the two uses diverge

Do not force everything into one format. Carbon projects need statistical sampling and uncertainty calculations. EUDR needs complete coverage of every plot supplying a product. A carbon project may cover only some farms in a cooperative, while the exporter needs all of them. Plan coverage for the stricter requirement in each case.

Who pays and who owns the data

Shared datasets raise commercial questions. Exporters want EUDR data for their supply chain, carbon developers want MRV data for their project, and cooperatives want both without losing control of their members’ information. Settle these points in writing before field work:

• who funds the initial mapping and who pays for updates,
• who holds the master copy and who can access which fields,
• whether farmers can see and correct their own records,
• what happens to the data if a buyer or developer leaves,
• how personal data is protected under Indonesian law.

Splitting costs between a carbon project and a commodity buyer is often what makes smallholder mapping affordable in the first place.

Common mistakes

• Collecting points for carbon and then re-mapping polygons for EUDR.
• Letting each buyer define its own farmer ID.
• Storing consent on paper only, with no link to digital plot records.
• Assuming a carbon validator’s acceptance means EUDR compliance, or the reverse.
• Forgetting that farmers must be able to see and correct their own data.

We build these shared datasets through our EUDR compliance and DMRV implementation services. You can also map plots with the akar Mapper. For background, start at the agroforestry hub.