TRACES didn't tell me why my file was rejected. How do I find out?

Paste the file into the validator above. It runs the same EUDR format rules and shows a specific, plain-language error and fix for each plot — the detail TRACES often doesn't give you.

My file passed your validator but TRACES still rejected it. Why?

This tool checks the geolocation file format. A rejection can also come from non-format issues — an incomplete Due Diligence Statement, account/permission problems, or server-side checks — which are outside a file validator's scope.

Is my rejected file uploaded anywhere when I check it here?

No. Validation runs entirely in your browser; your coordinates never leave your device.

Why TRACES rejected your EUDR GeoJSON

A geolocation file that looks fine can still be rejected by the EUDR Information System over a small formatting detail. Paste your file below to see exactly what’s wrong, or read the common causes and fixes underneath. Everything runs in your browser.

or paste below

🔒 Your file is validated entirely in your browser — nothing is uploaded to any server.

The most common EUDR GeoJSON rejection reasons

1. Coordinates don't have enough decimal places

Symptom: The file uploads but is flagged as imprecise, or coordinates look rounded.
Cause: EUDR requires at least 6 decimal places (~0.1 m). Passing data through a spreadsheet often rounds it to 4–5 decimals.
Fix: Re-export coordinates at full precision; never round latitude/longitude below 6 decimals.

2. Longitude and latitude are swapped

Symptom: Plots appear in the wrong country, the ocean, or the opposite hemisphere.
Cause: GeoJSON stores positions as [longitude, latitude] — longitude first. People used to writing 'lat, long' put them in the wrong order.
Fix: Swap the two values so longitude comes first and latitude second. EUDR coordinate format →

3. A large plot is given as a single point

Symptom: The file is rejected for plots that should be polygons.
Cause: Plots over 4 hectares must be a boundary Polygon. A single Point is only allowed for plots of 4 hectares or less.
Fix: Trace the boundary as a Polygon (or confirm the plot really is ≤ 4 ha). The 4-hectare rule →

4. The polygon crosses itself (self-intersection)

Symptom: 'Invalid geometry' or a self-intersection error on upload.
Cause: The boundary vertices are out of order, so edges cross. TRACES rejects self-intersecting polygons.
Fix: Re-trace the boundary so no edges cross; check the vertex order goes cleanly around the plot.

5. The polygon ring isn't closed

Symptom: 'Invalid polygon' or a ring/geometry error.
Cause: Each ring must start and end at the same coordinate and have at least 4 positions.
Fix: Make the last coordinate of every ring identical to its first.

6. The coordinate system isn't WGS-84

Symptom: Coordinates are large numbers (e.g. hundreds of thousands) instead of degrees.
Cause: The data is in a projected system (UTM, a national grid) rather than WGS-84 (EPSG:4326).
Fix: Reproject to WGS-84 geographic coordinates before submitting. Reproject with the converter →

7. The polygon has holes (interior rings)

Symptom: Excluded areas inside a plot are ignored, or the geometry is flagged.
Cause: The EUDR Information System ignores holes and reads only the outer boundary of a polygon.
Fix: Remove interior rings; represent any excluded area as separate polygons.

8. ProducerCountry is missing or wrong

Symptom: The submission is incomplete or the country isn't recognised.
Cause: Each plot is expected to carry a ProducerCountry property as an ISO 3166-1 alpha-2 code (e.g. BR).
Fix: Add a "ProducerCountry" property with the correct 2-letter country code.

9. The file isn't valid GeoJSON

Symptom: Upload fails immediately or the structure is not accepted.
Cause: Broken JSON (trailing commas, truncation) or the wrong top-level structure. GeoJSON must be a FeatureCollection of plot features.
Fix: Validate the JSON structure; ensure it is a FeatureCollection whose features are the plots.

10. The file is too large

Symptom: Upload is refused for size.
Cause: The whole Due Diligence Statement file must not exceed 25 MB.
Fix: Split very large submissions, or simplify overly dense polygon boundaries.

Frequently asked questions

TRACES didn't tell me why my file was rejected. How do I find out?: Paste the file into the validator above. It runs the same EUDR format rules and shows a specific, plain-language error and fix for each plot — the detail TRACES often doesn't give you.
My file passed your validator but TRACES still rejected it. Why?: This tool checks the geolocation file format. A rejection can also come from non-format issues — an incomplete Due Diligence Statement, account/permission problems, or server-side checks — which are outside a file validator's scope.
Is my rejected file uploaded anywhere when I check it here?: No. Validation runs entirely in your browser; your coordinates never leave your device.