TraceBean validates, corrects, and converts supplier geo-data — CSV, GeoJSON, KML, Excel — into verified GeoJSON ready for EUDR submission. Farm-level error reports. Auto-correction where possible. Clear supplier instructions where human action is needed.
Every coffee importer preparing for EUDR faces the same upstream bottleneck: farm data arrives in inconsistent formats, with errors that block submission. The fix is manual, slow, and repeated with every supplier.
Swapped lat/lon, comma as decimal separator, degree/minute/second notation instead of decimal — silent failures that block submission.
Unclosed rings, self-intersections, degenerate vertices, point geometries where polygons are required for farms over 4 hectares.
Coordinates in UTM, Gauss-Krüger, or local CRS instead of WGS84 — the only coordinate system the EUDR Information System accepts.
Farm IDs with spaces, empty columns, non-standard tags in KML, mismatched column headers — every supplier uses different conventions.
The EUDR Information System accepts GeoJSON only. Suppliers send CSV, Excel, KML. Someone has to convert — and conversion is not validation.
Geo-data errors found inside a compliance tool, days before a shipment clears customs — after the coffee has already been pooled at the washing station.
Upload your supplier file — CSV, GeoJSON, KML, or Excel. Any format, any origin country.
TraceBean runs automated checks, fixes what it can, and flags what needs human follow-up.
A corrected file ready for your EUDR tool, plus a full error report showing exactly what was fixed.
The rest are flagged with clear instructions for supplier follow-up. Nothing slips through silently.
Decimal separator normalisationComma-to-period conversion in coordinate fields
Lat/Lon swap detection and correction8 coordinate permutations tested against country bounding box
CRS detection and reprojection17 coordinate systems supported — all output in WGS84 EPSG:4326
Decimal shift correction"15050505" → "15.050505" — missing decimal point auto-detected
Duplicate vertex removalThree tolerance levels — bit-exact, 1mm, 1cm — cleaned automatically
Polygon geometry validationUnclosed rings, self-intersections, degenerate geometry — all detected
Field name normalisationFuzzy matching — "AreaHectares", "area ha", "superficie" all resolved
KML tag normalisationNon-standard tags corrected to EUDR-compatible format
Country bounding box validationCoordinates verified against actual country boundary polygon — not just a rectangular bounding box
Area calculation and threshold check4-hectare threshold verified — polygon area calculated from geometry
Format conversion to GeoJSONCSV, Excel, KML converted to valid GeoJSON — the only format EUDR accepts
Empty field detectionMissing farm IDs, coordinates, or area values flagged with farm-level detail
Point geometry flaggingFarms >4ha with centroid-only data — actionable supplier message generated
Deforestation overlay checkFarm polygons verified against Hansen GFC rasters
Direct trade relationships with dozens of origins — each sending data in a different format. TraceBean standardises it all.
You know the regulation. You shouldn't spend your time fixing CSV files. TraceBean handles the data — you handle the strategy.
Coffee, cocoa, rubber, palm oil. TraceBean's validation logic applies across all EUDR-relevant commodities — one process, any origin.
No per-farm calculation. You know the cost upfront before committing. First test batch up to 100 farms — free.
Mixed batches — centroid and polygon farms in the same file are billed separately at the applicable rate for each type. One corrected file, one error report.
Unlimited batches within your plan's size limit, all year — no per-batch invoice, no recalculating cost every time a supplier sends a correction round.
All plans include the same auto-correction logic for unclosed rings, duplicate vertices, decimal shifts, lat/lon swaps and non-standard field names. Plan tiers differ in batch size limits and the depth of polygon-specific checks — never in basic data quality or reliability.
Send us one supplier file. We'll return a corrected file and error report within 24 hours. No commitment required for the first batch.