When do I need a polygon instead of a single point?

Plots of 4 hectares or less may be reported as a single geographic point. Plots larger than 4 hectares require a polygon describing the perimeter of the plot of land.

What makes a GeoJSON geolocation file invalid?

The most common technical failures are unclosed polygon rings (the first and last coordinate pairs do not match), self-intersecting polygons, coordinates given in the wrong order (latitude, longitude instead of the required longitude, latitude), insufficient decimal precision, and using a coordinate reference system other than WGS84.

Can I check my GeoJSON file before submitting it?

Yes. Structural and coordinate problems such as open rings, self-intersections and swapped coordinates can be checked locally before submission using a GeoJSON validator, without uploading the file to a third party.

EUDR GeoJSON geolocation requirements explained

Q: What coordinate format does EUDR require?

Latitude and longitude in decimal degrees, to at least six decimal places, using the WGS84 coordinate reference system (EPSG:4326). GeoJSON coordinate order is longitude first, then latitude -- the reverse of how coordinates are commonly spoken or written.

Q: When does EUDR apply?

Following the December 2025 simplification amendment, large and medium operators and traders must comply from 30 December 2026. Micro and small operators have until 30 June 2027, except micro and small operators already covered by the EU Timber Regulation, who follow the earlier 30 December 2026 date.

Last reviewed 17 July 2026. Reflects Regulation (EU) 2023/1115 as amended in December 2025.

What EUDR geolocation is

The EU Deforestation Regulation (Regulation (EU) 2023/1115) requires operators and traders placing certain commodities on the EU market -- cattle, cocoa, coffee, oil palm, rubber, soya and wood, and derived products -- to submit a due diligence statement that includes the geolocation of every plot of land where the relevant commodity was produced.

Geolocation is not a free-text address. It is structured coordinate data, typically submitted as GeoJSON, that must meet specific format and precision requirements before it can be accepted.

In one sentence: plots of 4 hectares or less can be reported as a single point; larger plots need a polygon of the perimeter, and every coordinate must be in decimal degrees, WGS84, to at least six decimal places.

Current application dates

EUDR's application dates were pushed back twice, most recently by a December 2025 simplification amendment. The dates below reflect that amendment.

Large and medium operators and traders	30 December 2026
Micro and small operators	30 June 2027
Micro and small operators already covered by the EU Timber Regulation (EUTR)	30 December 2026 (follow the earlier date, not the general small-operator date)

Because the dates have changed twice, treat any date you find outside an official EU source as potentially outdated, and check the European Commission's EUDR page before relying on a specific deadline.

Point vs. polygon: the 4-hectare rule

The geometry type required depends on the size of the plot of land:

4 hectares or less: a single geographic point (latitude and longitude of the plot) is sufficient.
More than 4 hectares: a polygon describing the perimeter of the plot is required, not just a centre point.

This threshold applies per plot, not per shipment or per operator -- a single consignment sourced from several plots may need a mix of points and polygons depending on each plot's size.

Coordinate format

Coordinate system	WGS84 (EPSG:4326)
Format	Decimal degrees
Precision	At least six decimal places
Coordinate order in GeoJSON	Longitude first, then latitude -- `[lon, lat]`, not `[lat, lon]`
File format	GeoJSON (Feature or FeatureCollection)

The coordinate order is the single most common source of confusion. Most people say and write coordinates as "latitude, longitude" -- but the GeoJSON specification stores them the other way round, as [longitude, latitude]. A file with coordinates copied straight from a "lat, lon" source without swapping the order will place every plot in the wrong location, often in the ocean or a different hemisphere entirely.

Common submission errors

Unclosed rings: a polygon's coordinate ring must start and end on the exact same coordinate pair. If the first and last points do not match, the ring is not closed and the polygon is invalid.
Self-intersecting polygons: a polygon whose boundary crosses itself does not describe a simple, well-defined area and will be rejected.
Swapped coordinate order: latitude and longitude reversed, as described above -- the most frequent single cause of geolocation files that look fine in a spreadsheet but map to the wrong place entirely.
Insufficient precision: fewer than six decimal places can leave a coordinate imprecise enough to be rejected or to misplace small plots.
Wrong coordinate reference system: data exported in a national or regional projection instead of WGS84 will not line up correctly even if the numbers otherwise look plausible.

Common misconceptions

"A point is always enough." No. Points are only accepted for plots of 4 hectares or less; larger plots need a full polygon.
"Any coordinate format will do as long as the numbers are right." No. The reference system (WGS84), decimal degree format, six-decimal precision and longitude-first ordering are all specific requirements, not stylistic preferences.
"The application date is still in 2025 or early 2026." The dates changed in the December 2025 amendment. Large and medium operators now have until 30 December 2026, and most small operators until 30 June 2027.
"If the file opens in a GIS tool without errors, it's valid for EUDR." Not necessarily. A file can be syntactically valid GeoJSON and still fail EUDR-specific checks like the 4-hectare point/polygon rule or precision requirements.

Checking a file before you submit it

Open rings, self-intersections and swapped coordinates are exactly the errors that are easy to miss by eye but simple to catch with a structural check. The EUDR Plot File Studio validates and repairs GeoJSON geolocation files locally in your browser -- plot coordinates and area are never uploaded, and the built-in map lets you see each plot against real terrain before you rely on it.

Open EUDR Plot File Studio

Frequently asked questions

What coordinate format does EUDR require?

Decimal degrees, WGS84 (EPSG:4326), at least six decimal places, with GeoJSON's longitude-first coordinate order.

When do I need a polygon instead of a point?

Plots larger than 4 hectares need a polygon of the perimeter. Plots of 4 hectares or less can be a single point.

When does EUDR apply?

Large and medium operators and traders from 30 December 2026; micro and small operators from 30 June 2027, except those already covered by the EU Timber Regulation, who follow the 30 December 2026 date.

What makes a GeoJSON file invalid?

Unclosed polygon rings, self-intersecting polygons, coordinates in the wrong order, insufficient decimal precision, and the wrong coordinate reference system are the most common causes.

Can I check my file before submitting it?

Yes. Structural issues like open rings, self-intersections and swapped coordinates can be checked locally without uploading the file anywhere.

Sources

Regulation (EU) 2023/1115 (EU Deforestation Regulation) — eur-lex.europa.eu
European Commission — Regulation on deforestation-free products — environment.ec.europa.eu

This guide is general information about EUDR geolocation requirements, not legal advice. Application dates and technical requirements have changed more than once and implementing acts add further detail -- verify current dates and format rules against the Official Journal and the European Commission before relying on any figure. Not affiliated with the European Commission or the EU.