Survey123: Setting Geopoint via URL

[TylerShelton1]

I'm attempting to set a point at the location of a feature(parcel centroids) via the custom URL every time a survey is conducted. I've managed to pass through other fields relatively easily but the point pass through is tripping me up. my issue comes down to a few questions:

1. Does the survey need a geopoint question in order for the Center= lat/lon functionality to work?
2. I'm able to pass through the data when a geopoint question is present but the precision of the coordinates is off. It gives a general area but not to the specificity needed. In the Lat/Lon view of the geopoint question it seems to only go to 5 decimal places whereas the coordinates i'm attempting to pass have 13 putting the point in the general vicinity which is unfortunately insufficient for my needs. Is there a way to increase the specificity of the geopoint?

Ultimately i am attempting to create a accurately georeferenced and editable feature when a survey is conducted. I was joining surveys back to the parcel feature initially in AGO to achieve this but that proved insufficient as you can't edit features generated by a join in AGO. I'm fairly new to the online ESRI suite so if there is a more efficient way to achieve this task i'm all ears.

Thanks! 

[JosephDrahos]

I think I know what you're going through, as I recently experienced the same issues.

"Does the survey need a geopoint question in order for the Center= lat/lon functionality to work?"

No, you can pass latitude and longitude without specifying a geopoint. In fact, you may purposefully want to not include a geopoint question so that you automatically place the point for the user without giving them the chance to override it.

"I'm able to pass through the data when a geopoint question is present but the precision of the coordinates is off."

I’m assuming that you have latitude and longitude values in 2 different fields. If that is the case, then double-check the precision of those fields, by going into the pop-up options. I’ve noticed by default, AGOL will automatically try to truncate those to 2 decimals places. Go in there and set the decimals places to whatever the maximum is (can’t remember off the top of my head what it is). It doesn't actually truncate them, rather it hides those extra decimal places for display purposes, but they still don't get passed through.

That is what I have experienced anyway. Hopefully it helps.

[TylerShelton1]

Hi Joseph,

I've actually got them stored as a single string with a comma (lat,long) based on what i read in previous threads on this  subject.

[JosephDrahos]

Ah yes, that should work as well. Although I can’t say why your string wouldn’t work in that case since the decimal places for those values should all carry through.

Another option that I have been considering was to request joining Collector Aurora. I’ve been wanting to extract lat/lon from the geometry of the point using Arcade and passing those on to Survey123, but that functionality is not currently supported yet. I thought that I recall hearing that it is being incorporated into Aurora though.

Sorry I couldn’t be of more assistance.

[TylerShelton1]

It works (passes the data) it's just not accurate. Thanks for your responses, I'll look into Aurora.

I'll let you know if i come up with a resolution

[AndrewSouthern]

Experiencing this limitation as well.  My workflow is similar except that it's pulling XYs for tornado siren locations from an external CSV.  When the coordinates are imported from the CSV using the pulldata() function the coordinates are truncated at 2 decimal points causing the points to be roughly 75ft from where they "should" be.

[JamesTedrick]

Hi Andrew,

Are you using the web form or the field app?

[AndrewSouthern]

I am using the web form but was able to get it to work correctly.  For some reason my XYs were being truncated but when I concatenated them into one string using a calculate data type field and plugged into into the geopoint questions it worked fine.  Thank you for your response.