EUDR GeoJSON rejected: file is not a FeatureCollection
The EUDR information system reads exactly one file shape — a GeoJSON FeatureCollection with one feature per production place.
What the check requires
A blocking error — this record cannot pass deterministic validation until it is resolved.
Why this is reported
GIS tools can export the same plots in several JSON shapes: a bare geometry, a single Feature, or a FeatureCollection. Only the last one is accepted, and it must contain at least one feature — an empty collection fails the same way.
A related failure is a collection whose features list contains entries that are not features at all (null values or plain text), which some scripts and converters produce when a source row is empty.
How it gets fixed
There is no safe automatic repair for a file whose overall structure is wrong — inventing a wrapper around unknown content risks filing something you did not mean. Re-export from the tool that produced the file and choose GeoJSON FeatureCollection as the output shape.
If your data lives in KML, KMZ or CSV, the free check converts those formats into a well-formed FeatureCollection for you as part of the check.