EUDR Geolocation Requirements: Complete Guide to GPS & Polygon Data

Geolocation data is one of the most scrutinised elements of an EUDR due-diligence statement. Article 9(1)(d) requires operators to provide the geolocation of every plot of land where a regulated commodity was produced. This guide covers what you need to collect, the formats expected, and how to avoid the most common errors.

1. What Geolocation Data EUDR Requires

The regulation distinguishes between two types of geolocation data: point coordinates and polygon coordinates. For each plot of land in your supply chain, you must record either a single latitude/longitude pair (for plots up to 4 hectares) or a full polygon (for plots larger than 4 hectares). The coordinates must be provided in WGS 84 format — the same standard used by GPS devices worldwide.

The geolocation must be linked to a specific plot, not a general region or farm name. Each plot gets its own coordinates. If a single farm spans multiple plots, each plot must be identified separately.

2. Point vs Polygon: The 4-Hectare Threshold

The 4-hectare threshold is the key dividing line. If the production plot is 4 hectares or smaller, a single GPS point (latitude/longitude) is sufficient. If the plot exceeds 4 hectares, you must provide polygon coordinates — a series of points that trace the boundary of the plot.

Point coordinates: A single latitude/longitude pair, e.g., 5.6037° N, 0.1870° W. This is the minimum requirement for smallholder plots under 4 hectares.

Polygon coordinates: A sequence of at least three latitude/longitude pairs that define the outer boundary of the plot. The first and last points must connect to close the polygon. For irregularly shaped plots, more points are needed to accurately represent the boundary.

When in doubt, collect polygon data even for small plots. It provides stronger evidence of deforestation-free production and simplifies boundary verification against satellite imagery.

3. WGS84 Coordinate Format and Decimal Precision

All coordinates must use the World Geodetic System 1984 (WGS 84) datum. This is the global standard for GPS and is non-negotiable. Coordinates should be expressed in decimal degrees, not degrees-minutes-seconds (DMS).

Decimal precision matters. Six decimal places give you accuracy to approximately 0.1 metres — more than sufficient for agricultural plots. Most GPS devices and mobile apps record to at least five decimal places (approximately 1 metre accuracy).

4. GeoJSON Format Requirements

The EU Information System for due diligence (the ISV) accepts GeoJSON as a standard format for geolocation data. GeoJSON is an open format that represents geographic features as JSON objects. For EUDR purposes, each plot is represented as either a Point feature (for single coordinates) or a Polygon feature (for multi-point boundaries).

A typical GeoJSON Point feature for a smallholder plot looks like this: a Feature object with a geometry type of Point and coordinates listed as [longitude, latitude]. Note that GeoJSON uses longitude-first ordering (East, North), which is the reverse of the common latitude/longitude convention.

Always verify the coordinate order in any format you submit. Reversed latitude and longitude is one of the most frequent validation errors. Antaios automatically converts and validates coordinate order when you upload geolocation data.

5. KML and Shapefile Formats

While GeoJSON is the preferred format for the EU Information System, many supply chain actors work with KML (Keyhole Markup Language) or shapefiles (.shp). KML is commonly used in Google Earth, and shapefiles are the standard format for GIS software like ArcGIS and QGIS.

Antaios handles the conversion for you. Upload KML, shapefiles, or GeoJSON directly through the platform and we will normalise the data into the correct format for your due-diligence statement. The platform also validates coordinate ranges, detects coordinate order issues, and flags plots that may exceed the 4-hectare polygon threshold.

6. Collecting GPS Data in the Field

The most reliable GPS data comes from purpose-built field collection apps or dedicated GPS devices. Smartphone GPS apps are generally accurate enough for EUDR compliance, provided they record in WGS 84 and support decimal degree output. Dedicated handheld GPS units (e.g., Garmin, Trimble) offer higher precision, which is valuable for large plots.

Best practices for field collection:

• Record coordinates at the plot boundary, not at the centre — this is especially important for polygon data
• Allow the GPS to settle for at least 30 seconds before capturing coordinates to reduce signal drift
• Collect multiple points at the same location and average them for higher accuracy
• Tag each collection with the date, collector name, and plot identifier

7. Working with Smallholders and Cooperatives

Collecting geolocation data from smallholder farmers presents practical challenges. Many farmers may not own GPS devices or have experience with digital tools. Cooperatives and field officers play a critical role as intermediaries.

A proven strategy is to train field officers on GPS collection methods and provide them with simple mobile apps (GPS Essentials, Avenza Maps, or custom solutions). Field officers visit each farmer, walk the plot boundary, and record coordinates on behalf of the farmer. This approach scales well and produces consistent, high-quality data.

For cooperatives with many small plots, consider batch collection campaigns. Dedicate field teams to a region and collect data from all members in a single pass. This reduces per-plot cost and ensures uniform data quality across the cooperative.

8. Common Geolocation Errors and How to Fix Them

Auditors and the EU Information System flag the same errors repeatedly. Avoiding these pitfalls saves time and reduces the risk of DDS rejection.

• Coordinates outside the reported country of origin — this often happens when data is copied from a spreadsheet and pasted in the wrong order
• Missing closing vertex in polygon data — a polygon must have its first and last points identical to form a closed shape
• Self-intersecting polygons — when boundary lines cross each other, the polygon is invalid. Walk the boundary in one direction to avoid this
• Using latitude/longitude instead of longitude/latitude in GeoJSON — GeoJSON requires [lon, lat] order, not [lat, lon]
• Point coordinates for plots that clearly exceed 4 hectares — if a single point is provided for a large plot, the system will reject it

9. How to Validate Your Geolocation Data

Before submitting your due-diligence statement, validate your geolocation data against these criteria:

• All coordinates fall within the reported country's bounding box
• Polygon features have at least three vertices and a closed boundary
• Coordinate format is WGS 84 decimal degrees
• Each plot has a unique identifier linking it to supply chain records
• Polygon area calculation matches the declared plot size (within acceptable tolerance)

Antaios runs these validations automatically when you upload geolocation data. The platform highlights any issues before you finalise your DDS, giving you time to correct problems.

10. Integration with Global Forest Watch

EUDR compliance requires you to verify that no deforestation occurred on your production plots after the cut-off date (31 December 2020). Geolocation data is the link between your supply chain and satellite deforestation monitoring. Platforms like Global Forest Watch (GFW) use geolocation coordinates to run deforestation alerts against your specific plots.

Antaios integrates directly with GFW data. When you upload polygon coordinates, the platform automatically checks for deforestation alerts within your plot boundaries and flags any potential risks. This turns what would be hours of manual cross-referencing into an automated step in your compliance workflow.

Key Takeaways

Geolocation data is not just a checkbox — it is the foundation of EUDR deforestation-free verification. Collect coordinates in WGS 84 decimal degrees, use polygons for any plot over 4 hectares, validate before submission, and leverage automation where possible. Getting this right the first time saves significant effort during audits and avoids costly resubmissions.