EUDR
Geolocation: Polygon vs. GPS Point — What You Actually Need
Geolocation is the foundation of EUDR compliance. Without accurate
parcel-level location data, nothing else in the due diligence process
works: no deforestation verification, no risk assessment, no valid DDS.
Yet the regulation’s geolocation requirements have generated more
confusion among compliance teams than almost any other provision. This
article provides the clear answer.
Does EUDR
require a polygon or just a GPS point?
EUDR requires plot-level geolocation, which the EU Commission has
confirmed means polygon data: all boundary vertices defining the parcel
perimeter, not a single GPS coordinate. A GPS point is only acceptable
for parcels under 4 hectares under the simplified due diligence
procedure, and this threshold may be revised before the December 2026
enforcement date. For any parcel at or above 4 hectares, polygon data is
mandatory. There is no workaround.
The practical implication is significant. A polygon captures the
actual shape and extent of the production parcel. A GPS point captures
only a location. Deforestation risk assessment requires knowing exactly
which land area produced the commodity, because satellite monitoring
operates at the spatial level: a pixel of forest loss either falls
within the parcel boundary or it does not. A single GPS point cannot
answer that question with any precision.
Even for parcels below 4 hectares where a GPS point is technically
acceptable, the Commission’s guidance strongly favours polygon data.
Competent authorities reviewing submitted DDS documents have discretion
to request additional geolocation evidence. An importer who submits GPS
points for hundreds of sub-4-hectare parcels may face requests to
provide polygon data during post-submission review, delaying market
access.
The recommendation is clear: collect polygon data for all parcels,
regardless of size. The cost difference between collecting a GPS point
and a polygon during a single field visit is marginal. The compliance
risk difference is substantial.
How
to collect polygon data at scale for a Colombian supply chain of
thousands of farms
Collecting polygon data for 500, 5,000, or 50,000 small coffee farms
in rural Colombia is a logistics operation, not a technology problem.
The tools exist. The challenge is coordination, connectivity, and field
team capacity.
Tools for polygon collection:
- KoboToolbox (free, open-source): Works offline on
Android devices. Field technicians walk the parcel boundary with a phone
or tablet, recording GPS waypoints that define the polygon vertices.
Data syncs when connectivity is available. KoboToolbox is widely used by
development organizations in Colombia and requires minimal
training. - Google Earth Pro (free): For parcels visible on
high-resolution satellite imagery, boundaries can be digitized remotely.
Accuracy depends on image resolution and the ability to distinguish
parcel boundaries from surrounding land. Less reliable in cloud-covered
mountainous terrain, which describes most of Colombia’s coffee
belt. - Origo Field App: CleantechHUB’s data collection
tool, designed specifically for EUDR polygon capture. Integrates
directly with the Origo platform, so collected data flows into the
verification pipeline without manual export or reformatting.
Field logistics:
The standard approach for cooperative-level polygon collection is the
“registration day” model, organized by vereda (the smallest rural
administrative unit in Colombia). A field technician (tecnico de campo)
visits a vereda, sets up at a central location (school, community
center, cooperative office), and farmers arrive with their cedula and
any land documentation they have. The technician either walks each farm
boundary with the farmer or, for farms where the farmer knows the
boundaries, records the polygon from a nearby vantage point.
A trained technician can collect polygon data for 8-15 farms per day,
depending on terrain, farm size, and access. For a cooperative with
2,000 member farms, full polygon coverage requires approximately 150-250
field days, or 3-5 months with a team of two technicians.
The connectivity challenge: Much of Colombia’s
coffee-growing zone has limited or no mobile data coverage. Any polygon
collection tool must work offline with reliable local GPS (not
network-assisted GPS). KoboToolbox and the Origo Field App both support
full offline operation. Data uploads happen when the technician returns
to a location with connectivity.
What
happens if you submit GPS points instead of polygons: DDS rejection
risk
Submitting a DDS with incomplete geolocation data carries concrete
risk. The competent authority reviewing the DDS may reject it if the
geolocation does not meet the standard specified in Implementing
Regulation 2023/1731. A rejected DDS means the associated shipment
cannot be placed on the EU market until the deficiency is corrected and
a new DDS is submitted.
The risk is not hypothetical. Competent authorities in EU member
states are establishing their review procedures now, and early guidance
from several national authorities indicates that geolocation
completeness will be a primary screening criterion for DDS submissions.
A DDS referencing thousands of parcels with only GPS point data, even if
each parcel is below 4 hectares, may trigger an enhanced review that
delays market access by weeks or months.
There is also a secondary risk: reputational. EUDR includes
provisions for public transparency. Information about operators who have
been found non-compliant may become publicly accessible. For specialty
coffee importers whose brand identity depends on responsible sourcing, a
compliance failure related to something as fundamental as geolocation
data is particularly damaging.
The cost of collecting polygon data upfront is a fraction of the cost
of a single rejected shipment sitting at an EU port while geolocation
deficiencies are resolved.
How
Origo handles parcels where polygon data is incomplete or missing
In the real world, not every parcel will have complete polygon data
on day one. Some farmers are unreachable. Some parcels have disputed
boundaries. Some cooperatives are mid-way through their field data
collection campaign when a shipment needs to move. Origo’s workflow
accounts for this reality without blocking trade.
Fallback workflow for incomplete polygon data:
Step 1: Partial data flagged. When a parcel in the
Origo system has a GPS point but no polygon, or a polygon with
insufficient vertices (fewer than 3 distinct points), the system flags
it as geolocation-incomplete. The parcel cannot be included in a DDS in
its current state.
Step 2: Cooperative field team dispatched. Origo
notifies the cooperative that specific parcels need polygon completion.
The notification includes the farmer’s name, vereda, and existing GPS
point, so the field technician knows exactly where to go.
Step 3: Polygon completed and uploaded. The
technician collects the missing polygon data and uploads it to Origo via
the field app or KoboToolbox. The system validates the polygon (minimum
vertices, area consistency with historical data, coordinates within
Colombia’s boundaries).
Step 4: Verification resumes. Once the polygon is
complete, the standard IDEAM/JRC deforestation verification and SHACL
validation process runs. If the parcel passes, it is included in the
next DDS generation cycle.
No shipment is blocked without a clear resolution path. The system
tracks which parcels are pending polygon completion and provides the
cooperative with a prioritized list based on upcoming shipment
schedules. Parcels needed for imminent DDS submissions are flagged as
urgent.
For cooperatives that are still building their polygon database,
Origo can generate partial DDS documents covering the parcels that are
already verified, while flagging the remaining parcels for field
completion. This allows trade to continue for verified portions of the
supply chain while data collection catches up.
Check your supply chain’s geolocation readiness with a free
assessment on the Origo Risk
Screener, or visit the Origo
platform to begin cooperative-level polygon collection and EUDR
verification. For supply chains involving agroforestry
parcels, geolocation accuracy is doubly important: an imprecise
polygon boundary in an agroforestry zone can cause the wrong IDEAM land
use classification to be applied, compounding the misclassification
risk.
