Multiple geo points in form

[SueBoelk2]

Hello- You answered questions that I had concerning putting multiple geo points form and indicated that it is possible. 

You were very helpful but we continue to encounter problems:

We are trying to publish again and to port this over to an enterprise geodatabase based on a referenced feature; the main feature has the points but when we try to publish the data it is complaining that the chill water and water well related tables are only tables and not feature services.

Thanks again!

[Leena_Abdulqader]

Hi @SueBoelk2, so in Survey123, every geopoint question in the form must be mapped to a feature layer, not a table. If your related layers (like chilled water or water wells) are stored as tables (no geometry), the Survey123 publishing tool can't create a valid map layer from them. If it is true, I'm unsure what a workaround would be. I'll have to think about it🤔

[SueBoelk2]

Thanks Leena! I appreciate your response.

Just found these from a search this morning and am trying to read through them: 

Recording multiple geometries in one survey with ArcGIS Survey123 - Resource Centre | Esri UK

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

Error: This Survey Cannot Be Published. Only One Geometry Field is Allowed per Table, (X N

I often have trouble with ESRI documentation, but am going to see if I can glean some info from them.

Again, I appreciate you responding.

[Leena_Abdulqader]

Of course, @SueBoelk2! I wish I could help more, but I totally understand the Esri docs struggle. Wishing you all the best!

[ChristopherCounsell]

Survey123 geo questions need the target layer to support them. You can't capture points if the target is a table, or another geometry type like polygons.

You can:

• Recreate your database tables as feature classes, then recreate the relationship class and service
• Set the geopoint question field type to null in survey123. This means that no data will be submitted. You could create additional fields to calculate and store the lat/long as text/decimals. This would let you keep the table without geometry but isn't ideal.

[SueBoelk2]

Thank you Christopher. I have just recently begun to design surveys and am learning the finer points of publishing and trouble-shooting, recreating the relationship class and service.

I have found a page that sounds like your suggestion and am trying to work through it: Error: This Survey Cannot Be Published. Only One Geometry Field is Allowed per Table, (X N

Thanks for your response!