Error catalogueEUDReudr.geo.post-truncation-validity

EUDR GeoJSON error: geometry collapses after 6-decimal truncation

The current V3 file process keeps 6 decimal places. Distinct vertices must still remain distinct and every polygon must still enclose a real area after those extra digits are removed.

BlockingFix at the source

What the check requires

After six-decimal truncation, coordinates must still describe distinct points and a real polygon surface. Truncation must not collapse vertices, create adjacent duplicates or reduce an exterior ring to zero area.

A blocking error — this record cannot pass deterministic validation until it is resolved.

Why this is reported

This happens when two or more coordinates differ only beyond the retained precision. They look separate in the source file, but become the same coordinate after truncation. A short edge can disappear, adjacent duplicate vertices can appear, or an entire exterior ring can collapse to a line or a point.

This is a format and geometry-integrity check. It does not decide whether the land is compliant, deforestation-free or accepted by the EUDR Information System.

How it gets fixed

Inspect the flagged vertices in the source mapping tool and correct the boundary so its real points remain distinct at 6 decimal places. Do not add invented digits or move vertices just to silence the finding.

Export the corrected boundary again and rerun the check. If the source cannot provide a stable boundary at the required precision, ask the supplier or surveyor for a better plot file.

CitationEUDR GeoJSON File Description v1.5, straight-line and duplicate-coordinate failures after six-decimal processing; EUDR Operator API Reference v1.0, API V3 GEO-CORD-10profile 1.0.5 · Effective from 2026-07-17 · captured 2026-07-16