Is there any way to limit the address search extent for the GeoPoint input on a public survey (without login) using the web app? We have a public survey for users that are not part of our organization that requires a local GeoPoint and some users are confused when international results are returned.
There is actually an enhancement logged and is in the current product plan for Survey123!
ENH-000114785: Provide the option to use a boundary dataset or feature service to restrict the spatial input extent in a Geopoint question in Survey123.
Any update on when this feature might be deployed? I'm running into the same issue Chris described with a public-facing survey that relies entirely on geosearch rather than device location.
Unfortunately, Marisa was inferring from the status of the ENH request, and while that ENH request is tangentially related to what you are asking (an overall restriction of input), doesn't address directly what you are asking (provide a restriction to the geocoder search parameters).
In order to address this, Survey123 first needs to be able to specify a locator for public web forms. This does not have timeline yet.
As James indicated this is separate to the discussion in this thread, so please create a new post if you're interested.
Hi, this is possible today by leveraging Locator Service Views. The Geosearch control in Survey123 uses by default the locators defined in your ArcGIS Organization. You can configure the default locator in your organization to include a filter using a geographic extent. This is accomplished using Locator Views.
For an introduction to Locator Views:
We had set up a locator view and also configured a custom local locator, but problem was that only users from our organization that were logged in seemed to be able to use them. Anyone not logged in would revert to the ArcGIS World Geocoding Service at full extent. Our surveys are public and the users will not be logged in to ArcGIS Online. Am I missing something in configuring this for all users of the survey regardless of if they are logged in or not?
Thank you for your response, but I am running in to the same issue that we were with custom locator. After following your steps the locator shows up as the default locator for any user from our organization that is logged in, however, all public users that are not logged in revert to the ArcGIS World Geocoding Service.