EUDR Geolocation Data Requirements: Coordinates, Polygons and GeoJSON

Reviewed 18 October 2026. This explainer addresses technical data quality, not legal advice or an EUDR due-diligence opinion. Confirm the current law, covered product and buyer specification before relying on a file format.

Start with the plot and its source

A geolocation file needs a traceable connection to the production plot and the relevant supplier. A valid coordinate can still describe the wrong location. Preserve the original source file, collection method, plot identifier, owner permission and coordinate reference system. Do not treat successful parsing as proof of origin, legality or deforestation-free production.

Coordinates and polygons serve different needs

The EUDR geolocation definition uses latitude and longitude coordinates with at least six decimal digits. For non-cattle commodities on plots over four hectares, geolocation generally uses polygons that describe the perimeter. Confirm requirements for the exact plot and commodity. EFICO's coffee policy prefers polygons and permits GPS points for plots under four hectares; this buyer preference is distinct from the legal definition and boundary cases require care.

GeoJSON checks that catch practical errors

• Check axis order: GeoJSON coordinates normally use longitude, latitude, not the other way round.
• Verify CRS handling. Projected metre-based coordinates cannot simply be relabelled as longitude and latitude.
• Check polygon rings, closure, self-intersections and geometry type against the accepted specification.
• Keep unique plot IDs and reconcile declared area metadata using a documented method.
• Check that all required properties are present and linked to an authorised original record.

A technically supported reprojection or ring correction belongs in a working copy with its rationale and reviewer record. More decimal places do not create positional accuracy. Missing boundaries must come from an authorised source owner or an appropriately scoped survey; drawing plausible shapes is not a repair.

Deliver the exceptions with the file

A useful handover includes a versioned output, source manifest, issue register, supported corrections and remaining exceptions. The buyer or responsible operator still needs to conduct its own required due diligence and resolve substantive evidence gaps. Soilo's scoped QA checks technical integrity and supported relationships; it does not certify plots or submit due diligence statements.