plots.geojson
One file in the format the EU Information System asks for, ready to attach to your due diligence statement.
{ "ProducerCountry": "CI",
"ProductionPlace": "C-14",
"Area": 1.8 }
Point [-5.451100, 6.881200]
EUDR applies to large and medium operators from 30 Dec 2026
EUDR geolocation files, fixed overnight.
Send the spreadsheets, KML files and Kobo exports your suppliers sent. You get back one GeoJSON file built to the EU Information System's published rules, and a list of exactly which plots each supplier still has to fix.
- No account needed
- Results within 24 hours on working days
- Files deleted within 30 days
| plot | lat | lon | ha | shape | result |
|---|---|---|---|---|---|
| C-14 | 6.881200 | -5.451100 | 1.8 | point | Correctedlat/lon swapped |
| C-15 | 6.133333 | -5.950000 | 2.4 | point | CorrectedDMS converted |
| C-16 | 6.741200 | -7.350300 | 3.1 | point | Correcteddecimal commas |
| C-17 | 6.902100 | -5.388400 | 6.2 | point | Needs supplierover 4 ha, no boundary |
| C-18 | 6.874900 | -5.462300 | 5.6 | polygon ✓ | Correctedcrossing boundary repaired |
| C-19 | 6.875200 | -5.461900 | 4.9 | polygon | Reviewoverlaps C-18 by 30% |
4corrected
1to review
1need the supplier
Example data. A batch can be thousands of plots.
Send what your suppliers sent
- Excel (.xlsx, .xls)
- CSV, any separator
- KML / KMZ
- GPX tracks
- Zipped shapefiles
- KoboToolbox / ODK
- GeoJSON
Coordinates in decimal degrees, degrees-minutes-seconds, decimal commas, UTM metres, Google Maps links or WKT. Title rows above the header and mixed encodings are fine.
What comes back
Three files. One to upload, two to act on.
A plain-language report
What was corrected automatically, what to double-check, and which plots must go back to which supplier, with the reason.
Coop Sinfra · C-17Needs supplier
Coop Daloa · C-19Review
Coop Daloa · C-14Corrected
A traceable index
Every plot in the output mapped back to the file and row it came from, so any question has an answer.
feature 0 → coop_export.xlsx row 14 feature 1 → coop_export.xlsx row 15 feature 7 → walks_june.gpx track 3
How it works
From upload to statement in a working day.
Upload
Send the files and tell me the commodity and producer country.
Processing
I run them through geofix on my own machine. Nothing goes to any third-party processing service.
- within 24 hours, working days
Delivery
You get the three files and, after the free first batch, an invoice.
Submission
You attach plots.geojson to your statement. If it's rejected, send me the message and I fix it at no charge.
Sample report
See exactly what you'd get back.
The full report from a fictional batch: fifteen plots from three typical file types, one of them a 6-hectare plot recorded as a single point.
Plot location check
Sample · fictional data15plots received
14ready to submit
14corrected automatically
1with warnings
1need the supplier
Needs the supplier (not included in the output)
EUCHK-D-001Plot over 4 ha given as a single point. Ask the supplier for the boundary.Scope
What gets fixed, and what doesn't.
Coordinates
- Latitude and longitude swapped
- Degrees-minutes-seconds and decimal commas
- UTM metres reprojected
- Altitude and excess precision removed
Boundaries
- Self-crossing shapes repaired
- Unclosed rings closed
- Holes split into separate plots
- Walked GPS tracks closed, flagged to confirm
Technical details
File rules
- EPSG:4326, longitude first, 2D only
- Duplicate and collinear vertices removed
- Property names set to the EU schema
- Missing country codes filled when you give the country
Size
- Statements over the 25 MB limit split or simplified
- Any area change over 1% flagged
- Geometry kept valid after rounding to 6 decimals
For customs brokers and forwarders
Handling EUDR for several importers?
I can be the back office for the geolocation part: one contact, the same output format for every client, and volume terms.
Pricing
Start free. Pay per plot after that.
First batch
Free
One batch from one supplier set, full output and report. No card, no account.
After that
Per plot
Quoted before I start, based on the number of plots. No subscription.
Brokers
Volume terms
For files from several importers, agreed once and applied to every batch.
Who you're dealing with
Aleksi Svanidze
I'm a software engineer based in Tbilisi, Georgia. I build data and systems tooling, and I built geofix because the EU rules for geolocation files are precise and the files that arrive from supply chains rarely are. You deal with me directly.
Data handling
- StorageEU (Cloudflare R2, EU jurisdiction)
- ProcessingOn my own computer in Georgia
- RetentionDeleted within 30 days
- Used forYour batch only
- AgreementData processing agreement on request
Questions
Before you send anything.
Is this an official EU tool?
No. It's an independent service. The output is built to the GeoJSON rules the EU Information System publishes, and if a file is still rejected, I fix it at no charge.
When does EUDR apply?
From 30 December 2026 for large and medium companies, and from 30 June 2027 for micro and small companies.
What happens to plots that can't be fixed?
They're left out of plots.geojson and listed by supplier with the reason, for example a plot over 4 hectares recorded only as a point. You know exactly what to ask each supplier for.
My supplier files have no plot IDs. Is that a problem?
No. Plots get an ID from their file and row, and the index maps every one back to where it came from. Real IDs from suppliers make follow-up easier.
Where does my data go?
Uploads are stored in the EU and deleted within 30 days. Files are processed on my own computer in Georgia and used only for your batch. A data processing agreement is available on request.
Do you check deforestation risk?
No. I fix the format and geometry of the location data. Risk assessment is a separate step.
How large can a batch be?
Up to 20 files of 200 MB each per upload. Larger batches by arrangement. Statements over the EU's 25 MB geolocation limit are split or simplified, with any area change flagged.
EUDR applies from 30 December 2026