Module · Maps & Geo

Maps, polygons, and geographic intelligence for coffee

Visualize every producer plot on a real map. Validate GPS coordinates against satellite imagery. Layer deforestation data, regional boundaries, and altitude — the geographic picture of your supply chain at a glance.

01 · Context

Why coffee needs a geographic layer

Coffee is a geographic business. Altitude determines cup quality. Watershed determines processing water availability. Deforestation risk determines EUDR eligibility. Regional boundaries determine certification eligibility (Yirgacheffe, Sidamo, Guji). Without a geographic layer in your software, these facts are hearsay and tribal knowledge. With one, they're queryable, reportable, and auditable.

02 · Capabilities

What you get

Interactive polygon map

All producer plots on one map, colored by region, status, or deforestation risk. Pan, zoom, filter, and drill into any polygon for full producer context.

Satellite imagery overlay

Recent and historical satellite imagery from public sources, overlaid on polygon boundaries to visually validate accuracy — catch polygons drawn on water, roads, or urban areas before they get into a DDS.

Altitude and slope layers

Integrated elevation data per plot with metadata. Filter producers by altitude range, see terroir context at a glance, validate that high-altitude claims match the actual elevation.

Regional and administrative boundaries

Woreda, region, and kebele boundaries baked in for Ethiopian operations. Instantly verify that a producer's claimed origin region matches their actual GPS location.

GPS validation rules

Catch invalid polygons at capture time — plots inside water bodies, impossibly small or large areas, overlap with another producer's claimed plot. Reduces downstream correction work by 80%+.

03 · Process

How it works

01

Field agents capture polygons

Via the mobile app, offline. Walk the plot boundary, close the loop, attach photos. Syncs back when in coverage.
02

Automatic validation on sync

Each new polygon runs through altitude, boundary, and overlap rules. Valid polygons go live; flagged ones enter a review queue.
03

Operations reviews flagged polygons

Web dashboard shows each flag with satellite imagery and the specific validation that failed. Accept, request re-capture, or remediate.
04

Polygons feed downstream modules

Approved polygons automatically flow into EUDR compliance checks, traceability reports, and buyer verification vaults. No copy-paste, no CSV exports.

04 · Questions

Common questions

What mapping service do you use?

OpenStreetMap base layer plus satellite tiles from public sources (Sentinel-2, Landsat). No proprietary vendor lock-in. Enterprise plans support custom tile providers for higher-resolution imagery.

What if a producer's polygon is drawn incorrectly?

Review workflow in the web dashboard lets operations request re-capture. The field agent gets the request on their next sync, heads back to the plot, and re-walks the boundary. Old polygon versions are preserved in the audit log.

Can we import existing polygons from Shapefiles or GeoJSON?

Yes. Both formats are supported for bulk import. Each imported polygon goes through the same validation rules as field-captured polygons; bad ones land in the review queue.

How accurate are the polygons from phones?

Consumer smartphones capture GPS to roughly 3-5 meter accuracy under clear sky, degrading to 10-15m under tree canopy. That's sufficient for EUDR (which requires plot boundaries, not sub-meter precision) and for most buyer verification programs.

Works with