EUDR GeoJSON rejected: coordinates out of range — latitude and longitude swapped
GeoJSON coordinates are [longitude, latitude] in WGS84. Values outside ±180 and ±90 make the file unreadable — and swapped axes are the most common cause.
What the check requires
A blocking error — the EUDR information system refuses the file until it is resolved.
Why files fail this check
Many tools, formats and people write coordinates as latitude first. In GeoJSON that order is reversed, so a plot at 6.7° N, 79.9° E written the familiar way ends up claiming a latitude of 79.9° — outside the valid range once it moves far enough from the equator.
Out-of-range values that a swap does not explain usually mean the file is in a projected coordinate system (UTM metres, national grids) rather than WGS84 decimal degrees.
How it gets fixed
When every out-of-range position in a plot becomes valid with its axes swapped — and the in-range ones stay valid too — the engine offers the swap as a suggested repair. Because it is a judgment call, it is never applied silently: the fix is flagged, you apply it per plot, and you review the result on the map.
If the swap does not explain the values, reproject the file to WGS84 (EPSG:4326) in your GIS tool and export again — reprojection needs the source system, which only your tool knows.