EUDR Point Coordinates vs Polygons

A point marks a location; a polygon describes an area

EUDR permits geolocation through at least one latitude and longitude point, with at least six decimal digits, but requires polygons for non-cattle production plots larger than four hectares. A point identifies a position. A polygon uses connected coordinate positions to describe the perimeter of the production plot. These representations carry different information and are not freely interchangeable where the law requires the latter.

A plot of exactly four hectares does not exceed the legal threshold. A smaller plot may be represented with a polygon where useful, but a larger non-cattle plot cannot be reduced to a point simply because that is easier to upload. The decision concerns the actual production plot.

Apply the threshold to the correct unit

Article 2(27) defines the plot using the recognised real-estate property and sufficiently homogeneous conditions for assessing deforestation and degradation risk. The threshold does not concern the shipment's combined sourcing area, the cooperative's total membership land or the supplier company's entire global estate.

If ten legitimate two-hectare plots contribute to one lot, their combined area does not turn them into one twenty-hectare production plot. Each still needs its own appropriate location record. Equally, breaking a genuine ten-hectare plot into invented smaller units to retain point records does not faithfully apply the plot definition.

What a point can and cannot establish

For a plot eligible for point representation, the point should identify the production location rather than a nearby road, house or collection office. Keep the plot identifier, area information and source record alongside it. A point is less informative about the edge of the production area, which can matter when investigating nearby land changes.

For example, a point inside an established agricultural field may sit close to a forest-conversion alert on adjacent land. The reviewer may need additional boundary evidence to establish whether the alert concerns the production plot. The legal permission to use a point does not prevent asking for more evidence where the actual risk assessment requires it.

What a polygon needs to represent

A polygon must describe the production plot's perimeter with sufficient coordinates. It is not a rough rectangle enclosing a whole village or a convex outline combining unrelated farms and intervening land. Its relationship to the production area should be supported by the supplier's boundary evidence and acquisition method.

The polygon requirement guide explains the threshold in detail. For an irregular field, a shape with too few vertices can omit contributing land or include a materially different area. More vertices do not automatically mean better evidence, however; redundant points can add complexity without improving the boundary's faithfulness.

Precision is separate from representation

Both points and polygon coordinates must meet the numerical precision requirement. Adding decimal places to a poorly located point or an approximate boundary does not increase its observed accuracy. Preserve the source and any uncertainty so the reviewer can judge what the geometry actually establishes.

A phone observation made under obstructed conditions and a boundary drawn from suitable imagery may have different limitations. Neither should be described as accurate merely because its exported coordinates contain six decimal digits. The evidence should explain the collection method and why the geometry corresponds to the relevant plot.

Use the official exchange specification

The current Commission GeoJSON documentation uses WGS 84 decimal-degree coordinates and longitude before latitude in coordinate arrays. A familiar map display may label its fields in the opposite order, so export settings need checking. Coordinates in another reference system require a proper transformation rather than a change of column labels.

For polygons, the ring must close with the same first and last coordinate position. The Information System documentation also identifies unsupported geometries, including shapes with holes and self-crossing forms. A GIS file that displays locally is not automatically compatible with the current import rules. Test the intended export using the official specifications applicable to the workflow.

Cattle are not governed by the ordinary area test

For cattle, Article 9(1)(d) concerns all establishments where the animals were kept. The non-cattle polygon threshold should not be applied as a rule requiring a grazing establishment over four hectares to supply an ordinary crop-style polygon. Establishment identification and movement relationships are the central questions.

The narrow Article 4a primary-operator postal-address alternative also needs separate consideration. Neither cattle treatment nor that alternative permits an unrelated supplier office location to stand in for the required production places. Identify the legal regime before deciding which representation belongs in the file.

Keep a reasoned format decision

A practical record states the plot or establishment identifier, size basis, chosen representation, source, version and reviewer. Where an optional polygon is used for a smaller plot, record it consistently. When a larger plot becomes relevant, ensure the system does not silently reuse an old point record.

The EUDR geolocation requirements guide puts geometry within the wider evidence process. Use Article 2(28) for the legal threshold and the official GeoJSON description for file compatibility. Passing technical validation establishes neither correct production origins nor deforestation-free status.

For supplier onboarding, request one representative point record and one representative polygon before collecting thousands of entries. Check that the exported files preserve producer and plot relationships and that the reviewer can interpret the land correctly. This early test can reveal a format misunderstanding while correction is still straightforward, rather than after a whole season of records has been prepared.