KML → TRACES · EUDR
How to import KML / Google Earth data into TRACES for EUDR
Exported a plot from Google Earth as KML (or KMZ) and TRACES will not let you select it? The EUDR "Import Geojson" dialog only accepts .geojson/.json, so a KML file cannot be chosen at all. It has to be converted to GeoJSON first.
EUDR is mandatory for medium & large operators from 30 December 2026 — get your supplier files TRACES-ready now.
Files never leave your browser · no upload
Why TRACES will not take KML
KML is Google Earth's format; the EU system expects a GeoJSON FeatureCollection in WGS84. The file dialog filters KML out, and even a renamed file would fail, because KML carries altitude values, a different container and sometimes reversed coordinates — none of which TRACES reads.
KML → GeoJSON, repaired
Drop your .kml into DDSpass. It converts to GeoJSON, drops altitude, closes unclosed rings, standardises the country code, and flags anything a person must review. See KML to EUDR GeoJSON for the full conversion notes. The file never leaves your browser.
Which Import button to use in TRACES
Verified on TRACES build 8.2.0.2: upload the converted GeoJSON with the top-level Import button (next to “Add Production Place”) — that path fills the producer name, country of production and place description from the file. The Import GeoJSON inside “Add Production Place” reads only the geometry and leaves the country on “No country selection”.
Questions
Does TRACES accept KML or KMZ for EUDR?
No. Only GeoJSON can be imported for EUDR geolocation. KML/KMZ must be converted first.
I renamed my .kml to .json — why does it still fail?
Renaming does not change the contents. TRACES parses the file as GeoJSON; a KML body is not valid GeoJSON and fails. It must be genuinely converted.