EUDR GeoJSON rejected: polygon not closed
Every polygon ring must end where it starts — the last coordinate pair repeats the first. Many tools omit that closing pair.
What the check requires
A blocking error — the EUDR information system refuses the file until it is resolved.
Why files fail this check
This is one of the most common findings in supplier files, and one of the most harmless: plenty of GIS tools and converters consider a polygon implicitly closed and skip the duplicate final coordinate. The GeoJSON specification requires it explicitly, so the registry refuses the ring.
A ring with fewer than three distinct positions is a different problem — it cannot enclose an area at all, and needs to be re-mapped rather than closed.
How it gets fixed
The repair is deterministic and meaning-preserving: the first coordinate is appended as the last, closing the ring without moving a single vertex. The free check applies it automatically the moment your file is read, and records it in the repair log.
Nothing about your boundary changes — the polygon covers exactly the land it covered before.