TRACES is the EU system that receives EUDR due diligence statements. Your plot geolocation, as a GeoJSON, is attached to the statement. The frustration is familiar: you upload, TRACES returns a short error, and you are left guessing which of hundreds of plots is the problem.
What TRACES checks on upload
- The file parses as GeoJSON and the top level is a
FeatureCollection. - Each plot uses an allowed geometry: Point, Polygon, or MultiPolygon.
- Coordinates are WGS84, in range, at sensible precision.
- Polygon rings are closed, valid, and wound correctly.
- The file is under the 25 MB upload limit.
The 25 MB limit and large files
TRACES refuses uploads above 25 MB. A large supplier base with many detailed polygons can cross that line. The fix is to split the plots into smaller batches and submit them across several statements rather than one giant file.
Why the error is so unhelpful
TRACES tells you it rejected the file, not which plot or why in plain terms. That is the gap this tool closes: paste the same file, and every problem comes back with a stable rule ID, a plain explanation, and the matching TRACES reason, pointing you at the exact plot.
Fix before you submit
The reliable pattern is to validate and repair the file locally, confirm zero blocking errors, then upload the clean version to TRACES. For teams submitting per shipment, an API lets you check every file automatically before it ever reaches the portal.
Common questions
Why does TRACES reject my file without saying why?
TRACES returns a short error and does not point at the offending plot in plain terms. Validating the same file here gives you the exact rule, plot, and reason.
What is the TRACES upload size limit?
25 MB. Above that, split your plots into smaller batches across multiple statements.
Pass the TRACES upload first time
Validate free, repair the file, and upload a clean GeoJSON instead of guessing at a rejection.
Fix my file