EUDR GPS Geolocation for Kenyan Coffee Cooperatives — The Complete Tool-by-Tool Guide 2026

 

Every Kenyan coffee cooperative that exports to EU buyers faces the same operational challenge: by December 2026, every plot of land that contributed coffee to any EU-bound export lot must have GPS geolocation data on file — documented in a format the EU’s TRACES NT platform can process and verify against satellite deforestation maps. The principle is clear. The execution is where cooperative managers run into questions that the EU regulation documents and even Kenya’s EUDR guidance materials do not answer for their specific situation.

Which app do you use? How do you handle members who don’t own smartphones? What exactly is a polygon and how do you collect one? What is WGS84 and why does it matter? How do you get your data into TRACES NT? What happens if one of your member plots appears to sit on forest cover? This guide answers every one of these questions — with specific tools, field protocols, and a week-by-week implementation timeline built for Kenyan coffee cooperative conditions.

This is a companion guide to our complete EUDR Kenya guide for coffee exporters — which covers what EUDR requires, the full compliance framework, and the 5-step implementation timeline. This guide focuses entirely on the geolocation data collection operational challenge.

What Geolocation Data EUDR Actually Requires from Kenyan Cooperatives

Before choosing a tool or collecting a single GPS coordinate, it is critical to understand exactly what the EU Deforestation Regulation requires. Article 9 of Regulation (EU) 2023/1115 requires that due diligence statements include “the geolocation of all plots of land where the relevant commodities were produced, including the geographical coordinates of the relevant plots of land.” Where a commodity was produced on multiple plots, the coordinates of all plots must be included.

For Kenyan coffee cooperatives, this translates to a specific operational requirement: for every export lot prepared for an EU buyer, you must be able to show GPS coordinates for every member farm plot whose coffee was included in that lot. If you cannot produce this data, you cannot submit a valid due diligence statement. Without a valid DDS, your coffee shipment cannot enter the EU from December 2026.

Polygon vs GPS Point — Which Does Your Cooperative Need to Collect?

However, polygon collection is still strongly recommended even for plots below 4 hectares for two reasons: polygon data provides stronger deforestation verification when EU authorities cross-check your DDS against forest cover maps; and several EU buyers are already requesting polygon data as a condition of supply. Collecting polygon data now protects you from having to redo the collection programme later.

Practical recommendation: begin with GPS point collection for all member plots immediately to meet the December 2026 deadline. Where time and capacity allow, conduct polygon collection for plots flagged by preliminary deforestation screening. This phased approach delivers compliance by the deadline while building towards the stronger polygon dataset buyers increasingly require.

Tool Comparison — KoboToolbox vs ODK Collect vs Survey123 vs Garmin GPS

Four tools dominate the EUDR geolocation data collection landscape for East African smallholder supply chains. The right choice for your cooperative depends on technical capacity, connectivity, budget, and smartphone availability.

KoboToolbox — Complete Step-by-Step Setup for Kenyan Coffee Cooperatives

KoboToolbox is used by FAO, USAID, WFP, and dozens of NGOs operating in Kenya — which means local support expertise is available and field staff with development sector experience are likely already familiar with it.

Step 1 — Create your cooperative’s KoboToolbox account

Go to kf.kobotoolbox.org. Click “Create an account.” Use a cooperative institutional email address — not a personal Gmail — so the account remains with the organisation. Select “Non-profit / NGO / Research” as your account type for the free humanitarian tier with higher submission limits. No credit card required.

Step 2 — Build your EUDR data collection form

In KoboToolbox, create a new form. Your EUDR geolocation form needs these fields at minimum:

• Member ID — your cooperative’s internal member number
• Member Name
• Plot Name/Number — each member’s plot identifier
• Plot Area (hectares) — decimal number
• GPS Point — GPS question type, “Point” mode. Set accuracy threshold to 5 metres or better.
• GPS Polygon — GPS question type, “Polygon/Trace” mode. Set as optional for phase 1 GPS point collection.
• Land Use Declaration — select_one: “Coffee since before December 31, 2020” / “Converted from other use after December 31, 2020” / “Not sure — requires investigation”
• Collector Name and Collection Date — for quality control and audit trail

In GPS question settings, verify the coordinate system is WGS84 decimal degrees (the KoboToolbox default — confirm it has not been changed). Set GPS accuracy threshold to 5 metres.

Step 3 — Deploy to KoboCollect on field team phones

Download KoboCollect from Google Play Store on each field team Android phone. Log in with the cooperative’s KoboToolbox credentials. Configure for offline use — enable “Offline mode” and pre-download all pending forms before field teams leave areas with mobile coverage.

Step 4 — Export and format for TRACES NT

Export collected data as GeoJSON (for polygon data — directly uploadable to TRACES NT) or CSV (for GPS point data — convert to GeoJSON using the free CSV to GeoJSON converter at csvjson.com/csv2geojson before uploading to TRACES NT). Agrosocial Services provides data conversion support if this step presents a technical barrier.

ODK Collect — When and How to Use It

ODK Collect is the underlying technology behind KoboToolbox — KoboToolbox is essentially a managed, user-friendly deployment of the ODK framework. ODK Collect as a standalone tool is preferable over KoboToolbox in two scenarios:

• Very large cooperatives (500+ members) where KoboToolbox’s free tier submission limits may be reached — ODK Central (the server component) can be self-hosted for unlimited submissions at approximately KES 2,000–5,000 per month on a cloud provider.
• Cooperatives with an existing NGO technical support partner who already manages ODK infrastructure — adding EUDR data collection to an existing ODK server avoids creating a parallel KoboToolbox account.

The form design, field collection protocol, and data export process for ODK Collect are identical to KoboToolbox — both use the XLSForm standard. If you have used KoboToolbox before, you can use ODK Collect without additional training.

Garmin GPS Devices — For Non-Smartphone Zones and High-Accuracy Requirements

In highland coffee growing zones with poor mobile coverage — particularly Kirinyaga North, Mathioya (Murang’a), upper Kangema, and parts of Taita Hills — smartphone GPS accuracy degrades significantly due to the absence of assisted GPS. A dedicated GPS unit provides 3–5 metre accuracy consistently, regardless of mobile coverage.

The Garmin GPSMAP 64s or 66s are the recommended dedicated GPS units for Kenyan EUDR geolocation fieldwork. Both models support polygon trace collection via the track log function, export data as GPX and KML files (TRACES NT-compatible after minor conversion), and operate on AA batteries — practical for multi-day field campaigns in areas without reliable electricity.

Garmin setup for EUDR polygon collection: enable the Track Log function before entering each plot. Walk the plot boundary at a consistent pace. When you return to the starting point, save the track with the member ID and plot number as the track name. Export all saved tracks to a computer via USB at the end of each field day. Convert GPX to GeoJSON using GPS Visualizer (gpsvisualizer.com) or QGIS before TRACES NT upload.

Garmin units are available in Kenya from authorised dealers including Rongo Navigation Equipment and online via Jumia Kenya. Budget KES 35,000–55,000 per unit.

Field Collection Protocol — What Your Team Must Do on Every Plot Visit

Inconsistent field protocols are the primary source of EUDR geolocation data quality problems. The following protocol must be followed on every plot visit, by every field collector, without exception.

For GPS Point Collection

1. Walk to the centre of the plot — not the entrance, not the nearest road. The GPS reading must represent the plot, not the path to the plot.
2. Open KoboCollect and navigate to the GPS Point question. Tap “Record Location.” Wait for GPS accuracy to reach 5 metres or better — do not accept readings above 10 metres.
3. Hold the phone horizontally, at arm’s length from your body. Your body mass blocks satellite signals. Standing under dense coffee canopy reduces accuracy — take the reading in an open area within the plot where possible.
4. Wait a minimum of 30 seconds after accuracy reads 5m or better before tapping “Save.” This allows the GPS chip to average multiple satellite readings for a more accurate final coordinate.
5. Confirm Plot ID and Member ID match the plot you are physically standing in before moving on. Cross-reference with the paper member register.

For GPS Polygon Collection

1. Start at a clearly identifiable plot corner (fence post, large rock, pathway junction). Record a 5-second minimum at this starting waypoint.
2. Walk the plot perimeter clockwise at approximately 3 km/h. KoboCollect polygon mode records waypoints automatically; Garmin track log records continuously.
3. Pause for 5 seconds at each corner point to allow accurate position recording at the directional change. Moving through corners at full walking speed produces inaccurate corner coordinates.
4. Return to the starting corner and close the polygon. In KoboCollect, tap “Close Polygon.” In Garmin, stop the track log and save with the plot identifier as the track name.
5. Review the polygon on screen before leaving the plot. If the shape is clearly wrong — crossed lines, sharp spikes, shape that does not match the physical plot — delete the record and repeat.

WGS84 and Data Standards — Why the Coordinate System Matters

WGS84 (World Geodetic System 1984) is the coordinate reference system used by GPS satellites, Google Maps, TRACES NT, and virtually every global mapping application. It represents locations as latitude and longitude in decimal degrees — for example, Murang’a Town is at approximately -0.7667° latitude, 37.1500° longitude in WGS84. TRACES NT only accepts coordinates in this format.

If your GPS device or app collects data in a different coordinate system — such as UTM or degrees-minutes-seconds — your data must be converted before submission. Errors in coordinate system conversion produce incorrect plot locations that may place a plot kilometres from its actual position, triggering false-positive deforestation flags.

• KoboToolbox: WGS84 decimal degrees is the default. No action required.
• ODK Collect: WGS84 decimal degrees is the default. Verify in Settings → GPS.
• Garmin GPSMAP 64s/66s: go to Setup → Units → Position Format → hddd.ddddd° (decimal degrees). Also confirm Map Datum is set to WGS84 in Setup → Units.
• Garmin GPX/KML exports: always in WGS84. No conversion needed.

Validating Your Data Against Forest Cover Maps

After GPS data collection, every cooperative must validate its plot data against satellite-based forest cover maps to identify any plots that may be located in or adjacent to deforested areas. This validation step is what the EU will perform when it assesses your due diligence statements — doing it yourself first means you discover and resolve issues before they become compliance failures.

Free Validation Tools for Kenyan Cooperatives

• Google Earth Pro (free desktop application): import your GPS data as a KML file. Use the historical imagery feature to view each plot in satellite imagery from 2020 — if the plot was clearly under coffee cultivation at that date, it passes the basic deforestation check. Free to download, does not require mobile data once imagery is cached.
• Global Forest Watch (globalforestwatch.org): the authoritative deforestation monitoring platform the EU references in its EUDR risk assessment guidance. Upload your KML or GeoJSON plot data and overlay against the Hansen/UMD Tree Cover Loss layer. Any plot showing tree cover loss after December 31, 2020, within or adjacent to the plot boundary requires further investigation. Free, web-based.
• QGIS (free GIS software, qgis.org): for cooperatives with a technically capable data manager, QGIS allows bulk validation of all member plots simultaneously against downloaded forest cover raster layers — producing a formal spatial analysis report that can accompany your TRACES NT submission as supporting documentation. FAO Kenya office has Swahili training videos for QGIS on YouTube.

What to Do If a Member Plot Overlaps with Forest Cover

This is the most commercially serious scenario in the EUDR geolocation process — and the most important reason to complete validation well before the December 2026 deadline.

Three Scenarios and Their Responses

1. GPS collection error — the most common cause. The point was recorded at the wrong location (collector was outside the plot, or a coordinate format error shifted the position). Verify against the paper member register and revisit the plot for re-collection. Not an EUDR compliance issue — a straightforwardly correctable data quality issue.
2. Shade trees within the coffee agroforestry system — many Kenyan highland coffee farms use shade trees (Grevillea, Calliandra, Leucaena) within the plot. Tree cover detection algorithms may flag shade-tree coffee plots as having “tree cover” — but this is not deforestation. Document the shade tree species and coffee intercropping system in the plot’s land use declaration. EU guidance explicitly excludes agroforestry from EUDR deforestation classification.
3. Genuine post-2020 deforestation — if a member’s plot was genuinely cleared from forest after December 31, 2020, that plot cannot be included in EU-destined export lots under EUDR. Notify the member, segregate cherry purchases from that member from EU-destined lots, and document the segregation process for TRACES NT. The member’s plots can still contribute to domestic market or non-EU export lots. This scenario is expected to affect a small minority of Kenyan coffee cooperative members.

TRACES NT — How Kenyan Coffee Cooperatives Register and Submit Due Diligence Statements

TRACES NT (Trade Control and Expert System — New Technology) is the European Commission’s official EUDR due diligence statement submission platform at traces.ec.europa.eu. Every operator placing EUDR-regulated commodities on the EU market must submit a DDS through TRACES NT before each shipment.

TRACES NT Registration Process for Kenyan Cooperatives

1. Create an EU Login account at ecas.ec.europa.eu using a cooperative institutional email address. Verification takes 24–48 hours.
2. Log into TRACES NT at traces.ec.europa.eu using your EU Login credentials.
3. Register as an Operator. Provide: legal cooperative name, Kenya address (matching KRA registration), country (Kenya), commodity type (Coffee — HS code 0901 or 0902). Registration is free. You receive a TRACES NT Operator ID — keep this reference number.
4. For each export shipment, create a Due Diligence Statement (DDS) linking your specific export lot to the geolocation data of contributing farm plots. Upload GeoJSON or KML coordinates directly, or enter manually for small cooperatives.

Practical TRACES NT Tips

• Register immediately. EU Login account activation and TRACES NT Operator registration can take several weeks if queries arise from the Commission’s system.
• Your EU buyer may offer to submit the DDS on your behalf as the importer — confirm this in writing. Even if your buyer handles submission, you are responsible for providing accurate geolocation data.
• The DDS reference number must accompany the shipment before the coffee departs Kenya — it travels with the commercial invoice and phytosanitary certificate.
• Upload GeoJSON for polygon data. TRACES NT accepts GeoJSON directly. Convert CSV GPS point data to GeoJSON using csvjson.com/csv2geojson before uploading.

Note on broader certification compatibility: EUDR due diligence documentation overlaps significantly with ethical trade audit requirements. If your EU buyer also requires a SMETA (Sedex Members Ethical Trade Audit), the supply chain traceability documentation your cooperative builds for EUDR — member plot registers, lot-to-plot linkage records, land use declarations — directly supports SMETA’s supply chain mapping requirements. Build your EUDR and SMETA documentation systems together where possible.

Handling Members Without Smartphones — Practical Solutions for Kenyan Cooperatives

Smartphone penetration among Kenyan smallholder coffee farmers ranges from 40–70% depending on county and altitude zone. A cooperative cannot make EUDR GPS data collection conditional on members owning a smartphone.

Your EUDR Geolocation Implementation Timeline — Week by Week

The following timeline applies to a typical Kenyan coffee cooperative with 100–300 members. Starting in May 2026 gives adequate margin for the December 2026 deadline. Starting in September 2026 does not.

What EUDR Geolocation Costs in Kenya 2026 — Full Budget Breakdown

A 100-member Kenyan coffee cooperative exporting 50 tonnes of AA grade coffee to EU specialty buyers at USD 4.00–7.00/kg generates annual EU export revenue of USD 200,000–350,000. The EUDR geolocation cost (KES 205,000–420,000 — approximately USD 1,600–3,200) represents less than 1% of that annual revenue. It is also a once-completed investment — GPS coordinates do not expire and do not need to be recollected each year. The cost of losing EU market access is 100% of EU export revenue, permanently. The investment case requires no further analysis.

Frequently Asked Questions

What GPS data does EUDR require from Kenyan coffee cooperatives?

GPS coordinates for every member farm plot that contributed coffee to an EU-destined export lot. EUDR prefers polygon data but accepts a GPS point + area declaration (hectares) for plots under 4 hectares — the majority of Kenyan smallholder plots. All coordinates must be in WGS84 decimal degree format. Submitted via a Due Diligence Statement on TRACES NT before each EU shipment. Full framework: EUDR Kenya Coffee Exporters Guide.

What is the best free GPS tool for EUDR data collection in Kenya?

KoboToolbox — free, offline-capable, polygon collection supported, exports GeoJSON and KML for TRACES NT, Swahili UI, widely supported by development organisations in Kenya. Install KoboCollect from Google Play Store. ODK Collect is the equally capable alternative for cooperatives with technical staff. Google Maps is not suitable — cannot export coordinates in TRACES NT-compatible format.

What is TRACES NT and how do Kenyan cooperatives register?

TRACES NT is the EU’s official EUDR due diligence statement portal at traces.ec.europa.eu. Register by creating an EU Login account at ecas.ec.europa.eu, then register as an Operator on TRACES NT (cooperative legal name, Kenya address, HS code 0901 for coffee). Free registration. Takes 1–5 days. Register immediately — do not wait until GPS collection is complete. Your EU buyer may submit DDS on your behalf — confirm this in writing.

What is a polygon vs GPS point — and which does my cooperative need?

GPS point = single coordinate. Polygon = coordinates tracing plot boundary. For plots under 4 hectares (most Kenyan smallholder coffee plots), GPS point + area declaration is legally sufficient. Polygon is preferred for stronger deforestation verification and increasingly required by EU buyers. Practical recommendation: collect GPS points for all plots first to meet the December 2026 deadline, then upgrade at-risk plots to polygon. Full comparison table in the “Polygon vs GPS Point” section above.

How long does it take to collect GPS data for a 200-member cooperative?

4–8 weeks field collection (trained team of 3–4 collectors) + 2–3 weeks validation and TRACES NT setup = 10–14 weeks total from planning to first DDS submission. Starting May 2026 gives comfortable margin for December deadline. Starting October 2026 gives no margin for complications. Detailed week-by-week timeline is in the Implementation Timeline section above.

What if a member plot overlaps with forest cover on satellite maps?

Three scenarios: GPS collection error (revisit and recollect — most common); shade trees within a coffee agroforestry system (document shade species — not EUDR deforestation); genuine post-2020 deforestation (plot cannot enter EU export lots — segregate from EU batches and document in TRACES NT). Most Kenyan highland coffee plots fall under scenario 1 or 2. Validate all plots against Global Forest Watch before DDS submission. Full guidance in the “Forest Overlap” section above.

What does EUDR geolocation cost for a Kenyan coffee cooperative?

Small (50–100 members): KES 90,000–215,000. Medium (100–300 members): KES 205,000–420,000. Large (300–500 members): KES 365,000–745,000 with consultant support. Less than 1% of annual EU export revenue for most cooperatives. A once-completed investment — GPS coordinates are permanent. Full cost breakdown table in the “Costs” section above. Contact us for a specific quotation →

Can I use Google Maps for EUDR data collection?

No. Google Maps cannot export GPS coordinates in GeoJSON or KML format for TRACES NT. It requires mobile data at collection time (unlike KoboToolbox/ODK which work offline). Coordinates manually copied from Google Maps are error-prone. Use KoboToolbox or ODK Collect for data collection. Use Google Earth Pro (free) for validation — it accepts KML imports and allows satellite imagery overlay.