Validate your GeoJSON for TRACES
Upload the plot file your supplier sent you and we tell you, plot by plot, what TRACES would reject and how to fix it. No sign-up.
Which files it accepts
- GeoJSON (.geojson or .json): one Feature per plot, as TRACES expects.
- KML from Google Earth: each placemark or polygon is a plot. If you have a KMZ, unzip it and upload the KML inside.
- CSV with latitude and longitude columns (one point per row) or a WKT column with the polygon. Optional columns: name, country, producer and area.
Frequently asked questions
What does it check?
The rules TRACES uses to reject or correct a file: WGS84 coordinates in longitude, latitude order; closed polygons with no holes and no crossings; only points, polygons and multipolygons; a two-letter country code; the size limit per DDS. And what the Regulation asks for: 6 decimal places and a polygon above 4 ha (Art. 2(28)).
Do you keep the file?
No. It is read in memory, the report is built and the file is discarded. The CSV of the report is made in your browser.
What if everything passes?
It means the geolocation has the shape TRACES expects. It says nothing about deforestation after 31 December 2020: that is checked with satellite imagery and is part of the risk assessment.