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).
What it means
Geolocation is the coordinates that locate production — not the warehouse that ships. Without valid geolocation, a statement cannot truthfully claim the goods are deforestation-free for that production unit.
In the regulation
Article 9(1)(d) requires operators to collect geolocation of all plots of land where the relevant commodity was produced, with the date or time range of production. Article 2(28) defines what “geolocation” means (point vs polygon). The duty applies at every country risk tier.
How ERWAY treats it
Validation gates check GeoJSON structure, winding and size rules before a pack is filing-ready — the failure modes described in the geolocation articles on this site.
Related terms
- 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.
- Geolocation data
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.
- 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.
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