Skip to content

TRACES NT · GEOLOCATION TROUBLESHOOTING

Rejected file? Fix it.

The DDS goes through TRACES NT, and geolocation is where uploads break. The good news: almost every rejection is a format problem with a known fix — and format problems are checkable before you ever open the portal.

WHAT TRACES NT ACTUALLY ACCEPTS

Reference system
WGS84 (EPSG:4326) — the “GPS” one, unprojected
Format
Decimal degrees (not degrees-minutes-seconds), e.g. 5.351234
Precision
At least 6 decimal places per coordinate (≈11 cm)
Plots ≤ 4 ha
A single latitude/longitude point is sufficient (Art. 2(28))
Plots > 4 ha
A polygon — a closed ring of vertices (Art. 2(28))
Cattle
A single point per establishment, whatever its size (Art. 2(28))
Polygon closure
First vertex must equal the last vertex
File upload
GeoJSON in practice — KML/KMZ and shapefiles need conversion first

Geometry requirements (points vs polygons, six decimals, WGS84) are fixed by Art. 2(28) of the regulation; upload formats reflect the portal as commonly encountered. Interfaces change — if the portal tells you otherwise on screen, the portal wins.

THE SEVEN USUAL SUSPECTS

Every rejection cause we see, and its fix.

Work down the list against your file — most rejected files fail on two or three of these at once. Each fix below ends in the same place: validate before you re-upload.

CAUSE 01

Fewer than six decimal places

SYMPTOM
The portal rejects coordinates like 5.3512, -4.028 — or accepts them and the DDS later bounces at validation.
CAUSE
Art. 2(28) requires at least six decimal places in decimal degrees. Coordinates exported at two or four decimals — common in spreadsheet templates and older GPS units — fall short.
FIX
Re-export the coordinates at full precision from the source. Never pad with zeros by hand if true precision was lost — re-collect or re-export from the original device or file. The geo tools validator flags short decimals on paste.
CHECK YOUR FILE — FREE GEO VALIDATOR

CAUSE 02

Unclosed polygon ring

SYMPTOM
Polygon uploads fail with a generic geometry error, even though the shape looks fine on the map preview.
CAUSE
The GeoJSON ring does not loop back: the first vertex and the last vertex are not identical, so the boundary is technically an open line, not an area.
FIX
Append the first vertex to the end of the coordinate array (or use a tool that closes rings on export). While you are there, check for self-intersections — the figure-eight boundary fails for the same family of reasons.
CHECK YOUR FILE — FREE GEO VALIDATOR

CAUSE 03

KML or KMZ instead of GeoJSON

SYMPTOM
The file from Google My Maps or Google Earth is refused outright — wrong file type.
CAUSE
KML/KMZ (Google’s formats) and shapefiles are not what the TRACES NT geolocation upload takes in practice; GeoJSON is the working format.
FIX
Convert once, carefully: many converters silently change the coordinate order or drop precision on the way through. Convert, then validate the output before upload — paste the GeoJSON into the geo tools validator and check decimals, order and closure.
CHECK YOUR FILE — FREE GEO VALIDATOR

CAUSE 04

Wrong coordinate order in GeoJSON

SYMPTOM
Points land in the ocean or the wrong hemisphere when plotted — Madagascar instead of Ghana, or the antipodes.
CAUSE
GeoJSON specifies [longitude, latitude] pairs — x first, y second — the opposite of the “lat, lon” habit from GPS handsets and most web maps.
FIX
Swap the pair order when building the file. A quick sanity check catches it: Ghana is around lat 5–11, lon -3 to 1; no valid plot coordinate there exceeds ±90 in latitude.
CHECK YOUR FILE — FREE GEO VALIDATOR

CAUSE 05

A point on a plot over 4 hectares

SYMPTOM
The submission is rejected because a plot exceeding 4 ha is located by a single point.
CAUSE
Art. 2(28) draws the line at 4 hectares: points are acceptable for plots at or below it; above it, a polygon is mandatory. Aggregated estates mapped as one center point hit this constantly.
FIX
Collect a proper boundary for every plot over 4 ha — a walked GPS boundary, a cooperative mapping exercise, or digitization on current imagery. The points-vs-polygons guide covers collection at smallholder scale.
CHECK YOUR FILE — FREE GEO VALIDATOR

CAUSE 06

Latitude and longitude swapped in form fields

SYMPTOM
Coordinates validate but map to a mirrored location — or fail range checks with values like 95.4.
CAUSE
Manual entry into the portal’s separate latitude and longitude fields, with the values pasted into the wrong boxes. Six decimals make the swap look plausible at a glance.
FIX
Paste deliberately: latitude is bounded by ±90, longitude by ±180 — anything beyond ±90 in the latitude field is swapped. Spot-check one known plot against a web map before filing the batch.
CHECK YOUR FILE — FREE GEO VALIDATOR

CAUSE 07

Invalid characters and malformed files

SYMPTOM
Upload fails before geometry is even read — “invalid file”, parse error, or silent truncation after a certain number of plots.
CAUSE
Curly quotes or commas inside field labels exported from spreadsheet templates, non-UTF8 encoding, hidden BOM bytes, thousand-separators in coordinates, or hand-edited JSON with a trailing comma.
FIX
Regenerate the file from a clean source rather than hand-editing: keep labels plain ASCII where possible, save as UTF-8 without BOM, and validate the JSON parses before upload.
CHECK YOUR FILE — FREE GEO VALIDATOR

EUDR Clear does not file to TRACES for you — we screen plots and assemble evidence packs formatted to support your submission. Reviewing, signing and filing remain yours, and the due-diligence obligations remain with the operator (EUDR Art. 10).

Indicative screening for decision-support only — not a compliance determination, certification, or legal advice. Due-diligence obligations remain with the operator (EUDR Art. 10).

BEFORE YOU RE-UPLOAD

Validate first. File once.

Paste coordinates or GeoJSON — decimals, order, closure, format: checked free.

Open the geo validator

Indicative screening for decision-support only — not a compliance determination.