Is there a way to truly prevent a surveyor from submitting if they are not within a certain horizontal accuracy threshold? I know you can set a threshold in the column, but it only gives a warning and the user can still techincally submit. Is there a way to completely prevent a surveyor from submitting if they don't meet that threshold?
We basically have surveyors who are moving way too fast (because they have a lot of ground to cover in a day) and they ignore the warning causing their points to be up to a mile off the actual location.
Solved! Go to Solution.
I added a field called "child_pa" to calculate the horizontal accuracy and set it's type to calculate with field type double. I added the calculation "pulldata("@geopoint",${location},"positionAccuracy")" to its calculation field. Then in the geopoint question I added the constraint ${child_pa}<1 but it was not working. I realized you cannot set the geopoint question's appearance to hide-input because then it won't consider the calculated horizontal accuracy. After removing the hide-input it worked.
Put it in the threshold and the constraint column, with a constraint message.
Do you think it's possible that having the geopoint be read only and hide-input is interferring with it?
I added a field called "child_pa" to calculate the horizontal accuracy and set it's type to calculate with field type double. I added the calculation "pulldata("@geopoint",${location},"positionAccuracy")" to its calculation field. Then in the geopoint question I added the constraint ${child_pa}<1 but it was not working. I realized you cannot set the geopoint question's appearance to hide-input because then it won't consider the calculated horizontal accuracy. After removing the hide-input it worked.