@danbjoseph previously asked these questions about this (I'm
copying them here to consolidate them into this thread):
It's great that you are continuing to improve and build out the geo functionality of ODK Collect!
Would this be a control that is toggled in the survey form? Automatically something that the user would be able to do for a geopoint question? Or a new geo question type?
If the user adjusts the accuracy down/up, does it affect which points are included in the calculation looking at all those that have been collected since the question started? Or does it only affect which points are stored and used for the calculation going forwards?
I find the previous implementation example a little confusing. Is the "required accuracy" for the individual points or for the averaged location? Is the "GPS accuracy" the calculated average accuracy or the accuracy of the current sensor reading? Would it be useful to know the total number of collected points in addition to the number of acceptable points?
And this was my reply:
Thanks for these questions!
We're thinking of this as a feature of a GeoPoint question. Whether it's enabled by the app user or by the form designer (or both) is not yet determined.
In the example:
- The GPS accuracy shown is the accuracy of the current sensor reading.
- The "required accuracy" threshold is for the individual points.
- When "required accuracy" is adjusted, it changes which of the already collected points are included in the average. In other words, all the points are stored, and all of them are filtered according to this adjustable parameter.
That's how this particular prototype implementation worked, though I don't claim that it's the best design. It does give you a clue as to how it works because you can see how the number of acceptable points changes when you adjust the accuracy threshold, but still, I can see how the display would be ambiguous for someone who wasn't familiar with it.