Mapping a polygon for every tiny plot in a smallholder supply chain would be impractical. EUDR recognises this: a plot below 4 hectares may be given as a single point rather than a boundary. That makes geolocation feasible for cooperatives with thousands of small farmers. The condition is where operators slip.
The rule, precisely
- Below 4 hectares: a single Point geometry is allowed.
- The point must carry an Area: a point with no Area property is rejected, because the size cannot be assumed.
- 4 hectares or more: a point is not allowed. The plot needs a polygon boundary.
Why the Area matters
A point tells you where the plot is, not how big it is. Since the 4 hectare threshold decides whether a point is even allowed, the Area is what proves the point is permitted. Without it, the plot is incomplete.
Coordinates for points
A point uses the same coordinate rules as everything else: WGS84 degrees, longitude first, around 6 decimal places. At 6 decimals a point locates the plot to roughly a tenth of a metre, which is ample for a smallholder plot.
Handling thousands of points
Smallholder files are often long lists of coordinates in a spreadsheet. Converting them into valid point features, each with an Area, and checking every one is exactly the kind of bulk task a batch tool handles, rather than editing thousands of rows by hand.
Common questions
When can I use a point instead of a polygon?
For a plot below 4 hectares, provided the point carries an Area value. Plots of 4 hectares or more need a polygon.
Why is my point plot rejected?
The two usual reasons are a missing Area property, or an Area of 4 hectares or more, which requires a polygon instead.
Validate a smallholder point file
Paste your points and the tool checks each one has a valid Area and stays under 4 hectares, then builds clean features.
Fix my file