TRACES rejected your geolocation file? Fix it in 60 seconds.
Geolocation is the number one reason an EUDR due diligence statement stalls. TRACES returns a cryptic error and you are left guessing. Paste your GeoJSON or a CSV of coordinates below. We tell you exactly what TRACES will object to, then repair the file for you and hand it back clean.
Validation is free, unlimited in practice, and needs no account. The repaired download asks for an email so we can send you the change log. The first repair on an email is free.
Validate and fix your plot file
GeoJSON, a bare geometry, or a CSV with latitude and longitude columns. Nothing you paste leaves this page except the request to check it.
How it works
Three steps. No GIS specialist, no back and forth with the help desk.
Paste or upload
Drop in the exact GeoJSON TRACES rejected, or a CSV export of your plot coordinates. We convert the CSV into plot points for you.
See the real reason
Every problem comes back with a stable rule ID, a plain explanation, and the matching reason TRACES gives, so you know precisely what to change.
Download the fixed file
We repair what can be repaired safely and give you a clean file plus a per plot change log. Anything we cannot invent for you is listed clearly.
Why pay when free validators exist?
Free validators tell you what is wrong and stop there. You still have to open the file and fix every plot by hand. This does the repair, and it does it in bulk.
| What you need | Free validator | EUDR GeoCheck |
|---|---|---|
| Find the errors | Yes, that is all it does. | Yes, with the exact TRACES reason for each one. |
| Actually repair the file | No. You edit every plot yourself. | Rounds precision, closes rings, removes duplicate points, repairs self-intersections, corrects winding, strips a bad CRS. |
| A record of what changed | Nothing to show. | A per plot change log, and a flag whenever a repair moved a plot area by more than a whisker. |
| Whole batches at once | One file, one look. | Batch a folder of plots and get one clean file back. |
| Wire it into your own flow | Copy and paste only. | A simple API for per shipment volume, so every statement is checked before it reaches TRACES. |
What the fixer repairs
Deterministic repairs only. We never guess a producer name, an area, or a projection you did not give us.
Precision and rings
Rounds coordinates to 6 decimals, closes open rings, and removes duplicate consecutive vertices.
Invalid shapes
Repairs self-intersecting polygons with a topology safe method and flags any plot whose area moved during the repair.
CRS and winding
Strips a wrong coordinate system declaration and corrects ring winding to the right-hand rule the standard expects.
Simple pricing
Validation is free forever, and your first repaired file is free too, on any email. After that you need the Fix plan, and here is the honest part: you cannot buy it yet. There is no card form and no countdown. Ask for a second repair and we put your email on the list, then write to you the day it opens.
Free
- Validate any file
- Every rule ID and TRACES reason
- CSV to plot conversion
- One repaired file per email
- No account needed
Fix
- Everything in Free
- Repair as many files as you need
- Per plot change log
- Batch a folder of plots (planned)
- API key for per shipment checks (planned)
Team
- Everything in Fix
- Higher volume and rate limits
- Priority support
- Invoicing
Honest answers
The questions operators actually ask before they trust a tool with a submission.
Does this guarantee TRACES acceptance?
No, and be careful of any tool that says it does. We implement the checks in the published EUDR GeoJSON File Description version 1.5 and repair what is deterministic. TRACES can add checks, and your submission also depends on data you provide that no file tool can verify. This is not legal advice.
What exactly do you fix?
Coordinate precision, unclosed rings, duplicate vertices, self-intersecting polygons, ring winding, and a wrong coordinate system declaration. We wrap a bare geometry into a proper collection. We do not invent missing producer details or a plot area, because guessing those would be worse than telling you they are missing.
Can it handle a point instead of a polygon?
Yes. A point is allowed only for a plot below 4 hectares and it must carry an area. We flag a point that has no area, and a point that claims 4 hectares or more, because TRACES wants a polygon for those.
My coordinates are in a CSV, not GeoJSON.
Paste the CSV or upload it. As long as there is a latitude and a longitude column we build the plot points for you, then validate and fix them like any other file.
Do you keep my plot data?
The validator does not store your file. When you ask for a fixed download we record the email you enter so we can send you the change log and reach you about the service. You can ask us to delete it at any time.
How many files can I repair for free?
One per email address. Validation stays free and you can run it as often as you like. The repair is the part we intend to charge for, and the first one is on us so you can read the change log before deciding anything. There is no way to pay yet. If you need a second repair right now, write to the address in our terms and we will sort it out.
What are the deadlines again?
Large and medium operators must comply from 30 December 2026. Micro and small operators have until 30 June 2027. Geolocation of every plot is required from the start, so it is worth getting the file right early.