The EU Information System rejects due diligence statements when the GeoJSON file breaks the Commission’s rules, for example with open outlines, holes in polygons or points above four hectares. The checker reads your file in the browser and shows for each plot what the system would reject, what is risky and how to fix it. Your file never leaves your computer.
It is based on the Commission’s GeoJSON file description with its list of common errors, the validation rules and the interface description of the Information System, the user guide, the Commission FAQ and the Regulation itself. Each rule has one of three levels:
| Area of the check | What is checked |
|---|---|
| File | format (no PDF, ZIP, KML or CSV), extension, UTF-8, JSON syntax with line and column, size up to 25 MB |
| Structure | FeatureCollection and features, permitted geometry types, nesting, numbers instead of text, WGS84 reference system |
| Coordinates | value range, swapped axes (where the latitude then exceeds 90 degrees), metres instead of degrees, at least six decimal places, decimal comma, Null Island |
| Polygons | no holes, closed outline, at least four points, no duplicate points after truncation to six decimal places, no straight line, no self-intersection, parts of a MultiPolygon that overlap or share an edge, antimeridian, circular outlines |
| Area | point above 4 ha, Area missing or written as text, minimum area, Area against calculated area (acres, square metres) |
| Properties | spelling of ProducerName, ProducerCountry, ProductionPlace and Area, ISO country code, several countries in one file, number of producers |
| Duplicates | identical plots, points with identical coordinates (collection point), overlaps, points inside another plot’s polygon |
Not checked: freedom from deforestation and legality, both part of the risk assessment, whether a polygon covers exactly one plot, whether a point lies in the stated country of production, and whether longitude and latitude are swapped while both values stay within the valid range (that takes a match against the country of production). Where the Commission’s documents contradict each other, such as on the minimum area for points (0.1 ha in the user guide, 0.0001 ha in the validation rules), the report gives both.
Sources: Regulation (EU) 2023/1115, Commission GeoJSON file description (17 August 2026), API and UI validation rules, Operator API Reference V3, Information System user guide, version 3.0, Commission FAQ.
The checker runs entirely in your browser. The file is not uploaded, not stored and not sent to anyone; the tool loads no libraries and no map services, and the map sketch is drawn from your own coordinates. Close the page and everything is gone. For smallholders, ProducerName is often a person’s name, one more reason why the file stays on your computer. Only if you have accepted analytics in the cookie banner does Google Analytics count whether a check found errors, roughly how many plots it covered and which rules applied, never file names, names or coordinates.
Then the checker found no breach of the Commission’s published rules. That is no guarantee for the upload: by their own account, the validation rules do not describe every check the system runs. And the checker does not check whether the plots were deforested after 31 December 2020; that belongs in the risk assessment.
Article 2(28) of the Regulation requires coordinates with at least six decimal digits. According to FAQ 7.17 of the Commission, the Information System pads shorter values with zeros and accepts the file. The precision, however, stays that of your data, about 11 metres with four decimal places. That is why the checker reports a warning. Because many programs drop trailing zeros (6.140880 becomes 6.14088), it only warns about single points with five decimal places if the file as a whole looks like shorter coordinates.
The Commission’s documents contradict each other: the validation rules of the Information System require at least 0.0001 hectares, the user guide in version 3.0 says 0.1 hectares. The checker reports values below 0.0001 ha as errors and values below 0.1 ha as warnings. Test such plots in the acceptance environment first.
For polygons on the WGS84 ellipsoid, using the equal-area projection with authalic latitude. The Area values in the Commission’s examples match a sphere with a radius of 6,378,137 metres instead; the difference is below one per cent, and the report shows both values. For points the value in Area counts, because the GeoJSON file description only provides Area for points.
The Information System only accepts GeoJSON. The script in our EUDR geodata pack converts a CSV table to GeoJSON; the pack, templates and instructions are in the article on geodata from suppliers. Save an Excel sheet as CSV first.
No. The checker reads the file in the browser, sends it to no server and stores nothing, not even in the browser. You save the report yourself as CSV or as PDF through the print function.
What to request from suppliers, when a point is enough and which errors the Commission lists is covered in the article Geodata from suppliers for the EUDR, with templates in CSV and GeoJSON. Whether you need geodata at all, the EUDR check tells you in two minutes.
To try it out: example file without errors and example file with errors (GeoJSON, fictitious plots in Côte d'Ivoire).
Your suppliers enter their plots themselves through a portal without login, as coordinates or as polygons. Polygon One shows every plot on the map and flags anything that is missing or does not add up.
A no-obligation 30-minute call. We’ll show you the platform, discuss your supply chain and give you a transparent quote.
Or email us directly: a.ruetjes@polygon-one.com
The calendar is provided by HubSpot (Ireland) and sets cookies. Google Analytics and Leadfeeder stay off.