EUDR Plot File Fixer: GeoJSON validator and auto-repair
Pricing
from $10.00 / 1,000 plot processeds
EUDR Plot File Fixer: GeoJSON validator and auto-repair
EUDR geolocation file rejected? Upload GeoJSON, KML, CSV or Shapefile plots and get back a file that follows the EU Information System rules, with a report of every fix: broken polygons, holes, swapped coordinates, metres, country codes, area. KML to GeoJSON too. About $10 per 1,000 plots.
Pricing
from $10.00 / 1,000 plot processeds
Rating
0.0
(0)
Developer
Ghulam Nabi
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
3 hours ago
Last modified
Categories
Share
Did the EU system reject your EUDR geolocation file? Upload it here. In seconds you get back a GeoJSON file that follows the EU Deforestation Regulation (EUDR) Information System rules, plus a plain-language list of every change.
- ✅ Fixes the mistakes that get plot files rejected: broken or self-intersecting polygons, holes, swapped latitude and longitude, coordinates in metres, wrong property names, country names instead of ISO codes, area written as text
- 📂 Reads the files suppliers actually send: GeoJSON, KML/KMZ (Google Earth), CSV and zipped Shapefiles
- 🔒 Never guesses: a plot it can't fix safely is set aside with the reason, so you can ask the supplier
- 💵 Pay per plot, no subscription: about $10 for a 1,000-plot cooperative file, $0.50 for a 50-plot test
Why now: EUDR obligations apply from 30 December 2026 for large and medium companies, and from 30 June 2027 for most micro and small companies. Every due diligence statement needs the geolocation of every plot, and files from farms and cooperatives are often full of errors.
Built for EU importers, exporters, cooperatives, traders and compliance teams handling cocoa, coffee, palm oil, rubber, soy, cattle and wood.
What does EUDR Plot File Fixer do?
It reads your plot file, repairs every mistake that can be repaired safely, and tells you exactly what it changed. Plots that need a human are never silently altered: they're listed separately with the reason.
| Common problem in supplier files | What the fixer does |
|---|---|
| Self-intersecting ("bow-tie") polygons | Rebuilds a valid shape and reports any change in area |
| Polygon not closed, clockwise ring, repeated points | Closes the ring, turns it counter-clockwise, removes repeats |
| Holes inside polygons (not accepted by the EU system) | Opens each hole to the edge with a 30 cm channel; the hole stays excluded |
| Longitude and latitude in the wrong order | Swaps them when the order is certain, warns when it isn't |
| Coordinates in metres (UTM etc.) | Converts to WGS 84 using the Shapefile .prj, the GeoJSON crs, or the system you enter |
| Decimal commas, numbers as text, degrees-minutes-seconds, 3D heights | Converts to clean decimal degrees |
| Points that collapse at 6 decimals, duplicate plots | Merges or removes them |
Wrong property names (farmer, country, hectares, area_m2, acres...) | Renames to ProducerName, ProducerCountry, ProductionPlace, Area |
| Country names or 3-letter codes | Converts to ISO 2-letter codes (Ghana → GH, IDN → ID) |
| Area written as text ("2,5", "3 ha", "1.234,5") or in m²/acres | Converts to a number in hectares |
| More than 1,000 plots | Splits into files of up to 1,000 plots, under 25 MB |
What it will not guess
These plots go to needs_attention.geojson with a clear reason, so you can fix them at the source:
- A point with an Area over 4 ha (plots over 4 ha must be mapped as polygons; cattle excepted)
- Coordinates in metres with no known coordinate system
- Open GPS tracks, shapes with no area, unreadable geometry
It also warns about low GPS precision, points without Area (the EU system treats them as 4 ha), overlapping plots, a declared Area that doesn't match the mapped area, and points at 0,0.
How to use it
- Click Try for free.
- Paste a download link to your file in Plot file links, or paste GeoJSON, CSV or KML text.
- If your file is in metres and has no coordinate system, enter it (for example
EPSG:32630). - Click Start. Most files finish in seconds.
- Download
eudr_ready.geojsonfrom the Output or Storage tab and upload it to the EU Information System.
The input form comes pre-filled with a small example full of typical mistakes, so you can see the repairs straight away.
Input formats
- GeoJSON: FeatureCollection, Feature, a bare geometry or GeometryCollection
- KML / KMZ: from Google Earth or field apps; placemark names become
ProductionPlace - CSV: latitude and longitude columns, a WKT column, a single "lat, lon" column, or one row per corner with the same
plot_idfor polygons. Comma or semicolon separated; decimal commas understood. - Shapefile: zipped
.shp,.shx,.dbf(+.prjfor the coordinate system)
Output
| Output | What it is |
|---|---|
eudr_ready.geojson (or numbered parts) | Ready to upload to the EU Information System |
needs_attention.geojson | Plots that need a person, each with _eudr_errors explaining why |
| Dataset (table) | One row per plot: status, repairs, warnings, area in hectares, output file |
REPORT | The full report as JSON |
Example dataset row:
{"plot": 1,"status": "fixed","geometryType": "MultiPolygon","areaHa": 61.6138,"fixes": ["renamed property 'country' to 'ProducerCountry'","changed ProducerCountry 'Ghana' to ISO code 'GH'","converted Area '2,5' into the number 2.5 (hectares)","repaired an invalid shape (self-intersection)"],"warnings": ["declared Area 2.5 ha differs from the mapped area 61.6138 ha"],"errors": [],"outputFile": "eudr_ready.geojson"}
How much does it cost?
You pay per plot processed. The exact price is on the Pricing tab. At $0.01 per plot, for example, a 1,000-plot cooperative file costs $10, and a 50-plot test file costs $0.50.
There is no subscription. You can cap the cost of any run with the maximum-charge setting, and the fixer stops at that limit and tells you how many plots were skipped. The default example run (3 plots) costs $0.03. Runs are paid from your Apify balance; the free plan's $5 monthly credit covers a few default runs. Use Maximum cost per run in the run options to set a hard cap.
More tools from translucent_wire
Next step after fixing: the run's OUTPUT record has nextStep.georiskLocations: the centre of each ready plot, already in the format of GeoRisk Site Screener's locations input. Paste it there to check the plots for mapped forest, protected areas, flood and other site risks.
| Tool | What it does |
|---|---|
| Local Business Leads | Local businesses by type and city: email, website gaps, fit score, audit pages, map |
| Hiring Signals to Proposals | Companies hiring for a role your service can do: tasks covered, saving, email, proposal page |
| GeoRisk Site Screener | Flood, contamination, climate, EUDR forest and solar risk for any site or plot, A-F grades + report |
| Solar Roof Prospects | Business roofs that suit commercial solar: system size, saving, payback, email, estimate page |
Use it from an AI assistant (MCP)
Add Apify's MCP server to Claude, ChatGPT, Cursor or any MCP client and this Actor becomes a tool your assistant can run:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com/?tools=translucent_wire/eudr-plot-file-fixer"}}}
AI agents without an Apify account can also run it and pay per run in USDC through Apify's x402 support.
FAQ
Does this make my product EUDR compliant? No. It makes your geolocation file follow the published technical rules of the EU Information System. It doesn't check deforestation risk, legality of production, or any other due-diligence step, and it isn't legal advice.
Will it change correct plots? No. A plot that already meets every rule is passed through unchanged.
Is my data stored? Your files and results stay in your own Apify storage, under Apify's normal retention settings. Nothing is shared with anyone else.
Which rules does it follow?
The published EU Information System GeoJSON guidance: WGS 84, at least 6 decimal digits, Point/MultiPoint/Polygon/MultiPolygon only, closed counter-clockwise polygons without self-intersections or holes, the 4 ha point rule, numeric Area in hectares, ISO 2-letter ProducerCountry, 1,000 production places per commodity line and 25 MB per statement.
Can I use it from my own system? Yes. Call it through the Apify API or any Apify integration (Make, Zapier, n8n, Python, JavaScript) with the same input fields.
Feedback
Found a file it can't handle? Open an issue on the Issues tab, and attach a sample with the personal details removed if you can.

