POST
|
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
09-14-2016
04:48 PM
|
0
|
0
|
273
|
BLOG
|
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
09-14-2016
02:18 PM
|
2
|
0
|
17340
|
BLOG
|
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
09-14-2016
01:12 PM
|
1
|
0
|
1082
|
POST
|
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
09-12-2016
09:04 AM
|
0
|
7
|
824
|
POST
|
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
09-12-2016
08:59 AM
|
0
|
0
|
1461
|
BLOG
|
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
09-10-2016
07:30 PM
|
1
|
0
|
17340
|
POST
|
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
09-09-2016
10:09 PM
|
0
|
2
|
1461
|
POST
|
Hi. This behavior is expected. In early versions of Survey123 for ArcGIS we used to create domains for all select_ones. Very soon people started using cascading selects to handle lists of thousands of records and this caused issues when we were trying to create geodatabase domains for them. So we decided not to create domains for cascading selects. It would be technically possible for us to present some advanced options during the Publishing process where you could have more control over this. If you feel strongly about this topic, please post a new IDEA in the Survey123 category and lets see what people think about it. Thanks! Ismael
... View more
09-09-2016
04:37 PM
|
2
|
8
|
1609
|
POST
|
Hi Jamie, you are right. This is a bug in 1.7. We will look into this. I was able to get the expected behavior when rendering the result of the pulldata function in a text question, but when using a note (or a read-only text question) I was able to reproduce the problem you describe. Thanks so much for sharing this. I will get this in the development back-log. Note that this issue affects any note that is calculated within a repeat. Technically the problem is not with the pulldata function. It is just a refresh issue that triggers when the value of the note is calculated. Ismael
... View more
09-09-2016
04:23 PM
|
1
|
1
|
417
|
POST
|
On top of all the great suggestions above, when authoring your XLSForm, you can also look at the Types worksheet where you will find a quick guide of the most common question types, appearances and formulas you can use, right in Microsoft Excel.
... View more
09-09-2016
04:13 PM
|
1
|
0
|
513
|
POST
|
I think Cascading Selects could help you here. You could model this as three select_one questions in your survey (Township, Range and Section). In the Township select one you will show a list of all the Townships you care about. Then you will use the selected Township, to filter the choices presented in the Range question, and again filter the Sections according to the Range selected. To learn more about Cascading Selects: In Survey123 Connect, click on New Survey Select the Cascading Selects design from the Samples category Play with this sample to get the concept. You can concatenate as many cascading selects as you want. To learn more about Cascading Selects: Cascading and external selects—Survey123 for ArcGIS | ArcGIS (from our help) https://community.esri.com/groups/survey123/blog/2015/10/22/cascading-selects-and-external-selects (from our Blog) To handle very, very long lists (thousands of records) you will want to use an External Select, which is just a variation of a Cascading Select where the list of choices is stored in a separate worksheet. If you know in advance what Ranges exist within each Township, and what Sections within each Range, I think the solution above should work for you.
... View more
09-09-2016
04:08 PM
|
0
|
1
|
282
|
POST
|
Hi. I am including an attachment that may be helpful for your use case. In the ZIP file you will find two files: The XLSFile is for you to import in Survey123 Connect for ArcGIS (Click on New Survey, then select the File option so you can browse to it). The CSV file is for you to manually copy in the media folder of the survey you created in the previous step. You can do this, by opening the directory of your survey and then copying the file into the media folder As you will see, when you select a station, you will get a default permit area number in the second question. You can always overwrite the permit area. I used the new pulldata function for the example above. I used the CSV file as a lookup table, to associate a permit area with the selected station. The pulldata function is used in the calculation column. What I REALLY wanted to do is to set the permit area question as a select_one, so people could change the permit area if desired, but only picking a valid permit area. Unfortunately, calculations cannot change the value of a select_one (at least in the current 1.7 release), so I had to change the question type to integer (I could have also used a text type of question). Using a text or integer question can add room for user error, as they may overwrite your default value with an invalid permit area. Another approach you could take is to use favorites. Using favorites would work as follows: End user opens your survey in the mobile app. First thing they populate the station and permit area pulling from the available lists of choices. There will be no smart default value here. They really need to know what station they are on... Once they have populated these questions they would select the option in the app to copy as favorite answers. It is VERY important that the user at this moment ONLY answers the questions that should be kept as favorites. Once the questions have been answered, the user will save the survey as a draft. At this moment, your draft survey has become your survey containing your favorites. All answered questions in this survey can now be easily pasted into the next survey. This will include your station number. Since I assume people will probably sit in a station all day, this could also be a solution. If they move to another station, they could repeat the process outlined above to reset the favorites.
... View more
09-09-2016
03:56 PM
|
0
|
0
|
423
|
POST
|
The International Business Awards, known as the Stevies, is one of the best known international business award programs. Individuals and organizations worldwide are eligible to submit nominations in a variety of categories. The 2016 IBAs received 3,800 entries from more than 60 nations and territories. Survey123 wins a Stevie Award 2016 in the Apps category. I guess someone in the team will get to go to Rome to pick up the prize! Congratulations to the Survey123 team! More info here.
... View more
09-07-2016
10:24 PM
|
4
|
1
|
1138
|
POST
|
1.1.19? That is pretty old and Beta! Lets get you up to speed: First download the latest version of Connect (1.7) from here: Survey123 for ArcGIS | ArcGIS Second, update your Survey123 app. The latest version (1.7) is in the iTunes, Google Play and Windows stores Tip: We update Survey123 almost every month. Subscribe to this blog: Survey123 for ArcGIS or to our account on Twitter: Survey123forArcGIS (@esriSurvey123) | Twitter To learn what is new since 1.1.19 I recommend that you check this help topic:What's new in Survey123—Survey123 for ArcGIS | ArcGIS You may want to watch this Esri UC Technical Session: Video Link : 3452 as well as videos in this YouTube Playlist: Survey123 for ArcGIS Product Overview - YouTube
... View more
09-06-2016
10:36 PM
|
0
|
1
|
551
|
Title | Kudos | Posted |
---|---|---|
1 | 10-28-2022 08:40 AM | |
1 | 10-28-2020 12:50 PM | |
1 | 08-25-2023 02:15 PM | |
1 | 10-23-2023 12:34 PM | |
1 | 06-04-2021 08:42 AM |
Online Status |
Offline
|
Date Last Visited |
03-04-2024
05:27 PM
|