GUIDE 02 · 6 MIN READ · UPDATED SEP 2026
Geolocation rules: points vs polygons.
Plot geolocation is the EUDR’s signature demand. The rules are short — one threshold, one coordinate system — and the practice is where it gets interesting.
The 4-hectare rule#
The regulation draws one line: plots of 4 hectares or less may be located by a single point (a latitude/longitude pair); plots above 4 hectares must be located by a polygon — a boundary of connected vertices.
The threshold is per plot, not per farm: a large estate of small blocks still owes polygons only for the blocks above the line — though mapping the whole estate is usually easier.
FIG 01 — THE 4-HECTARE RULE
“Four hectares is the regulation’s dividing line: a dot on one side, a shape on the other.”
WGS84 & precision#
All coordinates use the WGS84 reference system (the “GPS” one — EPSG:4326), in decimal degrees with at least six decimal places: 5.351234, -4.028391. Six decimals puts you within roughly 11 cm of true position.
Common trap: coordinates exported in a projected CRS (metres) or in degrees-minutes-seconds. Convert to decimal degrees WGS84 before anything else.
Collecting polygons from smallholders#
If your supply base is thousands of smallholders, collect once at registration, not per shipment: a phone GPS app walking the boundary, a cooperative intake template, or KML/GeoJSON export from a mapping tool the co-op keeps current.
Acceptance criteria that save rework: closed rings (first vertex equals last), WGS84 decimal degrees, no self-intersections. A one-page intake template with those three checks prevents most rejection cycles.
PRACTICAL NOTE
Free check — paste coordinates or GeoJSON into the scope-checker and the geometry is validated before screening.
TRY THE SCOPE-CHECKERCommon validation errors#
The usual suspects: self-intersecting polygons (a boundary that crosses itself — the figure-eight), wrong CRS (projected metres read as degrees), duplicate consecutive vertices, and unclosed rings. All are trivially detectable — if you look before filing.
Automate the check at intake. Screening tools, ours included, validate geometry before any dataset query, so a malformed ring never reaches the expensive part.
“Most rejected geolocation isn’t wrong — it’s malformed.”
How screening uses the geometry#
Screening intersects your point or polygon with deforestation datasets — Hansen GFC tree-cover loss, GLAD/RADD alerts, Whisp convergence signals. A polygon gets per-area statistics inside the boundary, reported in hectares.
A point is screened as a point: it has no area, so the hectare figures cover only the pixel it falls in and will usually read 0.00 ha. That is a limit of the geometry, not a finding about the land, and every screening of a point says so on its result and on its pack. Where the EUDR lets you supply a point — holdings of four hectares or less — it is still worth supplying the boundary if you have it.
The output is a signal summary — indicative, decision-support — that becomes part of your evidence pack. Better geometry in, better signal out.
CONTENTS
GUIDE 02 OF 03