Re-centre geopoints for transect based data collection

[MB123]

Hi all,

I have a survey 123 form with a repeat that has a geopoint type which collects data as users walk down a transect. The way users have been entering each record is to enter all data and then press the plus to create a new record and then keep walking until a new observation is made. The geopoint does not seem to keep track as users walk down the transect re-centring the point location as users walk. This means that essentially that a user will actually collect the location of the previous position where the new record was made unless the users click the bullseye to ce-centre the location on the map. 

Is there a way to code the geopoint to be re-centred (i.e. the bullseye icon gets clicked again)?. Potentially when another field is selected in the form indicating this is the current location. The map is quite large so I would love to hide it so that the users can just capture data and walk with all fields on one page. 

Thanks

[ChristopherCounsell · Accepted solution]

Make the geopoint question relevant on the observation data being entered. Set the default for the geopoint to 'position'. This means:

1. User hits new repeat. Observation question appears (species, whatever)
2. User completes observation questions. Geopoint question appears based on relevancy, defaults to position.
3. user hits new repeat.

Geopoint questions that are switched from a non-relevant to a relevant state will not automatically update to the device's location. Set the default value as position to automatically get the current location identified by the device when the question is made relevant.

https://doc.arcgis.com/en/survey123/desktop/create-surveys/geopoints.htm#ESRI_SECTION1_6B32C981BC5E4...

[MB123]

Thanks Christopher.

It would help if I read the instructions now wouldn't it! I found those generic esri instructions hard to decipher for a survey123 layman.. but I got there eventually. I had actually initially tried putting in a relevance statement in the 'relevant' column before posting this but clearly I did not enter it in the proper format or did not save/publish it, as it worked perfectly this time around.