Point vs polygon
Article 2(28): a point is one latitude/longitude with at least six decimal digits; plots above four hectares (non-cattle) need a polygon describing the perimeter.
What it means
A point is a single coordinate pair. A polygon is a closed ring of points describing the plot perimeter. Supplying a point for a large non-cattle plot is a common reason statements fail technical checks.
In the regulation
Article 2(28) requires at least six decimal digits. For plots above four hectares used for a relevant commodity other than cattle, it requires polygons with enough points to describe each plot’s perimeter. Cattle establishments are declared as points.
How ERWAY treats it
Map and mitigation screens show point and polygon against the same risk layers so teams see why a pin is rejected for a large parcel.
Related terms
- Geolocation data
Four-hectare rule
Under Article 2(28), plots above four hectares used for a relevant commodity other than cattle need a polygon; at or under four hectares a single point (six decimal digits) can suffice.
- Geolocation data
Geolocation
Latitude and longitude of every plot of land where the relevant commodity was produced (Article 9(1)(d)), as a point or polygon under Article 2(28).
- Geolocation data
Plot of land
Land within a single real-estate property, homogeneous enough that deforestation risk can be assessed as one unit — not an arbitrary farm name that mixes unlike patches.
Keep reading
Geolocation dataPoints, polygons and the four-hectare rule
When EUDR geolocation may be a point and when it must be a polygon, what six decimal places actually buys you, and the geometry that fails validation.
7 min read
Geolocation dataGeoJSON that passes: the geometry errors that bounce a statement
The geometry and file errors that cause EUDR plot data to fail validation, why each one happens, and how to catch them while they are still cheap to fix.
5 min read