KML → EUDR GeoJSON
KML to TRACES-ready EUDR GeoJSON — without rejections
TRACES only accepts GeoJSON for EUDR geolocation — KML and KMZ are rejected outright. But converting the extension is not enough: the file has to match the Commission’s GeoJSON File Description, or your Due Diligence Statement bounces.
Fix your file — freeEUDR 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 rejects KML
The EU Information System expects a GeoJSON FeatureCollection in WGS84 (longitude, latitude). A KML export carries the right shapes but the wrong container, the wrong coordinate order in places, altitude values, and often unclosed polygons — each of which is a documented rejection cause.
DDSpass converts the KML to GeoJSON and repairs those issues: it closes rings, drops altitude, standardises the country code, and flags anything a person must review.
How to convert
Drop your .kml (or a KMZ unzipped to KML) into the tool. You get a clean, TRACES-ready GeoJSON plus a plain-language fix report you can send back to your supplier. Everything runs in your browser — the file is never uploaded.
Questions
Does TRACES accept KML for EUDR?
No. The EU system only accepts GeoJSON for geolocation. KML and KMZ must be converted first.
Is my supplier data uploaded anywhere?
No. Conversion and validation happen entirely in your browser; the file never leaves your device.