How screening data can support later DDS preparation
A screening report isn't a filable Due Diligence Statement. Here's what carries over to TRACES NT, what doesn't, and why.
Prepare plot geometry for the EUDR Information System
The Commission's Information System supports GeoJSON for bulk geolocation upload (FAQ 7.26). This tool accepts CSV, Excel, or WKT-in-CSV for screening and provides a GeoJSON export as a starting point for that later step.
What this tool gives you
A GeoJSON download on your results page, using WGS-84 geometry and built from this report's field names.
What you still need to check
Treat this download as a starting point, not a ready-to-file upload. Validate the geometry, required metadata, and current Information System requirements before filing.
What carries over, and what doesn't
Three kinds of fields: ones that map directly onto a real TRACES/DDS requirement, ones that support your own Article 10/11 risk-assessment paperwork without being a TRACES field themselves, and one real format gap.
| This tool's field | Maps to | Notes |
|---|---|---|
| lat, lon | DIRECT Geolocation point (Art. 2(28)) | TRACES requires ≥6 decimal digits. Short values are silently zero-padded rather than rejected (FAQ 7.17), so check your own precision before filing; don't rely on the padding. |
| geometry_wkt | DIRECT, format gap Polygon (plots ≥4ha) | Plots ≥4ha (any commodity except cattle) legally require a perimeter polygon, not a center point plus radius (FAQ 1.16). This tool's WKT already carries that boundary, but needs converting to GeoJSON to actually file. |
| location_source = "geocoded" | CONTEXT Postal-address exemption (Art. 9(1)(h)) | The Commission allows micro/small primary operators to substitute a postal address for coordinates. This tool's geocoded-address path is the same idea, but for screening precision, not a substitute for the operator's own declaration. |
| country | DIRECT Country of production (per Production Place) | Each country of production must be its own separate "Production Place" entry in the DDS (FAQ 7.13), relevant if one shipment sources from more than one country. |
| flag, flag_reason | CONTEXT ONLY Not a TRACES field | RED/AMBER/GREEN is this tool's own risk-screening output, not something entered into TRACES. Keep it as evidence supporting your own Article 10 risk assessment; it isn't the assessment itself. |
| due_diligence_label, due_diligence_note | CONTEXT Country risk tier (Reg. 2025/1093) | Tells you whether simplified due diligence is even available for this origin, and which Article (10 full vs. 13 simplified) applies to your own filing. Not itself a TRACES data field. |
| nearby_pressure_tier, data_quality | CONTEXT ONLY Not a TRACES field | Supporting evidence for your own risk-assessment file (Art. 10/11 mitigating-factors documentation), not something TRACES asks for directly. |
| (bulk upload format) | PARTIAL GeoJSON-only requirement | The results-page GeoJSON preserves the submitted geometry, but it is not a completed DDS payload. Check it against the current Information System requirements and your own account before filing. |
Screening and filing are two different steps
This tool answers "where should I look harder?": a fast, cheap first pass across your supplier list. Filing a Due Diligence Statement is a separate, later step, with its own stricter format (GeoJSON, 6-decimal precision, polygon-only above 4ha) and its own legal weight.
Confusing the two is exactly the kind of gap that leaves an operator underprepared at the actual filing stage, so we'd rather tell you where the line sits than let you assume this report is the finish line.
See these fields populated for your own suppliers.
Request a screening