The EUDR GeoJSON checklist: every rule your plot file must pass.Read it →

Your EUDR plot data, ready to submit.Verified on the ground.

Every supplier plot checked against the EUDR rules, rejections fixed before you submit, and doubtful plots surveyed in the field with GNSS receivers.

Lot auditCooperative [Name] · Cocoa · Campaign 2026
Satellite imagery
Loading map…
Desk reviewField checkSignal to review

Built for exporters, cooperatives, and European importers

Logo partenaire 1
Logo partenaire 2
Logo partenaire 3
Logo partenaire 4
Logo partenaire 5

From a messy supplier file to a declaration you can defend.

Loading map…
Desk reviewField checkSignal to review

Catch rejections before you submit

Around twenty checks replay the EU Information System’s validation rules on every plot: coordinates, geometry, data types and size limits. What can be fixed safely is fixed and logged.

Plot record · Example

LOT CI-0482 · Cattle · 3.2 ha

Desk review
CodeIssue foundOutcome
F01Latitude and longitude swappedFixed
F03Area stored as textFixed
G01Polygon not closedFixed
F04File above the upload limitSplit
G06GPS point for a plot over 4 haField mapping

Illustrative results only; they do not constitute regulatory validation.

Supplier file receivedGeoJSON · KML · Shapefile · CSV

Compliant

Straight to the export file

Screen review

An analyst decides on imagery.

Field check

A mission is created.

Every decision is stored with the plot, the imagery viewed, and the reason.

Only doubtful plots reach a person.

Each plot gets a risk score and one clear status. Clean plots go straight through, and expert attention goes only where judgement matters.

Illustrative workflow only: the displayed data, plots, and suppliers are fictional.

Know which plots are solid, and which need remapping.

Every outline is graded on its shape, its accuracy and how it fits with neighbouring plots. Small errors are corrected on screen. Weak outlines go straight to a GNSS field survey, so you only remap what needs it.

Plot quality

Sample data

CI-0482

Cocoa · 3.2 ha

Clean outline, area matches declaration

CI-0517

Cocoa · 1.8 ha

Spikes from GPS drift on two vertices

CI-0533

Cocoa · 4.6 ha

GPS point only, plot over 4 ha

CI-0541

Cocoa · 2.1 ha

Overlaps a neighbouring plot

Actions are simulated in this mock-up; no survey is changed or submitted.

A valid file can still be the wrong shape.

A phone’s GPS can drift by several metres, and more under cocoa canopy. The polygon passes every format check, yet misses the real boundary. A field survey with GNSS receivers and real-time corrections gives you an outline that matches the land.

  • Centimetre-level outlines with RTK corrections
  • Fix quality and accuracy stored with every outline
  • Anti-fraud checks on position, time, and photos

Phone GPS track

Autonomous
Placeholder
FixAutonomous
AccuracySeveral metres
Mapped area[0.00] ha

GNSS survey

RTK fixed
Placeholder
FixRTK fixed
Accuracy[± 0.0] cm
Mapped area[0.00] ha

GNSS receiver

Connected
FixRTK fixed
Horizontal accuracy[± 0.0] cm
Satellites in use[00]
Corrections[NTRIP / base station]

Field mission

Village [Name] · [0] plots

GNSS receiver mounted on a survey pole, illustrative photo

Transparent rules. Public sources. Nothing hidden.

Every check has a code, a source and a threshold you can read, so your GIS team, and any authority, can audit every decision.

Read the methodology →
CodeCheckSource
G02Self-intersecting polygonOGC geometry validity
C03Overlap between plotsSpatial index across the lot
R01Forest cover in 2020JRC Global Forest Cover 2020
R02Tree cover loss after 2020Global Forest Watch
R03Protected area or classified forestWDPA and national layers

What lands in your inbox, for every lot.

Audit report

Plots by status, main anomalies, a map of forest alerts and actions to take. Written for management.

Submission-ready file

Compliant plots only, in the EU Information System format, Type I and Type II, split to its limits.

Plot-by-plot audit trail

Status, score, anomaly codes, corrections and every human decision. Your evidence if an authority asks.

Deliverables are defined according to each engagement’s scope and needs.

Latex being collected from a rubber tree, illustrative photo

“A customer testimonial will be added here, in their own words and reflecting their real experience.”

Client name to be added

Role and organisation to be confirmed

—

Plots audited

Real figure to be provided

—

Field agents

Real figure to be provided

—

Cooperatives

Real figure to be provided

—

Countries

Real figure to be provided

For compliance and procurement teams

No GIS team? Send your files as they are.

Get a useful audit and the information you need—without opening a map.

Explore services →

For GIS and data teams

Clean, documented data for your tools.

Agreed formats, versioned rules, and anomaly codes your analysts can reuse.

Explore technology →

Send a sample lot and get every issue listed, with the reason and the fix.