EUDR GeoJSON validator and converter

Check plot geolocation files against the rules of the EU Deforestation Regulation information system, fix common errors automatically, and turn KML, Excel, CSV or Shapefile data into an upload-ready GeoJSON file. Your files never leave your browser.

Free, no sign-up Runs in your browser, nothing is uploaded Updated 12 October 2026

Drop your plot files here

or

GeoJSON, KML or KMZ (Google Earth), Shapefile (.zip), Excel or CSV, GPX

Your files are read by your browser. Nothing is uploaded.

Templates: Excel/CSV template · GeoJSON example
Paste text instead

What the tool checks

The checks follow the European Commission's GeoJSON File Description for the EUDR information system (version of 17 August 2026), its API and UI validation rules, and the definition of geolocation in Article 2(28) of Regulation (EU) 2023/1115.

Rule of the EU systemWhat the tool does
Only Point, MultiPoint, Polygon and MultiPolygon geometries. LineString and MultiLineString are rejected.Turns lines that end where they start into polygons.
WGS 84 (EPSG:4326) coordinates in decimal degrees, in the order [longitude, latitude].Converts UTM and other declared coordinate systems, and spots swapped latitude and longitude.
Coordinates are cut to 6 decimals before storing. Points that differ only after the 6th decimal become duplicates and make the polygon invalid.Cuts coordinates exactly like the system and removes the duplicates.
Polygons need at least 4 positions and must be closed. No holes, no crossing or overlapping sides, no straight lines.Closes polygons, removes points that double back, cuts holes out, and marks crossings on the map.
Only four properties are read: ProducerName, ProducerCountry, ProductionPlace and Area. Names are case-sensitive and Area must be a number.Renames misspelled properties, converts text to numbers and fixes country codes.
A point without Area counts as 4 ha. A point may not stand for more than 4 ha (except for cattle) or less than 0.0001 ha.Flags points that need a polygon and areas out of range.
At most 25 MB of geolocation data per due diligence statement, 1,000 producers per commodity and 10,000 per statement.Shrinks the file, and splits it into parts of at most 25 MB if needed.

On top of the official rules, the tool checks that each plot lies in the declared ProducerCountry, flags plots in the sea, duplicate and overlapping plots, and an Area that does not match the polygon.

Polygon or point?

Article 2(28) of the regulation defines geolocation as latitude and longitude coordinates of at least one point, “using at least six decimal digits”. For plots of land of more than four hectares used to produce relevant commodities other than cattle, the geolocation must be a polygon “with sufficient latitude and longitude points to describe the perimeter of each plot of land”.

  • 4 ha or less: a single point is enough. Add the plot size as Area in hectares; without it the EU system assumes 4 ha.
  • More than 4 ha: a polygon that follows the boundary of the plot.
  • Cattle: the geolocation refers to the establishments where the cattle were kept, and points are allowed whatever the size.

The four properties the EU system reads

PropertyContent
ProducerNameName of the producer. Optional.
ProducerCountryTwo-letter ISO country code, for example BR, CI or ID. Required on every plot in a file with several producers.
ProductionPlaceName of the plot. Optional, but recommended.
AreaArea in hectares, written as a number: 3, not "3", which counts as 0.

All other properties are ignored. Spelling matters: productionplace or Producer_Name are not recognised.

Type I and Type II files

The EU system knows two variants with the same structure. A Type I file holds the plots of one producer and is used with the API and for import at producer level. A Type II file holds several producers and is used for import at commodity level: plots are grouped by ProducerName and ProducerCountry, and every plot needs a ProducerCountry. The tool detects the variant from the file, or you can choose it in the settings.

Converting from Google Earth, Excel, KoBoToolbox or GIS

  • Google Earth (KML or KMZ): draw each plot with the polygon tool, save the folder as KMZ and drop it here. The name of each placemark becomes the ProductionPlace.
  • Excel or CSV: one row per point with latitude and longitude columns; one plot per row with a WKT or KoBoToolbox geoshape column; or several rows per plot with a plot ID column, in the order of the boundary. Decimal commas and degrees, minutes and seconds are recognised. Start from the CSV template if you are collecting new data.
  • KoBoToolbox and ODK: export the form data as XLSX or CSV. Geoshape columns (“latitude longitude altitude accuracy;…”) are read directly.
  • Shapefile: upload the ZIP, or select the .shp, .dbf and .prj files together. Projected coordinates are converted with the .prj file.
  • GPS tracks (GPX): a track that comes back to its starting point becomes a polygon.

When the rules apply

After the amendment by Regulation (EU) 2025/2650, the obligations apply from 30 December 2026. For operators that are natural persons or micro or small undertakings established by 31 December 2024, they apply from 30 June 2027, except for timber products already covered by the EU Timber Regulation. Micro or small primary operators in countries classified as low risk submit a one-off simplified declaration and may give the postal address of the plots instead of their geolocation.

Your data stays on your computer

Plot boundaries and producer names are sensitive supply-chain data. This tool reads your files in the browser and uploads nothing. The map draws only the country borders that come with the page, without online map tiles, so no map service learns where your plots are.

What a valid file does not prove

Passing these checks means the file has the format the EU information system expects. It says nothing about deforestation or legality: due diligence still requires a risk assessment of the plots themselves, for example with satellite imagery.

Frequently asked questions

What file format does the EUDR information system accept?

GeoJSON as defined in RFC 7946, with WGS 84 longitude and latitude in decimal degrees. Geometries can be Point, MultiPoint, Polygon or MultiPolygon, and the system reads four properties: ProducerName, ProducerCountry, ProductionPlace and Area. All files of one due diligence statement together may not exceed 25 MB. See the Commission's GeoJSON File Description.

How many decimal places do EUDR coordinates need?

At least six, according to Article 2(28) of Regulation (EU) 2023/1115. Six decimals of a degree are about 10 cm. The information system cuts longer coordinates to six decimals before storing them, so more digits add nothing and can even create duplicate points.

When do I need a polygon instead of a point?

For every plot of land of more than 4 hectares used to produce a relevant commodity other than cattle. For plots of 4 hectares or less, one point is enough; give the size as Area in hectares, otherwise the system assumes 4 hectares.

Why does the EUDR system reject my polygon?

The most common reasons are a ring that is not closed, a hole inside the polygon, sides that cross or overlap, points that become duplicates when the system cuts the coordinates to six decimals, and LineString geometries instead of polygons. The tool finds all of these, fixes the ones that can be fixed safely and shows the others on the map.

How do I convert a Google Earth KML file to GeoJSON for the EUDR?

Save your plots in Google Earth as KML or KMZ and drop the file into the tool above. It converts the placemarks to GeoJSON, turns closed paths into polygons, uses each placemark's name as ProductionPlace and removes the styling information the EU system does not need.

What can I do if my GeoJSON file is larger than 25 MB?

First remove what the system does not use: digits after the sixth decimal, altitude values and extra properties. The tool does this automatically. If the file is still too large, use single points for plots of 4 hectares or less, remove points that only continue a straight line, or spread the plots over several due diligence statements. The tool can split the file into parts of at most 25 MB.

What is the difference between Type I and Type II GeoJSON files?

Both have the same structure. Type I contains the plots of one producer and is used with the API or for import at producer level. Type II contains several producers and is used for import at commodity level; the plots are grouped by ProducerName and ProducerCountry, and every plot must have a ProducerCountry.

Are my files uploaded anywhere?

No. The files are read and checked in your browser, and the fixed file is created there too. The map uses country borders that come with the page instead of online map tiles, so your plot locations are not sent to any map service either.