Latest Contributions by IsmaelChivite

Hi Thomas. While GPS Accuracy Thresold was implemented sometime ago, we still do not have a good way for you to extract the X,Y and Z values of a geopoint as attributes in your feature.  Please have a look at this Idea and vote for it if you think it is important: Storing Positional Accuracy of GeoPoints  ... View more

 In Survey123 Connect for ArcGIS, click on New Survey and select the Community category. The following surveys include repeats: Arrest Form Polio Campaign Spawning Beach Survey Municipal Tax ... View more

Cross-referencing this thread: https://community.esri.com/thread/183062-unable-to-add-integration  ... View more

Hi Corey,  Survey123 is a bit temperamental to changes in the original folder structure of the Survey. Moving the Form or Feature Layer items away from the original folder will create all sort of issues.  Workforce is more tolerant to this type of change, but unfortunately the 1.0 version of the Workforce app will not work correctly with your app integration settings if you move the Workforce project away from its original folder. The upcoming 1.1 version of the Workforce app will resolve this problem. I am including here cgillgrass-esristaff‌ as there are specific steps you can take to make Workforce work. As far as  Survey123, the best is that for now you leave the Survey and Feature Layer in the original folder that Survey123 created. We are looking at giving more  flexibility on this in the future. Ismael ... View more

Hi Nicole, please refer to this thread; https://community.esri.com/groups/survey123/blog/2016/06/08/calculations-on-geopoints?commentID=41450#comment-41450  ... View more

Nicole Ueberschär‌  Eduardo Vasquez‌ Zoltan Kovacs‌ Here is an update on the issue you describe with geopoints in 1.7: Using ${mygeopointquestion} to extract a geopoint value as a string should never have worked in previous versions of Survey123.  I would not have done differently than you: if something works for me I typically go and use it.  So what do we do next? Technically for us it is very problematic for us to help you go back to a previous version (technically not possible in iOS and a real rabbit hole for us on Android).  This would not be a long term solution either because as soon as you update to 1.8, 1.9 or whatever is coming next will break your surveys again. We are working on a quick fix for you to get things into a reasonable state: The correct way to get a geopoint as a string will be string(${mygeopointquestion}).  This will start working in our next update. In practice, to get this going you would need to: Update your surveys to explicitly cast geopoint values into a string (using string() as described) Publish the survey again (will not cause you to lose  data) Ask end-users to update to our next update AND download the survey again I totally understand this may not be your desired flow: If something worked for me in the past I expect it to keep working... but unfortunately we run into a dead-end situation. Looking ahead, we also need to discuss what exactly you are trying to achieve by extracting the geopoint  values as strings.  If your end-goal is to parse the string to get the X,Y or Z values using substr, then we are in trouble too because while it may have worked for you, and unless you are  using some unknown magic, your XLSForm expression is bound to give you trouble soon: The number of digits in a latitude/longitude pair is not guaranteed to be fixed. Sometimes you get more  digits, some fewer.  For this reason,  you cannot reliably extract the X,Y values. As part of the quick fix, we are exploring the possibility of extending the pulldata function to support extracting the coordinates from a geopoint in a safe manner. It will look something like this: pulldata(“@geopoint”, ${location}, “x”) pulldata(“@geopoint”, ${location}, “y”) pulldata(“@geopoint”, ${location}, “z”) pulldata(“@geopoint”, ${location}, “HorizontalAccuracy”) We are working hard to try to get all the above sorted out soon for you. In order to expedite the fix, we will email you so we can work together on a resolution to this problem. Thanks a lot for so quickly report the issues you found. ... View more

Hi Andrew Hargreaves‌: The error message indicates that in row 23 you are referencing a list that does not exist in the choices worksheet. In fact, after looking at your XLSFile you are indeed missing a list called 'name'.  When you add s select_one or select_multiple type of question, you must reference a list in the choices worksheet. Otherwise, Survey123 would not know what list will populate your choices. It looks like you want  to use the pulldata function to pre-populate certain other questions based on the selection made in your 'name' question. That should be fine but you would need to add the 'name' list into your choices sheet. I would recommend that you watch this video tutorial for details on how to work with select_one questions. This quick intro into XLSForms may be useful as well as this basic step by step exercise. If you get stuck, do not hesitate asking. Thanks! ... View more

${previousQuestion}!='' ... View more

Hi. As long as the TPKs use the Web Mercator Auxiliary Sphere Spatial Reference it should work fine. If you would be so kind to share with us your TPK files we will have a look.  If the data is sensitive and you do not want to post as an attachment, please open an Esri Technical Support incident and share that way. Thanks. ... View more

Hi Philip, have a look at this thread: https://community.esri.com/thread/181809-survey123-feature-class-as-a-related-table There are  some details about making Survey123 work with related layers in an existing feature service. ... View more

OK. We will need to look into this. We have to different issues: I think that using substr to extract coordinates from a geopoint is not reliable, because the length of the X,Y coordinates is not constant.  Somehow, we need to be able to get the X and Y coordinates of a geopoint better. At this moment we do not have a good solution to this. Lately we have been discussing in the Survey123 team the idea of using the pulldata function as follows: pulldata(“@geopoint”, ${location}, “z”). We are still thinking if this wold be a good approach, in which case, we will make this available to you. The second issue relates to the fact that the note is not showing any value anymore. It was unexpected to me that this behavior changed. Let me do some more research on this. I or someone else from the team will get back to this topic.‌ ... View more

Hi Graham. When you publish a survey, under the covers we create a couple of items in your ArcGIS Online or Portal for ArcGIS account. One of them is a Form item, which is for exclusive use of Survey123 for ArcGIS. You will also find a feature service, which is associated with the Form. The feature service can also be used by other ArcGIS apps, including Collector for ArcGIS. There is nothing particularly unique to Survey123 feature services, so you can build your own Collector for ArcGIS projects on top of them. The easiest way to make Survey123 and Collector work on top of the same feature service is to publish a survey, and then have Collector also work on top of the survey's feature service. It is also technically possible, although not as straight-forward, to have Survey123 for ArcGIS work against a feature service you may already have. This is done by using the submission_url. You can learn more about it through this help topic: Submission URL—Survey123 for ArcGIS | ArcGIS  As of version 1.7 of Survey123 for ArcGIS, you can use the submission URL against hosted feature services in ArcGIS Online or Portal for ArcGIS. If you happen to have Portal for ArcGIS, you can also use submission_url against services from a Federated ArcGIS for Server.  Federate an ArcGIS Server site with your portal—Portal for ArcGIS (10.4.1) | ArcGIS for Server  Configure a hosting server—Portal for ArcGIS (10.4.1) | ArcGIS for Server  ... View more