This template provides a structured, field-ready framework for collecting EUDR-compliant geolocation data at the plot level. It covers coordinate capture specifications, device requirements, validation criteria, and photo evidence linkage — the minimum dataset needed to substantiate the geolocation component of a Due Diligence Statement under Article 9(1)(d).
Geolocation data is not evidence by default. Coordinates without collection timestamps, device attestation, and verification methodology are supplier claims. This template helps field teams capture the metadata that transforms raw GPS readings into auditable evidence.
What is EUDR geolocation data collection?
The EU Deforestation Regulation requires operators to collect and report the geolocation of all plots of land where EUDR-covered commodities were produced. Under Article 9(1)(d), this means a single GPS point for plots of four hectares or less, and polygon boundaries defining the perimeter for plots exceeding four hectares. The geolocation data must be precise enough to identify the exact land parcel, enabling competent authorities to cross-reference coordinates against deforestation alert systems, protected area registries, and satellite imagery baselines anchored to the December 31, 2020 cutoff date.
Geolocation is one of the most frequently rejected elements in due diligence submissions. Approximate coordinates, aggregated village-level centroids, or polygons with insufficient vertex density will not withstand regulatory scrutiny. Getting capture methodology right at the field level prevents costly recollection campaigns downstream.
What this template covers
Coordinate reference system and precision
- All coordinates captured in WGS84 (EPSG:4326) coordinate reference system
- Latitude and longitude recorded to 6-decimal-place precision (approximately 0.11 metre accuracy at the equator)
- Coordinate format uses decimal degrees, not degrees-minutes-seconds
- Datum transformation documented if local coordinate systems are converted to WGS84
Plot classification and capture method
- Plot area estimated or measured before capture to determine point vs. polygon requirement
- Single GPS point recorded for plots of 4 hectares or less (Article 9(1)(d))
- Polygon boundary captured for plots exceeding 4 hectares, with vertices at every significant boundary change
- Minimum of 4 vertices per polygon (excluding closing vertex); complex boundaries use more
- Polygon recorded in GeoJSON format compliant with RFC 7946 (right-hand rule for exterior rings)
Device and collector metadata
- GPS device make, model, and firmware version recorded for each capture session
- Collector identity recorded (name, organization, role)
- Collection date and time captured in ISO 8601 format with timezone offset (e.g., 2026-05-19T09:30:00+07:00)
- Reported GPS accuracy (HDOP or metres) logged at the moment of capture
- Device satellite count recorded at capture time
Accuracy thresholds and recapture rules
- GPS accuracy threshold set at 10 metres or better for open-canopy conditions
- Dense-canopy captures exceeding 10-metre reported accuracy flagged for recapture or SBAS-assisted re-reading
- Recapture performed on a different day or time to obtain better satellite geometry when accuracy threshold is not met
- All recapture attempts logged with reason for rejection of prior reading
Data validation criteria
- Polygon self-intersection check passed (no crossing boundary lines)
- Minimum area threshold applied (polygons below 0.01 hectares flagged as potential errors)
- Overlap check performed against adjacent plots in the same supply base
- Coordinate range validation applied (latitude within -90 to 90, longitude within -180 to 180)
- GeoJSON structural validation passed using ResourceLedger GeoJSON Validator or equivalent tool
Photo evidence linkage
- Geotagged photographs taken at plot boundary or centre point to corroborate GPS coordinates
- Photo EXIF metadata preserved (timestamp, GPS coordinates, device information)
- Minimum of one photo per point capture; minimum of four photos for polygon captures (one per cardinal boundary segment)
- Photos linked to the corresponding GeoJSON feature by plot identifier
How to use this template
Step 1 — Prepare devices. Before field deployment, verify that all GPS devices or mobile applications are configured to output WGS84 coordinates at 6-decimal precision. Record device metadata for each unit.
Step 2 — Capture in the field. At each plot, classify the area as point or polygon, capture coordinates following the checklist, and take geotagged photographs. Log reported accuracy and reject captures that fall outside the threshold.
Step 3 — Validate collected data. After field collection, run all GeoJSON files through structural and spatial validation checks. Flag self-intersections, overlaps, and accuracy outliers for recapture.
Step 4 — Archive with metadata. Store validated GeoJSON files alongside collection timestamps, device records, collector identity, and linked photographs. This complete dataset forms the geolocation evidence package for your Due Diligence Statement.
How to implement this in your organisation
Assign ownership. The field team lead owns data collection quality for each geolocation campaign, including GPS device provisioning and GNSS configuration before deployment. The data manager validates all incoming GeoJSON files before they enter your central system — when multiple teams operate in parallel, each lead is accountable for their campaign, and the data manager reviews across teams.
Set the review cadence. Check device configuration and satellite acquisition settings before every deployment. During active campaigns, run a daily QA sample — spot-check accuracy readings, validate GeoJSON structure, and confirm photo linkage. After each campaign, perform a full validation pass. If recapture rates exceed 10%, retrain field teams on capture methodology before the next deployment.
Define your escalation path. When coordinates fail accuracy thresholds or metadata is incomplete, return them for same-day recapture while the team is still in the area. If the team has already left, flag the record and schedule a return visit. Systematic failures — more than 15% of captures rejected — escalate to the programme manager for root cause analysis before additional field work proceeds.
Connect to existing workflows. Integrate device provisioning into pre-visit planning: configure GPS units alongside translator scheduling and consent form preparation. After validation, link each GeoJSON feature to the corresponding farmer record in your supply chain database and feed validated coordinates into your deforestation screening workflow. Attach geotagged photos to the same record so the complete evidence package is available when assembling your Due Diligence Statement.
Who needs this template
- Field officers collecting GPS coordinates at farm or plantation level during supplier visits
- Compliance officers defining geolocation capture standards and validating incoming data from field teams or suppliers
- Data managers building quality assurance workflows for spatial data before it enters the DDS submission pipeline
FAQ
What coordinate precision does the EUDR require?
The regulation does not specify a precision number, but 6-decimal-place precision in WGS84 (approximately 0.11 metres) is the defensible standard adopted by implementing bodies and technology providers. Fewer decimal places introduce ambiguity that competent authorities may challenge during verification, particularly when cross-referencing coordinates against high-resolution satellite imagery.
When do I need polygon boundaries instead of a single point?
Article 9(1)(d) requires polygon boundaries for any plot of land exceeding 4 hectares. Below that threshold, a single GPS point is acceptable. Measure or estimate plot area before capture. When in doubt, capture the polygon — a polygon can always be reduced to a centroid, but a centroid cannot be expanded into a boundary after the field visit.
What should I do when GPS accuracy exceeds 10 metres under dense canopy?
Dense canopy, steep terrain, and poor satellite geometry can degrade accuracy beyond 10 metres. Log the reading and flag it for recapture. Return at a different time of day for better satellite geometry, use an external GNSS antenna if available, or capture from a nearby clearing and document the offset. Never accept a degraded reading without documenting the limitation.
Are coordinates from a supplier sufficient evidence?
Coordinates from a supplier without independent verification are supplier claims, not evidence. Operators must verify through independent means: cross-reference against satellite imagery, perform spot-check field visits, or use a system that captures device attestation and collection timestamps at the point of origin. The burden of proof sits with the operator, not the supplier.
This template supports the geolocation component of EUDR due diligence. For a platform that captures, validates, and archives geolocation evidence with device attestation and satellite verification built in, book a demo to see how ResourceLedger works.