Why did TRACES reject my GeoJSON?

The most common causes are: coordinates with fewer than 6 decimal places, longitude and latitude swapped, a plot over 4 hectares submitted as a single point instead of a polygon, an unclosed or self-intersecting polygon ring, or a non-WGS-84 coordinate system. This validator flags each of these with a specific fix.

What file formats can I check?

This page validates GeoJSON (a FeatureCollection, Feature, or bare geometry). If your data is in CSV, KML/KMZ, shapefile or WKT, use the converter to turn it into EUDR-compliant GeoJSON first.

How precise do coordinates need to be?

EUDR requires WGS-84 latitude/longitude with at least 6 decimal places. Fewer decimals will be rejected.

When is a point acceptable instead of a polygon?

A single point is only valid for plots of 4 hectares or less. Larger plots must be described by a boundary polygon.

EUDR GeoJSON validator

Paste or upload your plot geolocation file. We check it against the EUDR geolocation rules and explain exactly what to fix — the same errors that get files rejected by TRACES / the EUDR Information System. Everything runs in your browser; your coordinates are never uploaded.

or paste below

🔒 Your file is validated entirely in your browser — nothing is uploaded to any server.

What this validator checks

failValid JSON
The file must be syntactically valid JSON.
failValid GeoJSON (RFC 7946)
Must be a GeoJSON FeatureCollection, Feature, or Geometry with a recognised type.
failCoordinate system is WGS-84 / CRS84
RFC 7946 GeoJSON is always WGS-84 with [lon, lat] order. A named CRS other than CRS84 is not allowed.
warnLongitude/latitude order looks correct
Detects the common lat/long swap by checking coordinate plausibility and ranges.
failAt least 6 decimal places
Coordinates must carry ≥ 6 decimal places.
failPoint vs polygon (4 ha rule)
Plots > 4 ha must be a Polygon; a Point is only valid for plots ≤ 4 ha.
failPolygon rings are closed
Each linear ring must start and end at the same position and have ≥ 4 positions.
failPolygon has no self-intersections
The boundary must not cross itself (a common cause of TRACES rejection).
warnNo duplicate/degenerate vertices
Consecutive identical vertices or zero-area geometry indicate a malformed plot.
warnNo polygon holes (interior rings)
The EUDR Information System ignores holes (interior rings) and reads only the outer boundary.
warnProducerCountry present
The EUDR GeoJSON format expects a ProducerCountry property (ISO 3166-1 alpha-2 code) on each plot.
warnLocation is plausible
Flags null-island (0,0), out-of-range values, and other implausible coordinates.

Frequently asked questions

Why did TRACES reject my GeoJSON?: The most common causes are: coordinates with fewer than 6 decimal places, longitude and latitude swapped, a plot over 4 hectares submitted as a single point instead of a polygon, an unclosed or self-intersecting polygon ring, or a non-WGS-84 coordinate system. This validator flags each of these with a specific fix.
What file formats can I check?: This page validates GeoJSON (a FeatureCollection, Feature, or bare geometry). If your data is in CSV, KML/KMZ, shapefile or WKT, use the converter to turn it into EUDR-compliant GeoJSON first.
How precise do coordinates need to be?: EUDR requires WGS-84 latitude/longitude with at least 6 decimal places. Fewer decimals will be rejected.
When is a point acceptable instead of a polygon?: A single point is only valid for plots of 4 hectares or less. Larger plots must be described by a boundary polygon.