EUDR GeoJSON rejected: coordinates are malformed
Every coordinate must be a [longitude, latitude] pair of numbers, nested at the correct depth for its geometry type.
What the check requires
A blocking error — the EUDR information system refuses the file until it is resolved.
Why files fail this check
Hand-edited files, spreadsheet round-trips and buggy exporters produce coordinates that look right at a glance but are not valid positions: numbers stored as text ("12.345678"), null entries, empty arrays, or a polygon missing its ring wrapper so the nesting depth is off by one.
A geometry with zero valid positions carries no location at all, so the whole feature fails — the registry cannot place a plot it cannot read.
How it gets fixed
Malformed coordinates cannot be repaired automatically — a repair must never invent geometry, and there is no way to know what a missing or garbled position was meant to be. The check reports the first defective paths inside the file so you know exactly where to look.
Re-export the affected plots from your GIS tool or source data. If the file came out of a spreadsheet, make sure coordinate columns are numeric, not text.