Home / Convert a CSV of coordinates to EUDR GeoJSON
Geolocation due 30 December 2026 for large and medium operators, 30 June 2027 for micro and small

Convert a CSV of coordinates to EUDR GeoJSON

Most plot coordinates start life in a spreadsheet, not a GeoJSON. TRACES wants GeoJSON. Here is how to bridge that gap cleanly, without hand-writing brackets and worrying about coordinate order.

Suppliers send coordinates the way they have them: a CSV with a column for latitude and a column for longitude, one row per plot. That is perfectly reasonable data, it is just the wrong container. TRACES needs a GeoJSON FeatureCollection, and converting by hand is error prone, especially the longitude and latitude order.

What a usable CSV looks like

  • A latitude column and a longitude column, however they are labelled.
  • One row per plot (a point), or grouped rows for a polygon boundary.
  • Optionally, producer name, producer country, and area columns to carry into the properties.

The conversion pitfalls

  • Order. GeoJSON is longitude, latitude. Spreadsheets often list latitude first. Swap them and every plot lands in the wrong place.
  • Precision. Coordinates should sit at about 6 decimals. Truncated or over-long values cause warnings.
  • Missing area. A point plot needs an Area to be valid, so an area column saves a round of rejections.
Paste the CSV or upload it. As long as there is a latitude and a longitude column, the tool builds the plot features for you, then validates and repairs them like any other file.

From CSV to a submittable file in one pass

The clean path is: paste the CSV, let the tool convert it to GeoJSON features, read the validation, and download the repaired file. You go from a spreadsheet a supplier emailed you to a file TRACES will accept, without touching a GIS program.

For large supplier lists

A CSV with thousands of rows converts the same way, and batch handling means you get one clean GeoJSON back rather than assembling it plot by plot.

Common questions

My coordinates are latitude first. Is that a problem?

GeoJSON expects longitude first. The tool handles the conversion, but doing it by hand with latitude first is a classic way to misplace every plot.

Can I include producer details from the CSV?

Yes. Producer name, country, and area columns can be carried into the plot properties, which reduces missing-property warnings.

Turn your CSV into a clean GeoJSON

Paste a CSV of coordinates and get a validated, repaired EUDR GeoJSON ready for TRACES.

Fix my file

Related guides