DrawMyPlot
Sign in

EUDR GeoJSON errors and how to fix them

Paste or open your file in the validator above: it lists the problems below, fixes the safe ones automatically, and shows the plots on a satellite map so you can see what is wrong.

1. Plots in the wrong place

Symptom: plots appear in the sea, in another country, or mirrored across the equator.
Cause: latitude and longitude swapped, or a minus sign missing.
Fix: correct the spreadsheet and re-import. See coordinate order and minus signs.

2. Coordinates in metres

Symptom: numbers like 385412 or 590230 instead of values between −180 and 180.
Cause: the file was exported in a projected system such as UTM.
Fix: re-export from your GIS in WGS84 (EPSG:4326). This cannot be guessed safely, so the validator reports it rather than fixing it.

3. Polygon lines that cross

Symptom: a plot shaped like a figure eight or a bow tie.
Cause: corners recorded out of order, for example when walking back and forth along a boundary.
Fix: redraw the plot on the map, or drag the corners into the right order. The validator marks the crossing.

4. Unclosed or too-small polygons

Cause: the last corner is not identical to the first, or the polygon has fewer than three distinct corners.
Fix: closing the ring is fixed automatically. A polygon with fewer than three corners should be redrawn or turned into a point.

5. Holes inside polygons

Cause: the polygon has an inner ring, for example to cut out a house or a pond.
Fix: holes are not supported in EUDR files. The validator removes them. If the excluded area matters, map the productive areas as separate plots.

6. Lines instead of polygons

Cause: the boundary was drawn as a path (LineString) in Google Earth or a GPS app.
Fix: the validator closes a line into a polygon. Check the result on the map.

7. Area written as text

Cause: "Area": "3.5" instead of "Area": 3.5, or a unit inside the value such as "3.5 ha".
Fix: the Area must be a number of hectares. Text that is a plain number is converted automatically.

8. Wrong property names

Cause: productionplace, Producer_Name or similar. Property names are case-sensitive: ProducerName, ProducerCountry, ProductionPlace, Area.
Fix: the case is corrected automatically.

9. Country written as a name

Cause: "Côte d'Ivoire" or "Brasil" instead of a two-letter ISO code.
Fix: use codes such as CI, BR, ID, VN, CO, GH. Invalid codes are reported.

10. Points for large plots

Cause: a point with an Area above 4 hectares.
Fix: draw the boundary as a polygon. See the 4-hectare rule.

Still rejected?

Send us the exact error message from the EU system (and, if you can, a sample file with names removed) at [email protected]. We add new checks to the validator based on real error reports.

More EUDR guides

How to create an EUDR GeoJSON file

Step by step, from a satellite map, a GPS spreadsheet or an existing KML file.

The EUDR 4-hectare rule

When a single point is enough and when you must draw a polygon.

EUDR coordinates format

WGS84, six decimals, longitude first, and how to convert degrees-minutes-seconds.

Google Earth KML to EUDR GeoJSON

Turn plots drawn in Google Earth or My Maps into an EUDR file.

Frequently asked questions

Does the validator upload my file?
No. The file is checked in your browser and never sent to our server.
Can it fix every problem?
It fixes formatting problems automatically. Problems that need a human decision, such as crossing lines or coordinates in metres, are reported so you can correct them.

Page updated 2026-10-11