EUDR geolocation guides
From the data you have (a Google Earth file, a shapefile, a spreadsheet, a phone) to a file the EU Information System accepts. Every rule stated is sourced.
From Google Earth (KML)
Draw plot boundaries in Google Earth Pro, save them as KML, and turn them into a GeoJSON file the EU Information System accepts, step by step.
From a shapefile
Turn a zipped shapefile from QGIS, ArcGIS or a survey team into WGS84 GeoJSON for an EUDR due diligence statement, keeping the coordinate system right.
From Excel or CSV
Turn a spreadsheet of plot coordinates into GeoJSON for the EU Information System: one row per plot, one row per corner, or WKT, including decimal commas and DMS.
From GPS phone apps
How to walk a plot boundary with a smartphone GPS app so the result passes the EU Information System: accuracy, corners, closing the loop, and exporting.
UTM to WGS 84
Recognise UTM and national-grid coordinates, find the right zone and EPSG code, and convert them to the WGS84 degrees the EU Information System requires.
Point vs polygon (4 ha)
When a single GPS point is enough for an EUDR plot and when a polygon is required: the four-hectare rule, the cattle exception, and the Area property.
The 25 MB limit
How the 25 MB per-statement limit works, what makes geolocation files big, how to reduce them without changing the land declared, and how to split and group statements.
Type I vs Type II
The EUDR specification defines two variants of the geolocation file. What each is for, which properties they need, and how the checker tells them apart.
Timeline
Every date that matters for EUDR geolocation (the cut-off, the application dates after two postponements, the 2026 changes) each checked against the Official Journal.
Pre-submission checklist
A practical checklist for the geolocation part of a due diligence statement: file format, coordinates, shapes, properties and limits, each linked to the rule behind it.