Plot-Level Geolocation

Under the EU Deforestation Regulation (EUDR), plot-level geolocation refers to the precise geographic identification of the land where a commodity was produced. 

This is done using: 

• GPS coordinates (latitude and longitude), or 

• Digitally mapped land boundaries (polygons) 

The purpose is to connect agricultural production to a specific, verifiable area of land  not just a region, district, or supplier address. 

In practical terms, it means being able to show exactly which piece of land produced the coffee, cocoa, palm oil, soy, timber, or cattle entering the EU market. 

Why Plot-Level Data Is Required 

EUDR prohibits placing commodities on the EU market if they were produced on land subject to deforestation after the regulation’s cut-off date. 

To verify this, authorities rely on: 

• Satellite imagery 

• Remote sensing datasets 

• Deforestation monitoring systems 

None of these tools can assess compliance using vague location data. 

Only precise spatial data allows authorities to: 

• Overlay farm boundaries with satellite imagery 

• Check forest cover history 

• Confirm whether land-use change occurred 

Without plot-level geolocation, compliance cannot be validated. 

Points vs Polygons 

Understanding the distinction is critical. 

GPS Points 

• Represent a single latitude/longitude coordinate 

• Indicate a location but not the size or boundaries of the farm 

• Often used for smallholder farms 

Limitation: 
A single point does not define the actual cultivated area. It cannot reliably verify whether the entire farm complies with deforestation rules. 

Polygons 

• Define the full boundary of a plot 

• Represent the total land area used for production 

• Enable accurate satellite overlay analysis 

Polygons are strongly preferred and, in many cases, necessary for demonstrating compliance  especially for larger farms. 

Accepted Data Formats 

Plot-level geolocation must be provided in standardized digital formats that can be processed and verified. 

Common accepted formats include: 

• GeoJSON – Lightweight and API-compatible spatial format 

• Shapefiles (.shp) – Common GIS format used in mapping systems 

• Validated coordinate datasets – Structured CSV or database exports with consistent coordinate reference systems 

Data must be: 

• Machine-readable 

• Spatially accurate 

• Consistent in coordinate system (e.g., WGS84) 

Common Errors 

Many operators underestimate how technical geolocation compliance can be. 

Frequent mistakes include: 

• Using a single GPS point for large commercial farms 

• Submitting overlapping or duplicated polygons 

• Mixing coordinate systems (leading to misplaced plots) 

• Incomplete data validation before submission 

• Failing to link geolocation data to production volumes or shipment batches 

A major compliance gap occurs when geolocation data exists but is not linked to specific exported goods. 

Best Practices 

To reduce compliance risk, operators should: 

1. Capture Geolocation at Supplier Onboarding 

Make spatial data collection part of initial supplier registration — not a last-minute request. 

2. Validate Against Satellite & Forest Monitoring Systems 

Cross-check submitted plots against deforestation datasets before placing goods on the EU market. 

3. Maintain Version Control 

Land boundaries can change due to: 

• Expansion 

• Subdivision 

• Ownership changes 

Maintaining historical records prevents future disputes. 

4. Link Plots to Volumes and Shipments 

Geolocation data must connect to: 

• Production batches 

• Procurement records 

• Due diligence statements 

Without this linkage, traceability is incomplete.

Frequently Asked Questions (FAQ’s)