How to Collect GPS Coordinates in ODK Forms
To collect GPS coordinates in ODK, add a geopoint question to your XLSForm — ODK Collect records latitude, longitude, altitude, and accuracy from the device's GPS. By default the point is captured from the sensor only, which is exactly what you want when location is a data quality check and not just a data point.
| type | name | label |
|---|---|---|
| geopoint | household_location | Capture the household location at the front entrance |
geopoint, geotrace, or geoshape?
- geopoint — a single point. Households, facilities, interview locations. This is the one you want 95% of the time.
- geotrace — a line of points. Walking routes, roads, water channels.
- geoshape — a closed polygon. Field boundaries, plot areas, catchment zones.
All three work fully offline; GPS does not need an internet connection.
Should you allow map-based placement?
Adding placement-map or maps in the appearance column shows a map and lets the enumerator move the pin or tap a location manually. Convenient — and it quietly destroys the verification value of your coordinates, because a manually placed pin proves nothing about where the interview happened.
If GPS is part of your data quality strategy — confirming enumerators actually visited respondents — use plain sensor capture with no map appearance. A hand-placed pin at the correct house is indistinguishable from a hand-placed pin from the office.
Use map placement only when respondents are reporting other places ("mark your farthest field"), where manual placement is the point.
The field protocol that produces usable accuracy
GPS quality is mostly behavior, not configuration. Train these four rules in enumerator training:
- Capture outdoors, under open sky — at the dwelling entrance, not inside or under a metal roof.
- Let the reading settle. ODK Collect shows live accuracy in meters and auto-saves once it is good enough; stand still for the seconds that takes.
- Never capture from a moving vehicle. Drive-by points are a known curbstoning shortcut and produce systematically offset data.
- Capture at the start of the interview, while the enumerator is reliably at the location.
Capture location continuously with the audit log
A geopoint records one moment. The ODK audit log can record location throughout the interview, in the background:
| type | name | parameters |
|---|---|---|
| audit | audit | location-priority=balanced location-min-interval=60 location-max-age=120 |
This is the stronger verification signal: a fabricated interview can fake one point far more easily than a 40-minute location track. The two together — geopoint for the data, audit trail for the verification — are the standard setup for curbstoning detection.
Review locations daily, not at endline
GPS points only protect your data if someone looks at them while fieldwork is running. Plot each day's submissions; clusters at the field office, points outside the sample frame, and identical coordinates across interviews are all same-day phone calls — part of the daily data quality routine. DataSnap does this automatically, mapping every submission with per-interview risk scores straight from your ODK server.
Check my data quality freeNext: The ODK audit log explained →
Frequently Asked Questions
How do I add GPS to an ODK form?
Add a row with type geopoint to your XLSForm's survey sheet. ODK Collect then captures latitude, longitude, altitude, and accuracy from the device GPS. Use geotrace for lines and geoshape for polygons; all three work fully offline.
Does GPS capture in ODK Collect work offline?
Yes. GPS positioning comes from satellites, not the internet, so geopoint capture works with no signal at all. Only the map display in map-based appearances needs connectivity or pre-downloaded offline map layers.
What GPS accuracy is good enough for household surveys?
Captured under open sky, phone GPS typically settles within 5 to 10 meters, which is sufficient to verify a household visit. Readings of 50 meters or worse usually mean capture happened indoors, under cover, or before the signal settled.
Can enumerators fake GPS coordinates in ODK?
A single geopoint can be faked with mock-location apps or map placement, which is why verification should rely on the audit log's continuous background location track instead. Faking a full interview-length location trail is far harder than faking one point.
Should I use placement-map appearance for geopoint questions?
Not when coordinates serve as a data quality check. Map appearances let enumerators place the pin manually, which makes the coordinate unverifiable. Use plain sensor-only capture for interview locations, and map placement only when respondents report other places.
How do I track location during the whole interview?
Enable the audit log with location parameters, such as location-priority=balanced with a minimum interval, in your XLSForm. ODK Collect then records a background location trail for the entire interview, independent of any geopoint question.
No Credit Card Required
Build the form first. Add hosting when you need it.
Start free with LooprAI, then deploy a managed ODK Central server or run DataSnap checks when your project is ready.
Automation handles the mechanical work.
Researchers decide what the evidence means.