Find geometry issues before they block preparation
Validate GeoJSON against the geometry rules the EUDR Information System expects: geometry types, coordinate order and ranges, polygon closure, holes, self-intersection and 6-decimal precision.
Files are processed locally in your browser and are not sent to EudrFlow servers. Passing this validator does not guarantee official system acceptance.
Frequently asked questions
What does this EUDR GeoJSON validator check?
It parses your file as JSON, requires a Feature or FeatureCollection root, checks geometry types (Point, MultiPoint, Polygon, MultiPolygon, GeometryCollection), validates coordinate order and ranges ([longitude, latitude], lon -180..180, lat -90..90), checks polygon ring size, closure, holes and obvious self-intersections, and flags coordinate precision beyond 6 decimal places.
What does it not check?
It does not verify that coordinates match a real farm, that a plot is deforestation-free, or that your data meets any legal requirement. It checks structure and format only — not legal compliance and not official system acceptance.
Which geometry types are supported?
Point, MultiPoint, Polygon, MultiPolygon and GeometryCollection are supported, matching the geometry types the EUDR Information System accepts for production places. LineString and MultiLineString are explicitly rejected.
Does passing this validator guarantee EUDR acceptance?
No. Passing means the file is structurally valid against the checks listed above. The official system may apply additional rules, and acceptance is never guaranteed by a third-party tool.
What coordinate system should I use?
Use WGS 84 (EPSG:4326) decimal degrees, with positions ordered as [longitude, latitude]. GeoJSON does not carry per-file CRS overrides for EUDR purposes.
Are uploaded files sent to a server?
No. Files are parsed and validated locally in your browser. Nothing is uploaded to EudrFlow servers, and file contents are never sent to analytics.