Home / The EUDR GeoJSON format, explained
Geolocation due 30 December 2026 for large and medium operators, 30 June 2027 for micro and small

The EUDR GeoJSON format, explained

TRACES expects your plot geolocation as GeoJSON in a specific shape. Get the structure wrong and it is rejected before a single plot is checked. Here is exactly what the format asks for.

The EU published a GeoJSON File Description for EUDR geolocation, currently version 1.5. It defines how every plot in your due diligence statement must be described. Most rejections are not about your land, they are about the file not matching this shape. Fix the shape and the rest follows.

The top level: a FeatureCollection of plots

The whole file is one GeoJSON FeatureCollection. Each plot of land is one Feature inside it, with a geometry and a set of properties. A bare geometry, an array, or anything that is not a FeatureCollection is rejected at the door.

{"type":"FeatureCollection","features":[
  {"type":"Feature",
   "properties":{"ProducerName":"Farm A","ProducerCountry":"BR","Area":2.4},
   "geometry":{"type":"Polygon","coordinates":[[[-51.1,-10.1], ... ]]}}
]}

Geometry: Point, Polygon, or MultiPolygon

Only three geometry types are allowed: Point, Polygon, and MultiPolygon. A point is permitted only for a plot below 4 hectares and it must carry an Area. Anything 4 hectares or larger needs a polygon.

Coordinates: WGS84, longitude then latitude, 6 decimals

  • WGS84 (EPSG:4326). Degrees of longitude and latitude, not a projected national grid. Projected coordinates are rejected.
  • Order. Longitude first, then latitude, as GeoJSON requires. Swapping them puts your plot in the wrong hemisphere.
  • Precision. About 6 decimal places. More is unnecessary and can be flagged, fewer places the plot imprecisely.

Polygon rules that trip people up

A polygon ring must be closed (the last coordinate equals the first), have at least 4 positions, not self-intersect, and follow the right-hand winding rule (exterior ring counter-clockwise). These four are the most common silent rejections.

A validator finds these. A fixer closes the ring, rounds the precision, repairs the self-intersection, and corrects the winding for you, then hands back a clean file.

Properties TRACES expects

Each plot should carry a producer name, a producer country as an ISO 3166-1 alpha-2 code (for example BR or CI), a description, and an Area for point plots. Missing these is usually a warning rather than a hard block, but a clean submission includes them.

Common questions

What version of the format should I follow?

The current EUDR GeoJSON File Description is version 1.5. Our checks implement that version.

Longitude or latitude first?

Longitude first, then latitude, as the GeoJSON specification requires. This is a frequent source of misplaced plots.

Check your GeoJSON against v1.5 free

Paste your file and see exactly where it departs from the format, then let the fixer repair it in 60 seconds.

Fix my file