File preparation · Local check
EUDR GeoJSON validator: what needs fixing in your file?
Check coordinates, polygon rings and selected import properties before trying the EUDR Information System. Each finding points to the affected part of your JSON and explains what to review.
Check your file
Check the file and preview its locations in your browser. No account or file upload. An optional online basemap is available after checking, with a separate privacy notice.
Up to 5 MB for this local check. Or paste your JSON below.
What does a passing check mean?
It means no problems were found within the checks listed below. GeoJSON structure and the selected EUDR import format are separate: for example, a polygon with a hole can be valid GeoJSON but unsuitable for the documented EUDR import. Each finding explains the applicable check.
The map displays the coordinates you supplied. It helps you inspect their position against mapped borders and coastlines; it does not automatically verify country or land coverage. Checking whether the declaration reflects actual production is outside this tool’s scope. We do not submit statements on your behalf.
Choose the format you intend to import
The Commission describes Type I for producer-level import and API use, and Type II for commodity-level import with producer properties on each Feature. Select the intended route before checking. This tool checks a documented subset; it does not reproduce every TRACES validation.
If you are still deciding what to ask suppliers for, the point and polygon requirements explain which locations you need. A file check cannot reconstruct missing land boundaries.
What the validator checks
JSON and geometry structure
Checks recognised object types and coordinate nesting. Lines and null geometries are not accepted as production locations in this check. Generic GeoJSON validity alone is not enough for the EUDR import.
Commission GeoJSON specificationCoordinate order and ranges
Checks finite numbers, longitude within ±180 and latitude within ±90. Cannot prove the CRS, actual location or correct axis order when both values are in range.
Commission GeoJSON specificationPolygon boundaries
Checks closure, distinct vertices, zero-length edges, zero signed area and non-adjacent intersections for bounded rings. Holes are flagged because the Commission documents them as unsupported. Does not check overlaps between different polygons or certify survey boundaries.
Commission GeoJSON specificationImport properties
Type II needs ProducerCountry per Feature. This check verifies the two-uppercase-letter shape, not membership in the system’s country list or whether the geometry lies in that country. Recognised name fields must be text; Area must be a positive number. Type I properties are optional.
Commission GeoJSON specificationPoints and plot area
With non-cattle selected, a Point carrying Area above 4 ha is flagged because the plot needs a polygon. MultiPoint requires manual review of each plot’s area. Commodity and actual area cannot be inferred from coordinates.
Regulation: Article 2(28)Stored coordinate precision
Flags adjacent polygon vertices that would collapse when truncated to six decimals. Does not reject missing trailing zeros or rewrite your geometry. Other precision-related changes may need GIS review.
Commission GeoJSON specificationLimits of this local check
Up to 5 MB of UTF-8 JSON; bounded traversal and topology work protect browser responsiveness. Large rings, antimeridian crossings and reporting limits are explicitly marked incomplete. The local 5 MB cap is not the Commission’s submission-size rule.
Local processing boundaryA clean result is not an accepted DDS
This tool does not check deforestation, legality, ownership, country boundaries, missing plots, all optional GeoJSON members or a complete DDS payload. It does not calculate plot area, validate identifiers or send a request to TRACES. Confirm the geometry against your source records and test the intended import in acceptance.
Your original content is never repaired automatically. When the file is ready, keep it associated with the relevant product in the DDS preparation workbook. Submission results and issued reference numbers are a separate step.
Want these checks built into your workflow?
Share how supplier files reach your team and what happens after a check fails. We can help scope automated validation, clear exception handling and a record of each result within your existing process.
Talk to us about your workflowOur EUDR submission implementation shows where validation fits into the wider process.
Rules reviewed 6 September 2026 against Commission GeoJSON guidance updated 17 August 2026 and RFC 7946. Files and pasted text are processed in memory, with no upload or persistent storage by this tool. The optional OpenStreetMap basemap requests tiles for the viewed area only after you enable it.