POST
|
Thanks! Looks like you have taken warnings to the next level. I'm sure that will come in handy.
... View more
02-02-2021
11:59 AM
|
1
|
0
|
1245
|
POST
|
The JavaScript function worked great for me once I figured out that I needed to create an "extensions" directory in my survey to house repeats.js. This solved a lingering question that I had from two years ago.
... View more
02-02-2021
11:51 AM
|
0
|
1
|
881
|
IDEA
|
@Anonymous User I no longer see the GitHub discussion, but this functionality was requested again recently by someone on GIS StackExchange, with a similar use case.
... View more
02-02-2021
11:02 AM
|
0
|
0
|
493
|
POST
|
@DougBrowning, I have also needed soft constraints or warnings for non-geopoint questions. Since the bind::esri:warning field doesn't work in these instances, I created a workaround: follow the target question with a "note" type question containing the warning text that you want (I made the text red) and put your constraint logic in the "relevant" field for the note. If the constraint condition is met the note field will appear with your warning text.
... View more
02-02-2021
10:15 AM
|
0
|
0
|
1755
|
BLOG
|
Okay, thanks, I figured it was something like that. Is there a way to get UTM coordinates with higher precision returned from the survey, or will I need to convert from the latitude & longitude values to get higher precision UTM coordinates?
... View more
01-14-2020
05:54 AM
|
0
|
0
|
2745
|
BLOG
|
Ismael Chivite, this information about precision is very helpful. I'd like to record UTM easting & northing to 2 decimal places, and have set up two questions with the following calculation: pulldata("@geopoint", ${Waypoint}, "UTM.easting",0.01) & pulldata("@geopoint", ${Waypoint}, "UTM.northing",0.01). I have the fieldType set to esriFieldTypeDouble. While I do now get 2 decimal places in my feature service for these fields, they are always zeros. What do I need to change? Can Survey123 not calculate UTM values more precisely than 1m? Thanks.
... View more
01-07-2020
06:30 AM
|
0
|
0
|
2745
|
IDEA
|
I have a complex survey with nested repeats (e.g., points within transects within sites), and it would be really helpful for navigating the survey if the repeat counters could be labeled (e.g., "Transect 1 of 5", "Point 12 of 100", etc. instead of them all just being "# of #"). It appears the idea (or something similar) has been suggested previously on this GitHub discussion ("/issues/1875"?).
... View more
09-04-2019
06:35 AM
|
12
|
2
|
532
|
POST
|
Johnathan Hasthorpe, I have attached the XLSForm. As an example, constraints for fields such as NewDistance, NewBearing, TransectLength, etc. are not enforced until I either advance to the next instance of the relevant repeat or try to submit. This is a particular problem for DataStartPoint, as this value is used to calculate TransectDistance in the Point Intercept repeat, hence it is possible to enter a whole bunch of data in the latter repeat based on an erroneous starting value, as the DataStartPoint constraint is not applied until advancing to the next transect. I am using Survey123 Connect version 3.5.157, Survey123 Android app version 3.5.164.
... View more
09-03-2019
01:59 PM
|
0
|
0
|
2009
|
POST
|
Johnathan Hasthorpe, I'm having this same problem but with a decimal field (constraints not applied until I try to submit survey). This is a problem for me as I have a number of other fields that are calculated based on this decimal field, so the late constraint may come after allowing a user to enter a bunch of data based on the entered value that should have been rejected. I seem to remember that the constraints used to be applied immediately, which seems more appropriate.
... View more
08-23-2019
10:04 AM
|
0
|
2
|
2010
|
POST
|
I'll be hoping to see this feature in an upcoming release.
... View more
08-21-2019
11:46 AM
|
1
|
0
|
1872
|
BLOG
|
Another option is to put =NOW() in the version field on the settings worksheet, then use version() in a calculate.
... View more
08-21-2019
07:37 AM
|
0
|
0
|
53882
|
BLOG
|
Ismael Chivite, thanks for the tip on selected-at(). One unexpected problem I have run into when using it is that the comma-separated list of values that is the result of a select_multiple question is not sorted based on the order of the choices in the choices worksheet, but based on the order in which the user selects them. My choice names are integers - is there a way to sort the selections, or calculate an additional field as a sorted version of the selections? I need to pull values from the list of selections using selected-at, and they need to be sorted ascending in order for the right values to be pulled. I could include instructions that selections should be made in ascending order, but I would prefer keep it behind the scenes (and not rely on users reading & following instructions).
... View more
08-21-2019
07:30 AM
|
1
|
0
|
17783
|
POST
|
I figured out a workaround. I made the end point field not required, but have a calculate field comparing the number of responses for the start point & end point fields (using aggregate functions), and if there are fewer end point responses I have a note field appear to warn the user and report how many instances of the repeat are lacking an end point.
... View more
08-21-2019
06:38 AM
|
0
|
0
|
314
|
POST
|
I have figured out how to code my own soft constraints using note fields with "relevant" rules encoding my constraints (note only appears if specific rule in "relevant" field is met). This will work for what I need, but it seems like it should be possible to do this with the bind::esri:warning field, and a pop-up that you have to interact with would be a stronger message than a note field appearing.
... View more
08-21-2019
06:34 AM
|
0
|
1
|
537
|
BLOG
|
Actually, looks like it DOES update the =NOW() field when I save/push to S123 Connect, which is perfect. I think this will work. Thanks for the suggestion, Dante Lee.
... View more
08-20-2019
12:09 PM
|
1
|
0
|
53882
|
Title | Kudos | Posted |
---|---|---|
1 | 08-20-2019 10:17 AM | |
1 | 08-21-2019 07:30 AM | |
1 | 02-02-2021 11:59 AM | |
12 | 09-04-2019 06:35 AM | |
1 | 08-21-2019 11:46 AM |
Online Status |
Offline
|
Date Last Visited |
01-10-2024
01:09 PM
|