Shapefile → TRACES · EUDR
How to import a Shapefile (.zip) into TRACES for EUDR
A Shapefile arrives as a .zip of .shp/.shx/.dbf/.prj parts — and TRACES will not let you select it. The EUDR "Import Geojson" dialog accepts only .geojson/.json. A Shapefile has to be converted, and usually reprojected, 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 a Shapefile will not import into TRACES
Shapefiles are the GIS/forestry standard, but they are a multi-file binary format, often in a national projected coordinate system. TRACES expects a single GeoJSON file in WGS84 decimal degrees. The file dialog will not accept the .zip, and the coordinates would be in the wrong system even if it did.
Shapefile → WGS84 GeoJSON
Drop the zipped Shapefile into DDSpass. It reads the .prj, reprojects to WGS84 decimal degrees, repairs the geometry issues that break EUDR files (self-intersections, unclosed rings), and exports TRACES-ready GeoJSON. Large forest boundaries are simplified within a 0.5% area guard to stay under the 25 MB limit. Nothing is uploaded.
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
Can TRACES import a Shapefile (.zip) for EUDR?
No. Only GeoJSON is accepted. A Shapefile must be converted to WGS84 GeoJSON first.
My Shapefile is in a national grid — will the coordinates be right?
Yes, if the .prj file is included in the zip. DDSpass reads it and reprojects to the WGS84 decimal degrees TRACES requires.