The Legal Requirement (Art. 9 and Art. 2(28)) in Plain Language
Article 9(1)(d) of Regulation (EU) 2023/1115 obliges the EU operator to collect "the geolocation of all plots of land where the relevant commodities were produced," plus the date or time range of production (EUR-Lex, accessed 2026-09-24). Article 2(28) defines the data itself:
"the geographical location of a plot of land described by means of latitude and longitude coordinates corresponding to at least one latitude and one longitude point and using at least six decimal digits; for plots of land of more than four hectares used for the production of the relevant commodities other than cattle, this shall be provided using polygons with sufficient latitude and longitude points to describe the perimeter of each plot of land." — — Regulation (EU) 2023/1115, Art. 2(28) (EUR-Lex)
Three engineering consequences follow: coordinates must be formatted to at least six decimal places; polygons are mandatory for plots above 4 hectares (cattle excepted — cattle establishments use points regardless of size); and there is no smallholder carve-out — every plot in the supply chain, down to a 0.5 ha coffee garden in Aceh, must appear in the buyer's due diligence statement (EUR-Lex).
Key facts
>4 ha / ≤4 ha
polygon mandatory / point permitted (Art. 2(28))
≥6 decimal digits
coordinate precision — formatting, not accuracy
GeoJSON, WGS 84
longitude-first submission format
1 dirty plot
disqualifies the entire consignment batch
Point vs Polygon: The 4-Hectare Rule
The rule in one line: ≤4 ha → a single lat/long point is permitted; >4 ha → a polygon tracing the full perimeter is mandatory. In practice this splits Indonesian supply bases in two. A Jepara furniture maker sourcing from community woodlots or a Lampung coffee cooperative buying from 0.5–2 ha gardens can run a point-based registry; an oil palm estate or a plasma scheme with contiguous blocks above 4 ha needs walked or imagery-traced polygons. Many supply chains need both — and the boundary between them should be decided per plot from measured area, not from farmer recollection.
Every plot counts — including smallholders
Art. 9 contains no minimum-size exemption and no developing-country derogation: the geolocation of all plots is required, smallholder plots explicitly included (EUR-Lex). The December 2025 simplification created a simplified-declaration relief for micro and small primary operators, but restricted it to operators established in low-risk countries — Indonesia is standard risk, so the relief is not available to Indonesian producers (EUR-Lex 2025/2650).
One polygon per plot — no bundling
Commission FAQ guidance is explicit: one polygon cannot cover several distinct plots of land — each plot gets its own geometry (Coolset). A cooperative cannot draw one big polygon around a village's entire coffee landscape and declare it compliant; each farmer's plot must be individually delineated and individually verified. This is the single most common design error we see in first-draft plot registries.
Coordinate Precision: Six Decimal Places Is Formatting, Not Accuracy
A persistent misconception: the "six decimal digits" rule is a formatting requirement — six decimals correspond to roughly 0.1 m of theoretical resolution — not a GPS-accuracy mandate. The Regulation names no receiver standard, no satellite vendor, and no accuracy threshold (Filovara). What matters operationally is that your coordinates are plausible and stable: a consumer smartphone (typically 3–10 m accuracy in open sky) produces data that passes validation, but a point that drifts into a neighbouring plot or a forest polygon will trigger questions. Good practice is to record with the device under open sky, average several readings, and sanity-check every point against satellite imagery before submission.
File Format: GeoJSON, WGS 84, Longitude-First
In practice, submissions to the EU Information System use GeoJSON in WGS 84 (EPSG:4326), with longitude listed first in each coordinate pair (Bosqio; T4 vendor source, consistent with Commission documentation). The Regulation itself contemplates EU Space Programme services — EGNOS, Galileo, Copernicus — as positioning and observation data sources.
Common validation errors
The failures that most often bounce a data pack back to the exporter:
1. Swapped latitude/longitude — Indonesian plots suddenly appearing in the ocean off Somalia. Remember: longitude first, and Indonesian longitudes are ~95–141°E while latitudes are −11 to +6°. 2. Wrong coordinate reference system — data captured in a local datum re-projected incorrectly, shifting plots hundreds of metres. 3. Oversized or malformed geometry — self-intersecting polygons, unclosed rings, or thousands of vertices where a clean 8–20-point perimeter would do. 4. Stale data — geometries captured before replanting or a tenure transfer that no longer match the productive plot.
Important: the EU Information System performs format and validation checks only — it does not verify that a plot is actually deforestation-free and offers no mapping tools (Verdant). Screening must happen before submission, at origin.
Mixing Rules: One Dirty Plot Kills the Batch
Art. 9(1)(d) carries the sharpest teeth in the Regulation:
"any deforestation or forest degradation on the given plots of land shall automatically disqualify all relevant commodities and relevant products from those plots of land from being placed or made available on the market or exported." — — Regulation (EU) 2023/1115, Art. 9(1)(d) (EUR-Lex)
Two mixing rules follow. First, classic mass balance is banned: mixing deforestation-free commodities with commodities of unknown or non-compliant origin is prohibited at every supply-chain step — segregation is required (Proforest/Zero Deforestation Hub). Second, the compliant blending model is "declaration in excess": for bulk blends, the operator may declare all plots that may have contributed to a consignment — provided every one of them is verified deforestation-free (TraceX). For an FFB collection centre or a rubber crumb facility, this means the practical unit of compliance is the registered supplier base, not the individual delivery.
Satellite Evidence and the JRC GFC 2020 Baseline
Geolocation tells the EU where the plot is; the operator must still show the plot has been deforestation-free since 31 December 2020. The Commission's reference dataset is the JRC Global Forest Cover 2020 map (GFC 2020): 10 m resolution from Sentinel-2, a 0.5 ha minimum mapping unit, free via the EU Observatory on Deforestation — and explicitly non-mandatory and non-exclusive. It is deliberately tuned toward over-flagging, so it produces false positives (JRC/HAL).
A credible verification pipeline therefore layers sources: GFC 2020 for the baseline; near-real-time alert systems for change detection — RADD radar alerts (Sentinel-1 C-band SAR, 10 m pixels, minimum detectable unit ≈0.2 ha, weekly cadence, works through cloud cover, via Wageningen UR/Global Forest Watch) (EO Atlas) and GLAD-S2 optical alerts (Sentinel-2, 10 m, UMD GLAD lab), with GLAD-L (Landsat, 30 m) providing loss history back to 2000 (Global Nature Watch). And because shade-grown coffee and agroforestry rubber can register as "forest" and generate false deforestation alerts, contested plots need escalation to very-high-resolution imagery (3–5 m class) and/or field verification — geotagged photos, land documents (TraceX; the VHR escalation tier is industry-corroborated; the Regulation itself is sensor-agnostic).
A Practical Mapping Workflow for Indonesian Smallholder Plots
From treeo.id's field operations, a workflow that scales:
1. Register the farmer and plot (align with STDB/e-STDB records where they exist; capture consent for data handling at the same time). 2. Capture: ≤4 ha → averaged point capture with a mobile app, offline-first for low-connectivity areas; >4 ha → walked polygon, or imagery-traced polygon validated by the field team. 3. Screen every geometry against the 2020 forest baseline and current alert layers; flag anything touching post-2020 forest loss. 4. Resolve flags: desk review of imagery, then targeted field visits for contested plots. 5. Publish the validated registry to your EU buyer's data pack in GeoJSON (WGS 84, longitude-first), keyed so each consignment traces to its contributing plots. 6. Re-verify on a cadence — alerts run weekly; a registry that is never refreshed quietly decays as tenure changes and replanting happens.
Frequently Asked Questions
Plots of 4 hectares or less may be declared with a single latitude/longitude point. Plots larger than 4 ha require a polygon with enough points to describe the perimeter (cattle establishments excepted — they always use points).
Stop mapping plots by hand
Mapping thousands of smallholder plots by hand is where most EUDR programmes stall. treeo.id's field-capture and satellite-verification stack was built for exactly this: offline-first plot capture, automated GFC 2020 screening, and DDS-ready GeoJSON exports.

