TRACES silent error · EUDR
TRACES Total Area shows 0.0000 after import — why, and how to fix it
You imported your GeoJSON, TRACES accepted it with no error — but the plot shows Total Area 0.0000. The declaration looks fine and will submit, yet the area is missing. Two file problems cause this, and TRACES flags neither.
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
Cause 1: the area is written as text
If a feature's area is quoted — "Area": "1.5" instead of "Area": 1.5 — TRACES reads it as 0.0000. Spreadsheets and hand-edited files do this constantly. For a point plot, where the hectarage is the only size information, that means submitting a plot with no area at all.
Cause 2: the geometry is not a Point or Polygon
If a plot's geometry is a LineString (or anything other than Point/Polygon), TRACES imports the feature but drops the shape — the production place is created empty, with Total Area 0.0000 and no location at all. The import still shows success.
Fix it in DDSpass
DDSpass coerces text numbers back to real numbers (keeping 6 decimals) and detects geometry it cannot use — flagging it in the fix report instead of emitting a location-less plot. You get a file with real areas and real shapes. If your area is almost zero rather than exactly zero, that is a different fault — see a collapsed self-intersecting polygon. Nothing is uploaded.
Questions
Why does TRACES show 0.0000 when my file clearly has an area?
The most common cause is the area being stored as text ("1.5" in quotes) instead of a number — TRACES reads a quoted value as zero. A non-Point/Polygon geometry also imports with zero area.
Will TRACES stop me submitting a zero-area plot?
No. It accepts the import silently. That is why it is worth catching before you submit.