The location attachment TRACES reads, built from a clean batch.
The EUDR Information System reads a geolocation file with a small, fixed set of properties. We build that file only after every plot in your batch is technically clean and you confirm nothing is missing.
What this file is
A geolocation attachment
One compact GeoJSON FeatureCollection per due diligence statement, in the shape TRACES' GeoJSON File Description v1.5 reads.
Built from a checked batch
Every plot must pass the technical check without a repair before the file can be created.
Yours to upload
You download the file and upload it in TRACES yourself, within the batch you reviewed.
What this file is not
Not a due diligence statement
The DDS itself, its commodity form and Article 9 fields stay in TRACES, not in this file.
Not a TRACES submission of this file
Origin Diligence does not upload this geolocation file for you. A separate filings page can transmit a due diligence statement using your own TRACES credentials. You remain the operator; we are not your authorised representative.
Not a compliance decision
Creating the file does not decide whether your organisation meets EUDR requirements.
What goes into the file
Only the properties TRACES defines for a geolocation attachment, and nothing else.
ProducerNameThe producer's name, required on every plot.
ProducerCountryAn ISO 3166-1 alpha-2 country code, resolved automatically from the country you recorded.
ProductionPlaceA short label for the production place.
AreaThe declared area in hectares, required on point plots and left out of polygons.
Before you can create the file
- Every plot in the batch passed the technical check without needing an automatic repair.
- You name one operator or importer, who remains the EUDR operator.
- You confirm every producer file for the statement is uploaded, and no producer or plot is missing.