EUDR plot file checker and fixer

1. Drop your plot file onto the map, or try the sample file to see what the checker finds and fixes.
2. Read the list: what was fixed in the new file, what you need to fix at the source, and what to check. Problem plots are marked in red on the map.
3. If some plots have no country, type it once. Then download the GeoJSON and upload it to your due diligence statement in TRACES.

Runs in your browser. Files are never uploaded.

Read the guide: What geolocation does the EUDR require? · Tools for EUDR geolocation data

Input

A KML, KMZ, shapefile (.zip or its separate files), GeoJSON, or a CSV or Excel sheet with latitude and longitude or polygon columns.

Output

A GeoJSON file in the EU format (split into parts over 25 MB), and a list of every fix, every problem to fix at the source, and every warning.

sample-coop-plots.geojson, the sample file on the page: seven plots from our demo account in Costa Rica, with mistakes put in on purpose.

7 plots · 1 problem · 3 checks · 6 fixes · sample-coop-plots-eudr.geojson
Problem · Its boundary crosses itself, like a figure eight, which TRACES rejects. The crossings are marked in red. To fix it here, open the plot and choose Edit boundary, or redraw it in your original file. (Plot 4)
Check · Overlaps another plot by 10 m² or more. Check the boundaries; the overlaps are marked in red. To fix one here, open the plot, choose Edit boundary and move its corners onto the other plot's boundary. (Plot 1, Plot 2)
Check · One GPS point and no area: TRACES counts it as 4 ha. Add its real area in hectares if you know it. (Plot 6)
Check · Over 4 ha but only one GPS point. Plots over 4 ha need their boundary mapped as a polygon, not a point, unless they are for cattle. (Plot 7)
Fixed · Columns renamed to the exact names TRACES reads: "producer_name" → ProducerName, "country" → ProducerCountry, "plot" → ProductionPlace, "area_ha" → Area.
Fixed · The area was text, so TRACES would read it as 0; written as a number. (Plot 1, Plot 2, Plot 7)
Fixed · Country "Costa Rica" written as its two-letter code, CR. (Plot 1, Plot 2, Plot 3, Plot 4, Plot 5, Plot 6, Plot 7)
Fixed · Boundary was drawn as a closed line; turned into a polygon. Check it is the plot's boundary. (Plot 5)
Fixed · Had a hole, which TRACES ignores; split into parts that leave the hole out. (Plot 3)
Fixed · Coordinates rounded to 6 decimals (about 10 cm), as TRACES stores them. (Plot 1, Plot 3, Plot 6)

• It checks the file only. It doesn't check for deforestation or legality, doesn't say whether you comply, and doesn't file anything in TRACES.
• The rules follow our reading of the EU's GeoJSON file description (v1.5). TRACES itself decides what it accepts.
• It can't tell whether a boundary is right on the ground. Self-crossing outlines are flagged, not redrawn: only the person who mapped the plot knows its real shape.
• Plots with a hole are split into two parts that leave the hole out. Lines are turned into boundaries only when they close.
• Files over 250 MB are too large to check in the browser.

Based on the official EU texts. See our EUDR sources, with the version we follow and the day we last checked each one.

The EU's GeoJSON file description asks for WGS84 coordinates, longitude first, cut to six decimals. Plots are Points, MultiPoints, Polygons, MultiPolygons or GeometryCollections; lines aren't accepted, polygons must be closed, and polygons with holes or crossing outlines aren't processed. The only properties read are ProducerName, ProducerCountry (a two-letter ISO code), ProductionPlace and Area (hectares, as a number), and their names are case-sensitive. A point with no Area counts as 4 hectares, and one statement takes at most 25 MB of GeoJSON.

No. This tool checks the file's format only. It doesn't check whether a plot was deforested after 31 December 2020, whether production was legal, or whether you comply, and it doesn't submit anything. It is independent and not made by the EU.

No. The file is read, checked and fixed in your browser and never leaves your computer.