Shapefile → EUDR GeoJSON
Convert a Shapefile to TRACES-ready EUDR GeoJSON — without rejections
Forestry, cadastral and GIS teams hand over plots as a zipped Shapefile — but TRACES only accepts GeoJSON. And a Shapefile is not one file: it is several, plus a coordinate system, so the conversion has to reproject and repair, not just rename.
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 a Shapefile needs more than a rename
A Shapefile is a set — .shp (shapes), .shx (index), .dbf (attributes) and crucially .prj (the coordinate reference system). Plots are often stored in a national projected grid in metres, not the WGS84 longitude/latitude degrees TRACES requires. Convert the extension without reprojecting and every plot lands in the wrong place — or fails outright.
DDSpass reads the .prj, reprojects to WGS84 decimal degrees, and repairs the geometry Shapefiles commonly carry — self-intersecting rings from machine tracing, unclosed polygons, holes — then flags anything a person must review.
Zip it, drop it, done
Put the .shp with at least its .shx, .dbf and .prj into one .zip and drop it in. You get a clean, TRACES-ready GeoJSON plus a plain-language fix report for your supplier. Cadastral and plot data is sensitive — everything runs in your browser, and the file is never uploaded.
Questions
Does TRACES accept a Shapefile for EUDR?
No. The EU system only accepts GeoJSON for geolocation. A Shapefile must be converted — and reprojected to WGS84 — first.
Which files do I need in the zip?
At minimum .shp, .shx and .dbf; include the .prj so the coordinate system is known. Without a .prj, DDSpass cannot reproject reliably and flags the plots as a local grid to re-send.
Is my Shapefile uploaded anywhere?
No. It is read, reprojected and validated entirely in your browser; the file never leaves your device.