google
[Geometry tasks] Require 15m accuracy when capturing location
@jo-spek FYI
A message should be shown asking the user to stand still to wait for more accurate location. @vittorino for UX @amegantz
@vittorino has initial designs, will discuss UXW with @amegantz.
This validation will apply when the primary action is triggered in both Capture location tasks and Drop pin tasks when location is enabled. We'll assume that if the location lock in Drop pin task that they care the location recorded is the current location, in which accuracy matters.
here's a suggestion (considering #3148 of combining the 2 tasks): @gino-m
This is great.
- Show the blue halo around blue dot representing accuracy.
- Show the accuracy in red when above 15m
- Show the "not accurate" message
@vittorino Are these all the deltas? Is the "Drop pin" button disabled when location lock is active and accuracy <15m? If so we may want to also say "..or drag the map to select a location manually."
This is great! Should we maybe discuss the threshold value again @gino-m and @kenstershiro? I guess 15m is just about enough, but when people wait a few seconds, they are usually quickly at 5m or better. The threshold in the Kobo Collect survey in Kenya is set at 5m.
This is great! Should we maybe discuss the threshold value again [@gino-m
](https://github.com/gino-m) and @kenstershiro? I guess 15m is just about enough, but when people wait a few seconds, they are usually quickly at 5m or better. The threshold in the Kobo Collect survey in Kenya is set at 5m.
Is that the default in Kobo Collect, or the value the survey designer chose?
Hi guys, given this is a blocking validation control I suggest we avoid tightening it too much - 5m is getting towards the boundary of what some older phones support in terms of GPS accuracy, and things like tree cover or bad weather could make that impossible in some cases. I would go with 15m for now, if we get more specific feedback we could look at adjusting or allowing survey organizers to adjust in future.
+1 to @kenstershiro 's comment. I'd advise avoiding introducing anything that would entirely block data collections from submitting data with no way to recover.
Hi all, the 15m suggestion was pretty arbitrary. We didn't want to go to strict, but we might want to reconsider. The KoboCollect campaign happening in Kenya is using 5m as a threshold. May I suggest we go for the middle ground and say 10m? @gino-m @kenstershiro
@jo-spek Are you sure it will always be possible to get 10m accuracy, even on older devices? If so, then no concerns. If not, are you ok with some small fractions of data collectors not being able to collect data while in the field?
Sorry, I researched around for too long and didn't give feedback. From field experience, most users arrived at an accuracy better than 10m. But let's stick with 15m for the moment. Most important is that no locations that are way off are registered anymore.
@gino-m @kenstershiro In the 0.3.1 - 2025-12-01 APK, I do see the warning, but worse accuracy than 15m does not prevent me from Capturing location. Was it intended like that? Having a warning, but the user can proceed anyway?
@anandwana001 Looks like you only added the warning, but didn't prevent the user from actually capturing location? Can you please take a look?